You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Daniel Quinlan <qu...@pathname.com> on 2005/04/04 09:35:34 UTC
closing in on 3.1
We only have about 40 bugs remaining, a large number of which can be
moved forward to 3.2.0, 3.1.1, or "Future". I whacked about a dozen
bugs over the weekend. ;-)
A few open issues and questions:
* History plugin: I think we can wait to add this, right?
* SURBL changes: we should definitely finish the SURBL-related bugs
related to efficacy (except the mix-up problem, unfortunately).
* spamd instability: the new spamd code does not seem as reliable as
the old code
Daniel
--
Daniel Quinlan
http://www.pathname.com/~quinlan/
Re: closing in on 3.1
Posted by Michael Parker <pa...@pobox.com>.
On Mon, Apr 04, 2005 at 12:35:34AM -0700, Daniel Quinlan wrote:
> A few open issues and questions:
>
> * History plugin: I think we can wait to add this, right?
I'd really like to get this in, if we can. All of the AWL stuff has
been marked as deprecated, so if we don't get it in we'll probably
want to change that.
Michael
Re: closing in on 3.1
Posted by Justin Mason <jm...@dogma.slashnull.org>.
On Mon, Apr 04, 2005 at 12:35:34AM -0700, Daniel Quinlan wrote:
> We only have about 40 bugs remaining, a large number of which can be
> moved forward to 3.2.0, 3.1.1, or "Future". I whacked about a dozen
> bugs over the weekend. ;-)
>
> A few open issues and questions:
>
> * History plugin: I think we can wait to add this, right?
>
> * SURBL changes: we should definitely finish the SURBL-related bugs
> related to efficacy (except the mix-up problem, unfortunately).
>
> * spamd instability: the new spamd code does not seem as reliable as
> the old code
BTW, I'm out of action until next weekend at least, due to a
sudden bereavement. :(
Getting access to email has been pretty tricky since I'm in rural
Ireland at the mo -- as such I probably won't be much help until post-
next weekend.
However I'd like to get someone to look at those spamd issues; IMO,
the new preforking system is a whole lot more stable and reliable
than 3.0.0's, due to the greatly improved memory profile it gives
us, and I'd be seriously negative about releasing 3.1.0 without
it.
--j.