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 ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!jordan
From: jordan@ucbvax.ARPA (Jordan Hayes)
Newsgroups: net.mail
Subject: Re: Mail routing -- problems showing up
Message-ID: <9569@ucbvax.ARPA>
Date: Thu, 1-Aug-85 20:16:30 EDT
Article-I.D.: ucbvax.9569
Posted: Thu Aug  1 20:16:30 1985
Date-Received: Sat, 3-Aug-85 02:46:46 EDT
References: <1386@peora.UUCP>
Reply-To: jordan@ucbvax.UUCP (Jordan Hayes)
Distribution: net
Organization: University of California at Berkeley
Lines: 24


In article <1386@peora.UUCP> jer@peora.UUCP (J. Eric Roskos) writes:
>4) Some people feel that "esu!cs!joe" is a route, whereas "joe@CS.ESU.UUCP"
>is a "domain", and that the latter does not specify any routing information.
>They feel domains simplify how much information you have to keep at your
>site.  When pressed to explain how this works, they say, "Simple!  You just
>send to your local UUCP name server, who then sends to the ESU name server,
>who then sends it to system CS, who sends it to joe."

That is not the correct answer. However, the answer is, of course, both
simple and elegant. It goes like this: check your table to see if you
have a gateway for CS.ESU.UUCP (which would only be true if you had a local
connection to it...). If so, resolve there. If not, check to see
if you have a gateway for .ESU.UUCP, which you'd have to have, even if you
were a simpleton site that had only one connection to bounce to, since
.ESU is the "top-level" for UUCP, an artificial domain set up for
our purposes (shhh... don't tell anyone...;-)

There's no reason to send everything you have to a UUCP central server.

------------
Jordan Hayes        jordan@UCB-VAX.BERKELEY.EDU
UC Berkeley                       ucbvax!jordan
+1 (415) 835-8767    37' 52.29" N 122' 15.41" W