[Tickets #11946] Re: No headers when viewing unread message

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/11946
------------------------------------------------------------------------------
  Ticket             | 11946
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | No headers when viewing unread message
  Queue              | IMP
  Version            | 6.0.3
  Type               | Bug
-State              | Feedback
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-01-21 12:58) wrote:

Ahh... this is a broken IMAP response.  You did not provide the entire  
IMAP log but I am guessing that this response:

S: * 1 FETCH (UID 9 BODY[HEADER] {1409}
S: <<<FULL HEADERS>>>
S: )
S: * 1 FETCH (FLAGS (\Seen))

Was caused by this command:

a UID FETCH 9 (BODY[HEADER])

A correct response would look like:

S: * 1 FETCH (UID 9 BODY[HEADER] {1409}
S: <<<FULL HEADERS>>>
S: ) FLAGS (\Seen))

--or--

S: * 1 FETCH (UID 9 BODY[HEADER] {1409}
S: <<<FULL HEADERS>>>
S: )
S: * 1 FETCH (UID 9 FLAGS (\Seen))

So the problem is that we are asking for UID fetch results, but the  
server is throwing in some sequence-only results instead.  And this is  
not allowed if, in fact, this is called from a UID FETCH command.   
 From RFC 3501 [6.8]:

       However, server implementations MUST implicitly
       include the UID message data item as part of any FETCH response
       caused by a UID command, regardless of whether a UID was specified
       as a message data item to the FETCH.

Can you verify the command that caused these responses and the IMAP  
software version used?