Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!vjs@rhyolite.wpd.sgi.com From: vjs@rhyolite.wpd.sgi.com (Vernon Schryver) Newsgroups: comp.mail.uucp Subject: Re: local site in a domain Summary: yes and no Message-ID: <88013@sgi.sgi.com> Date: 28 Feb 91 03:48:08 GMT References: <87512@sgi.sgi.com> <8YF-!-?@b-tech.uucp> <87732@sgi.sgi.com> Sender: guest@sgi.sgi.com Organization: Silicon Graphics, Inc., Mountain View, CA Lines: 34 In article , zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes: > Yes, [typing FQDM's] an inconvenience. There are aliases for frequent > recipients and most mail is via "reply". Otherwise, maybe a centralized > mail server (so all sgi users just type "user") is the way to go. Or a common, global, distribute name space. (Not to open the perennial centralized/distributed "discussion") > >[rules at at sgi.com include:] > > foo!user is immediately converted to user@foo > > user@bar is routed to: > > (1) bar.sgi.com if existent > > (2) directly connected UUCP neighbor if existent > > else (3) bounced > I assume that you also implement the policy that you won't have any > external uucp neighbors that have a uucp name the same as one of your local > names? Otherwise, someone offsite sending mail (routed via the > uucp maps) might send to sgi!foo!user and not have it end up where > they expected. That was the original point, and unless I missed > something, you could still suffer from this problem. Yes: I think it would be silly, ridiculous, wrong, impolite, and a sign of Bad Breeding to advertise in the UUCP maps a route to one place and send mail somewhere else. No: mail to sgi!!user, where is not in the sgi map entry and is in the sgi.com domain will go to the sgi host. Also No: if one of our map neighbors decides to add an alias in their UUCP map entry that happens to be the same as an internal machine, then mail sent to that alias will lose. Vernon Schryver, vjs@sgi.com