[Imap-protocol] Re: condstore mod-sequence 0

On Mon, Dec 3, 2012 at 4:46 PM, Johnathan Galton <[email protected]>wrote:

> In section 3.3.1 of RFC 4551 it says for FETCH to only return messages
> where the mod-sequence of the message is "bigger than" that specified (i.e.
> ">").  However, it seems reasonable for clients to be able to say "FETCH
> ... (CHANGEDSINCE 0)" and retrieve *all* messages (AFAICT thunderbird does
> this initially), however 0 isn't "bigger than" any valid value that we may
> store for the mod-sequence of a message.
>

Oops, actually this last sentence is incorrect because having a message's
mod-sequence of 0 is invalid ("*positive* unsigned 64-bit value") despite
being quite useful as a default/initial value.


>
> How do other folks handle this?  Is 0 explicitly special cased to mean "do
> not filter anything" in the server implementation even though (based on my
> reading) against the letter of the RFC?
>
> Interestingly enough in SEARCH MODSEQ (in section 3.4) is explicitly ">=".
>  Seems a little incongruent, not sure if it's intentional or not.
>
> Thanks for your time,
> John
>

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