You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@issues.apache.org on 2011/03/04 21:29:44 UTC
[Bug 6390] KHOP_SC_TOP200 scores don't take into account scbl score.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6390
Adam Katz <an...@khopis.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #7 from Adam Katz <an...@khopis.com> 2011-03-04 15:29:42 EST ---
(In reply to comment #6)
> Hey, I just thought of a way to handle this. Would it be possible to disable
> these scores entirely if network rules are enabled, and only enable if network
> is disabled? That would eliminate the overlap and make these rules useful.
KHOP_SC_TOP200 and KHOP_SPAMHAUS_DROP* use this to zero their score on
net+DNSEval runs. I believe the overlap from the other rules is beneficial.
As noted in comment #5, this overlap is intentional and is scored very low on
net runs. When run without net support, it is scored higher. When using the
net rules but DNSEval is disabled, it is also scored higher.
I have adjusted the channel's scores given the current performance from
http://ruleqa.spamassassin.org/20110226-r1074804-n?srcpath=khop_sc_. I also
lessened the weight of some of the rules. Spamhaus DROP actually earned more
weight due to its surprisingly low average spam scores (it had been zeroed).
score KHOP_SC_CIDR8 0.3 0.1 0.3 0.1
score KHOP_SC_TOP_CIDR8 0.2 0 0.2 0
score KHOP_SC_CIDR16 1.0 0.2 1.0 0.2
score KHOP_SC_TOP_CIDR16 2.0 0.3 2.0 0.4
score KHOP_SC_CIDR24 0.1 0 0.1 0
score KHOP_SC_TOP_CIDR24 2.7 0.5 2.7 0.5
score KHOP_SC_TOP200 4 0 4 0 # unnecessary if DNSBLs work
score KHOP_SPAMHAUS_DROP 1 0.2 1 0.2
score KHOP_SPAMHAUS_DROP_LE 2 0 2 0 # adds to KHOP_SPAMHAUS_DROP
score KHOP_PSBL_CIDR24 2 0.6 2 0.6
if (! plugin(Mail::SpamAssassin::Plugin::DNSEval) )
score KHOP_SC_CIDR8 (0) (0.2) (0) (0.2) # BRBL(98%)
score KHOP_SC_TOP_CIDR8 (0) (0.9) (0) (0.9) # BRBL(98%)
score KHOP_SC_CIDR16 (0) (1.5) (0) (1.5) # BRBL(99%), PBL(98%)
score KHOP_SC_TOP_CIDR16 (0) (1.7) (0) (1.7) # BRBL(99%), PBL(94%)
score KHOP_SC_CIDR24 (0) (0.9) (0) (0.9) # SC(99) BRBL(96) MSPIKE(96)
score KHOP_SC_TOP_CIDR24 (0) (2.5) (0) (2.5) # MSPIKE(99) SC(98) BRBL(97)
...
score KHOP_SC_TOP200 (0) (4.4) (0) (4.4) # SC(99) PSBL(99) ...
score KHOP_SPAMHAUS_DROP (0) (3) (0) (3) # SBL(93)
score KHOP_PSBL_CIDR24 (0) (1.5) (0) (1.5) # BRBL(98) XBL(95)
endif
I believe my response to this bug early last year was sufficient to close it.
These rules exist in SVN with regular updates purely for vetting purposes since
SpamAssassin currently lacks a mechanism to automatically publish timely
updates. Anybody looking to use these rules should subscribe to my sa-update
channel, which will pull daily+ updates to these CIDR regexps.
Any remaining issue with these rules accidentally getting published is a bug
related to the "nopublish" tflag rather than with this rule set.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.