if razor matches, the RAZOR2_CHECK rule will fire.
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.
Our maillog for the last few days has about 2250 hits for RAZOR2, of which about 450 don't include RAZOR2_CHECK but do hit one of the others. (SA 2.63, razor-agents 2.40.)
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.
Kelson Vibber
SpeedGate Communications <www.speed.net>
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Razor-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/razor-users
