On Wed, Nov 05, 2025 at 12:50:14PM -0500, Wietse Venema via Postfix-users wrote:
> Crection: I omitted a 'postfix reload' after the confiog change.
>
> > # postconf 'transport_maps = static:{retry:migration in progress}'
> > # postconf 'canonical_maps=static:any@where'
>
> After 'postfix reload', the address rewriting does change the result.
>
> # telnet 127.0.0.1 smtp
> Trying 127.0.0.1...
> Connected to 127.0.0.1.
> Escape character is '^]'.
> 220 wzv.porcupine.org ESMTP Postfix
> mail from:<>
> 250 2.1.0 Ok
> rcpt to:<some@where>
> 250 2.1.5 Ok
>
> This is with "mynetworks = 127.0.0.1/32". Wiet a different clkient
> the result becomes
>
> 554 5.7.1 <some@where>: Relay access denied
>
> Thus, address rewriting can pre-empt the delivery transport check.
> That is not what I expected.
Thanks, good to know we've landed in the same universe. :-) However
suprising the agreed behaviour may be at first blush, I believe that it
is logically "correct". After a rewrite the transport that will handle
the new address may be quite different from the one that would apply
to the original address (e.g. for virtual alias domains it would no
longer be "error:5.1.1 User unknown in virtual alias table").
So, unless some day smtpd(8) starts performing rewrites and somehow
applying policy to rewritten addresses (if 1-to-1???), the current
behaviour is the only one possible.
--
Viktor. 🇺🇦 Слава Україні!
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
