On Tue, Jun 22, 2004 at 09:21:03AM -0700, Kelson Vibber wrote: > Well, usually. I've seen a surprising number of messages that have - for > whatever reason - hit RAZOR2_CF_RANGE_11_50 or RAZOR2_CF_RANGE_51_100 but > not RAZOR2_CHECK. > > I've noticed this before, but it never seemed like a major problem. It > occurs to me now I probably ought to file a bug report with SA.
It's not likely to be a bug. RAZOR2_CHECK is the result of "does razor consider this spam", with the min_cf and logic_method settings having an impact. ie: it gives you the same answer as running "razor-check". RAZOR2_CHECK_CF_RANGE_* is simply looking at the message parts and the associated cf values. Whichever is the highest wins. Depending on your min_cf and/or logic_method setting, I wouldn't be surprised to see what you're seeing. -- Randomly Generated Tagline: "Chase the dream, not the competition." - Unknown
pgpXcqg6IWmL6.pgp
Description: PGP signature
