https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8381
Bill Cole <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Bill Cole <[email protected]> --- mail-tester.com is not a useful tool for understanding SpamAssassin results. They use the wrong sign on scores, with an obsolete version, and do not reliably update rules and scores, which can change daily. Anything they tell you about SpamAssassin is garbage. As for the specific issue of "bad" TLDs, that is a rule developed and scored based on the email sent to our QA contributors. The rule PDS_OTHER_BAD_TLD is limited to score 2.00 no matter what our re-scorer determines, because it is a very accurate test when it hits. 97% of mail hitting that rule is spam. That rule does sometimes hit on legitimate mail, as do nearly all of our rules. It is limited in its score to protect against SA misidentifying legitimate mail due solely to this rule. The default spam threshold is 5 and most legitimate mail hits multiple non-spam rules, so a rule scoring 2 shouldn't be marked *by SpamAssassin* as spam. On a normal SpamAssassin system, a message would need to match rules totaling a score over 3 (including non-spam rules with negative scores) in addition to PDS_OTHER_BAD_TLD. Note that SpamAssassin is not used (as far as we know) by any major email provider such as Microsoft, Yahoo, or Google. Very large mail systems typically use their own homegrown spam filters because they have unique needs. If your mail is being misidentified as spam by any of them, it is not due to SpamAssassin. HOWEVER, because things *do* change and that rule lumps together multiple TLDs, I have added a new rule to the default ruleset called SCC_TLD_WORLD which I have committed in r1932669. After that rule goes out in an update (likely 2-3 days due to QA processing) we will be able to determine whether ".world" is still as dominated by spam as it was when it was added to the rule. -- You are receiving this mail because: You are the assignee for the bug.
