[Tickets] New ticket (164): Foolish Outlook Express email format

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

-Ticket 164
-Queue: IMP
-Created By: 

-Summary:
Foolish Outlook Express email format

Comment by public at atuan.com on Tue May 11 00:53:29 2004 (today):
Note: I am using Imp 3.2.2 on Horde 2.2.5.  If this issue has been fixed
already, please disregard and I'll continue to badger my host about
upgrading.

I received an email message generated by Outlook Express 6.00.2800.1409.  In
the headers, it said:

MIME-Version: 1.0
Content-Type: multipart/related;
    type=multipart/alternative;
    boundary="----=_NextPart_000_002F_01C43698.8ADEC280"

Then, the body was structured like this:

------=_NextPart_000_002F_01C43698.8ADEC280
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0030_01C43698.8ADEC280"


------=_NextPart_001_0030_01C43698.8ADEC280

(text/plain version of message)

------=_NextPart_001_0030_01C43698.8ADEC280

(text/html version of message)

------=_NextPart_001_0030_01C43698.8ADEC280--

------=_NextPart_000_002F_01C43698.8ADEC280

(image/gif -- supporting image for HTML version of message)

------=_NextPart_000_002F_01C43698.8ADEC280--

The problem is that two different boundaries are being used here, and Imp
doesn't recognize the second.  It apparently skips over the sections whose
boundary starts with 001_0030, and because it doesn't find anything useable
following a 000_002F boundary, the message body is simply not rendered at
all.

I don't know whether this is a problem with Outlook Express sending poorly
formed MIME information, or if this is a part of the MIME standard that Imp
doesn't yet implement.  However, I thought it might be a good idea to report
it here so Imp can be made compatible with it.  I've marked this low
priority because this is the first time I've had this problem in a couple of
years of using Imp.  It might be a one-off.  Comments? Tomatoes?

--


http://bugs.horde.org/details.php?id=164

--