Thanks for the responses.
>We have an X.400 gateway here which can take Mac Mail messages and
>uuencode them for Unix Mail destinations. I have thus far been un-
>successfull in being able to uudecode these enclosures into a readable
>format on the Mac. Mail enclosures are almost exclusively MS Word and
>MS Excell and we are using MS Mail on the Mac side. Someone gave me a
>utility called "single" for the Unix side, which I compiled and tested,
>it doesn't seem to do much. My understanding is that there is something
>called the "Apple Double Format" which we need to have in order to
>properly retreive these documents into Word and Excell.
>Anyone know of such a utility?
>The Eudora clients we use are POP3 based. They have the ability
>to transport binary files across a Unix Sendmail carrier.
>For end-end Word and Excel MAC users this has been very effective,
>Somehow binhex is involved, and converting them to be readable
>for a MSDOS user running MS-Word, we use a program called
>mcvert. I have had no high demand for this implementation but
>it is a good search string for archie (that's how I got It).
>mcvert is a Sun binary.
>Thus endith the coredump.
>Hope it helps.
>COA/AAES Auburn University
I've downloaded the utility, spent a few minutes (so far) playing with
it, and I'm not quite sure how it works (yet).
>Yes. I have the same problem with uuencoded excel and word files sent
>to me by PC users using either DecPathworks or Windows for workgroups.
>Save the uuencoded mail message as a text file.
>Drag and drop the saved text file onto the attached app.
>I'd consider it early "alpha" release. But it works for me!
I didn't quite understand the reply, but I'll play with it.
>First off, I'd like a copy of 'single'.
>Having said that, you should know how macs work. A mac file consists of
>two halves, a resource fork, containing system information (to which app
>the file belongs, for instance), and the data fork containing the data.
>This is easy on a mac, but a UNIX machine does not understand two files.
>There are 3 ways of doing that:
> AppleDouble saves the data in two files. A file xyzzy would be xyzzy
> for the data fork, %xyzzy for the resource fork.
> Applesingle combines the two files in one file. Often used in emailing
> MacBinary combines the two files like AppleSingle, but in another way.
> This is supported in NCSA telnet.
>Now, to convert, you need a mac, a mac NFS redirector (GatorBox or NFS/share),
>and some luck. I don't know what format the email messages are, so you
>need to check yourself.
>Hope this entitles me for a copy of 'single' :-).
Thanks for the info, it was helpful. We are already using NFS/Share; our
problem, however, is on the e-mail side, specifically, mailing files from
Mac to Sun.
>Apples have additional information in their files: what kind of file created
>them, what kind of resources they're hooked to, etc. In transferring these
>files to a UNIX box, this additional data can be stored in various ways.
>Kept in the same file altogether, it's called Apple Double (if I remember
>right). There are also Apple Single and AUF formats.
>Try getting the CAP software from rutgers.edu. It contains programs to
>transform one format to the other gracefully. Find whichever format
>leaves the data in a separate file so you can examine it properly with
Thanks for the reply. I ftp'd to rutgers.edu, and downloaded the Track Catalog.
It appears as though we need to install Track to download any of the programs
there, and CAP is a file and printer sharing program for Macs and Suns. I
need to investigate this program and rutgers.edu a little more thoroughly.
Anyone interested in the utilities I've already downloaded from others
(mcvert and single), let me know, I've created a tar file of all the source
and will be happy to forward it along.
Thanks for all the replies, I believe credits are listed above.
Joshua Walfish Phone: (212) 648-4473
J.P. Morgan, Inc. Fax: (212) 483-5076
60 Wall Street Internal Email:walfish@newton
New York, NY 10260 External Email:Walfish_Joshua@jpmorgan.com
"But this has taken us far afield from interface, which is not a bad
place to be, since I particularly want to move ahead to the kludge.
Why do people have so much trouble understanding the kludge? What is a
kludge, after all, but not enough Ks, not enough ROMs, not enough RAMs,
poor quality interface and too few bytes to go around? Have I
explained yet about the bytes?"
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:54 CDT