Re: spamassassin 3.1.8

2007-02-14 Thread Steve Langasek
On Thu, Feb 15, 2007 at 12:42:37AM -0500, Duncan Findlay wrote: > On Tue, Feb 13, 2007 at 07:51:26PM -0800, Steve Langasek wrote: > > > Here's a summary of the changes from 3.1.7 to 3.1.8: > > > 3.1.8 is a major bug-fix release, including the following issues: > > > - bug 5318: set a maximum inte

Re: spamassassin 3.1.8

2007-02-14 Thread Duncan Findlay
On Tue, Feb 13, 2007 at 07:51:26PM -0800, Steve Langasek wrote: > > Here's a summary of the changes from 3.1.7 to 3.1.8: > > 3.1.8 is a major bug-fix release, including the following issues: > > - bug 5318: set a maximum internal length for URIs > > - bug 5240: disable perl module usage in update

Re: spamassassin 3.1.8

2007-02-13 Thread Duncan Findlay
On Tue, Feb 13, 2007 at 07:51:26PM -0800, Steve Langasek wrote: > > 3.1.8 is a major bug-fix release, including the following issues: > > - bug 5318: set a maximum internal length for URIs > > - bug 5240: disable perl module usage in update channels unless > > --allowplugins is specified > this

Re: spamassassin 3.1.8

2007-02-13 Thread Steve Langasek
Hi Duncan, On Tue, Feb 13, 2007 at 05:09:44PM -0500, Duncan Findlay wrote: > SpamAssassin 3.1.8 will be released shortly with a fix for > CVE-2007-0451, among other changes. > What I'd like to know is whether I should build a 3.1.7 package with > the backported security fix, or

spamassassin 3.1.8

2007-02-13 Thread Duncan Findlay
SpamAssassin 3.1.8 will be released shortly with a fix for CVE-2007-0451, among other changes. What I'd like to know is whether I should build a 3.1.7 package with the backported security fix, or whether I should upload 3.1.8 to unstable and ask that it be propogated to testing. What ar