with before queue filtering this should work through the default blacklist rule (pmg-smtp-filter would reject the mail, and it would not get queued on PMG)Is before queue filtering can help?
check the complete log - if pmg-smtp-filter replied with a 5xx code then the sending server sees this as a rejected message...Thank you for reply! But in Tracking Center it still shows blocked instead of rejected. Is this correct?
check the complete log - if pmg-smtp-filter replied with a 5xx code then the sending server sees this as a rejected message...
Sep 8 12:12:26 mailgw pmg-smtp-filter[4601]: 826885F574AF9A0274: block mail to <user@domain.com> (rule: Drop Blacklist)
Sep 8 12:12:26 mailgw pmg-smtp-filter[4601]: 826885F574AF9A0274: processing time: 0.879 seconds (0.792, 0.053, 0)
Sep 8 12:12:26 mailgw postfix/lmtp[4817]: 9152C82687: to=<user@domain.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.3, delays=0.34/0.02/0/0.93, dsn=2.7.0, status=sent (250 2.7.0 BLOCKED (826885F574AF9A0274))
This logline looks like it's from a system not configured for before queue filteringSep 8 12:12:26 mailgw postfix/lmtp[4817]: 9152C82687: to=<user@domain.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.3,
This logline looks like it's from a system not configured for before queue filtering
are the configuration templates for postfix (especially master.cf.in) without modifications?
please post your rendered '/etc/postfix/master.cf' (and your '/etc/postfix/main.cf')
this might explain why the scanning happens as after-queue filtering ....content_filter=scan:127.0.0.1:10024
Sep 12 09:48:06 mailgw postfix/smtpd[13604]: proxy-reject: END-OF-MESSAGE: 554 5.7.1 Rejected for policy reasons (82B945F5C6F25251C5); from=<user@google.com> to=<user@domain.com> proto=ESMTP helo=<mail-wm1-f46.google.com>
this was implemented (afair with 6.2) - the configuration templates in /etc/pmg/templates are monitored with ucf(1) - and you should get asked upon upgrade.and i guess some notification needed in such cases.
We use essential cookies to make this site work, and optional cookies to enhance your experience.