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

2015-03-25 22:30 GMT+03:00 Alexey Melnikov <[email protected]>:

> Hi Michael,
>
> On 25/03/2015 19:21, Michael M Slusarz wrote:
>
>> Quoting Kostya Vasilyev <[email protected]>:
>>
>>  New state reported without \Answered first (wrong), then with it (right),
>>> and the MODSEQ is the same (which is also wrong).
>>>
>>> 21:54:31.077 [IMAP.5800] Sending: kman25 UID STORE 196290 +FLAGS
>>> (\Flagged)
>>> 21:54:31.672  [IMAP_RAW.5800] Data is <167>:
>>> 21:54:31.672  * 20927 FETCH (FLAGS (\Flagged \Seen) MODSEQ (20736711) UID
>>> 196290)
>>> 21:54:31.672 * 20927 FETCH (UID 196290 MODSEQ (20736711) FLAGS (\Answered
>>> \Flagged \Seen))
>>> 21:54:31.672  kman25 OK Success
>>>
>> This is inefficient.  But it is perfectly acceptable IMAP.
>>
> I think this is not correct, because the two responses should use 2
> different MODSEQs, if they return different set of flags.


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.

-- K

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