Subject: Reading BinHex4.0 Messages

From: Steve Lowe <[email-masked]>
Date: Thu, 22 Aug 1996 21:29:31 -0500 (CDT)

Today, I received a BinHex 4.0 message.  The $64 question is how to read
the attachment.

My platform is Digital Ultrix and Pine 3.95.  Do I have to make an entry
in /etc/mailcap?

Thanks in advance.

 -- Steve Lowe
    Aurora University             [email-masked]
    630 844 5290

---

From: [email-masked] (Tim Mooney)
Date: 23 Aug 1996 11:39:19 -0500

[cc'ed and posted]

In article <[email-masked]>,
> Today, I received a BinHex 4.0 message.  The $64 question is how to read

Good luck.  You could get and install `mcvert', and add the following to
your mime.types file, if it's not already there:

application/mac-binhex40       hqx

Then add something like:

application/mac-binhex40;	mcvert %s

to your mailcap, but then you're just going to get to see whatever document
was `wrapped' (BinHex is kinda like `uuencode' -- once you've undone that
you're generally left with a binary file that you then have to figure out
how to interpret).

> My platform is Digital Ultrix and Pine 3.95.  Do I have to make an entry

More than likely, but you're probably still not going to be able to read
what was sent.

Tim
-- 
Tim Mooney                              [email-masked]
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J1, IACC Bldg.                 (701) 231-8541 (FAX)
North Dakota State University, Fargo, ND 58105

---

From: Jim Flanagan <[email-masked]>
Date: Fri, 23 Aug 1996 09:41:58 -0400

> My platform is Digital Ultrix and Pine 3.95.  Do I have to make an entry

  Binhex is the macintosh analogue to uuencode. It is generally used to
encode 
  applications, archives, and non-ascii documents (ex. MS Word) which
will
  likely only be useful on a mac once they are decoded. There is a unix
program
  called 'mcvert' which will decode binhexed files. It can be obtained
from

      http://www.shsu.edu/tex-archive/tools/mcvert/

  Or any other CTAN (Comprehensive TeX Archive Network) site.

  Jim Flanagan <[email-masked]>
  Computing and Communications
  Brookhaven National Laboratory
  http://pubweb.bnl.gov/~jimfl