Closed
Bug 307705
Opened 19 years ago
Closed 16 years ago
Sending content-type multipart/appledouble as encoding 8bit
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jerry.lundstrom, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050521 Firefox/1.0.4
Build Identifier: Thunderbird 1.0.6 for MacOS X
When sending an email with thunderbird in MacOS X that thunderbird hasn't assign
to a program thunderbird or mac says its content is "multipart/appledouble" and
thunderbird doesn't seem to know how to send it so it sends it with
"Content-Transfer-Encoding: 8bit" which isnt good when sending binary data such
as .doc .psd files.
I suspect that the content-type "multipart/appledouble" is some form of apple
magic that runs a program to detect what it really is, even so this shouldnt be
a problem.
I also expect (havn't had time to look in the sourcecode) that thunderbird sends
unknown content-types as 8bit, this is from my point very wrong. Thunderbird
should send unknown content-types as "Content-Transfer-Encoding: BASE64" to
ensure that the content is preserved.
Reproducible: Always
Steps to Reproduce:
1.Write a new mail
2.Attach a file which is unknown to Thunderbird
3.Send the mail
4.The recevied mail has Content-Transfer-Encoding: 8bit and after that binary data.
Actual Results:
You can't save the message in the Sent folder since most IMAP servers will bail
when you insert binary data.
Most (including Thunderbird) can't open the mail later since it contains corrupt
binary data.
Expected Results:
Send unknown content-types as base64 to ensure its arrival.
This has been tested on MacOS X 10.3 using Thunderbird 1.0.2 and 1.0.6 .
Related to bug 236239?
Reporter | ||
Comment 2•19 years ago
|
||
Yes, seem so.
Can it be that all my users upgraded and thunderbird 1.0.6 doesnt fix its
mimetypes on upgrade?
I havn't check what happens with a fresh install but I will when I get the time.
Comment 3•19 years ago
|
||
(In reply to comment #2)
> Yes, seem so.
>
> Can it be that all my users upgraded and thunderbird 1.0.6 doesnt fix its
> mimetypes on upgrade?
Same behaviour on thunderb. 1.0.7
> I havn't check what happens with a fresh install but I will when I get the time.
I suppose only creating a new profile would help.
or editing mimetypes.rdf as described in https://bugzilla.mozilla.org/show_bug.cgi?id=236239#c16
I just hope I didn't brake anything else in doing so.
Comment 4•18 years ago
|
||
Jerry Lundström, any reason to leave this bug open? If your problem basically went away with the fix to bug 236239, please dupe this bug to that one.
Comment 5•16 years ago
|
||
Reporter, does the issue still occur in the latest supported 2.0.0.x / trunk nightlies?
(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-08-07
Comment 6•16 years ago
|
||
RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2008-08-07
You need to log in
before you can comment on or make changes to this bug.
Description
•