56294 - [mac] problems sending / saving "Macintosh Files"

Status: VERIFIED DUPLICATE of bug 22090

(MailNews Core :: MIME, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

I've got an attachment that is an apple script file that I can only send and
save using 4.x.  using 6.0 to send or save it will always fail.

when I send and then read and save from 4.x, it shows the attachment as a file
with type "Macintosh File", encoding 7 bit, description unknown

send from 4.x, read & read from 4.x:		ok
send from 4.x, read & read from 6.0:		fail (the file that I save to disk is just the
mime part, I'll attach it to the bug)
send from 6.0, read & save in 4.x:		fail (the file is empty)
send from 6.0, read & save in 6.0:		fail (the file is empty)

spamming a bunch of mac folks for input.

Comment 1

[(not reading, please use [e-mail] instead)]

adding keywords 4xp.  is this a dogfood / rtm issue for mac users?

Comment 2

[(not reading, please use [e-mail] instead)]

Attachment: this is what I get when I send from 4.x, and read and save from 6.0

Comment 3

[jefft]

I guess no one ever have time to deal with apple single/double mac specific file 
attachments.

Comment 4

[Simon Fraser [no longer active]]

Are we dropping part of multipart/appledouble?

This sounds bad for Mac users who want to send attachments, and should be rtm+ I 
think.

Comment 5

[jefft]

Yes ...

Comment 6

[Jean-Francois Ducarroz]

I don't think so Apple Double is implemented yet. Rich?

Comment 7

[Simon Fraser [no longer active]]

Hoo boy. So we need to either refuse attachments that we know we'll fail to 
encode, or use BinHex. Do we do BinHex?

Comment 8

[rhp (gone)]

This was on my plate for a long time, but then I was told that the 4.x ongoing 
support team was going to help with Seamonkey issues so Steve Dagley told me he 
could help on the Mac. Here is the bug:

           http://bugzilla.mozilla.org/show_bug.cgi?id=22090

Comment 9

[Simon Fraser [no longer active]]

Should this be a dup of bug 22090?

Comment 10

[rhp (gone)]

Yes, this is a dup.

Comment 11

[selmer (gone)]

Marking dup of 22090.


*** This bug has been marked as a duplicate of 22090 ***

Comment 12

[pmock]

Verify as a duplicate of bug 22090.