It could be a unique batch we hadn't coded yet?

Is it possible the rulebase file hadn't been updated on your system?

Change rates were up a bit over the weekend preceded by a dip when we had our Primary DB outage Friday evening - perhaps these fell into that gap?

Reference:

http://www.sortmonster.com/MessageSniffer/Performance/ChangeRates.jsp


0        199
1        386
2        359
3        136
4        316

Hope this helps,
_M

At 02:29 PM 2/23/2004, you wrote:
I noticed today, after forwarding 22 spams I received over the weekend, that none of the spams got "caught" in sniffer. Usually I will have at least 50-75% caught because the rule base had been updated since I received the spam.

Any ideas?

Kevin


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

Reply via email to