https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6389
--- Comment #7 from John Wilcock <[email protected]> 2010-04-07 07:39:55 UTC --- Created an attachment (id=4735) --> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4735) Another FP My first FP sample was indeed "saved" by ALL_TRUSTED (and BAYES_00). Here's another one, an opt-in newsletter that was only saved by RCVD_IN_RP_CERTIFIED and RCVD_IN_RP_SAFE (it also had a valid DKIM signature, which I've no doubt invalidated by obfuscating the recipient's address). Any messages from people with highbit characters in their names, and with highbit characters in the subject and body will potentially hit the rule - and that is inevitably a fairly common scenario for non-English mail. What appears to be saving this rule from more FPs is the check for base64 encoding of the headers. Thunderbird, for instance, appears to use quoted-printable encoding for ISO-8859-1, its default charset, and only switches to base64 for UTF-8 and other multibyte charsets. Does the rule actually hit much spam that wouldn't be caught otherwise? On my two low-volume servers I have only one spam hit that would have scored under 10 points without this rule, and none that would have been FNs. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
