Re: [Imap-protocol] Gmail flags issue, timing-sensitive

On Thu, Mar 26, 2015, at 06:39 AM, Kostya Vasilyev wrote:
> Yes, that's what I meant by "which is also wrong".
>
> Every change to message flags should bump the message's MODSEQ value.
>
> Now in this case, there was no actual change *between* the two lines
> in the response, it's the server reporting wrong flags values first
> and correct values next (the message already had \Answered and \Seen
> prior to my adding \Flagged)...
>
> ...and the real issue is new flags reported without \Answered first,
> then with it, but...
>
> ... the identical MODSEQ values make it harder to work around this
> real issue.

I'm pretty sure this takes it from "annoying but legitimate" to
"strictly incorrect". That first line should not have the latest
MODSEQ value if it doesn't contain the flags that were set at the time
of that MODSEQ.

I spent a lot of work getting the Cyrus internals right for this
years ago, because there were bugs with the way Cyrus handled
per-user \Seen and modseqs, as well as around expunges. It was a lot
of work, but a half-functioning implementation means that clients
can't rely on anything.

Bron.

--
Bron Gondwana [email protected]

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