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.
On 2016-05-27 12:21, wie...@porcupine.org wrote:
For fine-grained content management, use amavisd-new, perhaps as a
Okay, I am convinced, actually I am investigating how to integrate this
tool.
Yes, it is possible to use different header/body_checks on different
IP addresses.
On 5/27/2016 3:51 AM, Konstantin Kletschke wrote:
> Hi,
>
> I wonder if there is a mechanism to implement a function to whitelist
> mime_header_checks or not.
>
> I read this is not possible, I also read this is possible with separate
> cleanup (because header_checks and mime_header_cheks
Konstantin Kletschke:
> Hi,
>
> I wonder if there is a mechanism to implement a function to whitelist
> mime_header_checks or not.
Postfix header/body_checks are blunt tools, primarily to block known
bad email that no-one should receive.
For fine-grained content management, use amavisd-new,
Hi,
I wonder if there is a mechanism to implement a function to whitelist
mime_header_checks or not.
I read this is not possible, I also read this is possible with separate
cleanup (because header_checks and mime_header_cheks belongs to cleanup)
and smtpd in master.cf... 50:50
I have a
