On Fri, Sep 08, 2023 at 11:13:02PM +1000, lists--- via Postfix-users wrote:
> # grep "C92564346E5" /var/log/maillog > Sep 8 16:41:31 geko postfix/cleanup[15407]: C92564346E5: > message-id=<[email protected]> > Sep 8 16:41:31 geko postfix/qmgr[1654]: C92564346E5: from=<[email protected]>, > size=3262, nrcpt=1 (queue active) > Sep 8 16:41:42 geko amavis[31308]: (31308-14) Passed CLEAN > {RelayedInternal}, ORIGINATING LOCAL [111.222.333.444]:52547 > [111.222.333.444] <[email protected]> -> <[email protected]>, Queue-ID: C92564346E5, > Message-ID: <[email protected]>, mail_id: > zj3cR-iB-usR, Hits: -3.069, size: 3681, queued_as: F22794346E8, 10889 ms > Sep 8 16:41:42 geko postfix/smtp[15464]: C92564346E5: to=<[email protected]>, > relay=127.0.0.1[127.0.0.1]:10026, delay=16, delays=5.4/0/0.01/11, > dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 > 2.0.0 Ok: queued as F22794346E8) > Sep 8 16:41:42 geko postfix/qmgr[1654]: C92564346E5: removed Your amavis content filter has a non-trivial backlog of mail, probably because each message takes a long time to process. Here the message sat 5.4 seconds in the incoming queue and then took 11 seconds to to deliver to amavis. This bottleneck suggess that the amavis filter is doing remote DNS lookups that are quite slow. You need to review your amavis configuration and disable or tune the actions that lead to the processing delays. -- Viktor. _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
