No rules triggered at all for that piece of spam. I'll check the MailScanner group to see if they have any experience with this issue.
Thanks, Donald -----Original Message----- From: SM [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 25, 2007 4:18 PM To: Dawson, Donald; users@spamassassin.apache.org Subject: RE: score-0 problem: SpamAssassin (not cached, score=0, required 5, autolearn=) At 13:41 25-07-2007, [EMAIL PROTECTED] wrote: >sm - We have the same configuration on all our MX servers. Here are >all of the headers for an example spam email: The SpamAssassin scoring should be the same then. >Note, it may be system/config-related - the /dev/shm directory is >used by spamassassin, but it is not getting cleaned out consistently. It might be Mailscanner leaving these files there. >Received: from dsl85-102-24083.ttnet.net.tr >(dsl85-102-24083.ttnet.net.tr [85.102.94.19] (may be forged)) This should trigger a rule at least. Can you verify your logs to see which tests were hit for that particular email? Regards, -sm
