https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6674
--- Comment #16 from Karsten Bräckelmann <[email protected]> 2011-10-27 00:49:55 UTC --- (In reply to comment #15) > ok. Let me explain something using example. > > While testing 419 emails SA accumulates score from rules like: > LOTTO_AGENT+MONEY_FRAUD_3+ADVANCE_FEE_3_NEW_MONEY+ADVANCE_FEE_4_NEW+... (many > more). And the cumulative score is usually above kill level. And this is > exactly what I expect from SA - to kill. The operative word here is "cumulative". Many rules, not a single one. Precisely what SA and a scoring system in general is about. > Therefore if I want the spam in polish emails to be killed - I have to set the > score like EICAR/GTUBE tests. I have only one bullet (rule) to kill and I want > this bullet to kill, not to wound. GTUBE has a score of 1000 -- for the one reason to counter *any* other rules. It is a *test-point*, not a rule for production to catch spam. Fortunately, you are wrong and did not set the score like for GTUBE. > If you want me to set SCORE=1 then my rules will be wasting CPU cycles because > cumulative score will be much less than $sa_tag2_level_deflt not to mention > $sa_kill_level_deflt (amavis variables) I don't think you understand why amavis even has more than one such level... And no one told you to set the scores to 1. We told you scores of 5 or even 10 definitely are bad. (Unless deliberately set by the admin.) Moreover, the most important point was the uridnsbl rules, and its requirement for a local rbldnsd. Especially regarding all your rather strict (read safe) body rules as mentioned in your original report comment 0, IMHO it likely is safe to use a score >1. Though 20 is not. > I have just comented out the scores and rbl.tld rules. And I believe I gave > enough explanation how the file should be used. Thanks! -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
