Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.UU.NET (Tom Neff)
Newsgroups: news.newusers.questions
Subject: Re: Compuserve -> Usenet
Keywords: CompuServe
Message-ID: <14727@bfmny0.UU.NET>
Date: 25 Sep 89 13:46:46 GMT
References: <3665@blake.acs.washington.edu> <1989Sep17.222953.14160@twwells.com> <432@laas.laas.fr> <1580@jolnet.ORPK.IL.US> <1989Sep24.005426.7882@NCoast.ORG> <1597@jolnet.ORPK.IL.US>
Reply-To: tneff@bfmny0.UU.NET (Tom Neff)
Distribution: na
Organization: ^
Lines: 17
Summary:
Expires:
Sender:
Followup-To:

In article <1597@jolnet.ORPK.IL.US> dattier@jolnet.UUCP (David W. Tamkin) writes:
>Moreover, mail over the net is only for text, so if the file contains binary
>data it will not arrive intact unless you are proficient enough with CIS to
>get a uuencoding program into your personal area.

It's not strictly necessary to perform the uudecode on CIS itself in order
for mailing uuencoded stuff to CIS to be useful.  If you wanted to mail
a binary file to someone who has a CIS account and can run uudecode on
his office or home computer, then you could uuencode the file and mail that
text to his CIS account, from which he downloads it to his machine and
uudecodes it there.

As long as you stay under 50k this works well, I have done it a couple
of times.
-- 
I'm a Leo.  Leos don't believe    *  *  *     Tom Neff
    in this astrology stuff.        *  *  *   tneff@bfmny0.UU.NET