On Fri, Nov 23, 2001 at 03:29:36PM -0500, Sam Varshavchik wrote:
Markus Stumpf writes:
------------------------------------------------------------------------
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="bound"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.
The bug is taking advantage of a MIME parsing bug in Outlook. The above
header line specifies a MIME multipart boundary delimiter that doesn't
really exist in the content of the mail (both of the X-header lines are
really syntactically a part of the MIME boundary delimiter), and that's why
reformime did not see any attachments. However, since Outlook does not
properly parse the MIME headers, it is fooled into thinking that the message
contains an attachment.
I am fully aware that this is a bug in the MIME parser of Outlook.
However (I dont want to start any religious wars here) wouldn't it
be a good idea to have the rfc2045 library to be a bit more fault
tolerant? As a quick glance at rfc2045 showed (please correct me if I am
wrong) the boundary could be clearly identified with the ending <">
(although the ";" is missing as more (syntactically invalid) tokens
follow) and the rest of the Content-type header field could be ignored
as faulty.
3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: reformime decompo...
