We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Thunderbird adding .txt to attachment

  • 2 件の返信
  • 1 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: PGGamer

more options

After Thunderbird updated to the newest version I can not open PDF attachments (Emails before the update work fine). When I double click on the attachment filename123.pdf and Thunderbird asks to chose to open it says it's a Text Document. So I say Open with Foxit Reader. When Foxit Reader opens it says filename123.pdf.txt not found. For some reason Thunderbird is adding a .txt at the end. I can save the file and open it just fine but I can't open it directly from Thunderbird. I've tried also opening it with Adobe Reader I've gone into Options-Attachments- and deleted and Actions

After Thunderbird updated to the newest version I can not open PDF attachments (Emails before the update work fine). When I double click on the attachment filename123.pdf and Thunderbird asks to chose to open it says it's a Text Document. So I say Open with Foxit Reader. When Foxit Reader opens it says filename123.pdf.txt not found. For some reason Thunderbird is adding a .txt at the end. I can save the file and open it just fine but I can't open it directly from Thunderbird. I've tried also opening it with Adobe Reader I've gone into Options-Attachments- and deleted and Actions

選ばれた解決策

Actually sounds like a defective mail client sending to me.

Open an email with such and attachment. Open message source (ctrl+U) Find (ctrl+F)

Content-Disposition: attachment;

once that is located along with the PDF file name. Or Find again (Ctrl+G) until you do

What is the content-type given as?

The blocks you will be looking at will look somewhat like the following.

Content-Type: application/pgp-keys;
 name="0xF0B3DEEB56268743.asc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="0xF0B3DEEB56268743.asc"

For a PDF file this should be given as application/pdf. IANA registration here https://www.iana.org/assignments/media-types/media-types.xhtml#application

My guess it is is given as something incorrect like text or application\octet stream. That one appear to be popular with .net developers that really do not understand mime types at all, so fumble in the dark for "something that works"

What many windows developers simple can not apparently grasp is the file type is declared in the mime type declaration and the file extension is not used. It make is much harder for executable malware to slip in like it used to with outlook express. But for windows only folks they sort of just don't get it. To borrow from the writings of Robert Heinlen, they don't GROK it.

この回答をすべて読む 👍 1

すべての返信 (2)

more options

選ばれた解決策

Actually sounds like a defective mail client sending to me.

Open an email with such and attachment. Open message source (ctrl+U) Find (ctrl+F)

Content-Disposition: attachment;

once that is located along with the PDF file name. Or Find again (Ctrl+G) until you do

What is the content-type given as?

The blocks you will be looking at will look somewhat like the following.

Content-Type: application/pgp-keys;
 name="0xF0B3DEEB56268743.asc"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="0xF0B3DEEB56268743.asc"

For a PDF file this should be given as application/pdf. IANA registration here https://www.iana.org/assignments/media-types/media-types.xhtml#application

My guess it is is given as something incorrect like text or application\octet stream. That one appear to be popular with .net developers that really do not understand mime types at all, so fumble in the dark for "something that works"

What many windows developers simple can not apparently grasp is the file type is declared in the mime type declaration and the file extension is not used. It make is much harder for executable malware to slip in like it used to with outlook express. But for windows only folks they sort of just don't get it. To borrow from the writings of Robert Heinlen, they don't GROK it.

more options

So I think you are right. Found out the only emails with issues are from an invoicing service. This is what I found Content-Type: ;

name="5253.pdf";

Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="5253.pdf"; The Content-Type seems to be blank.