https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6336
--- Comment #7 from [email protected] 2010-02-18 19:58:06 UTC --- (In reply to comment #6) > Manman, how often do you update the SOUGHT channel? How often do you update > stock rules? I am updating both rule sets on a monthly base. First I run sa-update for the stock rules only, then for the SOUGHT channel. Essentially, what caught my attention was that SA 3.3 rolled out and my 3.2 installation got upgraded, so I paid extra attention to sa-update, sa-compile etc. > When was the last time respectively? Right after adding my last comment above, but recompiling, reproduced the error. > Please *keep* a copy of the SOUGHT rules as on your box right now -- assuming > those are still the ones that triggered the issue. I'll happily keep this rule set for tests. Even upload them if asked. But please bear with me, since I am away from the installation and even SSH is disabled. Will be back on Monday, so I can perform any tests needed at that time. > Not terribly unexpected, since the SOUGHT FRAUD rule-set is disabled (score > set > to 0) in stock 50_scores.cf by default, which should overrule the channel. But > nice confirmation. :) :) > > 2) Then I remark'ed the "include sought_rules_yerp_org/20_sought.cf" line, > > leaving "include sought_rules_yerp_org/20_sought_fraud.cf" enabled. Result: > > No > > error! > > Effectively, both are disabled. > > Since the SOUGHT rule-set is part of stock SA since 3.3, a good guess would be > that you manually updated the SOUGHT channel after the last stock sa-update. Exactly, that's the order I'm always following. > And the issue is somehow related to the difference in __SEEK sub-rules or > meta'ing them. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
