Rob McMillin <[EMAIL PROTECTED]> writes: > When sysadmins in those TLDs fix their relays, I'll be happy to hear > them out.
The other problem with using this type of test in a spam corpus is that you're using a small subset of global spam. I don't do any business with people from some random country, so of course, all of my mail from them is spam. However, if someone else does business with that country, 99.99% of their mail from there is not spam. It's very specific to the user. Also, it's bad public relations for SA and spam-filtering in general. (Just a fact of life.) It would be better to find a rule that just worked. For example, one method would be a TLD "whitelist". As spamassassin receives mail, there are two counters for each TLD. One is total messages and the other is total number tagged as spam. Then rank the spam ratio by TLD. TLDs in the worst quartile get +1.0 score, TLDs in the next 25% get +0.5 score, TLDs in the next 25% get -0.5, TLDs in the best 25% get -1.0. You do use the same exact method for locales so spam detection based on locale would be autoconfiguring based on the user. (Probably languages too.) Dan _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
