Subject: UUEncode

From: [email-masked] (Nicholas Samuels)
Date: 29 Nov 1995 18:12:50 GMT

I've received an attachment encoded with UUEncode.

Is there any way I can view this with PINE?

If not, how can I decode it?

And, if MIME is the standard, why is anyone using UUEncode?  The message
was sent from s system using MCIMail, which apparently, uses UUEncode
automatically.

Thanks for whatever help anyone can offer.

---

From: [email-masked]
Date: Wed, 29 Nov 1995 23:43:54 +0100 (MET)

There is no builtin uudecode in PINE. And there is no ONE standard.

Check with archie for a prog called uudeview, that is a nice useful decoder
not only for uuencoded files.

uuencode was (and perhaps still is) one of the standards on most systems. Most
postings in newsgroups are still uuencoded. 

Perhaps you have uudecode on your system? try to export the mail and run uudecode
on that file if you get uudecode: not found than get uudeview.

Ciao,
 Michael

> Thanks for whatever help anyone can offer.
 
================================================================
Michael J. Joswig              [email-masked]

I believe I found the missing link between animal and civilized man.
It is us.
	(Konrad Lorenz)

---

From: Paul O Bartlett <[email-masked]>
Date: Wed, 29 Nov 1995 21:00:32 -0500

> Is there any way I can view this with PINE?

    Not by Pine as such.

> If not, how can I decode it?

    It depends.  If you are running Pine on some Unix flavor and have 
enabled piping, just pull up the attachement and pipe to uudecode.  The 
output file should be in the current directory (I think).  Otherwise you 
may have to export/save to an external file and uudecode it manually 
with a utility.

> was sent from s system using MCIMail, which apparently, uses UUEncode

    MIME is not really a standard as such' it's just what Pine uses.

Paul
--------------------------------------------------
Paul O. Bartlett         <[email-masked]>
P. O. Box 857     Vienna, VA 22183-0857     U.S.A.
Finger, keyserver, or WWW for PGP 2.6.2 public key
     URL: http://www.access.digex.net/~pobart     
--------------------------------------------------

---

From: Terry Gray <[email-masked]>
Date: Thu, 30 Nov 1995 07:31:25 -0800 (PST)

>     MIME is not really a standard as such' it's just what Pine uses.

Paul
This is incorrect.  MIME is *the* Internet standard for encoding and
labelling non-ascii messages.  See RFC-1521 (which, by the way, answers
Sven's question about what's wrong with uuencode.)

-teg

---

From: Paul O Bartlett <[email-masked]>
Date: Thu, 30 Nov 1995 11:26:35 -0500 (EST)

On Thu, 30 Nov 1995, Terry Gray wrote:

: On Wed, 29 Nov 1995, Paul O Bartlett wrote:
: 
: > > And, if MIME is the standard, why is anyone using UUEncode?  The message
: > > was sent from s system using MCIMail, which apparently, uses UUEncode
: > > automatically.
: >
: >     MIME is not really a standard as such' it's just what Pine uses.
: 
: Paul
: This is incorrect.  MIME is *the* Internet standard for encoding and
: labelling non-ascii messages.  See RFC-1521 (which, by the way, answers
: Sven's question about what's wrong with uuencode.)

    I stand corrected.  Thank you.

Paul