Цей вебсайт матиме обмежену функціональність, доки ми проводимо його обслуговування для поліпшення роботи. Якщо прочитана стаття не розв'язала вашу проблему і ви хочете поставити питання, наша спільнота підтримки з радістю допоможе вам на @FirefoxSupport у Twitter та /r/firefox на Reddit.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. 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.