Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!vsi1!lmb From: lmb@vicom.com (Larry Blair) Newsgroups: comp.mail.uucp Subject: Re: Who pays the bill? Message-ID: <1990Aug1.183347.11916@vicom.com> Date: 1 Aug 90 18:33:47 GMT References: <26A738A8.725B@tct.uucp> <65793@sgi.sgi.com> Organization: Vicom Systems Inc., Fremont, CA Lines: 35 In article emv@math.lsa.umich.edu (Edward Vielmetti) writes: =In article <65793@sgi.sgi.com> vjs@rhyolite.wpd.sgi.com (Vernon Schryver) writes: = = = 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. = =If you use fully qualified domain names whenever there is ambiguity, then =your own mail will not be bounced. = =If (random, internal) hosts put their fully qualified domain names in =Path: headers, then this path would look like = "bionet!oracle!decwrl!sgi!oni.sgi.com!apple.oni.sgi.com!user" =et voila, no ambiguity, no bounced. Why do I end up allways getting into these discussions? What `apple' means to sgi.com is no one's business but sgi.com. Just leave it alone! =And besides, if someone actually is posting news from this apple machine =internal to sgi, that news will never make it to the "real" apple, if =it puts "apple!" into the Path header and it's in the maps. How about apple.com? You know, I know that you rabid rerouters mean well. You're just trying to cure a genuine problem that comes from reverse-routitis. But I have found a far more effective solution. Every once in a while, when things are slack, I'll identify a site or two that are generating a lot of these garbage paths and send the postmaster some mail about it. This has, on several occasions, been effective. -- Larry Blair ames!vsi1!lmb lmb@vicom.com