Bug 2213 - Message not un-base64 encoded by spamassassin
Summary: Message not un-base64 encoded by spamassassin
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 2.55
Hardware: Sun Solaris
: P3 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on: 1527
Blocks:
  Show dependency tree
 
Reported: 2003-07-11 11:11 UTC by Chris Candreva
Modified: 2004-01-24 12:35 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
The mbox file of the base64 message as I received it, with SA reprt headers. text/plain None Chris Candreva [NoCLA]
Message as 'e'xported to a file from pine, with the SA header lines removed text/plain None Chris Candreva [NoCLA]
The output of spamc -R <message.txt on my system. text/plain None Chris Candreva [NoCLA]
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Candreva 2003-07-11 11:11:28 UTC 
I've received a particular base-64 encoded spam, that apparently wasn't
un-encoded  by SA before analysis, as none of the content rules were triggered.
After saving it out as ASCII from pine and re-running through spamc -R, the
content type rules (IMPOTENCE, AS_SEEN_ON, etc) are triggered.

I've placed the base64 message, ascii version, and SA report on the ASCII
version at http://www.westnet.com/~chris/SA-bug.tar.gz  As it seems a bit large
to paste here. (Please let me know if that should be done in the future).
Comment 1 Chris Candreva 2003-07-11 11:12:53 UTC 
Created attachment 1150 [details]
The mbox file of the base64 message as I received it, with SA reprt headers.
Comment 2 Chris Candreva 2003-07-11 11:13:29 UTC 
Created attachment 1151 [details]
Message as 'e'xported to a file from pine, with the SA header lines removed
Comment 3 Chris Candreva 2003-07-11 11:13:47 UTC 
Created attachment 1152 [details]
The output of  spamc -R <message.txt  on my system.
Comment 4 Theo Van Dinter 2004-01-18 16:49:25 UTC 
ok....  1151 is an invalid message.  1150 is properly parsed by the new mime 
parser in 2.70. :)
Comment 5 Theo Van Dinter 2004-01-24 21:35:55 UTC 
fixed in 2.70