🚀 go-pugleaf

Tom Wuttke writes
> 
> I do not have a Next, but someone I know mails me messages with 
> embedding things like sounds, pictures, and formatted text.  When I 
> look at the raw mail files, they look exactly like uuencoded 
> binaries.
> 
> So, the first thing I do is uudecode them.  This usually results
> in a file with a name like .tar.148.jpeg_FAQ.attach
> 
> Then, I proceed to assume that this is a tar archive of all
> the embedded objects, so I run this into tar to look at the
> list of files using syntax like:
> tar -tf .tar.148.jpeg_FAQ.attach
> 
> This always gives me a table of contents error, or a "hmmm, this 
> doesn't look like a tar file to me" error on the Next.
> 
> I believe the first part was right, uudecoding the message,
> but what should I do with this binary file that comes out of
> it, that seems like it should be an ordinary tarfile, but isn't?

I believe its both tarred and compressed.  If you rename the file  
148.jpeg_FAQ.attach.tar.Z and run it through uncompress and tar, it  
should come out fine.
You'll get a bunch of files, so its best to do this inside a  
directory you create for the purpose.  One of these files is called  
index.rtf.  This is the body of the message in Rich Text Format  
(RTF).  The rest of the files and directories are the attachments.   
Hopefully they are files that can be opened on the receiving system.    
If you have an editor that can read RTF files, use it to open  
index.rtf .  It will have the body of the text.  There will be no  
text if just an attachment was sent. 


--
-
Stefano Pagiola
Food Research Institute, Stanford University
spagiola@frinext.stanford.edu (NeXTMail encouraged)
spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)