Hi,
I could see following in RFC 2683 & RFC 2060.
"To alleviate this, a server may implement an inactivity timeout, unilaterally closing a session (after first sending an untagged BYE, as noted above). Some server operators have reported dramatic improvements in server performance after doing this. As specified in [RFC-2060], if such a timeout is done it must not be until at least 30 minutes of inactivity. The reason for this specification is to prevent clients from sending commands (such as NOOP) to the server at frequent intervals simply to avert a too-early timeout. If the client knows that the server may not time out the session for at least 30 minutes, then the client need not poll at intervals more frequent than, say, 25 minutes."
So, shouldn't an imap server like dovevot be configured with 30 minutes timeout.
-- Kind Regards, Sherin
On Fri, Sep 24, 2010 at 11:20 PM, Timo Sirainen tss@iki.fi wrote:
On Fri, 2010-09-24 at 10:24 +0530, Sherin George wrote:
Hello,
I am also in a similar position.
I have a server sitting behind hardware firewall which is configured to timeout all connections in 30 minutes.
So, I would like to set dovecot to 30 minutes.
Dovecot never disconnects IDLEing connections, because several clients expect to be able to do that. But I think you can configure kernel to send keepalive notifications more often (default is every 2,5h IIRC) and then it would notice died connections sooner.