The lower the number, the more that is considered a legitimate email or not spam. Generally, the higher the number, the more that it is considered spam. This is the numerical value assigned to the email by SpamAssassin based on it rated the email to be possibly spam. Here are some of the headers that will give you information on how SpamAssassin judged the email: X-Spam-Score When you become familiar with the sections of the header, it becomes much easier to identify the portions that deal with SpamAssassin. Reading the X-Spam scores in the header of an email can definitely appear to be difficult. This verifies that the email is coming from the listed sender and allows abusive messages to be tracked with more ease. The Domain Key is an e-mail authentication system that allows for incoming mail to be checked against the server it was sent from to verify that the mail has not been modified. Frequently Asked Questions - SpamAssassinĪnother option to help in keeping your email from being labeled as spam is to use Domain Keys.Other great sources of information that would help to keep your email from being labeled as spam or generating a false positive result includes: Email contains a valid, physical address.Email is not sent after a recipient had sent notice that they wish to no longer receive the email.Email includes a clear notice that there is an option to opt out. Include a type of return email address that allows recipient to opt-out.Provide indication that email is an advertisement.False or misleading information in the subject line.False or misleading information in the header.Here are some common issues as defined by the CAN-SPAM Act of 2003 (section 5): The main thing is to make sure that your email does not fall into the definition of being spam. (for older versions of SpamAssassin, see older versions of SpamAssassin) How to Lower Your SpamAssassin Score SpamAssassin Tests Performed (version3.3.x) If you want to see the tests being run using the latest version of SpamAssasin, go to: The number and complexity of the tests are so numerous that it can be difficult to understand why an email was given a particular score. SpamAssassin score settings can be changed within the cPanel. A user can also change the settings that SpamAssassin uses in order to determine if an email will score as a spam or not. SpamAssassin checks many variables within an email in order to determine the spam score. The following articles provides information on the tests that are used, methods to lower your spam score, ways to avoid being falsely identified as spam, and breaking down the Spam scores. Higher scores indicate that the email is spam, while lower scores will indicate that the email is legitimate. A spam score is provided that can be used to determine levels of how much an email may resemble spam. Hundreds of tests are performed by SpamAssassin on every email in order to determine if it is spam or not. Update channel based on the automated QA process, and there is aĬontinuous trickle of new rules, rule changes, and rule deletions comingįrom the development team that get integrated (or not) via RuleQA.SpamAssassin is an application that tests email messages in order to see if they are defined as spam or not. However, my view is that this was the right decision because Rule descriptions on the wiki, so there may be a more correctĮxplanation out there in the heads of the people who were on the PMC at I don't have a definitive reference for the decision to stop maintaining Not migrated, as they were largely outdated where they were not Old rules descriptions (which had not been maintained since v3.3) were The wiki was mostly migrated to the ASF Confluence instance recently and Here is what SpamAssassin support answered me : The code shouldn't change much, but the line numbers likely will, especially within the. (Line numbers are from the current trunk repository, not a release. This means the ratio of the text MIME part's length to the HTML MIME part's length must be equal to or above zero and also under 1%. My ($self, $pms, undef, $min, $max) = unless exists $pms-> = ($text / $html) In lib/Mail/SpamAssassin/Plugin/MIMEEval.pm, you'll find: # … line 214 This is an eval rule, so you'll have to look at the perl code to see exactly what it's doing. # … rules/50_scores.cf line 616 (also quite likely to change) The current definition for that rule (discounting translations) from rules/20_body_tests.cf is: # … line 139 (quite likely to change)īody MIME_HTML_MOSTLY eval:check_mime_multipart_ratio('0.00','0.01')ĭescribe MIME_HTML_MOSTLY Multipart message mostly text/html MIME You can get automated efficacy data for MIME_HTML_MOSTLY from the SpamAssassin Rule QA system, but not the definition. Not all rules are documented on the SpamAssassin wiki - there's way too many of them to do that.
0 Comments
Leave a Reply. |