Forwarding uuencoded news post results in uuencoded part being sent as is, instead of properly constructed MIME attachement



14 years ago
14 years ago


(Reporter: przemyslaw, Assigned: mscott)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pl-PL; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Thunderbird 1.0 Polish Localisation, Version 1.7.5: 2004120606

Uuencoded messages in newsgroups contains binary file encoded in uuencode. When
such message is shown in the newsgroup, Thunderbird properly recognize such
format and display picture encoded in uuencode or permits saving attachement to
However, when user tries to forward message containg attachement in uuencode, he
or she gets uuencoded file as plain text within body of the message instead of
properly formed mime attachemnt

Reproducible: Always

Steps to Reproduce:
1. View message in newsgroups containg uuencoded file (file behave as normal
MIME attachement).
2. Press forward button on toolbar.
3. Forward message using mail account to SMTP recipient.

Actual Results:  
Message contain uuencoded file in body of the message, ie.
begin 236 example.jpg
M_]C_X `02D9)1@`!`@$`2 !(``#...

Expected Results:  
Uuencoded file should be sent as a properly formed MIME attachement.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.