Hi, On Tue, Feb 15, 2005 at 09:03:14PM -0800, Robert Menschel wrote:
>GG> Lint output: warning: score set for non-existent rule SARE_MSGID_IP >GG> warning: score set for non-existent rule SARE_TOCC_NONE >GG> lint: 2 issues detected. please rerun with debug enabled for more >information. > >GG> I had custom scores for them but they seem gone now... > >They've been archived -- moved to the 70_sare_header_arc.cf file. > >In our latest mass-check runs, SARE_MSGID_IP hit over 600 ham, and >SARE_TOCC_NONE hit over 200 ham. Neither rule hit spam/ham at a 90% >ratio. I archive rules when they hit so much ham and too few spam to >make it worth while. okay next time I'll look at raising my rule count rather than raising scores to block spam. >Conflicting requirements: > >1) We need to be able to archive rules that no longer benefit the >filters. > >2) We don't want to break systems that have custom scores for these >rules and use RDJ to update them. > >An "easy" solution would be to replace the archived rules with a quick >"no-op" rule which is always false, maybe something like >> meta SARE_MSGID_IP HTML_MESSAGE && !HTML_MESSAGE I've not looked at what meta does, but I'll add this comment: My local.cf file is parsed after all other cf files, so my first thought is it's going to override anything set before it (as intended). Rather than squelching custom site rules, I think it more appropriate to verbosely report why rules become obsoleted (not necessarily in the new ruleset). Maybe a changes file for each cf file is appropriate? You cannot guarantee what or how anything is done in a local config, let the admin who created it address the changes too. // George -- George Georgalis, systems architect, administrator Linux BSD IXOYE http://galis.org/george/ cell:646-331-2027 mailto:[EMAIL PROTECTED]
