681657 - image of mime type image/x-citrix-jpeg will not display

Status: RESOLVED INCOMPLETE

(Core :: Graphics: ImageLib, defect)

Description

[Dan Stevenson]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0) Gecko/20110813 Firefox/6.0 SeaMonkey/2.3
Build ID: 20110813174900

Steps to reproduce:

Since upgrading from 2.0.14 to 2.3.1 have been receiving certain emails with inline .jpg attachments that will not display. Other emails received with .jpg's display ok whether inline or attached. Checked message source of emails that did and did not display to compare differences.


Actual results:

Found that the .jpg images that will not display are of the mime type image/x-citrix-jpeg. Here is the relevant section from the message source:

Content-Type: image/x-citrix-jpeg;
	name="image001.jpg"
Content-Description: image001.jpg
Content-Disposition: inline; filename="image001.jpg"; size=213469;
	creation-date="Wed, 24 Aug 2011 08:16:30 GMT";
	modification-date="Wed, 24 Aug 2011 08:16:30 GMT"
Content-ID: <image001.jpg@01CC6236.2044D640>
Content-Transfer-Encoding: base64

Here is a section of message source for an image that does display ok:

Content-Type: image/jpeg; name="image002.jpg"
Content-Description: image002.jpg
Content-Disposition: inline; filename="image002.jpg"; size=46713;
	creation-date="Fri, 19 Aug 2011 10:49:30 GMT";
	modification-date="Fri, 19 Aug 2011 10:49:30 GMT"
Content-ID: <[e-mail]281820>
Content-Transfer-Encoding: base64


Expected results:

In SeaMonkey 2.0.14 even though messages with .jpg attachments of the image/x-citrix-jpeg would not display at least the attachment window was visible so the .jpg could be saved and opened with another application. Since upgrading to 2.3.1 the attachment window is not visible when receiving these type of .jpg's so there is no way to save them. If this is a difficult bug to fix could the attachment window be forced to show again so the .jpg's could at least be saved and viewed externally?

Comment 1

[Philip Chee]

Bug 677905 (Add menuitem to "show all body parts") might help. This should be in SeaMonkey 2.5a. Need someone to help test.

Comment 2

[Dan Stevenson]

(In reply to Philip Chee from comment #1)
> Bug 677905 (Add menuitem to "show all body parts") might help. This should
> be in SeaMonkey 2.5a. Need someone to help test.

Is this something an end user could help test? If you can point me to a download for the 2.5a version you mentioned I'd be glad to give it a try.

Comment 3

[Philip Chee]

<http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/>
Just a word of warning. Alphas are of course not production quality and haven't been excessively tested. You should set up a new throw-away profile that doesn't contain any data important to you and test 2.6a with this.

Comment 4

[Dan Stevenson]

Just installed and tested 2.6a. No change from 2.3.1, image/x-citrix-jpeg types will not display in the message body. I did not see any new options under "View > Message Body As". I tried the three view options with the same results as version 2.3.1. If I use "Plain Text" a link to the image appears in the body which I can then save or open. Of course then the rest of the message body will not display correctly if it is an html message.

Comment 5

[Philip Chee]

OK. Thanks for trying. Sorry for the red herring.

Comment 6

[Dan Stevenson]

no problem, thanks for the suggestion.

Comment 7

[Ian Neal]

If you search the registry for x-citrix-jpeg does it give any entries?
Are these images available from a website with that mime type set? If so do they open up using browser or Firefox?
There are a number of image content types that are recognised by Gecko but x-citrix-jpeg does not appear to be one of them.
If it is going to be fixed it will probably need doing in Gecko.

Comment 8

[Dan Stevenson]

(In reply to Ian Neal from comment #7)
> If you search the registry for x-citrix-jpeg does it give any entries?
> Are these images available from a website with that mime type set? If so do
> they open up using browser or Firefox?
> There are a number of image content types that are recognised by Gecko but
> x-citrix-jpeg does not appear to be one of them.
> If it is going to be fixed it will probably need doing in Gecko.

No entries show up for x-citrix-jpeg in the registry. If I switch to "plain text" view for the email message body then I get clickable links for the .jpg images which will then open in the SeaMonkey browser window. From what I read it seems that these image types are created when someone running in a citrix terminal session attaches a .jpg image to an email. Why citrix changes the mime type for the image I don't know but maybe the new type can be added or there could be an option to show the small attachment window like what used to show in 2.0.14.

Comment 9

[Tony Mechelynck [:tonymec]]

(In reply to Philip Chee from comment #1)
> Bug 677905 (Add menuitem to "show all body parts") might help. This should
> be in SeaMonkey 2.5a. Need someone to help test.

Dan (reporter): That menuitem exists only in SeaMonkey 2.5a2 or later. In order for it to be visible, the preference mailnews.display.show_all_body_parts_menu must first be set to true in about:config. There is no checkbox for it in the Preferences dialog.

1. Type about:config in the URL bar, then hit Enter
2. If told that this could void your warranty, promise that you'll be prudent.
3. type body_ (with the underscore) in the Filter box
4. If you see
   mailnews.display.show_all_body_parts_menu    default    boolean    false
   double-click it to make it true

After that, you should see an additional menuitem, "View → Message Body As → All Body Parts".
Selecting this option forces all attachments, even "hidden" ones, to be shown in the Attachments box, but it also displays the message as plaintext even in HTML messages, so you may want to go back to "Original HTML" or "Simple HTML" after you're finished with the "problematic" message.

Comment 10

[Tony Mechelynck [:tonymec]]

On rereading previous comments, I'm not sure if the problematic image is sent with the message or not; if it isn't, comment #9 won't help.

There might be grounds to turn this bug, or a followup bug, into a bug for the appropriate l10n component of the "Tech Evangelism" product, in order to try to convince whoever is responsible for that weird MIME type (whoever makes the mail agent which set that MIME type if the image was sent with the message, or the webmaster of the serving site if it wasn't) to use image/jpeg instead.

See http://www.mozilla.org/projects/tech-evangelism/site/procedures.html about how Tech Evangelism bugs should be handled.

Comment 11

[Dan Stevenson]

(In reply to Tony Mechelynck [:tonymec] from comment #10)
> On rereading previous comments, I'm not sure if the problematic image is
> sent with the message or not; if it isn't, comment #9 won't help.
> 
> There might be grounds to turn this bug, or a followup bug, into a bug for
> the appropriate l10n component of the "Tech Evangelism" product, in order to
> try to convince whoever is responsible for that weird MIME type (whoever
> makes the mail agent which set that MIME type if the image was sent with the
> message, or the webmaster of the serving site if it wasn't) to use
> image/jpeg instead.
> 
> See http://www.mozilla.org/projects/tech-evangelism/site/procedures.html
> about how Tech Evangelism bugs should be handled.

Tony, 
Thanks for your replies and the instructions for changing the display option setting in about:config. That setting would work perfect if it also left the original html in the message body alone. We receive a lot of these messages because I work for a company that does, among other things, water heater installations for a major utility company in our area. Apparently the employees at the utility that sends us these work orders via email are using Citrix terminals so that is where the problem originates. Unfortunately they will not make any changes on their end because they say that all the other contractors they send to have no problem viewing their emails. I'm guessing the other contractors are using ms outlook to receive these emails. 
Why Citrix had to create a new mime type for a standard .jpg image is beyond me but hopefully it will either be adopted as a standard or changed back to the normal mime type eventually. For now we can keep using SeaMonkey version 2.0.14 since it displays both the html message body and the attachment window for messages that contain this weird mime type. I'll keep checking this thread for any new info that might come up. 
Thanks,
Dan

Comment 12

[Tony Mechelynck [:tonymec]]

In reply to comment #11: IMHO the problem is not with users of Citrix but with makers of Citrix. Maybe you could try to convince them that by using a MIME type of image/x-citrix-jpeg where image/jpeg is the industry standard, they make the images undisplayable in recent versions of SeaMonkey, Thunderbird, etc.?

Of course, if the problem is fixed in recent versions of Citrix, then your utility company customer should upgrade their software. After all, SeaMonkey, Thunderbird and Firefox all use the same display engine, and unlike Outlook Express they are available not only for Windows, but also for Mac and even Linux.

Comment 13

[Dan Stevenson]

I agree, the Citrix software is the cause of this issue. Unfortunately if I mention anything to the sending party about the issues we have with their emails I get the standard answer "maybe you should switch to outlook, our other contractors are not having problems with our emails". I'm so tired of hearing "it's a microsoft world so you might as well just use outlook, ie, office, etc. No thanks, I'll stick with my SeaMonkey, Lotus Smartsuite, etc.

Comment 14

[Tony Mechelynck [:tonymec]]

In reply to comment #13:
I sympathize with your predicament.
My standard reply to that kind of high-handed brush-off is, "Sorry, I can't afford a software which costs an arm and a leg, breaks down constantly, and is known to suffer from uncountable viruses, worms and Trojan horses. I'll stick to Linux, thank you." Of course if you're still on Windows you can't use such an "extreme" form of rebuttal though...

Comment 15

[Ian Neal]

(In reply to Dan Stevenson from comment #13)
> I agree, the Citrix software is the cause of this issue. Unfortunately if I
> mention anything to the sending party about the issues we have with their
> emails I get the standard answer "maybe you should switch to outlook, our
> other contractors are not having problems with our emails". I'm so tired of
> hearing "it's a microsoft world so you might as well just use outlook, ie,
> office, etc. No thanks, I'll stick with my SeaMonkey, Lotus Smartsuite, etc.

What would be useful would be if you knew of a website that had images with this image/x-citrix-jpeg type set.

Comment 16

[Dan Stevenson]

(In reply to Ian Neal from comment #15)
> (In reply to Dan Stevenson from comment #13)
> > I agree, the Citrix software is the cause of this issue. Unfortunately if I
> > mention anything to the sending party about the issues we have with their
> > emails I get the standard answer "maybe you should switch to outlook, our
> > other contractors are not having problems with our emails". I'm so tired of
> > hearing "it's a microsoft world so you might as well just use outlook, ie,
> > office, etc. No thanks, I'll stick with my SeaMonkey, Lotus Smartsuite, etc.
> 
> What would be useful would be if you knew of a website that had images with
> this image/x-citrix-jpeg type set.

I have not been able to find any websites with the x-citrix-jpeg type. I can find very little info at all about these strange mime types but they seem to be generated when someone attaches an image to an email during a citrix terminal session. This is the best info I have been able to dig up (see link below) but everything on this page mentions image/x-citrix-pjpeg. Although I'm betting that it is basically the same as the image/x-citrix.jpeg I have been receiving.

http://stackoverflow.com/questions/200912/what-is-the-difference-between-image-x-citrix-pjpeg-and-image-pjpeg

Comment 17

[Joe Drew (not getting mail)]

If you attach a file of that type, I can at least look at what's going wrong. We basically totally ignore mime types and sniff the actual content to determine image types, so I'd like to know where that's going wrong.

Comment 18

[Dan Stevenson]

Attachment: sample image

This is a sample of an image of mime type image/x-citrix-jpeg that will not show in the email message body

Comment 19

[Dan Stevenson]

(In reply to Joe Drew (:JOEDREW!) from comment #17)
> If you attach a file of that type, I can at least look at what's going
> wrong. We basically totally ignore mime types and sniff the actual content
> to determine image types, so I'd like to know where that's going wrong.

I changed the view to plain text and saved one of the offending images to my desktop so I could attach it here. When in plain text view I right click the link and click "Save Link Target" the file extension has .jpg so that shows that it is being detected as a .jpg image but it will not display in the message body. I am also going to attach a couple screen shots of how the link to the image appears in the message body when view is set to original html as compared to when it is set to plain text.

Comment 20

[Dan Stevenson]

Attachment: image/x-citrix-jpeg with view set to original html

screenshot of how an image of mime type image/x-citrix-jpeg displays with message body set to original html

Comment 21

[Dan Stevenson]

Attachment: image/x-citrix-jpeg with view set to plain text

screenshot of how an image of mime type image/x-citrix-jpeg displays with message body set to plain text

Comment 22

[Mike Kaply [:mkaply]]

Very old bug. Marking INCOMPLETE. Please reopen if still an issue.