Mozilla 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

When I receive an email as a file attached to an email TB renames it "ForwardedMessage.eml". Why does it do this and can I prevent it happening?.

  • 5 प्रत्युत्तर
  • 1 यह समस्या है
  • 12 views
  • के द्वारा अंतिम प्रतियुतर Godfreyp

more options

As an example the email my colleague sent me from Outlook included two attachments that were emails. In the attached partial screenshot (from Squirrelmail) the files start 04.a RE: Draft and 05. AW:FW:ISAP. When I look at this email in TB both attachments have the name "ForwardedMessage.eml". Is there anything I can do to correct this?

As an example the email my colleague sent me from Outlook included two attachments that were emails. In the attached partial screenshot (from Squirrelmail) the files start 04.a RE: Draft and 05. AW:FW:ISAP. When I look at this email in TB both attachments have the name "ForwardedMessage.eml". Is there anything I can do to correct this?

चुने गए समाधान

If the source is Outlook, it will be the way Outlook encodes the information. Check the mime type of the attached files in the message source and that the information is complete and correct. Microsoft have a nasty habit of transmitting everything as Content-Type: application/octet-stream; instead of more specific and accurate mime types eg Content-Type: application/pdf and expecting the rest of the world to code around their sloppiness.

संदर्भ में यह जवाब पढ़ें 👍 1

All Replies (5)

more options

Which part of this is the concern? The renaming, or the .eml filetype?

more options

The renaming. It deletes the original file name (which is not helpful) and results in multiple "ForwardedMessage.eml file leading to name conflicts.

I have added the screenshot I could not add originally.

more options

चयनित समाधान

If the source is Outlook, it will be the way Outlook encodes the information. Check the mime type of the attached files in the message source and that the information is complete and correct. Microsoft have a nasty habit of transmitting everything as Content-Type: application/octet-stream; instead of more specific and accurate mime types eg Content-Type: application/pdf and expecting the rest of the world to code around their sloppiness.

more options

Thanks Matt (Erroneous duplicate that I do not appear to be able to delete).

Godfreyp द्वारा सम्पादित