Matt, > The BAD_HEADER defaging copies errant headers. An email which has e.g. a > broken 'Subject' line is defanged if, $defang_bad_header is true. The > defanging routine, however just copies the original headers to the newly > created mail - the new mail will have a broken header again. > > This does not solve any problem the problem :-(. Email with poorly > standard compliant email is known to produce problems in MDA or MUAs.
Thanks, fixed in 2.0.4-pre6 I hope. > Anthother proposed feature: > defang_bad_header is only called if the email does not fall into any > other class i.e. the mail is not: "CLEAN", "VIRUS", "BANNED", ... how > about making $defang_bad_header orthogonal to all other classes. > > Usually you do not want to defang spam. But still you want to defang > every mail with bad_headers to protect mail clients and ensure the > validity of index files, filter rules,... When defanging is underway (for any reason), header will be cleaned regardless of the reason for defanging (now in -pre6). Mark ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&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/
