Edgar Fu? via Postfix-users:
> > You forgot to
> I guess in case I did forget one of these, the test mail wouldn't show up
> in mailq as held with the 450 message.
>
> > postconf transport_maps
> $ /usr/pkg/sbin/postconf transport_maps
> transport_maps = hash:/tmp/transport
>
> > postmap hash:/tmp/transport
> I didn't mention it, but no, I didn't forget that
> $ ls -l /tmp/transport*
> -rw-r--r-- 1 ef wheel 52 Nov 4 10:00 /tmp/transport
> -rw-r--r-- 1 ef wheel 16384 Nov 4 10:00 /tmp/transport.db
>
> > postfix reload
> I did the equivalent /etc/rc.d/postfix reload.
>
> So I must be missing something else.
I missed something. The SMTP server looks at the trivial-rewrite
reply, and rejects an address if it resolves to the error(8) transport.
I should have updated the SMTP server to also special-case the
'retry' transport when that was added in Postfix 2.4.
Unfortunately, my example will not work with the error transport:
postconf transport_maps='static:{error:4.1.2 Migration in progress}'
# telnet localhost smtp
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 wzv.porcupine.org ESMTP Postfix
mail from:<>
250 2.1.0 Ok
rcpt to:<anyone@anywhere>
550 5.1.2 <anyone@anywhere>: Recipient address rejected: Migration in
progress
The error transport forces a oft error into a hard error. That
does make sense; to report a soft error, use the retry agent.
> What confuses me is that transport(5) says
> The table is searched by the trivial-rewrite(8) daemon.
> but according to doc/OVERVIEW, smtpd(8) doesn't talk to trivial-rewrite(8).
Yes, I should have updated the text. It was written four years
before the retry agent was added.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
