On 2016-05-27 22:00, Noel Jones wrote:
The separate cleanup+header_checks must listen on a different IP:port.
*urks*
You'll need to arrange with the sender to use the alternate IP:port rather than your normal MX:25, or use firewall tricks to redirect the sender to the alternate IP:port. Both these are inconvenient and prone to breakage because they're different from normal mail flow. So... whitelisting (mime_)header_checks is not possible without fragile infrastructure changes that don't scale well. And it's not really whitelisting, it's exempting specified clients from any header_checks.
Thanks for your comprehensive answer. I am convinced now, to go the amavisd-new way. It is the preffered tool to do what we need.
Kind Regards, Konstantin
