Re: [SAtalk] report_safe_copy_headers still broken in RC3.

2003-08-30 Thread Larry Rosenman
Gak. I didn't realize y'all had changed things to **NOT** read /etc/mail/spamaassin/* for config files. When I symlink /usr/local/etc/mail/spamassassin/local.cf to /etc/mail/spamassassin/local.cf it works as advertised. PLEASE revert whatever change was made to NOT read /etc/mail/spamassassin

[SAtalk] report_safe_copy_headers still broken in RC3.

2003-08-29 Thread Larry Rosenman
In rc3, with the following /etc/mail/spamassassin/local.cf: $ cat local.cf # This is the right place to customize your installation of SpamAssassin. # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # tweaked. #

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-26 Thread Larry Rosenman
--On Monday, August 25, 2003 10:41:08 -0400 Theo Van Dinter <[EMAIL PROTECTED]> wrote: On Mon, Aug 25, 2003 at 09:34:09AM -0500, Larry Rosenman wrote: You may want to look at the perldoc, as it seems to imply the {} are necessary... (Are they?) The doc was wrong, I already fixed it. The braces

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-26 Thread Larry Rosenman
--On Monday, August 25, 2003 09:27:17 -0400 Theo Van Dinter <[EMAIL PROTECTED]> wrote: On Mon, Aug 25, 2003 at 09:07:12AM -0400, Theo Van Dinter wrote: This is somewhere between a bug and a feature. I'm thinking SA should support multiple headers though. Oh, but in some testing it looks like r

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-26 Thread Theo Van Dinter
On Mon, Aug 25, 2003 at 09:34:09AM -0500, Larry Rosenman wrote: > You may want to look at the perldoc, as it seems to imply the {} are > necessary... (Are they?) The doc was wrong, I already fixed it. The braces indicated that the headers were one of a certain set, ala add_header: add_header {

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-26 Thread Theo Van Dinter
On Mon, Aug 25, 2003 at 09:07:12AM -0400, Theo Van Dinter wrote: > This is somewhere between a bug and a feature. I'm thinking SA should > support multiple headers though. Oh, but in some testing it looks like report_safe_copy_headers doesn't work at all now. :( So that's definitely a bug. :( -

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-26 Thread Theo Van Dinter
On Mon, Aug 25, 2003 at 09:42:21AM -0500, Larry Rosenman wrote: > Ok, that makes sense. I didn't see that change in the patch in the bug... Heh. Yeah, I did the patch then changed the docs seperately. Our policy during release cycles is that doc changes/commits are allowed as necessary, but cod

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-26 Thread Larry Rosenman
--On Monday, August 25, 2003 09:07:12 -0400 Theo Van Dinter <[EMAIL PROTECTED]> wrote: On Sun, Aug 24, 2003 at 11:58:03PM -0500, Larry Rosenman wrote: report_safe_copy_headers { Received } Those braces are just going to confuse thing. As for Received, it will copy it over. However, at the mom

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-25 Thread Theo Van Dinter
On Mon, Aug 25, 2003 at 09:21:42AM -0500, Larry Rosenman wrote: > Do I need to bugzilla it? Nope, I already did. Even have a patch up already. :) http://bugzilla.spamassassin.org/show_bug.cgi?id=2356 I'm hoping to get an rc3 out today, so hopefully all this stuff will be done up quickly. -- Ra

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-25 Thread Justin Mason
Theo Van Dinter writes: > On Sun, Aug 24, 2003 at 11:58:03PM -0500, Larry Rosenman wrote: > > report_safe_copy_headers { Received } > > Those braces are just going to confuse thing. As for Received, it will > copy it over. However, at the moment any header that you want to copy > which appears

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-25 Thread Larry Rosenman
--On Monday, August 25, 2003 10:27:28 -0400 Theo Van Dinter <[EMAIL PROTECTED]> wrote: On Mon, Aug 25, 2003 at 09:21:42AM -0500, Larry Rosenman wrote: Do I need to bugzilla it? Nope, I already did. Even have a patch up already. :) http://bugzilla.spamassassin.org/show_bug.cgi?id=2356 I'm hopin

Re: [SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-25 Thread Theo Van Dinter
On Sun, Aug 24, 2003 at 11:58:03PM -0500, Larry Rosenman wrote: > report_safe_copy_headers { Received } Those braces are just going to confuse thing. As for Received, it will copy it over. However, at the moment any header that you want to copy which appears multiple times in the original messag

[SAtalk] report_safe_copy_headers, does it work for Received:?

2003-08-25 Thread Larry Rosenman
I am running 2.60-rc2, and am trying(!) to have the received: headers copied into the report_safe report. I have the following /etc/mail/spamassassin/local.cf: $ cat local.cf # This is the right place to customize your installation of SpamAssassin. # See 'perldoc Mail::SpamAssassin::Conf' for de

Re: [SAtalk] report_safe_copy_headers

2003-07-29 Thread Kyle Wheeler
On Tue, Jul 29, 2003 at 12:43:02PM +1200, Simon Byrnand quoth: > At 18:34 28/07/2003 -0500, Kyle Wheeler wrote: > >Hello all, > > > >I've got two questions I am looking for help with. > > > >I recently learned of the Trustic RBL and have been trying to integrate > >it with my spamassassin installat

Re: [SAtalk] report_safe_copy_headers

2003-07-28 Thread Simon Byrnand
At 18:34 28/07/2003 -0500, Kyle Wheeler wrote: Hello all, I've got two questions I am looking for help with. I recently learned of the Trustic RBL and have been trying to integrate it with my spamassassin installation. I followed the instructions on their website to add a trustic.cf to /etc/mail/

[SAtalk] report_safe_copy_headers

2003-07-28 Thread Kyle Wheeler
Hello all, I've got two questions I am looking for help with. I recently learned of the Trustic RBL and have been trying to integrate it with my spamassassin installation. I followed the instructions on their website to add a trustic.cf to /etc/mail/spamassassin, and that seems to work nicely. No