[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-30 Thread Malte S. Stretz
On Saturday 30 August 2003 06:05 CET Chris Barnes wrote: > I've got 2.60 installed from the cvs, but a version prior to rc1. I've > held off ungrading for now for 2 reasons: > > 1) the version I have seems to be working just fine > 2) the rc versions seem to have some bugs (to be expected - that's

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-30 Thread Chris Barnes
I've got 2.60 installed from the cvs, but a version prior to rc1. I've held off ungrading for now for 2 reasons: 1) the version I have seems to be working just fine 2) the rc versions seem to have some bugs (to be expected - that's why they are "rc"). My question is, when the final release comes

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-30 Thread Malte S. Stretz
On Saturday 30 August 2003 00:16 CET Simon Byrnand wrote: > > I don't like that behaviour, too, and will see what I can do about it > > Malte > > All I was attempting to do with the \n's was to change the X-Spam-Status > header to look like 2.55's - where there is a (folded) newline between > "requ

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-30 Thread Malte S. Stretz
On Saturday 30 August 2003 01:19 CET Lucas Albers wrote: > I'm curious to know what sort of performance increase you should see > because of this. Using an network protocol (TCP) for communications on one machine generates quite some overhead. UNIX sockets don't have this overhead and are thus b

Re: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Simon Byrnand
> On Friday 29 August 2003 04:34 CET Theo Van Dinter wrote: >> On Fri, Aug 29, 2003 at 01:57:27PM +1200, Simon Byrnand wrote: >> > Fixed now, but the second part of Theo's fix (assuming he did it :) >> > doesn't seem to be in there - using any \n's to add a newline into a >> > report header still e

Re: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Simon Byrnand
> On Fri, 29 Aug 2003, Malte S. Stretz wrote: > >> to make it work like before (or make a symlink from /usr/local/etc to >> /etc). >> See also bug 2374 [1]. > >> [1]http://bugzilla.spamassassin.org/show_bug.cgi?id=2374 > > Ah. Reading through the suggestions on Bugzilla - having everything in > /us

Re: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Simon Byrnand
> On Friday 29 August 2003 17:02 CET Christopher X. Candreva wrote: >> Is there a build switch to tell spamc to use a Unix doimain socket (and >> the socket name) by default ? > > Nope. > >> Also, for some reason on rc3, perl Makefile.PL built a system that was >> looking in /usr/local/etc/spamas

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Malte S. Stretz
On Friday 29 August 2003 23:31 CET Kai Schaetzl wrote: > Malte S. Stretz wrote on Fri, 29 Aug 2003 17:32:52 +0200: > > > Also, for some reason on rc3, perl Makefile.PL built a system that > > > was looking in /usr/local/etc/spamassassin for local.cf instead of in > > > /etc/mail/spamassasin, as pr

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Malte S. Stretz
On Friday 29 August 2003 21:52 CET Henrik Schmiediche wrote: >I would like to second the notion that having to specify SYSCONFDIR > is going to cause sys-admins problems that do not follow this list. I > have no problem with the idea in principle; I just think it needs to be > well documented,

Re: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Justin Mason
"Henrik Schmiediche" writes: > > I would like to second the notion that having to specify SYSCONFDIR >is going to cause sys-admins problems that do not follow this list. I >have no problem with the idea in principle; I just think it needs to be >well documented, preferable with a run-time-instal

RE: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Henrik Schmiediche
: Re: [SAtalk] Re: SpamAssassin 2.60 rc3 released On Fri, 29 Aug 2003, Malte S. Stretz wrote: > to make it work like before (or make a symlink from /usr/local/etc to /etc). > See also bug 2374 [1]. > [1]http://bugzilla.spamassassin.org/show_bug.cgi?id=2374 Ah. Reading through the sugge

Re: [SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Christopher X. Candreva
On Fri, 29 Aug 2003, Malte S. Stretz wrote: > to make it work like before (or make a symlink from /usr/local/etc to /etc). > See also bug 2374 [1]. > [1]http://bugzilla.spamassassin.org/show_bug.cgi?id=2374 Ah. Reading through the suggestions on Bugzilla - having everything in /usr/local/etc may

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Malte S. Stretz
On Friday 29 August 2003 17:43 CET Christopher X. Candreva wrote: > That means any of my users who put spamc in their .procmailrc file has to > know 1) to use a socketpath, and 2) what the path is. I'm looking for a > compile option to Makefile.PL (or ./configure, or whichever) so that > spamc, wi

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Malte S. Stretz
On Friday 29 August 2003 17:02 CET Christopher X. Candreva wrote: > Is there a build switch to tell spamc to use a Unix doimain socket (and > the socket name) by default ? Nope. > Also, for some reason on rc3, perl Makefile.PL built a system that was > looking in /usr/local/etc/spamassassin for

[SAtalk] Re: SpamAssassin 2.60 rc3 released

2003-08-29 Thread Malte S. Stretz
On Friday 29 August 2003 04:34 CET Theo Van Dinter wrote: > On Fri, Aug 29, 2003 at 01:57:27PM +1200, Simon Byrnand wrote: > > Fixed now, but the second part of Theo's fix (assuming he did it :) > > doesn't seem to be in there - using any \n's to add a newline into a > > report header still effecti