First, why use SASL auth? It needs a database. Have you considered
more scalable alternatives such as TLS client certificates?
Postfix can use certificate fingerprints instead of PKI.
Second, if you must use SASL auth:
What is the authentication backend database query latency? Have you
looked
Some feedback.
It may be possible that you're running out of file handles,
either the kernel limit, or the per-process limit.
I did not have time to actively check this.
postconf "max_use = 10"
postfix reload
Error fatal: no SASL authentication mechanisms and postfix process exit,
Thank you for your response. For clarity, this issue has been present
for several weeks now.
warning: SASL: Connect to Dovecot auth socket 'private/auth'
failed: REASON FOR FAILURE HERE
I do not have this warning in the logs.
Can you try these commands:
postconf "max_use =
Hello,
Currently our Postfix server is experiencing a problem with intermittent
SASL auth problems.
This mail server worked well up to a point, when the "fatal: no SASL
authentication mechanisms" errors started. From this point I started
researching and changing the mail server configuration
