34 lines
1.3 KiB
Plaintext
34 lines
1.3 KiB
Plaintext
MBOX-Line: From dave at cridland.net Mon Sep 18 08:42:20 2006
|
|
To: imap-protocol@u.washington.edu
|
|
From: Dave Cridland <dave@cridland.net>
|
|
Date: Fri Jun 8 12:34:38 2018
|
|
Subject: [Imap-protocol] Avoiding connection-loss
|
|
In-Reply-To: <Pine.OSX.4.64.0609180815470.368@pangtzu.panda.com>
|
|
References: <009901c6daf1$1026f580$2d65a8c0@ProImage.local>
|
|
<Pine.OSX.4.64.0609180815470.368@pangtzu.panda.com>
|
|
Message-ID: <5273.1158594140.711631@invsysm1>
|
|
|
|
On Mon Sep 18 16:22:40 2006, Mark Crispin wrote:
|
|
> The workaround for this problem is, after 29 minutes with no new
|
|
> mail, to send a fake EXISTS that alleges that there is one new
|
|
> message. Then, when the client issues a DONE to exit IDLE mode,
|
|
> send a fake EXPUNGE to revoke that "new message". This will cause
|
|
> that client to issue a new idle.
|
|
|
|
Whilst I'm impressed at the devious nature of that workaround, it
|
|
occurs to be that you'd have to be fairly careful, since:
|
|
|
|
1) You'd have to ensure the EXPUNGE was sent prior to the tagged OK
|
|
of the IDLE. Easy enough, but:
|
|
|
|
2) You'd also have to increment UIDNEXT etc in order to avoid
|
|
confusing the client later.
|
|
|
|
Dave.
|
|
--
|
|
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org
|
|
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
|
|
- http://dave.cridland.net/
|
|
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
|
|
|