I will be sticking with 2.64 for a while as well.

-----Original Message-----
From: Martin Hepworth [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 10, 2005 3:42 AM
Cc: users@spamassassin.apache.org
Subject: Re: maintaining the 2.6 branch

Another reason....

I've been doing some testing ove the last couple of days with 3.02 and 
found it's scores are way lower on all test emails than 2.64. (anywhere 
upto 33% lower in limited tests).

I've managed to get most of my 2.64 rules etc over (along with bayes), 
but I'm nervous about switching given the amount of spam 2.64 IS 
catching vs 3.02 MIGHT miss.

Alot of the defaults rules have reduced scores (esp when running 
bayes+net combination) and I don't want to give my users the spam.

I've seen several other people that complain/note this issue as well so 
it seems I'm not alone on this.

I shall be sticking to 2.64 for the forsee-able future as 3.02 gives me 
no advantage and quite a high likelihood of more spam dropping through 
the system!

--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300


Per Jessen wrote:
> Ron Johnson wrote:
> 
> 
>>>Per Jessen wrote:
>>>
>>>> Show of hands,
>>>>who's still on 2.64 with no exact plans to upgrade?
> 
> 
> Alright, so far I've seen 4-5, maybe 6 people saying they intend to
stick to
> 2.64 for the foreseeable future.  Is that really all? 
> I'm quite willing myself to put an effort in in maintaining 2.64, and
I'll
> probably be doing it on a personal level anyway, but to work to
produce actual
> releases for others, I think a bit more of an interest is needed. 
> 
> 
> 

**********************************************************************

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.

**********************************************************************


Reply via email to