Changes between Version 8 and Version 9 of LoadRulesConfig


Ignore:
Timestamp:
Sep 7, 2007, 7:15:15 AM (11 years ago)
Author:
dmorton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LoadRulesConfig

    v8 v9  
    25252. The scores that appear in the quarantine/cache lists have been rounded to one decimal place, but in fact the scores are calculated internally to three decimal places.  What you see as 1.2 on the quarantine/cache list may in fact have been something like 1.175 or 1.228.  If you add up the rules in the Mail Viewer's report and you find a total that rounds up or down to the value shown on the quarantine/cache list, there's no reason for concern.
    2626
    27 3. In the case of the AWL rule (i.e. SpamAssassin's [http://wiki.apache.org/spamassassin/AutoWhitelist Auto-Whitelist] feature), the score will always show up as 1.000 in the Mail Viewer.  That's because the score value of the AWL rule is dynamic--SpamAssassin assigns a different score each time the AWL rule is triggered, so there's no way for Maia to know what that value is for any given e-mail.  The AWL rule is special--it's supposed to be scored according to the "reputation" of the sender, so that if the sender has a history of sending you spam, the AWL rule score should be higher, and if he has a history of sending you non-spam the score should be lower.  In the example above, for instance, we could guess that the AWL rule actually scored somewhere around -0.603 (1.2 - 1.803), if all the rules and scores in Maia's database are current.
    2827
    29 4. Similarly, if you are using [wiki:OCRmain OCR] to scan text, the score for that rule will always show up as 1.000 in the Mail Viewer, as it too, is dynamic.  If a rule triggers both AWL and an OCR rule, then it is no longer possible to determine the actual score.
     283. Some rules provided by third parties such as the SARE rules are missing descriptions and don't get loaded into Maia's database. See #357.
    3029
    31 === Future work ===
     30'''UDPATE: '''The following items are no longer valid in version 1.0.2, as we can now calculate this score
    3231
    33 There is upcoming support to log the actual score assigned, thanks to some new functionality within SpamAssassin. When this is completed, then the dynamic scores will not cause any more questions.
     324.  In the case of the AWL rule (i.e. SpamAssassin's [http://wiki.apache.org/spamassassin/AutoWhitelist Auto-Whitelist] feature), the score will always show up as 1.000 in the Mail Viewer.  That's because the score value of the AWL rule is dynamic--SpamAssassin assigns a different score each time the AWL rule is triggered, so there's no way for Maia to know what that value is for any given e-mail.  The AWL rule is special--it's supposed to be scored according to the "reputation" of the sender, so that if the sender has a history of sending you spam, the AWL rule score should be higher, and if he has a history of sending you non-spam the score should be lower.  In the example above, for instance, we could guess that the AWL rule actually scored somewhere around -0.603 (1.2 - 1.803), if all the rules and scores in Maia's database are current.
    3433
     345. Similarly, if you are using [wiki:OCRmain OCR] to scan text, the score for that rule will always show up as 1.000 in the Mail Viewer, as it too, is dynamic.  If a rule triggers both AWL and an OCR rule, then it is no longer possible to determine the actual score.
     35
     36
     37 
    3538----
    3639