>
> Besides letting mail with bad headers pass
> $final_bad_header_destiny=D_PASS;
> (which is mostly harmless, but can be annoying), with
> amavisd-new 2.4.4 or
> later you can disable some of the header tests selectively, e.g.
> $allowed_header_tests{'multiple'}=0;
>
> The %allowed_header_tests is also switchable through policy banks,
> e.g. can allow more freedom for internal hosts, compared to the rest.
>
> Note that whitelisting is only for spam, it has no effect on
> other tests.
Ok did not know that. Is it possible to whitelist or enable/disable per
destination domain/email? If so, how? If not, this could be a useful
feature.
Also the idea of at least with multiple, make it acceptable to allow
multiples for specific fields and not for others. It's common for a
hijacked web form spam to have two Subjects:
-L
--
Larry Ludwig
Empowering Media
1-866-792-0489 x600
Have you visited our customer service blog?
http://www.supportem.com/blog/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
