SpamAssassin marks ALL mail as spam

[Julian Field]

If you kill the mailscanner process ("ps -fe | grep mailscan" then kill it)
then start it up with check_mailscanner, what does it print to the console?
Anything about a lack of configuration text? I got this when I upgraded my
perl but didn't re-install SpamAssassin afterwards. The perl
previous-version-searching doesn't work with SpamAssassin.

At 12:37 06/01/2002, you wrote:
> > -----Original Message-----
> > From: MailScanner mailing list On Behalf Of Julian Field
> > Sent: Sunday, January 06, 2002 1:05 PM
> > To: MAILSCANNER at JISCMAIL.AC.UK
> > Subject: Re: SpamAssassin marks ALL mail as spam
> >
> > As SpamAssassin is saying it is spam, so is my code. I suspect
> > you have hit
> > a SpamAssassin bug (I've seen some strange behaviour sometimes too). I
> > suggest you contact the SpamAssassin guys for help.
>
>I think I hit a very strange situation. When I turn of SA in MailScanner and
>put the SA recipe in my .procmailrc, the mail checks out ok, with both the
>MailScanner and SA headers:
>
>X-Mailscanner: Found to be clean
>X-Spam-Status: No, hits=0 required=5 tests=
>
>So it's not really SA that marks the mail as spam when I do the test
>separate from the MailScanner proces.
>With these results, I don't have anything to 'slap' the SA developers
>with...
>
>I'll try to think of some more things I can test. I will post any results
>here.
>
>Thanks for your help.

--
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