Closed Bug 340271 Opened 20 years ago Closed 20 years ago

with outgoing encoding set to utf8, plain text attchments are base64 encoded

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 248639

People

(Reporter: rene.herman, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060516 SeaMonkey/1.0.2 I could not find a category for message composition/sending... Seamonkey-1.0.2 mail shares a longstanding bug with Thunderbird. When the outgoing encoding is set to UTF8, all attachments are sent Base64 encoded. This is very annoying for posting to lists where binary attachments are not welcome -- if you forget to switch to ISO8859-15 (or whatever) or did not notice the mailer switched to UTF8 itself in reply to an incomming UTF8 messahe, you end up posting things luke unidiffs base64 encoded to development lists. Reproducible: Always Steps to Reproduce: 1. Set outgoing encoding to UTF8 2. Attach a plain text file 3. See it being base64 encoded Actual Results: A Base64 encoded attachment Expected Results: A plain text attchament As said; the bug's shared with Thunderbird where it's not being fixed for years now. Have my hopes set on seamonkey...
*** This bug has been marked as a duplicate of 248639 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.