> On Oct 21, 2018, at 5:14 PM, Peer Heinlein <p.heinl...@heinlein-support.de>
> wrote:
>
> If a client connects to smtpd and then breaks the connection because
> there's only STARTTLS or AUTH ONLY we have those remaining smtpd
> processes -- which makes the server looking busy, while he isn't.
>
> If there's really a long peak then the server IS busy and I WANT to have
> an alarm.
You could look for "smtpd" processes with with "-o stress=yes" on their
command-line. These are spawned by master(8) when process limit has
been hit.
http://www.postfix.org/STRESS_README.html#adapt
http://www.postfix.org/STRESS_README.html#feature
The document does not mention one detail you may care to know:
/*
* When all servers for a public internet service are busy, we start
* creating server processes with "-o stress=yes" on the command
* line, and keep creating such processes until the process count is
* below the limit for at least 1000 seconds. [...]
*/
So it takes ~16 minutes without hitting the limit before the stress setting
is "relaxed".
On a modern server you can reasonably run around 1000 smtpd(8) processes,
and postscreen(8) should help to keep the typical process count lower than
it would be otherwise.
--
Viktor.
