http://bugzilla.spamassassin.org/show_bug.cgi?id=3751
Summary: content-type header parsing doesn't catch malformed
boundaries
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P5
Component: Libraries
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
while debugging bug 3749 I found that we strictly followed rfc 1521 for
content-type/boundary parsing:
Content-Type: multipart/mixed;boundary=
"----=_NextPart_000_00CF_35AE65B6.B53B4CCB"
(there's a space between the "=" and the open quote)
that's invalid according to the RFC, and so we deemed it invalid and didn't
catch the boundary. We really should though.
patch forthcoming
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
