http://bugzilla.spamassassin.org/show_bug.cgi?id=3823
Summary: spamassassin: causes amavisd-new to choke when pyzor or dccifd is enabled Product: Spamassassin Version: 3.0.0 Platform: Other URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273290 OS/Version: other Status: NEW Severity: normal Priority: P5 Component: Libraries AssignedTo: dev@spamassassin.apache.org ReportedBy: [EMAIL PROTECTED] Package: spamassassin Version: 3.0.0-1 Severity: grave Tags: patch I use amavisd-new, which calls SA. Upon upgrading to spamassassin 3.0, everything turned into a mess. The reason for the severity is that due to this bug mail will be delayed, mangled, or sent to the wrong recipients entirely. I started receiving mail with no body and the recipients stripped out: X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at silverdream.org X-Spam-Status: No, hits=-5.9 tagged_above=-999.0 required=3.5 tests=ALL_TRUSTED, AWL, BAYES_00, NO_REAL_NAME X-Spam-Level: Message-Id: <[EMAIL PROTECTED]> Date: Fri, 24 Sep 2004 03:02:34 +0100 (BST) From: [EMAIL PROTECTED] To: undisclosed-recipients:; Subject: (No Subject) I also noticed that some mail was delivered to the wrong recipients entirely. That's not only a very Bad Thing(tm) in terms of loss of mail, on a multi-user mail server it's an invasion of privacy. In addition, amavisd-new does not shut down cleanly, I assume this is because of the SA bug. Turning off pyzor and dcc fixes the all the problems described. I don't know much about the internals, but having discussed the issue on the amavis-user mailing list, it appears to be a known problem with SA 3.0.0 and external applications such as pyzor and dccifd, when SA is called by amavisd-new. Sep 24 04:15:27 lorien amavis[26206]: (26198-01) Passed, <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, Message-ID: <[EMAIL PROTECTED]>, Hits: -2.6 Sep 24 04:15:27 lorien amavis[26206]: (26198-01) LMTP: 500 5.5.2 Error: bad syntax; PENALIZE: X-Envelope-From: <[EMAIL PROTECTED]>\n The issue is discussed in the 'Upgrade Problems' thread on the amavis- user mailing list: http://marc.theaimsgroup.com/?l=amavis-user&m=109586950804559&w=2 I built the package from source and applied the following patch from http://marc.theaimsgroup.com/?l=amavis-user&m=109591870017386&w=2, which seems to cure the problem: --- Dns.pm.ORIG Wed Sep 22 13:24:09 2004 +++ Dns.pm Wed Sep 22 13:24:56 2004 @@ -789,9 +789,9 @@ dbg("DCC command: ".join(' ', $path, "-H", $opts, "< '$tmpf'", "2>&1"),'dcc',-1); - # my $pid = open(DCC, join(' ', $path, "-H", $opts, "< '$tmpf'", "2>&1", '|')) || die "$!\n"; - my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC, - $tmpf, 1, $path, "-H", split(' ', $opts)); + my $pid = open(DCC, join(' ', $path, "-H", $opts, "< '$tmpf'", "2>&1", '|')) || die "$!\n"; + #my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC, + # $tmpf, 1, $path, "-H", split(' ', $opts)); $pid or die "$!\n"; my @null = <DCC>; ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.