[imp] MIME boundary problems

[Michael M Slusarz]

Quoting Myke Place <mp at xmission.com>:

| Hi,
|
| Once again, thanks to all who develop Horde/IMP, it really is a beautiful
| piece of work.
|
| We seem to be having a problem wherein messages that have a MIME boundary
| that begin with a '=_' are not being parsed correctly. For instance,
| looking at a message that has the following line in the header:
|
| Content-type: multipart/alternative;
| boundary==_e60daa4e5399a7b47a38bced5aa1f5b1

This is an invalid header.

| will display an empty message. Whereas
|
| Content-type: multipart/alternative;
| boundary=e60daa4e5399a7b47a38bced5aa1f5b1
|

This is a valid header.

The first header appears to be missing quotation marks around the boundary
string.  It should be:
boundary="=_e60daa4e5399a7b47a38bced5aa1f5b1"
(This is the boundary string that IMP/Horde HEAD produces.  And yes, there
 _should_ be an equal sign right after the first equal sign.
 See RFC 2045 [6.7]:
 "A good strategy is to choose a boundary that includes a character
 sequence such as "=_" which can never appear in a quoted-printable body.")

Without quotation marks, the two "=" in a row are causing problems - thus
the empty message.

michael

______________________________________________
Michael Slusarz [slusarz at bigworm.colorado.edu]
The University of Colorado at Boulder