Getting Past SpamAssassin

[Peter Ong]

Martin,

Brilliant! I was just going to do that.

p


----- Original Message -----

> From: "Martin Hepworth" <maxsec at gmail.com>
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Sent: Monday, October 4, 2010 11:41:39 AM
> Subject: Re: Getting Past SpamAssassin
> 
> HI
> 
> 
> try putting in the additional headers for spamassassin in the mails,
> then you'll know what spamassassin actually said about the email as as
> far as MailScanner was concerned. Make the following changes to the
> settings in MailScanner.conf:
> 
> 
> 
> 
> Spam Score Number Format = %5.2f
> 
> Detailed Spam Report = yes
> 
> Include Scores In SpamAssassin Report = yes
> 
> Always Include SpamAssassin Report = yes
> 
> Spam Score Number Format = %5.2f
> 
> 
> 
> 
> 
> 
> 
> Also the "X-Spam-Status:No" headers isn't anything do with MailScanner
> unless you're trusting this header which is perhaps a bad thing.
> 
> 
> --
> Martin Hepworth
> Oxford, UK
> 
> 
> 
> On 4 October 2010 18:03, Peter Ong < peter.ong at hypermediasystems.com >
> wrote:
> 
> 
> Dear MailScanner Gods,
> 
> MailScanner: 4.79.11
> spamassassin-3.2.5-1.el5
> 
> 
> Please hear my prayers. Here's the weirdest thing...
> 
> Under what circumstance could an email come through without passing
> through SpamAssassin? My configuration is as close to vanilla as
> possible. There have been no esoteric changes.
> 
> A piece of spam came through this morning. It does not appear to have
> been scanned by SpamAssassin. Just to test, I scanned it as root. It
> scored a whopping 25.5 points. Then, I thought, maybe MailScanner runs
> spamassassin as postfix. So I scanned the same email as postfix, and
> spamassassin gave it a 32 points. Either way this should've been
> obliterated, but it shows:
> 
> X-Spam-Status: No
> X-DTi-MailScanner-From: myemail at myserver.com
> X-DTi-MailScanner: Found to be clean
> X-DTi-MailScanner-ID: 7BB9B1908B1.AB3F2
> X-DTi-MailScanner-Information: Please contact the ISP for more
> information
> X-Greylist: delayed 303 seconds by postgrey-1.32 at mygateway.tld;
> Mon, 04 Oct 2010 06:22:01 UTC
> Received: from 240.34.177.94.netvisiontelecom.ro (unknown
> [94.177.34.240])
> by myserver.com (Postfix) with ESMTP id 7BB9B1908B1
> for < myemail at myserver.com >; Mon, 4 Oct 2010 06:22:01 +0000 (UTC)
> 
> At first, I thought this was the reason:
> Max SpamAssassin Size = 200k
> 
> But the message was only 4K. Therefore, it is something else.
> 
> Running spamassassin as postfix, I got these:
> [26774] warn: config: cannot write to
> /var/spool/postfix/.spamassassin/user_prefs: No such file or directory
> [26774] warn: config: failed to create default user preference file
> /var/spool/postfix/.spamassassin/user_prefs
> 
> Could these have something to do with my problem? Under what
> circumstance could an email come through without passing through
> SpamAssassin?
> 
> Thanks.
> 
> p
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
> 
> Before posting, read http://wiki.mailscanner.info/posting
> 
> Support MailScanner development - buy the book off the website!
> 
> 
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
> 
> Before posting, read http://wiki.mailscanner.info/posting
> 
> Support MailScanner development - buy the book off the website!