No longer can open PDF files from mail folders

[mKovy]

Since upgrading to the new version of Thunderbird, 52.1.0 (32-bit) a couple of days ago, I can no longer open new PDF files sent or any previously sent PDF files in mail folders. I'm using 2017 Adobe Acrobat Reader.
"Adobe Acrobat Reader could not open the filename.pdf because it is either not a supported file type or because the file is damaged"
I'm hoping the upgrade did not corrupt the thousands of pdf in various mailfolders. I can open up PDF files outside Thunderbird that have been previously saved to the hard drive (prior to upgrade) and can open up PDF files online with Firefox using the same Adobe program.
I've even installed Foxit and after changing default reader to Foxit. I can open other pdfs stored on hard drive, but give me "Format error: Not a PDF or currupted." when attempting to open a PDF attachment within Thunderbird. Saving pdf to hard drive then trying to open it up give the error too.
So to me it appears this issue affects attached PDFs emails in various Thunderbird folders.
I have 5 POP email accounts and 1 IMAP account.
Any assistance would be appreciated.

[tanstaafl]

I have numerous PDF file attachments and have no problem reading them from Thunderbird 52.1.0 under Windows 10 using "Nitro Reader" (a free PDF editor/viewer that I prefer over Acrobat Reader and Foxit Reader). I haven't noticed anybody else reporting similar problems, in other threads.

Its possible the mimetypes.rdf file in the profile is corrupt (that occurs sometimes, the workaround is to delete it, and when Thunderbird restarts it replaces the file. Then you just set what to do with attachments again) but that seems unlikely if you have problems opening a .PDF file that you saved from an attachment to your hard disk, and opening it directly.

The storage format used by mail folders didn't change in 52.*. Do you have any signs of a corrupt folder such as message fragments, resurrected messages that you had previously deleted, or invalid dates such as January 1, 1970 or December 31, 1969 (what it defaults to when the Date: header is missing) in the folder listing?

Try logging into webmail using a browser for the IMAP account. See if you have the same problem opening a .PDF file attachment. If you don't, then the remote folders (and your messages for that IMAP account) are okay.

[mKovy]

deleting mimetypes.rdf did not solve it. Should also mention some folders are missing, I see the msf files in mail/localfolders/inbox, but they do not show in Thunderbird. Tried delete the msf of the missing folder while TB is closed and reopening TB does not restore the folders. The folder containing all the subfolders of the emails in question is still intact as well as the emails but can't open the email.
This bit of info may help to. If I forward the email with PDF attached back to me, I can open up the attachment.

[tanstaafl]

*.msf files are basically a cache of the folder listing. They don't have any messages and will be re-created if needed from the contents of the corresponding mbox file, which has the messages for that mail folder. "inbox." is the mbox file (has the messages) for the inbox folder, "inbox.msf" is the cache of the folder listing (a so-called index file), and "inbox.sbd" is a renamed directory used to help organize mail folders into a hierarchy.

A mbox file is a 7-bit ASCII text file containing all of the messages for the corresponding mail folder, named after the folder, but with no file extension. You can open it with a text editor (DO NOT use a word processor) and read the contents to verify it has messages, though it will be very user unfriendly as in each message you will see dozens of headers that are normally hidden, raw HTML tags rather than interpreted HTML, and big blocks of run together characters that is a base64 encoded copy of any binary data (such as a image attachment).

Deleting the *.msf file is a over-rated attempt to fix corruption. See http://kb.mozillazine.org/Compacting_folders#Real_fix . If the mbox file is gone and you delete the corresponding .msf file there will be no trace of the folder. If the mbox file exists and the *.msf file is gone Thundebrrid will re-create the *.msf file.

[Boostland]

I am also seeing some users with the same issue opening or saving a PDF attachment to the HDD from a gmail imap account since the upgrade to 52.1.0

PDF file opens fine from Gmail either with their viewer or if you save attachment to HDD and open with Adobe reader.

Seems to be some sort of problem decoding the PDF file, from what I can see so far the emails that have no body text and only the attachment are affected.

[tanstaafl]

What is different about the users who don't have this problem?
Do the users that have this problem have it with every message with a *.pdf attachment, or just some?
If they copy one of the messages that has this problem to "Local Folders" does the problem still occur with the copied message?

[Boostland]

I added some more info to another post that does not appear to be approved as yet.

I flipped to another screen when I first posted and did not see the message about approval so thought that the post disappeared.

When you forward it appears to fix it as it adds a body to the email forwarding to your own email may be a work around for now.
Or to open the PDF simply forward email then before you send you can open the attachment in the top right.
Then close the email without sending.

[tanstaafl]

If you use view -> message source or Control-U to look at the raw message source of one of these messages before you forward it, what are the values of each Content-Type: and Content-Disposition: header? For example I have a HTML message with a PDF file attachment. It has:

Content-Type: multipart/mixed;
boundary="------------1E23D1A6B8719FBB6FC0E043" shortly after the subject. Then

Content-Type: text/html; charset=utf-8 near the start of the message body and then

Content-Type: application/pdf;
name="Quick Carbon 1GCBoston Globe32215.pdf"
Content-Disposition: attachment;
filename="Quick Carbon 1GCBoston Globe32215.pdf"

for the PDF file attachment.

[Boostland]

MIME-Version: 1.0
Importance: Normal
X-Priority: 3 (Normal)
X-Mailer: SAP NetWeaver 7.03
Content-Type: application/pdf;
name="New Purchase Order.pdf"
Content-Transfer-Encoding: base64
Content-Description: New Purchase Order

[Boostland]

Copying message from Imap to local inbox still does not allow PDF to decode correctly and open with Adobe Reader or Edge.

[Boostland]

Problem is repeatable on a freshly installed profile.

Emails without a body from NetWeaver 7.03 are failing to decode PDF from multiple senders.

Other emails with body text appear to work fine.

[tanstaafl]

The headers you copied and pasted didn't include the first Content-Type: header for the message (it's near the Subject:) which basically specify what type of message it is. If that is because they are missing Thunderbird might refuse to display anything (since it has no clue what type of message you sent) , never mind let you open an attachment. That is consistent with it sort of working after you forward it, because that would make it part of a valid message with a real Content-Type: header.

I suggest you install an older version of Thunderbird in a different directory (select custom setup to do that). That will reuse the existing profile. See if that effects the problem, especially for the IMAP account. See http://kb.mozillazine.org/Go_back_to_an ... hunderbird . I suggest you use version 45.8.0 (prior major version). A english-us windows version of its setup program is at https://ftp.mozilla.org/pub/thunderbird ... 45.8.0.exe

[mKovy]

I feel better that this issue is duplicatable, that means a fix will be coming. The IMAP account is there but has not actually been in use for a few years. I can verify the emails that I can't open the PDF that are in multiple folders, do not have any body text. Now if I forward any of those emails back to me, I can open up the PDF. Just can't open any that were previously sent OR new emails from the same source with no body text.

[Boostland]

Full Headers (some names edited)

Code: Select all

From - Mon May 08 18:08:53 2017
X-Mozilla-Status: 1001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Delivered-To: sales@test.com.au
Received: by 10.200.39.103 with SMTP id h36csp51513qth;
        Thu, 16 Mar 2017 15:19:03 -0700 (PDT)
X-Received: by 10.237.38.194 with SMTP id q60mr11524825qtd.84.1489702743239;
        Thu, 16 Mar 2017 15:19:03 -0700 (PDT)
Return-Path: <liz@coal.com.au>
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com. [216.82.243.198])
        by mx.google.com with ESMTPS id x33si4971028qta.126.2017.03.16.15.19.03
        for <sales@hvfs.com.au>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 16 Mar 2017 15:19:03 -0700 (PDT)
Received-SPF: pass (google.com: domain of liz@coal.com.au designates 216.182.243.198 as permitted sender) client-ip=216.182.243.198;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of liz@coal.com.au designates 216.82.243.198 as permitted sender) smtp.mailfrom=liz@coal.com.au
Return-Path: <liz@coal.com.au>
Received: from [216.82.242.46] by server-6.bemta-8.messagelabs.com id 6F/4A-29357-65F0BC85; Thu, 16 Mar 2017 22:19:02 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrEIsWRWlGSWpSXmKPExsWSummypW4Y/+k
  Ig6anKhZ9WyayOzB6HL12mSWAMYo1My8pvyKBNWP3N/GCc4/YK9r/X2dvYLxxlb2LkZNDSGAX
  o8SqeUA2F5C9l1FiV99sJpAEi4CqxNGut2A2m4CJxPlZK1lBbGEBPYlvH/6zgdgiAuIS278eZ
  QaxeQUCJS68essOYQtKnJz5hAXE5hQQkui42gnWKyEgJjFh3S9mCFtG4sOJ92BxZoEAiTfbJ7
  FD2IoSU7ofQtlWEtven2LsYuQAOk5L4u1PvgmM/LOQbJiFpHsWku5ZSLoXMLKsYtQoTi0qSy3
  SNTTXSyrKTM8oyU3MzNE1NLDQy00tLk5MT81JTCrWS87P3cQIDM96BgbGHYwbPkYeYpTkYFIS
  5e08eSpCiC8pP6UyI7E4I76oNCe1+BCjDAeHkgQvA9/pCCHBotT01Iq0zBxgpMCkJTh4lER4T
  UDSvMUFibnFmekQqVOMuhyPeo+9YRJiycvPS5US533JC1QkAFKUUZoHNwIWtZcYZaWEeRkZGB
  iEeApSi3IzS1DlXzGKczAqCfM6gqziycwrgdv0CugIJqAj3n44AXJESSJCSqqB8eExHb0vnll
  cV/eHCX9lW7kghUHHxM3UrVtXLPvGk3cnOKeulz3d56JT3175+BLXk02zQ7m/auY9U+rb+vq8
  3pYdnJ9DXzY88qj73/WHbVbgyzCT3D9PHlRyeX7/e/z91cK/334aK0/6I7bWPvLHjAW9b3PDh
  Y+WNVw+vXHHvn+Sjw78nX3W9bgSS3FGoqEWc1FxIgCARFSW1QIAAA==
X-Env-Sender: liz@coal.com.au
X-Msg-Ref: server-3.tower-96.messagelabs.com!1489702739!21185974!1
X-Originating-IP: [101.178.147.57]
X-StarScan-Received:
X-StarScan-Version: 9.2.3; banners=coal.com.au,-,-
X-VirusChecked: Checked
Received: (qmail 24331 invoked from network); 16 Mar 2017 22:19:01 -0000
Received: from unknown (HELO YAU-DS1-VMS02.coal.com.au) (101.178.147.57)
  by server-3.tower-96.messagelabs.com with AES128-SHA256 encrypted SMTP; 16 Mar 2017 22:19:01 -0000
Received: from YAU-DS1-VMS01.coal.com.au (10.225.77.76) by
 YAU-DS1-VMS02.coal.com.au (10.225.77.77) with Microsoft SMTP Server (TLS)
 id 15.0.1076.9; Fri, 17 Mar 2017 09:18:59 +1100
Received: from COAL.COM.AU (10.225.173.66) by YAU-DS1-VMS01.coal.com.au
 (10.225.7.76) with Microsoft SMTP Server id 15.0.1076.9 via Frontend
 Transport; Fri, 17 Mar 2017 09:18:59 +1100
Date: Fri, 17 Mar 2017 09:18:54 +1100
From: liz <liz@coal.com.au>
Subject: New Purchase Order
To: <sales@test.com.au>
Message-ID: <RDP4200000008391940092D0A8C29E021ED782D2D26D3D8017C6@COAL.COM.AU>
MIME-Version: 1.0
Importance: Normal
X-Priority: 3 (Normal)
X-Mailer: SAP NetWeaver 7.03
Content-Type: application/pdf;
	name="New Purchase Order.pdf"
Content-Transfer-Encoding: base64
Content-Description: New Purchase Order

[Boostland]

It was working fine on 45.8.0 and still works on that version when I reinstalled it to test just now.

Does not work in the 53 beta or the 54 alpha they behave exactly the same as the 52.1.0 version.