Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!julian!reggers From: reggers@julian.UUCP Newsgroups: comp.mail.uucp Subject: Re: uucp vs. kermit Message-ID: <264@julian.UWO.CDN> Date: Tue, 14-Apr-87 12:32:27 EST Article-I.D.: julian.264 Posted: Tue Apr 14 12:32:27 1987 Date-Received: Wed, 15-Apr-87 02:41:34 EST Reply-To: reggers@julian.UWO.CDN (Reg Quinton) Distribution: world Organization: University of Western Ontario, London Lines: 29 Keywords: kermit, quick, dirty I can't help but comment on this debate since we've been using Kermit for well over a year as the transport protocol to link many different machines together for the purpose of E-mail. Here's an abstract to a paper I wrote about a year ago describing our system. MLNET: Using Kermit to Build a Network (Interim Solutions) MLNET is an electronic mail network at The University of Western Ontario which links a diverse set of machines (VM/CMS, VAX/VMS, Tops-10, CDC/NOS, Unix, and Prime) and provides a gateway service between several mail networks (BITNET, UUCP, CDN, MLNET, and others through remote gateways). Kermit is a public domain protocol, developed at Columbia, available for a diverse set of machines, and typically used for PC to mainframe file transfer under user control. The MLNET/MFS uses Kermit protocols, when available, to transport mail messages -- machines with Kermit can be added to the network with minimal programming effort. This paper reviews the design of the MLNET/MFS and shows how Kermit solves a major problem for our network. The system provides an attractive interim strategy since it may be implemented on machines as small as the IBM AT (under Xenix), connects over available asynchronous lines (including modems), transports messages using available protocols, and requires minimal programming effort to add new hosts. -- Telephone: (519) 661 2151 x6026 CDN: {postmaster/reggers}@UWO.CDN BITNET: {postmaster/reggers}@uwovax.BITNET UUCP: {postmaster/reggers}@julian.UUCP (...!watmath!julian..)