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

38 lines
1.5 KiB
Plaintext

MBOX-Line: From benny at diku.dk Fri Jan 24 04:17:32 2014
To: imap-protocol@u.washington.edu
From: Benny =?utf-8?q?Kj=C3=A6r?= Nielsen <benny@diku.dk>
Date: Fri Jun 8 12:34:52 2018
Subject: [Imap-protocol] Gmail and IDLE flags changes
In-Reply-To: <1F07B294-2A10-424C-9299-434013CBEE6D@isode.com>
References: <CABDm0O-OnP08r5-d6EpU9JM34FAaebRQGOUwRNi1nY=+x9BhBQ@mail.gmail.com>
<5955E352-F7CD-4DBB-A191-F748CCD3932E@gmail.com>
<52E18829.40305@earthlink.net>
<CABa8R6u0_=+EesY6=P2RasNaGzGgPmRdOHfE32f8Tw44baSPFw@mail.gmail.com>
<1F07B294-2A10-424C-9299-434013CBEE6D@isode.com>
Message-ID: <03EA56BC-6D49-4156-A842-D043A2099570@diku.dk>
On 24 Jan 2014, at 11:50, Alexey Melnikov wrote:
>> On 23 Jan 2014, at 21:32, Brandon Long <blong@google.com> wrote:
>>
>> Yes, gmail currently only notifies of new messages and expunged
>> messages during idle.
>
> Can you add an IMAP capability (or can an existing one be used) so
> that client can detect this behaviour?
I second that! I've played with a simple workaround for Gmail in which I
regularly check for flag changes when in the IDLE state, but I haven't
enabled it because I don't like that the workaround is not automatically
disabled when/if Gmail IDLE is improved.
I've also been wondering: The RFC on IMAP IDLE does not state it as a
requirement that servers must (or even should) report flag changes when
in the IDLE state. Has anyone done any experiments showing whether or
not this is a widespread IMAP server limitation (beyond Gmail)?
--
Benny
MailMate: http://freron.com