Facebook
Twitter
andreios
Basic Pleskian
When using Plesk to setup maximum number of connections, under mail server settings (in my case 1024), the client_limit setting is not adjusted as intended.
I found this support article that talks about this problem.
In this article it is suggested to increase default_client_limit to solve the problem.
However, the dovecot settings depend on Plesk and will disappear after an update.
I therefore suggest to let Plesk do the setting by calculating the setting as follows.
This is the warning that doveconf gives me:
This shows exactly how the value is calculated. If I insert the larger of the two calculated values into dovecot.conf, the message disappears.
Here are the dovecot directions for "anvil" and "auth" in the docs.
I found this support article that talks about this problem.
In this article it is suggested to increase default_client_limit to solve the problem.
However, the dovecot settings depend on Plesk and will disappear after an update.
I therefore suggest to let Plesk do the setting by calculating the setting as follows.
This is the warning that doveconf gives me:
Code:
doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248). Counted for protocol services with service_count != 1: service managesieve-login {
process_limit=100 } + service pop3-login { process_limit=1024 } + service imap-urlauth-login { process_limit=100 } + service imap-login { process_limit=1024 }
doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251). Counted with: service managesieve-login { process_limit=100 } + service pop3-login { process_limit=1024 } + service imap-urlauth-login { process_limit=100 } + service imap-login { process_limit=1024 } + service auth { process_limit=1 }
Code:
default_client_limit = 2251Here are the dovecot directions for "anvil" and "auth" in the docs.
