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,
appeared again.
No other warnings.
Then set the default process limit value to 100:
postconf "default_process_limit = 100"
postfix reload
Error fatal: no SASL authentication mechanisms and postfix process exit,
appeared again.
No other warnings.
All the debug logging is causing systemd to drop imprtant information.
I enabled debug logging for 24 hours only on 1 Aug, logging was normal
before and after.
Ultimately, it may be better to limit the nunber of conections at
the source, on the Kubernetes application side.
This is the crux of the matter and the correct solution. The source will
be updated at some point in time, this is in process, as I stated in my
first mail.
For the time being I need to make the mail server work as best as
possible, given what I have to work with. If it means not accepting the
odd 100 mails out of 25K+, then so be it.
I have reverted "max_use = 10" back to default and I bumped the default
process limit up to 200. The active queue became very slow andhad
collected 4k mail and climbing, by the time I could check on it again.
Stuart
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
