[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cyrus-info
Subject:    Re: cyrus 2.5 imap idle/stuck connections (DOS like)
From:       Wolfgang Breyha <wbreyha () gmx ! net>
Date:       2019-03-07 16:09:45
Message-ID: 8c284ebc-e4c5-68e6-fc81-3d088528f9c1 () gmx ! net
[Download RAW message or body]

Heiler Bemerguy via Info-cyrus wrote on 07/03/2019 16:30:
> My   "man imapd.conf" doesn't list this option at all. I think my Cyrus 
> 2.5.10 is older than it..

Yes. It appeared in 2.5.11 according to my build environment.

But there already was the option
     timeout: 30
before. So every connection was closed by default after 30 minutes if there
was no activity.

"imapidletimeout" uses the value of "timeout" as upper limit default as well.

> But I've added it to the .conf anyway. Won't hurt if it doesn't exist 
> yet, right? lol
I currently don't remember if imapd ignores unknown options or fails on startup.

But maybe the better option is to use
tcp_keepalive: yes
anyway.

We had "dead" connections as well before imapidletimeout existed and I was
able to get rid of them by activating keepalives to trigger the "timeout: 30"
check.

Greetings, Wolfgang
-- 
Wolfgang Breyha <wbreyha@gmx.net> | https://www.blafasel.at/
Vienna University Computer Center | Austria

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
[prev in list] [next in list] [prev in thread] [next in thread]