My major client uses mostly Microsoft products: Outlook + Exchange and Office. It turns out that the compatibility with OpenOffice is limited when it comes to large documents and defined styles, so I upgraded my old Office 2003 to Office 2010 on my Windows 7 PC desktop. And then ran into another problem: file corruption in email attachments.
I use Thunderbird 3 to fetch mail via IMAP from the Exchange server, but every time someone sent me a Word document, I’d get this error message about not being able to open it in Word 2010 because it was corrupted. If I used the Outlook Web Access client it worked fine, so it wasn’t a corruption at the server. And Word 2003 used to open the same types of documents sent to me by the same person, so at first I wondered if it was something to do with Word’s upgrade.
Hunting around Mozilla’s getsatisfaction.com web site gave me a pointer to Special Thunderbird IMAP Settings at the Michigan State University’s Physics-Astronomy Computing Support Site (they have interesting articles on lots of related issues). Basically, the issue is due to Thunderbird chunking the file as it pulls it down from the server, which introduces some corruption. The same apparently also applies to using the Gmail IMAP server, although I haven’t noticed any issues with that.
To fix it, go into Tools…Options. Select the Advanced tab, click on “Config Editor”. Search for chunks. Click on the resulting settings to make sure they’re all set to “user set” “false” (they will be in bold once this is done). Close the window and press OK to save. I then restarted Thunderbird to be on the safe side (not all config settings take effect without a restart and I didn’t feel like testing it). Then (and the web page I linked to didn’t include this step), right-click on the account name in the list of accounts/folders on the left (in the standard window configuration), and choose “Properties”. You should see a “Repair Folder” button. Click on this to make Thunderbird fetch everything again, with the new settings.
Problem solved! I still don’t know why Word 2010 had problems with documents that Word 2003 could read, but I don’t care enough to try to find out.