MIME implementations that break Pine

[William McBrine]

I've found that some mailers have a different (and, I presume, inferior)
understanding of the MIME specs than Pine does; they leave out the
"boundary=" part of the Content line on multipart messages. Pine displays
these messages as blank (until I edit the spool file and manually insert
the boundary definition).

Unfortunately, though I've only come across two mailers that do this, one
of them is AOL's, and the other is Microsoft Outlook something-or-other.
(I'd never heard of it, but given the MS name, I fear it will soon be in
wide use, if it isn't already.)

I'm using Pine 3.95 and 3.96.

--
William McBrine | http://www.clark.net/pub/wmcbrine/html/
wmcb...@clark.net | Unsolicited commercial emailers will be annihilated

[David L Miller]

On 10 Dec 1997, William McBrine wrote:

WMB> I've found that some mailers have a different (and, I presume, inferior)
WMB> understanding of the MIME specs than Pine does; they leave out the
WMB> "boundary=" part of the Content line on multipart messages. Pine displays
WMB> these messages as blank (until I edit the spool file and manually insert
WMB> the boundary definition).

The most common cause of this problem I have seen is that someone with
a non-MIME mailer forwarded a multipart message, in which case the
Content-Type line is missing entirely. However, an ancient version of
the MIME spec allowed the boundary to be missing, in which case it
defaults to "-" which Pine should accept...

Pine 4.00 will have an option to allow you to display the raw text of
messages with this sort of bogus MIME...

--DLM