FC 10/ KDE
I have one person that sends me .jpg pictures in a Email and thunderbird can not display them , when I try to Open them I can only "Save" them to my Picture folder to view them. That person uses WindowsXP.
I recieve .jpg pictures from every one else and I can view them in Thunderbird.
What could it be ??
Jim wrote:
I have one person that sends me .jpg pictures in a Email and thunderbird can not display them , when I try to Open them I can only "Save" them to my Picture folder to view them. That person uses WindowsXP.
I recieve .jpg pictures from every one else and I can view them in Thunderbird.
What could it be ??
The MIME type declared in the e-mail is incorrect.
Kevin Kofler
On 05/30/2009 12:50 PM, Kevin Kofler wrote:
Jim wrote:
I have one person that sends me .jpg pictures in a Email and thunderbird can not display them , when I try to Open them I can only "Save" them to my Picture folder to view them. That person uses WindowsXP.
I recieve .jpg pictures from every one else and I can view them in Thunderbird.
What could it be ??
The MIME type declared in the e-mail is incorrect.
Kevin Kofler
So what your saying is that the Mime type setting in her Outlook is wrong ?
How would she change that in Outlook ?
Jim wrote:
I have one person that sends me .jpg pictures in a Email and thunderbird can not display them , when I try to Open them I can only "Save" them to my Picture folder to view them. That person uses WindowsXP.
I recieve .jpg pictures from every one else and I can view them in Thunderbird.
have a look at; https://addons.mozilla.org/en-US/thunderbird/addon/2307 which may handle problem.
main problem is as kevin is telling you, if mime type is written wrong in email, thunderbird will have problem knowing what to do with attachment.
use <ctrl+u> to look at full email. you should have below message body something similar to;
|> --------------090209040005060100010505 |> Content-Type: image/jpeg; |> name="tbird app local folders.JPG" |> Content-Transfer-Encoding: base64 |> Content-Disposition: inline; |> filename="tbird app local folders.JPG"
this is how thunderbird knows that attachment is a jpeg file.
being that sender is using ms xp, there is your major problem. ms does not comply with email rfc. if sender does not has file with a '.jpg' extension, ask them to try sending with extension name.
On 05/30/2009 01:54 PM, g wrote:
Jim wrote:
I have one person that sends me .jpg pictures in a Email and thunderbird can not display them , when I try to Open them I can only "Save" them to my Picture folder to view them. That person uses WindowsXP.
I recieve .jpg pictures from every one else and I can view them in Thunderbird.
have a look at; https://addons.mozilla.org/en-US/thunderbird/addon/2307 which may handle problem.
main problem is as kevin is telling you, if mime type is written wrong in email, thunderbird will have problem knowing what to do with attachment.
use<ctrl+u> to look at full email. you should have below message body something similar to;
|> --------------090209040005060100010505 |> Content-Type: image/jpeg; |> name="tbird app local folders.JPG" |> Content-Transfer-Encoding: base64 |> Content-Disposition: inline; |> filename="tbird app local folders.JPG"
this is how thunderbird knows that attachment is a jpeg file.
being that sender is using ms xp, there is your major problem. ms does not comply with email rfc. if sender does not has file with a '.jpg' extension, ask them to try sending with extension name.
I think this may explain it here. Every picture shows this Content-Type
Content-Type: application/octet-stream; name="ATT00049.gif" Content-Transfer-Encoding: base64 Content-ID:00bc01c9e13f$7f193f00$7221D355@lynn
Thanks guy for your help I learn something new today. I could say in about 50 years I would know everything there was about Linux, to know it all.
NOT!!!
Jim wrote:
I think this may explain it here. Every picture shows this Content-Type
Content-Type: application/octet-stream; name="ATT00049.gif" Content-Transfer-Encoding: base64 Content-ID:00bc01c9e13f$7f193f00$7221D355@lynn
that will squirrel the bird.
something you could 'try for the fun of it'. cerate a new subfolder and *copy* email to it.
close thunderbird and then with a _plain_text_ editor, vi, kwrite, etc, open email and change 'application/octet-stream' to 'image/jpeg'.
delete '.msf' file associated to subfolder and delete 'panacea.dat' in your profile directory, '/home/jim/.thunderbird/????????.default/'.
reopen thunderbird and it will rescan your folders. then open email and click attachment to see if it will open as a '.jpg' file.
i have done a lot of things to modify thunderbird emails, but never tried above. it may work. it may not. if not, it is problem with 'octet-stream' coding attachment differently from what an 'image/jpeg' would be.
Thanks guy for your help I learn something new today.
you are very welcome.
'live and learn. die and forget'. may you live long to forget plenty. :)
I could say in about 50 years I would know everything there was about Linux, to know it all.
my first round with linux was when red hat was on floppies and latter a permanent install from cd. i am still learning and enjoying. :)
NOT!!!
perseverance.
On Sat, 2009-05-30 at 14:45 -0400, Jim wrote:
I think this may explain it here. Every picture shows this Content-Type
Content-Type: application/octet-stream; name="ATT00049.gif" Content-Transfer-Encoding: base64 Content-ID:00bc01c9e13f$7f193f00$7221D355@lynn
Didn't you say it was a JPEG file? Those headers are for an undifferentiated binary file whose name implies it's a GIF, which isn't the same thing.
Thanks guy for your help I learn something new today. I could say in about 50 years I would know everything there was about Linux, to know it all.
Your problem has nothing to do with Linux. The sender's email configuration (or host platform) is broken. They may not think it's broken if their Windows-using friends can see the images in messages, but it's still broken.
poc
Patrick O'Callaghan wrote:
Didn't you say it was a JPEG file? Those headers are for an undifferentiated binary file whose name implies it's a GIF, which isn't the same thing.
correct on gif. i did not realize i i told jim;
|> close thunderbird and then with a _plain_text_ editor, vi, kwrite, etc, |> open email and change 'application/octet-stream' to 'image/jpeg'.
until i read your post. i guess too much reading of '.jpg' in his post.
it should have read;
|> open email and change 'application/octet-stream' to 'image/gif'.
as i stated, i do not know how thunderbird will handle such a change because graphic files do have type embedded in first 9 bytes of file.
in fact, just to see what would happen, i sent my self a '.gif ' file and changed '.gif' to '.jpg'. thunderbird showed '.jpg', yet it did display correctly inline.
so, how ever thunderbird is reading file, file itself is being used to determine how to be displayed.
therefore, i tend to conclude that ms email client may be doing more to hide file type.
Your problem has nothing to do with Linux. The sender's email configuration (or host platform) is broken.
he said they are using windows. it is not broken, it is just another case of msbsos doing things 'their way'. 'the world is wrong. ms is right.'
On 05/30/2009 05:49 PM, Patrick O'Callaghan wrote:
On Sat, 2009-05-30 at 14:45 -0400, Jim wrote:
I think this may explain it here. Every picture shows this Content-Type
Content-Type: application/octet-stream; name="ATT00049.gif" Content-Transfer-Encoding: base64 Content-ID:00bc01c9e13f$7f193f00$7221D355@lynn
Didn't you say it was a JPEG file? Those headers are for an undifferentiated binary file whose name implies it's a GIF, which isn't the same thing.
Thanks guy for your help I learn something new today. I could say in about 50 years I would know everything there was about Linux, to know it all.
Your problem has nothing to do with Linux. The sender's email configuration (or host platform) is broken. They may not think it's broken if their Windows-using friends can see the images in messages, but it's still broken.
poc
Thunderbird is seeing the Attached pictures as .jpg, I noticed the .gif extension in Content. You know how Windows users are, they will not admit they have problems, it's that damn ole Linux.