Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!usc!rutgers!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!rd0k+
From: rd0k+@andrew.cmu.edu (Richard Drew Dean)
Newsgroups: comp.sys.next
Subject: Re: NeXT multi-media message file format
Message-ID: <cb0qMBW00VpaIIFEd6@andrew.cmu.edu>
Date: 28 Sep 90 15:02:37 GMT
References: <1990Sep27.212624.6406@sti.fi>,
	<8242@milton.u.washington.edu>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 12
In-Reply-To: <8242@milton.u.washington.edu>

NeXT's multi-media mail is RFC-822 compatible and formatted something like:
	take all the stuff which isn't plain ASCII, and tar/compress/uuencode
it into the message body.  The trick here is compress; the filename part
of the uuencoded file does _not_ end in .Z, but the file has been run
through compress. 
	Send a Next message to yourself on a Sun/VAX/generic Un*x box, strip
the headers with your favorite editor, uudecode, uncompress, tar -xvf,
and you'll have the right things....

Drew Dean
rd0k+@andrew
(Certainly not an official opinion of CMU...)