TB should handle messages with incorrect MIME parts better and allow access to attachments if body is missing, see comment #11.



MailNews Core
2 years ago
a year ago


(Reporter: kpdozer, Unassigned)


(Blocks: 1 bug, {testcase})

Firefox Tracking Flags

(Not tracked)



(3 attachments, 2 obsolete attachments)



2 years ago
Created attachment 8754246 [details]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce:

I receive a message that contains an attachment * .doc

Actual results:

Attachment appears as text in the message body. There is no possibility saving attachments.

Expected results:

Attachments should appear in a list at the bottom of the letter. Must be able to save an attachment.


2 years ago
Severity: normal → major


2 years ago
Keywords: testcase
Attachment #8754246 - Attachment mime type: message/rfc822 → text/plain
I don't know how this message was generated.

It does NOT contain a .doc attachment. The attachment is HTML. Read the message source:

Content-Disposition: attachment;
Content-Transfer-Encoding: base64
Content-Type: text/html;

TB displays the HTML as message body, since there is otherwise no message body.

There's little we can do about that. The message is in many ways corrupt.

Since TB displays the HTML, I copied that into a HTML file, which looks mainly like mojibake (https://en.wikipedia.org/wiki/Mojibake).
Last Resolved: 2 years ago
Resolution: --- → INVALID

Comment 3

2 years ago
However, this investment has the extension * .doc. And this document is opened in Microsoft Word. The main problem is that I can not save it as a file. Any e-mail service (mail.ru, yandex.ru etc.), which has a web interface makes it without problems. I have to use the extension "Show All Body Parts 1.2" to save the attachment. I do not consider the problem solved.


2 years ago
Resolution: INVALID → ---

Comment 4

2 years ago
I add. The name of the topic, I did not specify what kind of content is the file actually is. I ask to pay attention only to the file extension * .doch
Created attachment 8754299 [details]
Manuall corrected message.

As I said, the message was corrupt. I've manually corrected it, so you now have a plain text part and an attachment. I can't open the attachment, but perhaps you can.
As I said, the message is corrupt. We have no resources to support users who present corrupt messages.

Although you may not consider the problem solved, no one will work on it. If you found an add-on that offers a work-around, even better.

Please respect the decision to close this bug.
Last Resolved: 2 years ago2 years ago
Resolution: --- → INVALID
Add-on comment says:

You might need this if someone sends you a message with a “hidden” attachment, i.e., a message whose structure is *malformatted* such that Thunderbird is *“correct” not to display it*, but you still need to get access to it.
Summary: *.doc Attachments are not displayed → Message with incorrect MIME parts does not show text/html part as *.doc attachment
Created attachment 8754315 [details]
HTML contained in the message.

OK, I base64 decoded the text/html part. This time it looks right.
It's not .doc, it's HTML data.
Attachment #8754287 - Attachment is obsolete: true
Created attachment 8754316 [details]
Manually corrected message.

The message attachment contains HTML, not MS Word format. You can just open this with Firefox. MS Word will open it, too ;-)
Attachment #8754299 - Attachment is obsolete: true

Comment 10

2 years ago
I understand all that you have written to me. And I understand that the attachment was not formed properly and may not be a man. Still Tunderbird can not gracefully handle this situation. Why can not I save attachments even if I turn off the "Display attachments inline"? Web interfaces provide an opportunity to preserve such an attachment. Okay. It does not matter. I will use the extension. Many thanks.
OK, you can always make software more error tolerant. But we have no resources for that.

OK, I'll reopen this with a different summary. Don't expect any action here soon ;-(
Severity: major → enhancement
Ever confirmed: true
Resolution: INVALID → ---
Summary: Message with incorrect MIME parts does not show text/html part as *.doc attachment → TB should handle messages with incorrect MIME parts better and allow access to attachments if body is missing, see comment #11.


2 years ago
Component: Untriaged → MIME
Product: Thunderbird → MailNews Core
Version: 45 Branch → unspecified
There is a hidden preference:

Set this to true. Then under
View > Message Body as
you set "All body parts". That will give you access to all the parts including the attachment you're missing.

I think this is graceful enough.
Last Resolved: 2 years ago2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.