User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.23) Gecko/20110920 Firefox/3.6.23 ( .NET4.0E) Build ID: 20110920075126 Steps to reproduce: PDF attachments show up with a red x and are not able to be opened. This was broken in earlier T'bird. Fiexed in 6.0, now broken again. VERY FRUSTRATING! I am attaching a screen shot showing this.

xref 674473 and 684844. Can you look into the email and tell use how the attachment is defined (use the view source funtion in thunderbird) ?

Content-Type: application/octet-stream;name="23531.011 Eval Summary.pdf" octet-stream is bad and that's why we don't show it.

Thanks. But what must I tell the sender to do so I'll be able to read their pdf attachments in the future, as these come from a business associate that I must interact with daily. When you say 'bad' - do you mean malware/virus prone? I can open the attachments in comcast webmail client. Am I taking a risk by doing that? Thanks for the fast replies!

Thunderbird can't know it is a pdf and how to open it. I probably is not good to guess the file type by the extension when the sender marked it as a general binary blob=octet stream. Are you at least offered the option to save the attachment to disk?

Not not a viruse but some configuration on his machine doesn't send the proper mime type for PDFs.

Do we expect the sender's client to send the proper mimetype? How does it find it out? Does TB do it?

Same problem as next bug? > Bug 517796 : thunderbird does not let me view application/octet-stream attachments Note-1: Next bug exists for convenient operation for application/octet-stram. > Bug 559014 : provide open-with dialog for application/octet-stream Note-2: Bug like next occurs. > Bug 576663 : TB3.1 does not recognize the action of the NZB file. TB 2.0.0.24 Does it correctly. > (if .NZB file=XML_format is sent with application/octet-stream > instead of correct application/x-nzb, Tb 3.1 adds ".xml" to file > name when Tb passes data to application.)