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:

--=====================_947052952==_
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'!!%"!!!
"!!%!!2rE!%-!#!B'"`B&#!F("`N*#!S-&!d-#`X-'4)6$a3G'KmH(4SF(#!N,LF
J)L`M("`S0bNX-$%d0$3I*cNp1$)m,M-d-[rE!%-"#3N*$!X-'!d0'$)K(#%b-M)
...

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?  Or perhaps he
was just forwarding it from somebody else...

I'm sorry if this has been asked already.

Thanks,
Andy

Reply via email to