MBOX-Line: From imap at tlinx.org  Tue Aug  9 10:42:28 2005
To: imap-protocol@u.washington.edu
From: Linda Walsh <imap@tlinx.org>
Date: Fri Jun  8 12:34:36 2018
Subject: [Imap-protocol] Protocol Q: IMAP(s) svr (want tcp)-> IMAP client
In-Reply-To: <Pine.OSX.4.63.0508072357050.477@pangtzu.panda.com>
References: <42F6B7FD.2000408@tlinx.org> <8764uhgp3l.fsf@windlord.stanford.edu>
	<Pine.OSX.4.63.0508072357050.477@pangtzu.panda.com>
Message-ID: <42F8EB04.2030804@tlinx.org>

It was connection breakage related.

My statefull firewall hardware device defaulted to a max session time of
30 minutes so it apparently closed out the ability for some types
of return TCP communications.  A bit weird, though, since it didn't
seem to block out receiving of emails.  For now, I increased timeout
on imaps connections to 24 hours.  Will see if I only get these
messages once a day now (may be reasonable), or if, at the end of
24 hours it will start logging the denial messages for some long
period. I might just have to set the IMAPS connections to not
timeout, as that is how fetchmail runs (current uptime of 87 days)...

Thanks for the pointers to the obvious...:-)
Linda

Mark Crispin wrote:

> Note as well that a NAT box that times out a session too quickly can 
> do this.  An IMAP session in IDLE can stay open for up to 30 minutes 
> without any traffic, and the server can break the inactivity.
>
> Most NAT boxes are stupid and assume that only clients break inactivity.
>
> -- Mark --
>
> http://staff.washington.edu/mrc
> Science does not emerge from voting, party politics, or public debate.
> Si vis pacem, para bellum.


