Bug 548067 - thunderbird does not decode base64 emails
Summary: thunderbird does not decode base64 emails
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-16 14:29 UTC by Tom Cross
Modified: 2018-04-11 15:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-17 17:05:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
A base64 encoded email (1.41 KB, text/plain)
2009-12-16 14:29 UTC, Tom Cross
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 535584 0 None None None Never

Description Tom Cross 2009-12-16 14:29:40 UTC
Created attachment 378765 [details]
A base64 encoded email

Description of problem:
An email that is base64 encoded is not decoded.  Making it somewhat difficult to read.  Using another mail client allows me to read that email just fine, leading me to believe that it is thunderbird, not the email itself.


Version-Release number of selected component (if applicable):
thunderbird-3.0-3.fc11.x86_64
thunderbird-lightning-1.0-0.11.20090715hg.fc11.x86_64


How reproducible:
Everytime I receive a base64 encoded email

Steps to Reproduce:
1. Get base64 email
2. attempt to read
3. scratch head
  
Actual results:
Thunderbird will show the contents of the email like this:

VVBEQVRFIGludmVuX21hbmFnZW1lbnRfcG8gU0VUIGN1c3RfYmluID0gJ0kwMi0wMS0wMicgIFdI
RVJFIHBvX2tleSA9MTE2NDQ5IEFORCBsaW5lbnVtID0gNDA=

Expected results:

Decode my message!  Like evolution does.

Additional info:

Sample base64 encoded message attached.  It appears a perl script that uses MIME::Lite to send messages to me is especially good at creating base64 emails that thunderbird happily forgets to decode.

Comment 2 Matěj Cepl 2009-12-17 17:05:50 UTC
We filed this bug in the upstream database (https://bugzilla.mozilla.org/show_bug.cgi?id=535584) and believe that it is more appropriate to let it be resolved upstream.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.


Note You need to log in before you can comment on or make changes to this bug.