Bug 2739 - Base64 issue during nightly corpora run ...
Summary: Base64 issue during nightly corpora run ...
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on: 1527
Blocks:
  Show dependency tree
 
Reported: 2003-11-07 07:10 UTC by Theo Van Dinter
Modified: 2004-01-23 12:28 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
message that triggers warning text/plain None Theo Van Dinter [HasCLA]
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 Theo Van Dinter 2003-11-07 07:10:07 UTC 
I'm still trying to figure out which message(s) this comes from.

Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Premature padding of base64 data at
/home/felicity/SA/spamassassin-corpora/masses/../lib/Mail/SpamAssassin/Util.pm line 383.
Comment 1 Theo Van Dinter 2003-11-07 08:36:20 UTC 
Created attachment 1545 [details]
message that triggers warning

took me a bit to find this message, but ... it's from bugtraq, I've stripped
out some headers and changed identification information, but it won't change
the behavior.
Comment 2 Theo Van Dinter 2003-12-15 21:29:07 UTC 
a little more debugging ... the line that makes b64 barf is:

================================================

which is not a b64 encoded section, so I'm not sure why we're trying to decode 
it.
Comment 3 Justin Mason 2003-12-16 12:27:54 UTC 
do we still have the code in the parser that looks for base64 data in MIME parts
*without* a Content-Transfer-Encoding?  (does that bug still exist in the field?)

that strnig would probably trigger an attempted decode.
Comment 4 Theo Van Dinter 2003-12-16 12:35:50 UTC 
Subject: Re:  Base64 issue during nightly corpora run ...

On Tue, Dec 16, 2003 at 01:23:17PM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote:
> do we still have the code in the parser that looks for base64 data in MIME parts
> *without* a Content-Transfer-Encoding?  (does that bug still exist in the field?)
> 
> that strnig would probably trigger an attempted decode.

yeah, that's what I figure it is.  as I recall, we have the new parser
in the code, but we're not actually doing anything with it yet, so the
old code remains.  it's going to be a "fun" bunch of work to convert over.
Comment 5 Theo Van Dinter 2004-01-23 21:28:58 UTC 
yep, the new mime parser takes care of this. ;)