Inline images from word / outlook / hotmail

[bouncingmolar]

After reading the article : <a href="http://kb.mozillazine.org/Images_in_messages_do_not_appear">Images in messages do not appear</a>
And viewing thread: <A href="http://forums.mozillazine.org/viewtopic.php?t=131293">Images in Thunderbird</a>

It appears that the reason why inline images don't appear is because of what word/outlook does to it.

Contrary to the reasons given in the above thread I think I know the real reason why these images are not being displayed inline.

this is what an image attachment header <b>should</b> look like:

<b>Content-Type: image/jpeg;</b>
name="IMAGE_1.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="IMAGE_1.jpg"

I viewed the source from an msoffice 12 created email where the images were not being displayed inline:

<b>Content-Type: application/octet-stream;</b>
name="IMAGE_2.jpg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="IMAGE_2.jpg"

It appears that the reason it doesn't display properly is because MSoffice is not changing the content-type to :image/jpeg and so thunderbird doesn't realise that "application/octet-stream" is an image.

In some of my older emails, the following prevents images being displayed inline:

<b>Content-Type: application/x-unknown-content-type-ViewerFrameClass;</b>

Is this the right place to ask if someone can make it possible for thunderbird to recognise "application/octet-stream" / "application/x-unknown-content-type-ViewerFrameClass;" as an inline attachment?

[Daifne]

Not really.

Established in 1998, MozillaZine is an independent Mozilla news, community and advocacy site. MozillaZine is not run by the Mozilla Foundation and is not an official part of the Mozilla project. MozillaZine is hosted at the Open Source Lab at Oregon State University.

Bugzilla is the proper place.

[novaflash]

Yeah now if only they did something about it. The bug is STILL there.

[rsx11m]

The sending application is responsible for providing the correct type of the attachment, which is image/jpeg here and nothing else. Just the fact that other vendors make up their own standards as they go doesn't imply that applications which do adhere to the official standard have to adapt to those.

The combination of Content-Type: application/octet-stream; and Content-Disposition: attachment; would clearly indicate to the receiving e-mail client that this is nothing to be shown inline...

[LIMPET235]

Please start a new thread if you have a problem.
Locking this oldie.