Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site okstate.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!okstate!vasoll From: vasoll@okstate.UUCP Newsgroups: net.bugs.uucp Subject: Re: Help with UUCP on Telenet! Message-ID: <32400003@okstate.UUCP> Date: Sun, 6-Jan-85 00:22:00 EST Article-I.D.: okstate.32400003 Posted: Sun Jan 6 00:22:00 1985 Date-Received: Fri, 4-Jan-85 08:07:56 EST References: <32400002@okstate.UUCP> Lines: 22 Nf-ID: #R:okstate:32400002:okstate:32400003:000:779 Nf-From: okstate!vasoll Dec 29 23:22:00 1984 First, I would like to thank all of the people who responded with helpful answer to my Telenet question. The general consensus was that we should be using the 'f' protocol that was distributed in net.sources. This will solve most of our problem, but we do talk to a system that does not have the source and therefore cannot install this new protocol. We are trying to find a workaround on this such as a system within local calling range that does have the 'f' protocol and would be willing to act as a relay. Thanks again. Mark Vasoll Department of Computing and Information Sciences Oklahoma State University ...!ihnp4!umn-cs!isucs1!\ UUCP: ...!ucbvax!mtxinu!ea! > okstate!vasoll ...!convex!ctvax!uokvax!/ ARPA: vasoll%okstate.csnet@csnet-relay.arpa