1364055 - Base64-encoded binary part in non-multipart message wrongly saved encoded

Status: RESOLVED DUPLICATE of bug 1361422

(Thunderbird :: Untriaged, defect)

Description

[Ale]

Attachment: Message triggering the "attachment" saving problem.

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170504112025

Steps to reproduce:

I received a mail from our voicemail system, consisting of a single part (not a multipart message) encoded in Base64 and being a (binary) WAV file, and tried to save the attachment. See the attachment of this bug for a message triggering the issue (some headers redacted for privacy of concerned users, but otherwise untouched—the attached voice message is just a hangup noise).

I'm using Thunderbird 52.1.0 (32-bit) on Windows 7 (64-bit).


Actual results:

The file contained in the message got saved as-is (encoded in Base64) and could thus not be played. This issue only happens since 1-2 weeks, I'm not sure whether a Tunderbird update is involved or a change server-side. Nevertheless, the received mail has no evident malformed headers and seems perfectly valid, but its encoding is ignored when saving.


Expected results:

The file contained in the message should have been saved after decoding the Base64 encoding. This only seems to happen with non-multipart messages, and only when saving the "attached" file. I tried with a text/plain message encoded in Base64 (but having a Content-Disposition header with a file name): the encoded message is _displayed_ correctly, but saved encoded if the file is saved to disk. Converting the message to a multipart/mixed message with a boundary does NOT trigger this bug.

Comment 1

[Jorg K (CEST = GMT+2)]

Will be fixed in TB 52.1.1. Sorry about the inconvenience. You can go back to 52.0.1 or use a Daily ESR build from here:
http://ftp.mozilla.org/pub/thunderbird/nightly/2017/05/2017-05-10-03-02-03-comm-esr52/

Comment 2

[Ale]

Thanks for info, and sorry for the duplicate bug, I didn't find the "original" one for some reason, before submitting mine... probably wrong keywords.