Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!aramis.rutgers.edu!remus.rutgers.edu!declan From: declan@remus.rutgers.edu (Declan McCullagh/LZ) Newsgroups: comp.sys.next Subject: Re: Dumb terminal user mail agent Message-ID: Date: 18 Feb 91 08:31:47 GMT References: <16779@venera.isi.edu> <4miHX2w163w@ersys.uucp> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 39 > bromine@ISI.EDU (Bill Romine) writes: > > PS: Does anyone have a filter to convert a NeXT-type mail message to > something a human can read (for when NeXT user's send NeXT mail > to non-NeXT users). After the message is saved to a file ('s filename' if you use /usr/ucb/Mail), it'll be in uuencoded form first, so: uudecode filename The file uudecode creates will be similar to ".tar.xxx.subject_name.attach" (if memory serves me correctly), where xxx is a positive integer, and subject_name represents the message's subject (truncated). At this point, the mail message will be in compressed/tar'd form, so to fully extract all the files: mv .tar.xxx.subject_attach filename.Z zcat filename.Z | tar xf - This will extract all the attachments and place them in your current directory. An index file, called "index.rtf", will also be created. If the mail message was an RTF-only letter without any attachments, you might want to convert it to ASCII for easier reading. I have a program somewhere called "stripText" which will do this for you, or you could look in a back message, where garp!pbiron@keynes.ucsd.edu (Paul Biron) listed a set of filters (rtf2text, rtf2troff) available for FTP; check out comp.text or comp.sys.mac.apps for more information. And, of course, you could automate this whole thing in a shell script. Perhaps this should be in the FAQ list if it isn't already - Pascal? Declan McCullagh Independent NeXT Developer -- ----- foo!! -----