wasm-demo/demo/ermis-f/imap-protocol/cur/1600094998.22583.mbox:2,S

39 lines
1.5 KiB
Plaintext

MBOX-Line: From tom at close.io Wed Jul 22 22:47:43 2015
To: imap-protocol@u.washington.edu
From: Thomas Steinacher <tom@close.io>
Date: Fri Jun 8 12:34:55 2018
Subject: [Imap-protocol] Strange behavior with Gmail IMAP when using
CONDSTORE extension
In-Reply-To: <7B85E579-D6EB-4054-82E7-0A98C6B46F6B@close.io>
References: <CAO3aFYuDxSFaVU_O8dVwpO_40_pdY3h-b2B8pPDyfm_=9MG1oQ@mail.gmail.com>
<CACU8CfRygwG7dL4REXzUtGPYbR_P9ePGzrQkgZuJ1R8uQtd0mg@mail.gmail.com>
<7B85E579-D6EB-4054-82E7-0A98C6B46F6B@close.io>
Message-ID: <F86D6E44-8A4C-4FE1-B7CA-CD6E058503EA@close.io>
> What to do you get for either:
>
> T5 FETCH 1:* (UID FLAGS) (CHANGEDSINCE 14055062)
>
> or
>
> T6 UID FETCH 1:208198 (FLAGS) (CHANGEDSINCE 14055062)
>
> That might show if there's anything interesting happening with '*'.
> Your exchange definitely reads like incorrect CONDSTORE logic to my
> slightly tired eyes...
>
> Bron.
The two commands above give the exact same same response back as "T4 UID FETCH 1:* (FLAGS) (CHANGEDSINCE 14055062)", i.e. UID 207722 is missing. Also, replacing "*" with 208198 in T5 doesn't change the response.
> On 2015-07-22, at 17:21, Jamie Nicolson <nicolson@google.com> wrote:
>
> This could be a bug. I can't tell from this snippet, but what was the last modification to happen to the message with UID 207722? Was it the delivery of the message, marking it as read (STORE +FLAGS \Seen), or something else?
The user replied to message 207722 and archived the thread in Gmail.
Thomas