MBOX-Line: From tss at iki.fi  Mon Oct  4 18:43:21 2010
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] Fwd: iOS IMAP IDLE (Standard "Push Email")
	Deficiency, Explanation?
In-Reply-To: <alpine.OSX.2.00.1010041808260.392@hsinghsing.panda.com>
References: <352410DE-19D8-4EE4-8741-AB82741D7A18@sabahattin-gucukoglu.com>
	<4CAA0F5C.7030009@lists.grepular.com>
	<alpine.OSX.2.00.1010041034520.392@hsinghsing.panda.com>
	<7D32DBF6-2ECC-4854-85A8-84261D828ED2@sabahattin-gucukoglu.com>
	<11166.1286223088.054596@puncture>
	<alpine.OSX.2.00.1010041338040.392@hsinghsing.panda.com>
	<4CAA7379.3070307@aol.com>
	<alpine.OSX.2.00.1010041749370.392@hsinghsing.panda.com>
	<4CAA79EE.20003@aol.com>
	<alpine.OSX.2.00.1010041808260.392@hsinghsing.panda.com>
Message-ID: <9687DB24-F5DF-436E-8F5E-0454C23BEF3B@iki.fi>

On 5.10.2010, at 2.18, Mark Crispin wrote:

> There's no enforcement of such a requirement.  If IDLE is simply a
> checklist requirement (which it usually is) then the simplest way to get
> it checked is via an internal poll.
> 
> After all, who's gonna know?

I often force a refresh by marking some existing message unseen and then back again to seen while waiting for a message that I know is going to arrive, clicking this key combination often enough until it I see the mail. So it is possible to know, although that assumes the server notices new messages during flag changes.

(I realized only during this thread that this is actually a server problem while using Mail.app, because I'm using Solaris that doesn't have Linux-like inotify. I guess I should either increase my polling timeout to 1 second or implement some IPC of my own so at least I'd get rid of this habit half the time I read mails.)
