SpamAssassin or MailScanner problem?
darian at BEPINC.COM
Tue May 21 06:51:04 IST 2002
I should have said that it came from outside our network, from a host not
listed in the whitelist. If it happens again I'll let you know.
----- Original Message -----
From: "Julian Field" <jkf at ECS.SOTON.AC.UK>
To: <MAILSCANNER at JISCMAIL.AC.UK>
Sent: Monday, May 20, 2002 6:37 PM
Subject: Re: SpamAssassin or MailScanner problem?
> At 22:13 20/05/2002, you wrote:
> >Do you think the following was caused by Mailscanner or SpamAssassin?
> Most likely cause is the mail coming from an address or a network which is
> listed in "Accept Spam From" or spam.whitelist.conf.
> If you switch off "Always Include SpamAssassin Header = no" then the
> X-MailScanner-SpamCheck header should disappear altogether on this
> >X-MailScanner-SpamCheck: not spam, SpamAssassin (score=15.8, required 5,
> > MSG_ID_ADDED_BY_MTA_2, WORK_AT_HOME, CLICK_BELOW, EXCUSE_14,
> > EXCUSE_16, UNSUB_PAGE, SUPERLONG_LINE, CLICK_HERE_LINK,
> > DIFFERENT_REPLY_TO, RCVD_IN_OSIRUSOFT_COM, X_OSIRU_SPAM_SRC)
> >Clearly it made the minimum hit requirement, but was marked as not spam.
> Julian Field Teaching Systems Manager
> jkf at ecs.soton.ac.uk Dept. of Electronics & Computer Science
> Tel. 023 8059 2817 University of Southampton
> Southampton SO17 1BJ
More information about the MailScanner