On Thu, Dec 08, 2022 at 11:44:53AM -0500, Jonathan Capra wrote:
> I tried the config from your last email and got the same results:
>
> rcpt to: t...@fongaboo.com
> 550 5.1.1 <t...@fongaboo.com>: Recipient address rejected: User unknown in
> relay recipient table
In other words, Postfix rejects relay recipients not listed in
relay_recipient_maps.
> relay_domains = hash:/etc/postfix/relay_domains
> relay_recipient_maps = hash:/etc/postfix/relay_recipients
>
> Ran postmap on relay_domains and relay_recipients for good measure.
> Confirmed the respective .db files had a current timestamp.
> Restarted postfix:
>
>
> $ telnet ca2ceus.wtfayla.net 25
> Trying 50.75.172.140...
> Connected to ca2ceus.wtfayla.net.
> Escape character is '^]'.
> 220 caduceus.wtfayla.net ESMTP Postfix (Debian/GNU)
> helo fongaboo.com
> 250 caduceus.wtfayla.net
> mail from: fonga...@gmail.com
> 250 2.1.0 Ok
> rcpt to: t...@fongaboo.com
> 250 2.1.5 Ok
> data
> 354 End data with <CR><LF>.<CR><LF>
> this is going to t...@fongaboo.com
> .
> 250 2.0.0 Ok: queued as E99942E40AC
In other words, this recipient matches your relay recipient maps.
> Is this the best I can hope for? That the secondary still sends it on,
> but the primary rejects it outright?
You get the behaviour you configure.
> Shouldn't the secondary be able to 'slam the door' immediately on any
> rcpt to: not in its relay_recipients file?
Of course, as you already demonstrated when the recipient table was
empty.
--
Viktor.
