Good afternoon list.
We have a number of clients who have misconfigured applications on their
network, which is sending
anything from warning to info messages to the developer.
Our servers are used as an outbound relay (smarthost) for our clients.
Is there a way to filter messages before
On Thu, Mar 24, 2011 at 11:54:03AM +0200, Tom Kinghorn wrote:
We have a number of clients who have misconfigured applications
on their network, which is sending anything from warning to info
messages to the developer.
Our servers are used as an outbound relay (smarthost) for our
clients.
Tom Kinghorn:
Good afternoon list.
We have a number of clients who have misconfigured applications on their
network, which is sending
anything from warning to info messages to the developer.
Our servers are used as an outbound relay (smarthost) for our clients.
Is there a way to
On 3/24/2011 3:09 PM, /dev/rob0 wrote:
On Thu, Mar 24, 2011 at 11:54:03AM +0200, Tom Kinghorn wrote:
If you can figure out how to do this without relying on content,
other options are available, including restriction classes and
policy servers:
On 3/24/2011 3:10 PM, Wietse Venema wrote:
If you make the rule too specific, no-one will fix their application.
The following moves the pain to the party that is making the problem:
/etc/postfix/main.cf:
smtpd_client_restrictions =
check_client_access
Tom Kinghorn:
On 3/24/2011 3:10 PM, Wietse Venema wrote:
If you make the rule too specific, no-one will fix their application.
The following moves the pain to the party that is making the problem:
/etc/postfix/main.cf:
smtpd_client_restrictions =
check_client_access
On 3/24/2011 3:33 PM, Wietse Venema wrote:
Then trigger on the sender address.
/etc/postfix/main.cf:
smtpd_sender_restrictions =
check_sender_access hash:/etc/postfix/client_access
/etc/postfix/sender_access:
user@example 450 4.7.0 Please see http://www.example/whatever
