[Spambayes] SpamBayes Outlook Fails to Move Mail Identified as Spam

[Brown, Jim]

First, let me say that SpamBayes seems nearly perfect. I can't get over
the accuracy with which it identifies spam.

 

I'm having a problem with the SpamBayes Outlook client v0.81 that I
can't figure out. Frequently, it fails to _move_ spam if the spam is the
most recent email in the inbox at the time Outlook is started. Please
note that SpamBayes does process the message and identify it as spam, it
simply fails to move the message from the Inbox for some reason.

 

This is a very specific failure. If Outlook is running when the spam
arrives, it is always moved. If the spam isn't the most recent piece of
mail in the inbox, it is always moved. The problem only occurs when
Outlook is being opened and the most recent piece of mail in the inbox
is spam.

 

I have verified that the emails in question should have been moved by
looking at the log. The log shows that the message was processed and
identified as spam. Looking at the spam clues for the message, the
message in question almost always has a 99%+ spam rating.

 

I've enabled background filtering with a 10 s start delay and a 0.5 s
processing delay.

 

The email account being filtered resides on an Exchange server. All but
one of the rules I'm using are server side rules, and cannot interfere
with  SpamBayes when Outlook is started; they've fired on the message
well before Outlook knows the message exists.

 

I do have _one_ rule that is client side. That rule is "Apply this rule
after the message arrives: notify me using 'You have new messages.'
except with 'yahoo.com' or 'aol.com' or 'hotmail.com' or 'msn.com' or
'pslgroup.com' or '.ca' or '.us' or '.de' or '.cc' or '.fr' or '.nl' in
the sender's address."

 

Any ideas?

 

Thanks.

 

---Jim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/spambayes/attachments/20040125/b88c1e86/attachment.html