Mailscanner not catching SPAM but manual run via SA catches it
danc at bluestarshows.com
Mon Nov 13 18:01:04 GMT 2006
I dont understand whats going on.
Here's a header that was marked as spam.
X-Bluestar-MScan-SpamCheck: spam, SpamAssassin (not cached, score=9.897,
required 6, BAYES_99 3.50, FORGED_RCVD_HELO 0.14, HTML_40_50 0.50,
HTML_IMAGE_ONLY_12 1.87, HTML_MESSAGE 0.00, MIME_HTML_ONLY 0.00,
Doesn't this tell me that mailscanner is using Spamassassin?
If it is, why when I manually run spam that doesn't get marked through
spamassassin I get an output like this?
Content analysis details: (9.0 points, 5.0 required)
pts rule name description
---- ---------------------- ------------------------------------------------
0.1 FORGED_RCVD_HELO Received: contains a forged HELO
1.0 BAYES_60 BODY: Bayesian spam probability is 60 to 80%
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP
[184.108.40.206 listed in dnsbl.sorbs.net]
3.9 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[220.127.116.11 listed in sbl-xbl.spamhaus.org]
1.9 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[18.104.22.168 listed in combined.njabl.org]
The header shows:
Please someone tell me how to stop this crap from getting through?
----- Original Message -----
From: "Dan Carl" <danc at bluestarshows.com>
To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
Sent: Monday, November 13, 2006 9:38 AM
Subject: Re: Mailscanner not catching SPAM but manual run via SA catches it
> ----- Original Message -----
> From: "Glenn Steen" <glenn.steen at gmail.com>
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Sent: Saturday, November 11, 2006 2:26 AM
> Subject: Re: Mailscanner not catching SPAM but manual run via SA catches
> > On 10/11/06, Dan Carl <danc at bluestarshows.com> wrote:
> > >
> > (snip)
> > > > If you've upgraded SA, did you run the sa-update after that?
> > > I ran sa-update
> > Good.
> > > > Does it look like MailScanners instance of SA is finding/using the
> > > > /var/lib/spamassassin/<version>...?
> > > >
> > > sorry not sure how to verify this.
> > Well, the output you just showed (snipped by me:) is an indicator. You
> > could add a rule that would be sure to fire into that directory,
> > restart MS and run a testmessage through... and look at what rules
> > fired...
> Can you please explain how to do this?
> Do these need to be set?
> SpamAssassin Install Prefix =
> SpamAssassin Local Rules Dir =
> SpamAssassin Default Rules Dir =
> The conf says that if spamassassin is installed in its defualt
> location(which mine is)
> they don't need to be set.. Correct?
> > -- Glenn
> > email: glenn < dot > steen < at > gmail < dot > com
> > work: glenn < dot > steen < at > ap1 < dot > se
> > --
> > 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
> Before posting, read http://wiki.mailscanner.info/posting
> Support MailScanner development - buy the book off the website!
More information about the MailScanner