Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!ox.com!b-tech!zeeff From: zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) Newsgroups: comp.mail.uucp Subject: Re: local site in a domain Message-ID: Date: 27 Feb 91 15:41:10 GMT References: <87512@sgi.sgi.com> <8YF-!-?@b-tech.uucp> <87732@sgi.sgi.com> Organization: UMCC Lines: 34 >of machines within sgi.com complain bitterly at having to type >"host.subdom" instead of "host". They'd get out their pitchforks and >torches if told to type "host.subdom.ain.sgi.com"! Yes, it'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. It makes it much less confusing - I hate questions like "why do I send to bill with just bill, chris with chris@site, and jan with jan@site.domain". "Why does jan tell me that everyone else can reach her with "jan@site" and yet I can't". I also hate to constantly have to remember which machine I'm on, ie do I need to use joe, joe@site, or joe@site.domain? Depends on which window I'm in. >Here, > 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. -- Jon Zeeff (NIC handle JZ) zeeff@b-tech.ann-arbor.mi.us