![]() 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. 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 The current definition for that rule (discounting translations) from rules/20bodytests. You can get automated efficacy data for MIMEHTMLMOSTLY from the SpamAssassin Rule QA system, but not the definition. Not migrated, as they were largely outdated where they were not 2 Answers Sorted by: 1 Not all rules are documented on the SpamAssassin wiki theres way too many of them to do that. ![]() 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 If you find that SpamAssassin is marking messages as Spam when it should not be, or that SpamAssassin is not marking messages as spam when it should. This is an eval rule, so you'll have to look at the perl code to see exactly what it's doing. It performs the evaluation of the message based on preconfigured rules that tell it what to look for, and what score to apply to the message based on the results of the tests defined in the rule. # … 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. |