Re: [SAtalk] AWL problem ...

2002-10-22 Thread joe
On October 22, 2002 07:17 pm, Michael Moncur wrote: > > Hmm? I upgraded to 2.43 the day it was released and noticed all [snip] > It sounds like your particular situation isn't one where > autowhitelisting will do much good. My conclusion too. I use tmda to handle my 1-1 type correspondence

RE: [SAtalk] AWL problem ...

2002-10-22 Thread Michael Moncur
> Hmm? I upgraded to 2.43 the day it was released and noticed all my > spam email was being let through after about 2 weeks. I run spamd with > the -a (autowhitelist optio) on. I have since turned off the > auto-whitelist option and everything works fine since. Version 2.43 definitely fixed

Re: [SAtalk] AWL problem ...

2002-10-22 Thread Duncan Findlay
On Tue, Oct 22, 2002 at 06:58:31PM -0700, joe wrote: > On October 22, 2002 06:26 pm, Duncan Findlay wrote: > > On Wed, Oct 23, 2002 at 03:08:47AM +0200, Steffen Evers wrote: > > > But it does exactlly the opposite: AWL gives -5.0 points, so it is > > > no longer recognized as spam! > > > > > > Is t

Re: [SAtalk] AWL problem ...

2002-10-22 Thread joe
On October 22, 2002 06:26 pm, Duncan Findlay wrote: > On Wed, Oct 23, 2002 at 03:08:47AM +0200, Steffen Evers wrote: > > But it does exactlly the opposite: AWL gives -5.0 points, so it is > > no longer recognized as spam! > > > > Is this an intended behaviour? > > Yes... sort of. It WAS intended be

Re: [SAtalk] AWL problem ...

2002-10-22 Thread Duncan Findlay
On Wed, Oct 23, 2002 at 03:08:47AM +0200, Steffen Evers wrote: > But it does exactlly the opposite: AWL gives -5.0 points, so it is no > longer recognized as spam! > > Is this an intended behaviour? Yes... sort of. It WAS intended behaviour at the time. But we are wiser now, and that change was r

[SAtalk] AWL problem ...

2002-10-22 Thread Steffen Evers
Hi! Using 2.42 (Debian testing package on woody) AWL seems not to work the way it supposed to be: I have removed the AWL files in order to reset the AWL data. Than I have piped through the same spam message (9.50 hits, 5 required) several times with 'spamassassin -a < spam-mail > spam-mail1.resul