Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!mips!twg.com!david From: david@twg.com (David S. Herron) Newsgroups: comp.mail.uucp Subject: Re: Who pays the bill? Message-ID: <7704@gollum.twg.com> Date: 6 Aug 90 18:33:34 GMT References: <26A738A8.725B@tct.uucp> <65793@sgi.sgi.com> Reply-To: david@twg.com (David S. Herron) Organization: The Wollongong Group, Palo Alto, CA Lines: 58 In article <65793@sgi.sgi.com> vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes: >In article , lear@turbo.bio.net (Eliot) writes: >As has been said many times, not all machines are permitted in the maps. >The machine "apple.sgi.com" exists, and answers to "apple" as well as >"apple.sgi.com". For good reasons I am sure you know, that machine will >never be permitted in maps by the N.Calif. map coordinators. If I had >anything to say about it, the machine would not be named "apple.sgi.com", >or even "apple.corp.sgi.com" simply because it would be too similar to the >other machine named "apple". However, I don't have any say, and even if I >did, the arguement that Domains Save All would still be valid. Exactly.. you can have your domain name and use it too. Or something like that.. One of the things you have to do is make sure that stuff you're advertising in e-mail headers & Path: lines are `correct'. In your case, since your apple isn't the other apple, then you should make sure your apple claims to be it's FQDN (Fully Qualified Domain Name) (at least) in headers & Path: lines. Anything less and you WILL run into the confusion you suggest. >(I suppose it's too much to hope that no one will suggest that the users of >machines on the same ethernet as apple.sgi.com be forced to type >"user@apple.sgi.com" instead of "user@apple".) No.. The current BIND resolver (for instance) allows defaulting of unqualified domain names to live within a list of possible hierarchies. By default the hierarchies are super-sets of your FQDN, and is user-settable. MMDF automagically allows that same defaulting and I assume that sendmail.cf's can be configured to do the same defaulting. >If you reduce the UUCP path > "bionet!oracle!decwrl!sgi!oni.sgi.com!apple!user" >into > "bionet!apple!user" or "user@apple.com" >then you have just gratuitously bounced someone's mail. So when putting that UUCP path out there make ABSOLUTELY DAMN sure it doesn't say "apple", but the appropriate FQDN. On the other hand.. you're right.. people shouldn't be looking beyond the first site in the list because they really don't have the right to interpret the rest of the path. IF you put FQDN's into your path then there would be no chance for confusion. Everybody would know it was your apple and, if they were Rabidly Rerouting, would act accordingly. If they were Rationally Rerouting (my definition of Rational == not looking beyond the first hop) they would still work since you put out `sgi'. If they route on the first FQDN, again, it will work since you'd be putting out two FQDN's.. (given your example) -- <- David Herron, an MMDF weenie, <- Formerly: David Herron -- NonResident E-Mail Hack <- <- Sign me up for one "I survived Jaka's Story" T-shirt!