Bug 512519 - spamass-milter has a broken -B and -b option
Summary: spamass-milter has a broken -B and -b option
Keywords:
Status: CLOSED DUPLICATE of bug 496763
Alias: None
Product: Fedora
Classification: Fedora
Component: spamass-milter
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-18 14:19 UTC by Steven W. Orr
Modified: 2009-11-18 12:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-18 12:55:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
diff -c (805 bytes, patch)
2009-07-18 14:19 UTC, Steven W. Orr
no flags Details | Diff

Description Steven W. Orr 2009-07-18 14:19:33 UTC
Created attachment 354253 [details]
diff -c

Description of problem:

spamass-milter (hereafter called SPM) is a milter that is run from sendmail and is used to filter all incoming mail through spamassassin (SA). SPM can be jiggered to either accept the mail or prevent the mail from being accepted. I have it set to reject if I hit a score of 5.0. Occasionally, a false negative gets through and when that happens, I pass it to a script that runs sa-learn and forwards it to spamcop. But, all the messages that were being caught were not being reported to spamcop. So I added the -B option to the SPM invocation. All the spam that was caught was sent to spamcop but spamcop was not able to parse the message. It turns out that a couple of the headers were improperly processed by SPM. If you go to

http://savannah.nongnu.org/bugs/?func=detailitem&item_id=17178

you will see that back in '06, Joe Wagner fixed it, checked it into CVS, and a 0.3.2 was never released.

What I did was to unpack the Fedora f10 src rpm, then unpack the tar.gz file, and compared that with the copy that I sucked out of the CVS repository. There are two small changes. I put a context diff below.

%%%%%%%%%%%%%start of diff%%%%%%%%%%%%%
*** spamass-milter.cpp  Sat Jul 18 08:46:36 2009
--- spamass-milter.cpp~ Thu Mar 23 16:41:36 2006
***************
*** 1002,1010 ****
  
                assassin->output((string)
                        "Received: from "+macro_s+" ("+macro__+")\r\n\t"+
!                       "by "+macro_j+"("+macro_v+"/"+macro_Z+") with "+macro_r+" id "+macro_i+";\r\n\t"+
                        macro_b+"\r\n\t"+
!                       "(envelope-from "+assassin->from()+")\r\n");
  
        } else
                assassin->output((string)"X-Envelope-To: "+envrcpt[0]+"\r\n");
--- 1002,1010 ----
  
                assassin->output((string)
                        "Received: from "+macro_s+" ("+macro__+")\r\n\t"+
!                       "by "+macro_j+"("+macro_v+"/"+macro_Z+") with "+macro_r+" id "+macro_i+"\r\n\t"+
                        macro_b+"\r\n\t"+
!                       "(envelope-from "+assassin->from()+"\r\n");
  
        } else
                assassin->output((string)"X-Envelope-To: "+envrcpt[0]+"\r\n");
%%%%%%%%%%%%%END OF DIFF%%%%%%%%%%%%%%%
After the patch was applied, I reconstructed the tar.gz file, put it into SOURCES, ran rpm -bc, and replaced the spamass-milter in /usr/sbin. Then I restarted SPB and the -B option did what it was supposed to do, but this time the messed up headers were good and spamcop was able to properly parse the submittal.

Version-Release number of selected component (if applicable):
spamass-milter-0.3.1

How reproducible:
Run SPB with the -B or -b option. You can use any old address to send to yourself. The address will have a missing ')' and a ';' in at least one of the "received" headers.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

I'd be happy to amplify if you need anything else. Also, I did not look at any other changes that might have been made.

To get the src code was just

mkdir spm
cd spm
cvs -z3 -d:pserver:anonymous.nongnu.org:/sources/spamass-milt co .

and the file is spamass-milt/spamass-milter.cpp

Comment 1 Paul Howarth 2009-07-26 08:29:05 UTC
Can you try the version (0.3.1-14) in updates-testing?

# yum --enablerepo=updates-testing update spamass-milter

There's a similar fix in there from Bug #496763 but I've never had any feedback on whether it fixed the reporter's problem.

Comment 2 Steven W. Orr 2009-07-26 12:22:36 UTC
If you could please tell me the command to fetch the src.rpm I'd be happy to look at that first before trying it. The patch described in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510665 is different than what I described.

I say:

1005c1005
<                       "by "+macro_j+"("+macro_v+"/"+macro_Z+") with "+macro_r+" id "+macro_i+";\r\n\t"+
---
>                       "by "+macro_j+"("+macro_v+"/"+macro_Z+") with "+macro_r+" id "+macro_i+"\r\n\t"+

He sez:

-                       "by "+macro_j+"("+macro_v+"/"+macro_Z+") with "+macro_r+" id "+macro_i+"\r\n\t"+
+                       "by "+macro_j+" ("+macro_v+"/"+macro_Z+") with "+macro_r+" id "+macro_i+"\r\n\t"+

So I have no idea what you'd be offering me without looking at the src.

Also, he sez that his is important. ;-)

Comment 3 Paul Howarth 2009-07-27 09:49:52 UTC
$ yumdownloader --enablerepo=updates-testing --source spamass-milter

Comment 4 Bug Zapper 2009-11-18 12:10:28 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Paul Howarth 2009-11-18 12:55:20 UTC

*** This bug has been marked as a duplicate of bug 496763 ***


Note You need to log in before you can comment on or make changes to this bug.