60 lines
2.3 KiB
Plaintext
60 lines
2.3 KiB
Plaintext
MBOX-Line: From kmansoft at gmail.com Wed Mar 25 12:39:17 2015
|
|
To: imap-protocol@u.washington.edu
|
|
From: Kostya Vasilyev <kmansoft@gmail.com>
|
|
Date: Fri Jun 8 12:34:54 2018
|
|
Subject: [Imap-protocol] Gmail flags issue, timing-sensitive
|
|
In-Reply-To: <55130CEA.7050608@isode.com>
|
|
References: <CAN7dqjCYRb2sbOZS49hiqgrSsfKFTzyT-b5fKHm0U4mBGvDRzA@mail.gmail.com>
|
|
<CABa8R6t01i4CMumftDbTdY_xC7WYWLCmh7__Qg+zrsw8dZxHwA@mail.gmail.com>
|
|
<CAN7dqjAxtu=k65vF-gshYYiEdMVeJ_j_ZruB2RLQRHTxouRckA@mail.gmail.com>
|
|
<CAN7dqjBcK_UZ1uYcT-G=a7N7W=g_JoAXf=kHSL6sz9EmMtc-9g@mail.gmail.com>
|
|
<20150325132119.Horde.H9br3-icKPf32c5xmMNhdfM@bigworm.curecanti.org>
|
|
<55130CEA.7050608@isode.com>
|
|
Message-ID: <CAN7dqjAOo1bJjGFUbT2aVx1ZBmhYkF1JHMtjkFbT=TrxEfThpA@mail.gmail.com>
|
|
|
|
2015-03-25 22:30 GMT+03:00 Alexey Melnikov <alexey.melnikov@isode.com>:
|
|
|
|
> Hi Michael,
|
|
>
|
|
> On 25/03/2015 19:21, Michael M Slusarz wrote:
|
|
>
|
|
>> Quoting Kostya Vasilyev <kmansoft@gmail.com>:
|
|
>>
|
|
>> 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
|
|
-------------- next part --------------
|
|
An HTML attachment was scrubbed...
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20150325/4b24c035/attachment.html>
|