Zitat von Andres Vergara <wal...@0xffff.com.ar>:
Hello there, list
I'm setting up a new mailserver (postfix -> amavisd-new ->
postfix) for a company and while debugging (smtpd -v,
trivial-rewrite -v) i've noticed this
Feb 27 02:14:06 sandbox postfix/smtp[5700]: D95C920175B:
to=<wal...@0xffff.com.ar>,
relay=pop3.0xffff.com.ar[200.51.197.201]:25, delay=1.2,
delays=0.06/0.2/0.31/0.66, dsn=2.0.0, status=sent (250 2.0.0 Ok:
queued as D00D31B8EC4)
Feb 27 02:14:06 sandbox postfix/qmgr[5689]: D95C920175B: removed
Feb 27 02:14:07 sandbox postfix/smtpd[5692]: proxymap stream disconnect
Feb 27 02:14:08 sandbox postfix/smtpd[5692]: rewrite stream disconnect
Feb 27 02:14:08 sandbox postfix/trivial-rewrite[5695]: connection
closed fd 128
Feb 27 02:14:09 sandbox postfix/trivial-rewrite[5695]: connection
closed fd 130
Feb 27 02:14:09 sandbox postfix/trivial-rewrite[5695]: connection
closed fd 131
Feb 27 02:14:09 sandbox postfix/trivial-rewrite[5695]: connection
closed fd 129
Feb 27 02:14:10 sandbox postfix/trivial-rewrite[5695]: idle timeout
-- exiting
Feb 27 02:15:43 sandbox postfix/smtpd[5692]: idle timeout -- exiting
Those last idle timeouts.. the mails are flowing fine and amavisd is
playing nice (afaik), but i'm a bit concerned about the nature of
this timeouts. Is this an expected behaviour? I've digged through
the mail list archive and i couldn't find an answer.
Postfix processes are the perfect worker. When no work is to be done
they quit and therefore waste no resources (RAM,CPU-cycles) which may
be needed otherwise. If there is mailflow "master" create new
processes (smtpd, smtp..) as needed.
As said if you remove the debug flag (-v) nothing will be logged for this.
Regards
Andreas
