217104 - Improper handling of BinHex attachments

Status: RESOLVED EXPIRED

(MailNews Core :: Attachments, defect)

Description

[Paul Bryan]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2

When a file is attached to a message and encoded with BinHex 4.0, Mozilla fails
to properly decode or save the attachment.

Reproducible: Always

Steps to Reproduce:
1. Have a friend using Mac OS 9 send you a binary (e.g. ZIP) file with Eudora.
2. Save the attachment.
3. Try to open/use/view the saved attachment.
Actual Results:  
The saved attachment does not resemble the actual binary file sent.

Expected Results:  
I expected to see the binary attachment, properly decoded.

I considered the possibility that this was a duplicate of Bug 202353; however
that bug is reporting a problem interfacing with Stuffit Expander on the Mac
platform, and points out that on non-Mac platforms Mozilla decodes BinHex
attachments.

Comment 1

[Paul Bryan]

Attachment: Sample email sent from Mac with BinHex attachment.

Here is a sample file sent to me. It is a ZIP file, which contains the Mozilla
logo from the mozilla.org web page.

Comment 2

[Jo Hermans]

related to bug 215335 ?

Comment 3

[Boris Zbarsky [:bzbarsky]]

The binhex decoder was pretty broken in 1.4... See bug 220611

Please retest with a build from tomorrow or later to see whether this problem is
fixed...

Comment 4

[Gervase Markham [:gerv]]

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 5

[Gervase Markham [:gerv]]

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.