> On Dec 13, 2018, at 8:25 PM, Alex <mysqlstud...@gmail.com> wrote:
>
> We had a Mimecast user report today that their mail was being rejected
> with a 4.7.0 "too many connections" error. This is a "soft" error, in
> that the mail client will later attempt to resend, correct?
Should be.
> Isn't the default of 50 concurrent connections sufficient for most
> environments? Is there really any reason I should consider increasing
> that limit?
Do read the log you post...
> Dec 13 17:01:18 mail03 postfix/smtpd[27153]: warning: Connection
> concurrency limit exceeded: 5 from us-smtp-delivery-100.mimecast.com[2
> 16.205.24.100] for service smtpd
5 < 50.
> Dec 13 17:01:18 mail03 postfix/smtpd[27141]: warning: Connection
> concurrency limit exceeded: 6 from us-smtp-delivery-100.mimecast.com[2
> 16.205.24.100] for service smtpd
6 < 50.
> postconf -d|grep smtpd_client_connection_count_limit
> postscreen_client_connection_count_limit =
> $smtpd_client_connection_count_limit
> smtpd_client_connection_count_limit = 50
The "postconf -d" command reports compiled-in defaults, not your
settings, which are reported with "postconf -n" or just "postconf"
if you also want to see any unchanged defaults.
--
Viktor.
