Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uwvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!uwvax!david
From: david@uwvax.UUCP (David Parter)
Newsgroups: net.micro.att
Subject: Re: 3b2 has no uuencode/uudecode??
Message-ID: <213@uwvax.UUCP>
Date: Tue, 4-Jun-85 15:09:57 EDT
Article-I.D.: uwvax.213
Posted: Tue Jun  4 15:09:57 1985
Date-Received: Thu, 6-Jun-85 08:16:25 EDT
References: <198@uwvax.UUCP> <1072@cp1.UUCP> <200@uwvax.UUCP> <267@cuae2.UUCP>
Distribution: net
Organization: UWisc Systems Lab
Lines: 40

> In article <200@uwvax.UUCP> david@uwvax.UUCP (David Parter) writes:
> >The purpose of uuencode/uudecode is to encode/decode binary files
> >for transmission via (uucp) mail.  
> 
> Sounds like a KLUDGE to me....
> 
> The real solution is to use uucp file transfer in the first place and
> not pretend that binary files are just text.
> -- 
> Ron Heiby	heiby@cuae2.UUCP	(via wnuxa or wnuxb)
> AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109


ok, now i will repeat what i have been busy answering via private mail
since i posted the original complaint/question:

	1) uucp works fine for transfering binarires -- from one uucp
	   site to another -- but if you are in a situation where you
	   can't do this -- ie  machine A communicates to machine B via
	   some other method, and machine B communicates with machine C
	   via uucp, you have the following choices:

			a) copy the file from A to B with whatever methods you have,
			   and the login to B and uucp from B to C, or

			b) encode the file, and mail iot from A to C. Mail knows how
			   to negotiate the gateway from A to B to C.
		
		also, if you CAN'T login on site B, method b) above is the only
		choice avaliable.
	
	2) i have uuencode/decode for 4.2, and will port it.

david
-- 
david parter
UWisc Systems Lab

...!{allegra,harvard,ihnp4,seismo}!uwvax!david
david@wisc-rsch.arpa