This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

Inline screenshot from Outlook won't display

  • 2 respostas
  • 1 has this problem
  • 16 views
  • Last reply by jehurd

jehurd
jehurd
more options

2 PCs running latest version of TB: 52.1.0. When a screen shot, embedded in an email, from a MS Outlook email is opened, the screen shot displays as it should on 1 PC, but not on the other PC. One PC is running Windows 10, the other runs W-7. I have tried all the advice out lined in this article: http://mzl.la/1BsOFeL to no avail. I tried to compare the about:config outputs of both PCs side by side, but they do not match line by line. The only items I spotted that do not match for certain are that the W-7 box [issue] is running NT 6.1 and the [working] box is on NT 10.0. I don't see how that can be causing the issue. More strangely, if the Outlook sender sends the email to the W-7 box and CCs me in on the [same] email to the W-10 box, then the in line screen shot appears correctly on BOTH PCs [!]. Again, this should not have anything to do with it, but...... 2 More clues: when the image does not display on the W-7 box, there is a line where the image should be with a file name something like "Image001.png@b21s584". In other words, what appears to be a.png image file with the "@" sign & various letters and numbers immediately after the "png". Further, there is an attachment for the email listed as "winmail.dat". While the appended/corrupted png file designation may be confusing TB, the image displays correctly on the W-10 box and the is no attachment appended to the email on the W-10 box.

I am out of ideas. Any suggestions?

2 PCs running latest version of TB: 52.1.0. When a screen shot, embedded in an email, from a MS Outlook email is opened, the screen shot displays as it should on 1 PC, but not on the other PC. One PC is running Windows 10, the other runs W-7. I have tried all the advice out lined in this article: http://mzl.la/1BsOFeL to no avail. I tried to compare the about:config outputs of both PCs side by side, but they do not match line by line. The only items I spotted that do not match for certain are that the W-7 box [issue] is running NT 6.1 and the [working] box is on NT 10.0. I don't see how that can be causing the issue. More strangely, if the Outlook sender sends the email to the W-7 box and CCs me in on the [same] email to the W-10 box, then the in line screen shot appears correctly on BOTH PCs [!]. Again, this should not have anything to do with it, but...... 2 More clues: when the image does not display on the W-7 box, there is a line where the image should be with a file name something like "Image001.png@b21s584". In other words, what appears to be a.png image file with the "@" sign & various letters and numbers immediately after the "png". Further, there is an attachment for the email listed as "winmail.dat". While the appended/corrupted png file designation may be confusing TB, the image displays correctly on the W-10 box and the is no attachment appended to the email on the W-10 box. I am out of ideas. Any suggestions?

jehurd modificouno o

Chosen solution

get the person that is sending corrupt messages to fix their copy of outlook, or have their system administator fix Micrsift exchange if that is the source of the problem.

See https://support.microsoft.com/en-us/help/138053/how-to-prevent-the-winmail.dat-file-from-being-sent-to-internet-users

I am guessing the windows 7 box had the appropriate add-on installed to allow non Microsoft mail applications to interpret the winmail.dat file, but really the sender needs to fix their mess, not you install a workaround.

See https://support.mozilla.org/en-US/kb/what-winmaildat-attachment

Ler a resposta no contexto 👍 0

All Replies (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Chosen Solution

get the person that is sending corrupt messages to fix their copy of outlook, or have their system administator fix Micrsift exchange if that is the source of the problem.

See https://support.microsoft.com/en-us/help/138053/how-to-prevent-the-winmail.dat-file-from-being-sent-to-internet-users

I am guessing the windows 7 box had the appropriate add-on installed to allow non Microsoft mail applications to interpret the winmail.dat file, but really the sender needs to fix their mess, not you install a workaround.

See https://support.mozilla.org/en-US/kb/what-winmaildat-attachment

jehurd
jehurd Question owner
more options

Thanks for the response. From other online research, this seem to be the cause. I now need to convince staff here to notify the company sending them that it is their issue and they need to fix it :)