Noel Jones: [ Charset ISO-8859-1 unsupported, converting... ] > On 4/4/2011 9:54 PM, email builder wrote: > > > > OK, sorry again. I had assumed because you can turn off header checking by > > using receive_override_options, you could also override (change) them. > > It is possible to override header_checks by defining a > different cleanup_service_name for smtpd, then defining that > cleanup service with a header_checks override. This can get > pretty messy, you can find examples in the list archives. > > The better solution is to use multiple instances. All postfix > versions support multiple instances. Newer versions include > tools to make multiple instance creation/maintenance easier.
He seems to want sender IP address selection based on some message attribute. We discussed that early 2010 in http://www.irbs.net/internet/postfix/1001/0390.html I solved this specific problem a few days later with Postfix 2.7 by changing the effect of "FILTER transport:" (i.e. transport without next-hop destination). The OP appears to be stuck on Postfix 2.3 so he will have to use the solution that involves specifying "FILTER smtp:nexthop" where each nexthop is a separate Postfix instance with its own myhostname and inet_interfaces setting. In the 2010 discussion I forgot to mention that he'd also have to change the inet_interfaces setting of the primary Postfix instance to avoid "mail loops back to myself" errors. To fix this, specify "inet_interfaces = 127.0.0.1 1.2.3.4" where 1.2.3.4 is the primary IP address. This way, the primary instance won't try to receive mail for the additional instances. Wietse
