[Tickets #10677] Re: Cyrus returning OK when fetching non-existant messages

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10677
------------------------------------------------------------------------------
  Ticket             | 10677
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Cyrus returning OK when fetching non-existant messages
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-10-24 12:53) wrote:

> Yes. I noticed this while using the showMessage ajax call which  
> returns a complete message object in that case, but with all  
> properties empty. An exception would be easier to deal with.

Still don't think this should be handled at the IMAP Client level  
though.  It is perfectly acceptable (and may be desirable) to do  
something like fetching a range of UIDs, without the expectation that  
any/all of those IDs actually exist.  This is the recommended  
behavior, for example, when syncing the local cache when CONDSTORE  
isn't available.

Existence checking needs to be done instead at the application level,  
where the code knows what the fetch results are actually being used for.

I'm assuming you are looking at this for the mobile view.  Try the fix  
I just committed.