"Enzo Michelangeli" wrote in message
...

"Steve Cochran" wrote in message
...
That was my point. IE has a means of handling MHTML, but Firefox
doesn't, which is why it works in Firefox. G

I think that one is not the real issue, because the problem occurs even
with the MIME Content-type set to "application/octet-stream", which is not
taken as MHTML.

(Besides, why does MSIE consider message/rfc822 equivalent to MHTML even
when the message contains no HTML parts at all??)


Because they coded it that way. G The registry association is with
mshtml.dll for IE, when it should probably be inetcomm.

steve



Enzo