User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 I have filed a bug report with SM ) who asked that I file one with TBird as well. We are seeing an influx of users reporting that docx files sent from SM are not properly being displayed in Thunder Bird. The binary data of the docx file is being displayed in the message body as seen in this screen shot : http://www2.potsdam.edu/yacketrj/2010-06-22%20at%209.37.22%20AM.jpg It appears to be a Content-Type issue where the Content-Type: appears to have a line feed before the type forcing the data to a second line (see screen shot). When Thunder Bird is used to send the same docx file everything behaves as expected. Arguably this could be an issue where Thunder Bird is not properly handling extra spaces (?) line feeds (?) before the Content-Type data. Additionally if you attempt to open the docx file from within Thunder Bird notepad is used. Reproducible: Always Steps to Reproduce: 1. Send a docx attachment via SM 2. Open Mail in TBird and watch the binary data fill up the message window 3. Open the attachment and watch notepad being launched Actual Results: see 'Steps to Reproduce' Expected Results: Nothing displays in message window and TBird launches Windows 7 to open the docx attachment. See bug report with SM for more info as well https://sourceforge.net/tracker/?func=detail&atid=100311&aid=3020303&group_id=311

I think this is a dup - I think there's also a patch in the dup but we're waiting for a unit test that works, iirc.

I searched for docx, binary and a few other key words and did not find anythign relevant. If this is a dup can you kindly point me to the dup?

bug 87653 is the bug I was thinking of.

dup of bug 538641?

Ronald do you agree with comment #3 or comment #4? It is this a dupe?

RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change has been made in error, please respond to this bug with your reason why.