> In case of problems with the functioning of SA Bugzilla, > is useful to retain the record of the interaction to help prevent repeated Even when a report is determined to not be a bug, it > It is not common to remove bug reports. > Hello! I'm coming back to you because I'd like to erase all traces of this > (In reply to multu14200 from comment #6) actually marking legitimate mail as spam.) The inclusion of the 'online' TLD in the "suspicious" list is grounded in observed empirical fact, and the scoring of the rules using that list is constrained to limit the potential for broad damage (i.e. There is nothing about this that is addressable as a "bug" in SA. definitely below 5.) Some sites set their thresholds lower, but very rarely lower than 4. It's not critical to minimize your SA score, it only matters that you don't score too high (i.e. If your mail scores below 5 IN TOTAL then SpamAssassin is saying that it is probably not spam. By design, every message will match some SA rules that have positive (spammy) scores and some that have negative (hammy) scores. Note that the inclusion and scoring of rules in the default ruleset is controlled by a daily automated process that uses submitted corpora of "spam" and "ham" mailĪnd their scoring. We assume that no one filing a bug here is actually spamming unless they say so. Whether you are spamming or not isn't determined by a SA score, it's determined by whether you have the consent of the people you're mailing.
#Apache spamassassin how to
> Do you know how to avoid this by keeping the same domain name so that I To be deemed "spam" by SpamAssassin using the default configuration, you'd need a score over 5. Most of that is from the last rule, which checks domains found in the body of mail: in theory just from URLs, but that's loosely parsed. Total score: 2.225 as shown, 2.800 by current release scoring. > -1.725 PDS_OTHER_BAD_TLD Untrustworthy TLDs > -0.001ğROM_SUSPICIOUS_NTLD_FPğrom abused NTLD > -0.499ğROM_SUSPICIOUS_NTLDğrom abused NTLD That's entirely unrelated to domains, it's a quirk of your email's transport encoding which is formally improper but not *per se* significantly correlated to a message being spam or non-spam. > -0.001 MIME_QP_LONG_LINE Quoted-printable line longer than 76 chars That's not specific to your domain or TLD, it is a result of the addressing of your email: different domains in the From header and SMTP envelope. > -0.249 HEADER_FROM_DIFFERENT_DOMAINSğrom and EnvelopeFrom 2nd level mail It seems to be showing negative scores for rules that should have positive (spammy) scores and the score values do not match recent versions of the standard ruleset. NOTE: whatever you're using to get a SpamAssassin score is broken. No, the past users of the same gTLD have given it a bad reputation. > SpamAssassin filter gives my domain name a bad reputation. Hello! I don't know if this is the right place, but I see that your