Stefan Foerster:
* Wietse Venema wie...@porcupine.org:
This is implemented by specifying FILTER actions with empty next-hop
destinations in access maps or header/body_checks, and by configuring
in master.cf one Postfix SMTP client for each SMTP source IP address,
where each client has its
Wietse Venema:
Stefan Foerster:
* Wietse Venema wie...@porcupine.org:
This is implemented by specifying FILTER actions with empty next-hop
destinations in access maps or header/body_checks, and by configuring
in master.cf one Postfix SMTP client for each SMTP source IP address,
postfix-2.7-20100117 changes the meaning of content filters of the
form transport: (note: no next-hop destination) so that this
form can be used to implement sender reputation schemes. Typically,
mail is split into classes, and all mail in class X is sent out
from an SMTP client IP address that
On Sun, Jan 17, 2010 at 05:38:12PM -0500, Wietse Venema wrote:
According to discussions on the Postfix list there is a legitimate
need for such functionality. Until now this requires one Postfix
instance per source IP address.
I am not entirely convinced the need is legitimate, as this
Victor Duchovni put forth on 1/17/2010 5:43 PM:
On Sun, Jan 17, 2010 at 05:38:12PM -0500, Wietse Venema wrote:
According to discussions on the Postfix list there is a legitimate
need for such functionality. Until now this requires one Postfix
instance per source IP address.
I am not
* Wietse Venema wie...@porcupine.org:
This is implemented by specifying FILTER actions with empty next-hop
destinations in access maps or header/body_checks, and by configuring
in master.cf one Postfix SMTP client for each SMTP source IP address,
where each client has its own -o myhostname and
