Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ucsfcgl!cca.ucsf.edu!wet!epsilon From: epsilon@wet.UUCP (Eric P. Scott) Newsgroups: news.newusers.questions Subject: Usenet is *not* synonymous with uucp (was Re: Compuserve -> Usenet) Summary: damage control Message-ID: <588@wet.UUCP> Date: 25 Sep 89 01:13:15 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> Reply-To: epsilon@wet.UUCP (Eric P. Scott) Organization: Wetware Diversions, San Francisco Lines: 31 WE INTERRUPT THIS ARTICLE FOR AN IMPORTANT REMINDER! * * USENET is NOT uucp! You can not send ->MAIL<- to a "USENET * address." *No* individuals have addresses on USENET. * Individuals have addresses on the International uucp network, * the Internet, HEPNET/SPAN, BITNET, etc. You cannot send mail * from Compuserve--or anywhere else--to USENET. USENET is a * logical network that makes use of a variety of transport * mechanisms to propagate news. It is not a part of uucp, it * does not require uucp, and uucp does not require it. Nor is * it a part of UNIX, although some vendors distribute netnews as * contributed software, and there are non-UNIX implementations as * well. * A major reason why usenet works as well as it does is that * major flow paths use NNTP and *not* uucp. You should not (and * often can not) use Path: lines to route mail replies. News and * mail should be considered entirely separate animals, with * different goals and considerations. well!microx, do you copy? * WE NOW RETURN YOU TO YOUR REGULARLY SCHEDULED NEWS ARTICLE, ALREADY IN PROGRESS. In article <1989Sep24.005426.7882@NCoast.ORG> gints@ncoast.ORG (Steve Juhasz) writes: >Can this be used to send files from Compuserve to another usersite for later >downloading (i.e. save on Compuserve connect time)? There is a 50,000 byte per message limit for EasyPlex users. -=EPS=-