Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!Tomobiki-Cho!mrc From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) Newsgroups: comp.sys.next Subject: Re: NeXT multi-media message file format Message-ID: <8263@milton.u.washington.edu> Date: 28 Sep 90 19:04:42 GMT References: <1990Sep27.212624.6406@sti.fi> <8242@milton.u.washington.edu> Sender: news@milton.u.washington.edu Organization: Mendou Zaibatsu, Tomobiki-Cho, Butsumetsu-Shi Lines: 27 In article rd0k+@andrew.cmu.edu (Richard Drew Dean) writes: >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.... Ahem. You said "formatted something like". The's the whole point. It's pretty easy for a human to take a NeXT Mail message and unscramble it on some other platform. It is quite another thing for an application to do so with all possible forms of NeXT Mail, much less compose a message that is guaranteed to be compatible with NeXT Mail, without a *complete* specification. In any case, RFC-1154 is a standard, and offers a superset of the apparent NeXT Mail format. _____ | ____ ___|___ /__ Mark ("Gaijin") Crispin "Gaijin! Gaijin!" _|_|_ -|- || __|__ / / R90/6 pilot, DoD #0105 "Gaijin ha doko?" |_|_|_| |\-++- |===| / / Atheist & Proud "Niichan ha gaijin." --|-- /| |||| |___| /\ (206) 842-2385/543-5762 "Chigau. Gaijin ja nai. /|\ | |/\| _______ / \ MRC@CAC.Washington.EDU Omae ha gaijin darou" / | \ | |__| / \ / \"Iie, boku ha nihonjin." "Souka. Yappari gaijin!" Hee, dakedo UNIX nanka wo tsukatte, umaku ikanaku temo shiranai yo.