Subject: attached files forced into Mime?

From: [email-masked] (Alan Morris)
Date: Fri, 17 Mar 1995 19:33:38 GMT

I'd appreciate any help with the following problem.
I've RTFM (maybe just not the right spots), and continue to have a 
problem attaching readable files to email sent with Pine.

I uuencode a file, enter pine, and attach the uuencoded file.  
However, the files are reaching the destination as mime encoded, 
and are not readable with a simple uudecode.  

I'm using Pine 3.91.  I've been able to grab and uudecode files sent to 
me with no problem, but since several recipients have been unable to 
uudecode files I've attached I need to do something differently.

Thanks for any help,

Alan Morris
--

---

From: Rahul Dhesi <[email-masked]>
Date: 18 Mar 1995 04:20:57 GMT

>and are not readable with a simple uudecode.  

When you tell pine to 'attach' a file, it normally encodes it using
base-64 encoding.  So, in your case, the file ends up being encoded
twice:  First with uuencoding, then again with base-64 encoding.
Possible solutions (pick any one):

1. Ask the recipient to read the message with pine, save the attached
   file, then exit pine and uudecode the file.  (Or read with any mail
   reader that can decode MIME-encoded messages.)

2. Ask the recipient to pipe the message through 'metamail', which
   will send the base-64-decoded contents to standard output.  This
   should be directed to a file, and then uudecoded in a separate
   step.

3. When composing your message, don't ask pine to attach the file.  Instead,
   use the ^R key while composing the body of the message.  This will
   let you include the file in the body without encoding it further.
   Now the recipient can uudecode the message directly.

-- 
Rahul Dhesi <[email-masked]>
"please ignore Dhesi" -- Mark Crispin <[email-masked]>