https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6510

--- Comment #7 from Daryl C. W. O'Shea <[email protected]> 2010-11-06 
18:14:33 UTC ---
(In reply to comment #0)
> The nightly masscheck which generates the scores for production rules updates
> has recently started generating 0 scores for rules which have dependencies
> (leading to warnings).
> Examples:
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6504
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6509

OK, I've confirmed that this doesn't prevent sa-update from working, or from SA
from working.  In fact, I would say this (or at least the possibility for it)
is by design.  The GA is deciding (apparently) that rules aren't worth having
(due to overlaps/whatever that makes the rules have no real bearing on the
outcome across the entire corpus) even though they are technically good enough
to be promoted.

Historically, before sa-update, this wasn't an issue since we just wouldn't
ship those rules or rules that depended on them.  Updates via sa-update open up
the possibility of problems, it seems (although I'm not sure why yet, maybe
something is broken).

(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > (In reply to comment #1)
> > > > +  sed -e 's/0\.000/0.001/g' < trunk-rulesrc-scores/72_scores.cf >
> > > > trunk/rules/72_scores.cf
> > > 
> > > Yeah, that won't work well.  It'll enable net rules in non-net scoresets.
> > Would that cause problems given the presence of "tflags net" on net rules?
> > Surely SA does not rely on the score being zero to disable net rules when 
> > run
> > in local mode...
> Good point, investigating now.

Looks like the 'sed' is actually fine as long as net rules have their tflags
net (which, if they don't is a different problem).

I'm looking at getting the GA to not 0 them, or if it does, make sure there are
no dependencies.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to