Re: [Imap-protocol] Courier bug(?)

On Thu, Jan 24, 2013, at 03:20 PM, Michael M Slusarz wrote:
> a ENABLE QRESYNC
> * ENABLED QRESYNC
> a OK ENABLE completed.
> b SELECT INBOX
> [...]
> * OK [HIGHESTMODSEQ 5] Highest
> b OK [READ-WRITE] SELECT completed.
> c UID FETCH 9 (BODY[HEADER])
> * 1 FETCH (UID 9 BODY[HEADER] {1409}
> [...headers...]
> )
> * 1 FETCH (MODSEQ (6) FLAGS (\Seen))
> c OK FETCH completed.
> 
> Are we accepting that this is allowable?  Even if it is the  
> BODY[HEADER] FETCH that is causing the \Seen flag to be set?  Looking  
> at the QRESYNC docs - it appears that ONLY the FETCH untagged  
> responses to the SELECT/EXAMINE are required to contain both UID &  
> MODSEQ information.  All other FLAGS responses require MODSEQ but not  
> UID.  This is a subtlety that I don't think I've thought about before.

I always send UID for QRESYNC, and I even have a handy comment about it:

    /* http://www.rfc-editor.org/errata_search.php?rfc=5162
     * Errata ID: 1807 - MUST send UID and MODSEQ to all
     * untagged FETCH unsolicited responses */
    if (usinguid || state->qresync)
        prot_printf(state->out, " UID %u", im->record.uid);
    if (printmodseq || state->qresync)
        prot_printf(state->out, " MODSEQ (" MODSEQ_FMT ")", im->record.modseq);

Bron.
-- 
  Bron Gondwana
  [email protected]

_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol