MBOX-Line: From barryleiba at computer.org  Fri Jan 24 07:47:53 2014
To: imap-protocol@u.washington.edu
From: Barry Leiba <barryleiba@computer.org>
Date: Fri Jun  8 12:34:52 2018
Subject: [Imap-protocol] Gmail and IDLE flags changes
In-Reply-To: <03EA56BC-6D49-4156-A842-D043A2099570@diku.dk>
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>
	<03EA56BC-6D49-4156-A842-D043A2099570@diku.dk>
Message-ID: <CAC4RtVDfVXES2=1EDJA_ByrcYr2gWTh9mm21+=kPf5rX1UCaGA@mail.gmail.com>

> 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.

That's because there isn't an IDLE "state": IDLE is a command that
continues "running", and IMAP servers are supposed to report state
changes while commands are in progress.  There's nothing special here
that's different to any other command.  If gmail fails to sent state
updates for flag changes during, say, FETCH or APPEND commands, then
they're being consistent (and wrong).  If they're doing some special
case for IDLE, then they're being peculiar (and wrong).

But there's no reason for the IDLE spec to say anything about flag
changes in particular.  Head to the base IMAP spec to see what status
updates servers should be reporting.

Barry

