Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

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.