At 09:09 PM 1/5/00 -0500, Andrew J. Schorr wrote:
>Can anyone tell me how to handle a MIME attachment that was encoded
>using BinHex 4.0? I received an e-mail containing several JPEG photos
>that were attached as follows:
[snip]
>Content-Type: application/mac-binhex40; name="putin4.jpg"
>Content-Disposition: attachment; filename="putin4.jpg"
>
>
>(This file must be converted with BinHex 4.0)
>:#R"eG'PZ0#jUF'F!5P"&4dT@9e)!!!!!%Ld!!!!!X)Mrf2rJ!""+4NP'!!%"!!!
[snip]
>Is there any way of configuring the mailcap file to handle such an
>attachment automatically? And where does one find a BinHex 4.0 decoder
>that runs on Solaris and/or Linux? Is uudeview the best bet (I found
>it on freshmeat.net)?
>
>Furthermore, does anybody have any idea why somebody would send photos
>this way? The message includes the following header line:
>
> X-Mailer: Windows Eudora Light Version 1.5.4 (32)
>
>The sender of the message is not a sophisticated user. Does anybody
>know why Windows Eudora would send the file this way?
OK, at the moment I am sending this from Eudora 2.2 (32) which is
vintage 1995 or so. Still works, Y2K and all.
Under "options", for attachments, there are three:
MIME
BinHex
Uuencode
as well as a separate choice for whether to include the "attachment"
within the message or not. Testing, the MIME choice yields octet-stream,
using BASE64 encoding, probably the stuff you can easily handle.
BinHex gives exactly the type of stuff that you showed, including
the "mac-binhex40".
> Or perhaps he
>was just forwarding it from somebody else...
Or perhaps he has an options menu and never bothered (or knew)
to set it to something else. (I say "perhaps" because
Eudora Light is the free version, lacking some features.)
Hopefully, you can get him to set it more usefully.
Can't help you with how to de-BinHex stuff on Solaris though.
Cheers,
Stan
