You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Timothy Richter <tr...@execinc.com> on 2005/02/07 18:08:38 UTC

Spamassassin 3.0.2

Good Morning,

Recently, we upgraded from Spamassassin 2.61 to 3.0.2. Guinevere is on version 2.17. Our threshold had been 4.9, and we typically blocked 60% of our mail as being spam.

Since the upgrade, we are blocking less than have of our email as being spam. I have taught the Bayesian filter another 600 spam and 600 ham messages, adjusted the Bayesian filter scores, and dropped the threshold down to 2.9. We are still catching much less spam then with the older version.

Does anyone have advice on improving Spamassassin?


Spamassassin is installed on Server 2003 and is being invoked by Guinevere 2.17.


Thank you,

Tim


Re: Spamassassin 3.0.2

Posted by John Andersen <js...@pen.homeip.net>.
On Tuesday 08 February 2005 07:58 pm, John Andersen wrote:
> On Monday 07 February 2005 08:08 am, Timothy Richter wrote:
> > Good Morning,
> >
> > Recently, we upgraded from Spamassassin 2.61 to 3.0.2. Guinevere is on
> > version 2.17. Our threshold had been 4.9, and we typically blocked 60% of
> > our mail as being spam.
> >
> > Since the upgrade, we are blocking less than have of our email as being
> > spam. I have taught the Bayesian filter another 600 spam and 600 ham
> > messages, adjusted the Bayesian filter scores, and dropped the threshold
> > down to 2.9. We are still catching much less spam then with the older
> > version.
> >
> > Does anyone have advice on improving Spamassassin?
> >
> >
> > Spamassassin is installed on Server 2003 and is being invoked by
> > Guinevere 2.17.
>
> V3 relies heavily on DNS tests (perhaps too heavily) if you tell
> it that they are installed.
>
> If they really don't work you're worse off than
> you would be by just not installing them.
>
> I've found that all the st0ck pushers are really beating
> SA 3.0.2.

And note that this message did not hit ANY St0ck scam tests...!!??

-- 
_____________________________________
John Andersen

Re: Spamassassin 3.0.2

Posted by John Andersen <js...@pen.homeip.net>.
On Monday 07 February 2005 08:08 am, Timothy Richter wrote:
> Good Morning,
>
> Recently, we upgraded from Spamassassin 2.61 to 3.0.2. Guinevere is on
> version 2.17. Our threshold had been 4.9, and we typically blocked 60% of
> our mail as being spam.
>
> Since the upgrade, we are blocking less than have of our email as being
> spam. I have taught the Bayesian filter another 600 spam and 600 ham
> messages, adjusted the Bayesian filter scores, and dropped the threshold
> down to 2.9. We are still catching much less spam then with the older
> version.
>
> Does anyone have advice on improving Spamassassin?
>
>
> Spamassassin is installed on Server 2003 and is being invoked by Guinevere
> 2.17.

V3 relies heavily on DNS tests (perhaps too heavily) if you tell
it that they are installed.  

If they really don't work you're worse off than
you would be by just not installing them.

I've found that all the st0ck pushers are really beating
SA 3.0.2.  

-- 
_____________________________________
John Andersen

RE: Spamassassin 3.0.2

Posted by Bret Miller <br...@wcg.org>.
> Recently, we upgraded from Spamassassin 2.61 to 3.0.2. 
> Guinevere is on version 2.17. Our threshold had been 4.9, and 
> we typically blocked 60% of our mail as being spam.
> 
> Since the upgrade, we are blocking less than have of our 
> email as being spam. I have taught the Bayesian filter 
> another 600 spam and 600 ham messages, adjusted the Bayesian 
> filter scores, and dropped the threshold down to 2.9. We are 
> still catching much less spam then with the older version.
> 
> Does anyone have advice on improving Spamassassin?
> 
> 
> Spamassassin is installed on Server 2003 and is being invoked 
> by Guinevere 2.17.

I had to lower our threshhold to 4.0 when I moved to SA 3.0. It's lower than
I'd like, but messages are scoring too low otherwise. I just haven't had the
time to tweak enough rules to higher scores to get the level back up to 5.

Bret