🚀 go-pugleaf

	What happens when a new uucp site comes up that is also on the arpanet?
	One of the vaxen here on campus will (hopefully soon) be uucp'd with
	nprdc.
This is beginning to happen a lot - there are currently a bunch of
sites running both arpanet and uucp (lbl-unix, sri-unix, ucla-security,
rand-unix) and we expect more to follow (our arpavax, nprdc, Shasta [at
Stanford], and possibly something with CSNET.)  At least one of these
sites is already a gateway for arpa-uucp mail, and several are
seriously considering it.  With this many gateways it should be
reasonable to keep the traffic levels through any one site quite
reasonable.  I'm not announcing which site yet because I am not completely
clear on their policy, and I don't want to flood them with mail
unexpectedly.  They are also still having enough bugs that a high
volume of mail would probably only get in the way.  It would be real
nice if I could announce a SET of at least 3 gateways at the same time,
to avoid branding any one as the "default".

	Should all `ta.*' stuff go through ucbvax or can it go to other
	uucp<-->arpanet machines?
There is already far too much traffic through ucbvax.  I would welcome the
offer from any other site to be the one that ta.* goes through to get to
the arpanet.  However, this may soon be moot with gateways springing up,
since ordinary mail could once again be sent to the mailing list.

	Mark