Closed
Bug 248584
Opened 20 years ago
Closed 19 years ago
Option to force text file attachments to be uuencoded (BASE64)
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: bugz743, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 If I compose a mail message and add an attachment that is a text file, the file is NOT uuencoded. However, this is a real problem if the text file contains the string "From" as the first word on a line (something that happens in my files quite often). In this cirsumstance, many mail servers will change the "From" to ">From". Archiving the text file first is not really feasible as many of my recipients do not have the tools (or technical skill) to un-archive. An option to force uuencoding for ALL files (and not just "binary" files) would be welcome. Reproducible: Sometimes Steps to Reproduce: 1. Attach a text file with the word "From" as the first word on a line. 2. Mail it someone. 3. Actual Results: You will (probably) see the "From" changed to ">From". Expected Results: Allow me to force the attachment to be uuencoded.
related: bug 121946, bug 121947, bug 194382 Fixing those would make this bug redundant.
Comment 2•20 years ago
|
||
The three bugs in comment #1 appear to be about escaping "From" in an attachment. There are other problems (see bug #249049 for an example) with broken clients that we all have to put up with if we want to realisticly interact with the rest of the world.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: sspitzer → mail
Comment 3•19 years ago
|
||
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•