[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              | Unconfirmed
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


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

Guess I am not seeing what the Horde/IMP bug is?

When parsing FETCH results, we only parse a result if an untagged  
response appears (see line 4238 in Client/Socket.php).  So in a  
conversation like you provided, no fetch responses would be parsed so  
we should theoretically be returning an empty array from the fetch()  
command.

Is the issue that IMP is trying to display the message, and we are  
relying on an exception to be thrown instead of checking for array key  
existence in the return array?