Hello George, Tuesday, February 15, 2005, 7:29:07 PM, you wrote:
GG> On Sat, Feb 12, 2005 at 02:26:02PM -0800, Robert Menschel wrote: >>Just a quick note that SARE's header rules files have been updated. >>Information concerning these rules files can be found at >>http://www.rulesemporium.com/rules.htm#header GG> BTW - know anything about SARE_MSGID_IP and SARE_TOCC_NONE from GG> 70_sare_header.cf? Yep. 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. 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 Does anyone have any better ideas how to handle this type of situation, and/or any suggests as the best/fastest/efficientest false noop rule to use? Bob Menschel
