Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to run a benchmarking application which connects to my IMAP server and has a "warm up" phase during which IMAP connections are being established. I've set my limits properly and the mail server should be able to handle all the connection just fine (2GB memory, 50GB space, 2vCPUs).

However, this warmup phase takes a while. In the meantime, while all my tcp connections to dovecot are being established, the ones that are established first seem to be getting closed (or maybe I'm running out of sockets, but I've set all system limit pretty high).

Here's my dovecot log of this happening:

Could anyone advise how I could possible increase dovecot's *keep_alive* default? Or perhaps increase the maximum number of sockets it could use? I've checked all I could think of, but any suggestions at all would be quite welcome.

Note: I'm intenationally using plaintext authentication and IMAP only.

share|improve this question
up vote 0 down vote accepted says that if you have set secure mode via

service imap-login {
  service_count = 1

each client fork his own login process and then

If the maximum login process count is reached, the oldest process in logging-in state (ie. non-proxying) is destroyed. That is intended to allow newly connected clients to get connection.

If you set up so called hi performance mode via

service imap-login {
  service_count = 0

then all incoming connections will be processed by one process - without limitations.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.