Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version VT3.4 8/17/84; site vortex.UUCP
Path: utzoo!linus!decvax!vortex!root
From: root@vortex.UUCP (The Superuser)
Newsgroups: net.decus,net.wanted
Subject: VMS UUCP
Message-ID: <411@vortex.UUCP>
Date: Mon, 1-Oct-84 02:42:46 EDT
Article-I.D.: vortex.411
Posted: Mon Oct  1 02:42:46 1984
Date-Received: Tue, 2-Oct-84 05:56:11 EDT
Organization: Vortex Technology, Los Angeles
Lines: 23

The reasons I've continued work with my VMS UUCP (in the presence
of the VUCP thing that the Canadian firm has) are basically
threefold:

1) I get lots of reports of trouble with VUCP -- which isn't at all
   surprising given the mess of porting Unix code to VMS.

2) I consider close integration of UUCP with the VMS mail system
   to be essential for a full mail/uucp implementation (as opposed
   to simple mail kludges).  It became obvious that only by coordinating
   my efforts closely with DEC could I accomplish this and also track
   future VMS changes.

3) My code is independent of Unix code and thusly does not (unlike the
   other product) require a Unix binary (which the customer must pay
   for of course) to be imbedded within the product.

Anyway, to some these points might not matter, but to others
they well might.  My whole package has been oriented toward being a 
full mail/uucp package with 822 compatibility, rather than 
a "simple" system to mainly replace tape transfers...

--Lauren--