cvs commit: qpsmtpd/lib/Apache Qpsmtpd.pm

2004-10-12 Thread Matt Sergeant
cvsuser 04/10/12 00:39:04 Added: lib/Apache Qpsmtpd.pm Log: Connection handler for mod_perl/apache 2.0 Revision ChangesPath 1.1 qpsmtpd/lib/Apache/Qpsmtpd.pm Index: Qpsmtpd.pm ===

Re: (again) Proposed Patch for Spamassassin

2004-10-12 Thread Robert
If Robert is happy with the ability to preserve the headers, but having the default behavior change, I'm satisfied and would commit the change. Perhaps I am being too compulsive here; I've been working on a few patches to the Subversion project, where the compatibility guarantees are very stri

Re: (again) Proposed Patch for Spamassassin

2004-10-12 Thread Robert
So Robert, please make a comment on this. I just saw a posting from Robert on P5P: Perl5 Bug Summary -- Live from the middle of the Adriacic Sea, on the way to Greece. Perl Whirl 2004! So I wouldn't hold your breath... ;) Yeah. What the hell am I doing checking my email? -R (somewhere o

Re: (again) Proposed Patch for Spamassassin

2004-10-12 Thread Peter Eisch
If you were to have a local-custom header added by one of your scanners, couldn't you detect that and skip it on the others? If the subsequent scanners have more rigorous rules than the first, then your effectively ignoring the first scan anyway. On 10/12/04 7:31 AM, "Robert" <[EMAIL PROTECTED

Re: (again) Proposed Patch for Spamassassin

2004-10-12 Thread Keith C. Ivey
Robert <[EMAIL PROTECTED]> wrote: > Mode '1' seems to be the compromise solution. I do find it odd to delete the headers and thus lose information (making impossible to reconstruct the original message), but that is what SpamAssassin itself does. Munging the header names as you suggest (with

Re: (again) Proposed Patch for Spamassassin

2004-10-12 Thread Robert
I do find it odd to delete the headers and thus lose information (making impossible to reconstruct the original message), but that is what SpamAssassin itself does. Munging the header names as you suggest (with X-Old- or whatever) to preserve them makes more sense to me. qpsmtpd != SpamAssass

Updated proposed fix for spamassassin

2004-10-12 Thread Michael Holzt
Now that we got quorum from two spamassassin maintainers, i've updated my patch accordingly. The parameter is now a string, either: "keep", "rename" or "drop". Default is now "rename". Patch is attached. -kju -- It's an insane world, but i'm proud to be a part of it. -- Bill Hicks diff -

Re: anti-spamassassin [was Re: (again) Proposed Patch for Spamassassin]

2004-10-12 Thread Brian Grossman
On Mon, 11 Oct 2004 20:50:12 +0100 Matt Sergeant <[EMAIL PROTECTED]> wrote: > My top tips: > > Block anything without a Message-ID header. > Block anything without any Received headers. > Block anything found in CBL, SBL and SORBS. > Block anything HELOing with a string matching \d+[\.-]\d+ Have

Re: anti-spamassassin [was Re: (again) Proposed Patch for Spamassassin]

2004-10-12 Thread Matt Sergeant
On 12 Oct 2004, at 21:09, Brian Grossman wrote: On Mon, 11 Oct 2004 20:50:12 +0100 Matt Sergeant <[EMAIL PROTECTED]> wrote: My top tips: Block anything without a Message-ID header. Block anything without any Received headers. Block anything found in CBL, SBL and SORBS. Block anything HELOing with a

cvs commit: qpsmtpd/plugins spamassassin

2004-10-12 Thread John Peacock
cvsuser 04/10/12 18:52:35 Modified:plugins spamassassin Log: plugins/spamassassin New option to strip/rename/keep old X-Spam headers (Michael Holzt) Revision ChangesPath 1.14 +43 -0 qpsmtpd/plugins/spamassassin Index: spamassassin ==

Re: Updated proposed fix for spamassassin

2004-10-12 Thread John Peacock
Michael Holzt wrote: Now that we got quorum from two spamassassin maintainers, i've updated my patch accordingly. The parameter is now a string, either: "keep", "rename" or "drop". Default is now "rename". Committed, thanks! John p.s. glad that's over with... ;)