Spamassassin works but not with MS

[Mariano Absatz]

IIRC, SA 2.42's AWL is broken... upgrade SpamAssassin to 2.43. 2.43's main 
reason to be was to fix this bug.

More info on SA's page & mailing list.

El 18 Oct 2002 a las 8:25, Stephen Lee escribió:

> On Fri, 2002-10-18 at 02:33, Peter Peters wrote:
> > On Thu, 17 Oct 2002 22:47:10 -0700, you wrote:
> >
> > >I'm running MS 3.24-1 with SA 2.42 on Trustix 1.5/Perl 5.6.1. It appears
> > >that SA correctly identifies spam but through some interaction with MS,
> > >the message is not tagged as spam. Here's an example header:
> > >
> > >X-Spam-Flag: YES
> > >X-Spam-Level: Spam-Level SSSSSSSSSSS
> > >X-Spam-Checker-Version: SpamAssassin 2.42 (1.115.2.14-2002-10-04-exp)
> > >X-Spam-Report: 11.40 hits, 5 required;
> >
> > I didn't find any indication your SA uses whitelisting.
> 
> But the auto-whitelist file is getting larger and the file timestamp is
> current. Doesn't that mean SA is using whitelisting?
> 
> >
> > >X-MailScanner: Found to be clean
> > >X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.5, required 5,
> > >     AWL)
> >
> > The MS version of SA uses AWL.
> 
> Yes, I intended to use the AWL feature. The SA docs say that auto white
> listing is turned on with the "-a" switch. I presume that turning on AWL
> somehow passes that request onto SA?
> 
> Thanks,
> Stephen


--
Mariano Absatz
El Baby
----------------------------------------------------------
Violence is the last refuge of the incompetent.
         -- Isaac Asimov