Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!sun!guy
From: guy@sun.uucp (Guy Harris)
Newsgroups: net.bugs.uucp,net.bugs.usg,net.unix,net.unix-wizards
Subject: Re: UUCP from 4.2BSD->AT&T 3B2
Message-ID: <3171@sun.uucp>
Date: Fri, 17-Jan-86 15:15:43 EST
Article-I.D.: sun.3171
Posted: Fri Jan 17 15:15:43 1986
Date-Received: Sun, 19-Jan-86 04:40:31 EST
References: <1519@sphinx.UChicago.UUCP>
Organization: Sun Microsystems, Inc.
Lines: 15
Xref: watmath net.bugs.uucp:671 net.bugs.usg:419 net.unix:6861 net.unix-wizards:16445

> I am attempting to establish a UUCP connection between my Pyramid and a
> AT&T 3B2-400.  When we call the 3B2, uucico fires up on their side and
> identifies their system properly.  It then sends LOGIN where my system is
> expecting OK.

See reply to other similar reported problem.  It has nothing whatsoever to
do with the UUCP running on the calling side; it could be anything from V7
to System V Release 2, and probably even Honey Danber, and the same problem
would occur.  The problem is that the *called* side hasn't had its USERFILE
(or the Honey Danber equivalents) set up right; System V Release 2's UUCP
enforces rules that had never been enforced before, and which people got
used to not being enforced.  You *must* enable logins for *every* account
used by UUCP in the USERFILE or whatever file(s) Honey Danber uses.

	Guy Harris