Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Thunderbird adding .txt to attachment

  • 2 antwurd
  • 1 hat dit probleem
  • 12 werjeftes
  • Lêste antwurd fan 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

Keazen oplossing

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.

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (2)

more options

Keazen oplossing

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.