On Monday, October 25, 2004, 1:58:49 PM, Mark wrote: MES> I just noticed a huge increase in SPAM today and noticed that none of them MES> were being trapped by the Message Sniffer rules. MES> I did an upgrade to the new test version the other day and am guessing MES> that's what's going on.
MES> Here's what I'm seeing in the logs of all 3 of our servers. MES> Build v2-3.0i9 MES> [CODE] 20041025173043 -INITIALIZING- 0 0 ERROR_RULE_AUTH MES> 73 0 0 0 0 When this happens suddenly it is almost always a corrupted rulebase file. Be sure that your update script is using the latest snf2check.exe utility to validate your rulebase file before putting it into service. When this happens after an upgrade other change in the sniffer program it is most likely a typ-o in the license ID when renaming (branding) the program. Hope this helps, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
