Prev: smtpd_helo_required compliance with the RFC
Next: sender-dependent default_transport using FILTER
From: Michael on 30 Dec 2009 04:09
I have a couple of mail servers that act only as SMTP relay, and SMTP backup
servers.

How can I reject invalid recipient addresses at these servers?

I have investigated the manual on local_recipient_maps, however it appears
that this is only useful for email where the machine involved is the final
destination.

In this case these 2 machines operate in a load-balanced manner, forwarding
email onto the final server, or in a few instances acting as an MX20 backup.

I can make available to these servers (via SQL replication) a list of 'valid'
email addresses from the destination mail server(s), how can the
valid/invalid address accept/deny be deployed?

From: Martijn de Munnik on 30 Dec 2009 04:16
On Wed, 2009-12-30 at 22:09 +1300, Michael wrote:
> I have a couple of mail servers that act only as SMTP relay, and SMTP backup
> servers.
>
> How can I reject invalid recipient addresses at these servers?
>
> I have investigated the manual on local_recipient_maps, however it appears
> that this is only useful for email where the machine involved is the final
> destination.
>
> In this case these 2 machines operate in a load-balanced manner, forwarding
> email onto the final server, or in a few instances acting as an MX20 backup.
>
> I can make available to these servers (via SQL replication) a list of 'valid'
> email addresses from the destination mail server(s), how can the
> valid/invalid address accept/deny be deployed?
>
Look for relay_domains and relay_recipient_maps, that will solve your
problem.



--
Martijn de Munnik <martijn(a)youngguns.nl>
YoungGuns

From: Eero Volotinen on 30 Dec 2009 04:30
Quoting Michael <pfml(a)nettrust.co.nz>:

> I have a couple of mail servers that act only as SMTP relay, and SMTP backup
> servers.
>
> How can I reject invalid recipient addresses at these servers?
>
> I have investigated the manual on local_recipient_maps, however it appears
> that this is only useful for email where the machine involved is the final
> destination.
>
> In this case these 2 machines operate in a load-balanced manner, forwarding
> email onto the final server, or in a few instances acting as an MX20 backup.
>
> I can make available to these servers (via SQL replication) a list of 'valid'
> email addresses from the destination mail server(s), how can the
> valid/invalid address accept/deny be deployed?

See address verification (verify) at postfix documentation

--
Eero

 | 
Pages: 1
Prev: smtpd_helo_required compliance with the RFC
Next: sender-dependent default_transport using FILTER