Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ptsfa.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!amdcad!lll-crg!lll-lcc!dual!ptsfa!jmc
From: jmc@ptsfa.UUCP (Jerry Carlin)
Newsgroups: net.bugs.uucp
Subject: Re: multihop uucp
Message-ID: <1102@ptsfa.UUCP>
Date: Thu, 16-Jan-86 11:14:03 EST
Article-I.D.: ptsfa.1102
Posted: Thu Jan 16 11:14:03 1986
Date-Received: Sat, 18-Jan-86 08:37:31 EST
References: <1564@emory.UUCP> <425@hoptoad.uucp> <647@down.FUN>
Reply-To: jmc@ptsfa.UUCP (Jerry Carlin)
Organization: Pacific Bell, San Francisco
Lines: 18

In article <647@down.FUN> honey@down.FUN (Peter Honeyman) writes:
>john gilmore's "political commentary" aside, there is the option of
>purchasing honey danber, which supports forwarding (although it's
>incompatible with old system v forwarding (for good reason)).
>
Having to live with that incompatability every day, I can state that 
whatever the 'good reason' it is NOT good enough. Note that people
upgrading from old System V to Honey-Danber (aka AT&T BNU) will have
their multi-hop uucp break unless they upgrade all their machines at
the same time. Of course, not all vendors offer Honey-Danber uucp so
--gotcha--. One hack around it is to ignore multi-hop uucp and write
a separate forwarder that lives on each machine and which works
the way mail/rmail works (you would not uucp a!b!c you would then
"foo a!b!c" in the same way you now "mail a!b!c").

-- 
voice= 415 823-2441
uucp={ihnp4,dual,qantel}!ptsfa!jmc