Dito here - already reported it as a False Positive:
s u='20090908183815' m='D:\IMail\spool\proc\work\Dd948c4c42c68.smd'
s='54' r='2654821'
m s='54' r='2654821' i='1905' e='1952' f='m'/
p s='0' t='15' l='4270' d='38'/
g o='0'
The scores over here for the messages that trigger on rule 2654821
today:
spam that hit the rule: 4
... and were porn: 0
ham that was held by my weight system: 5
ham that was allowed by my weight system: 3
subsequent panic log lines: 139
Thanks for the heads up, Darin.
I was able to re-queue
We had a lot... 534 hits between 3:26 and 4:41pm ET, which is when we added the
rule panic. It appears the rule was added in a rulebase that was automatically
updated at 3:26pm ET.
Pete? Status?
Darin.
- Original Message -
From: Colbeck, Andrew
To: Message Sniffer Community
Darin Cox wrote:
We had a lot... 534 hits between 3:26 and 4:41pm ET, which is when we
added the rule panic. It appears the rule was added in a rulebase
that was automatically updated at 3:26pm ET.
Pete? Status?
Here is a preliminary report on the bad rule:
The rule was coded in error --
