> max_idle was the option I was looking for. Thank you.
>
> I always grepped for something like timeout/daemon/time and I never
> found max_idle. :-)
Lowered here as well...
--
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG, 80333 München
> It could also be very great to have Postfix like this, showing some
> informations about the connection:
>
> smtpd [unused/virgin]
> or
> smtpd [, , , ]
>
> Could be great for analysis and to get a quick overview about what's
> going on on busy servers.
That's a nice idea on systems where this
> On Oct 21, 2018, at 5:14 PM, Peer Heinlein
> 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 p
Am 20.10.2018 um 19:06 schrieb Wietse Venema:
Hi,
>> If a client disconnects very early, the smtpd is still "unused" and
>> remains in server memory, waiting for the next connection.
>
> The Postfix behavior has nothing to do with the duration of an SMTP
> session. It is determined by the max_id
we're monitoring the amount of active smtpd processes to make sure, that
we do not reach the max-proc limit from master.cf.
The number I found most useful to indicate something was going wrong
is the number of messages in the queue. For the servers I manage,
normally that number would be
On 10/20/2018 7:24 AM, Peer Heinlein wrote:
we're monitoring the amount of active smtpd processes to make sure, that
we do not reach the max-proc limit from master.cf.
If a client disconnects very early, the smtpd is still "unused" and
remains in server memory, waiting for the next connection.
Peer Heinlein:
>
> Hi,
>
> we're monitoring the amount of active smtpd processes to make sure, that
> we do not reach the max-proc limit from master.cf.
>
> If a client disconnects very early, the smtpd is still "unused" and
> remains in server memory, waiting for the next connection.
The Postfix
We simply monitor established tcp sessions to smtpd port. if client flies
away, tcp session does as well:
lsof -i tcp:25 | grep ESTABLISHED | wc -l
Am Samstag, 20. Oktober 2018 schrieb Peer Heinlein :
>
>
>
> Hi,
>
> we're monitoring the amount of active smtpd processes to make sure, that
> we do
