Mihaly Zachar via Postfix-users:
> On Sun, 7 May 2023 at 13:59, Wietse Venema via Postfix-users <
> postfix-users@postfix.org> wrote:
>
> > > > Look at output from:
> > > >
> > > > (postconf -n; postconf -P) | grep soft_bounce
> > > >
> > >
> > > this gives an empty set...
> >
> > In that case I need the COMPLETE postscreen logging for
> > such connections, NOT just the 450 response.
> >
> >
> Here it is:
>
> May 07 01:59:28 mail postfix/postscreen[7389]: CONNECT from
> [209.85.221.44]:48443 to [b.b.b.b]:25
> May 07 01:59:28 mail postfix/postscreen[7389]: ALLOWLIST VETO
> [209.85.221.44]:48443
> May 07 01:59:28 mail postfix/dnsblog[7396]: addr 209.85.221.44 listed by
> domain list.dnswl.org as 127.0.5.0
> May 07 01:59:28 mail postfix/dnsblog[7392]: addr 209.85.221.44 listed by
> domain dnsbl.sorbs.net as 127.0.0.6
> May 07 01:59:28 mail postfix/dnsblog[7395]: addr 209.85.221.44 listed by
> domain hostkarma.junkemailfilter.com as 127.0.0.3
> May 07 01:59:28 mail postfix/dnsblog[7395]: addr 209.85.221.44 listed by
> domain hostkarma.junkemailfilter.com as 127.0.1.1
> May 07 01:59:38 mail postfix/tlsproxy[7399]: CONNECT from
> [209.85.221.44]:48443
> May 07 01:59:38 mail postfix/postscreen[7389]: NOQUEUE: reject: RCPT from
> [209.85.221.44]:48443: 450 4.3.2 Service currently unavailable; from=<
> sen...@gmail.com>, to=<recipi...@domain.tld>, proto=ESMTP, helo=<
> mail-wr1-f44.google.com>
>
> Note: address "b.b.b.b" is my secondary MX address.
This client failed the MX policy test. And that is the only test
failure that postscreen logs. No DNSBL test failure, no PREGREET
test failure.
You have:
postscreen_denylist_action = enforce
postscreen_greet_action = enforce
postscreen_dnsbl_action = enforce
ANd none of those are relevant for a failed MX policy test.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
