Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!udel!princeton!twg.com!david From: david@twg.com (David S. Herron) Newsgroups: comp.mail.uucp Subject: Re: Paths and Precedence (Re: Question about From: lines) Message-ID: <7619@gollum.twg.com> Date: 17 Jul 90 22:49:08 GMT References: <3RK4TQE@xds13.ferranti.com> <269B6560.3F1E@intercon.com> <[$6je2.vl6@smurf.sub.org> Reply-To: david@twg.com (David S. Herron) Organization: The Wollongong Group, Palo Alto, CA Lines: 53 In article <[$6je2.vl6@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes: >< In article <269B6560.3F1E@intercon.com> amanda@mermaid.intercon.com (Amanda Walker) writes: >< > We don't. You send paths through UUCP. The fact that currently you can >< > "tunnel" UUCP paths through the internet is a bug, not a feature. Once >< > mail gets to the Internet, it should have an address, not a route. eh? the internet-gateway can fully handle the translation of a!b!c!d to <@a,@b:d@c> and back to b!c!d once it gets to a ... what's the problem?? Other than a little unavoidable header translation that is.. >I'm currently running my mailer (MMDF, with the UUCP stuff somewhat modified) >based on the reasonable assumption that anyone hanging off me has either >Pathalias, is on the Internet, or is a node with one single connection (to >me). Quickly stepping in to save MMDF's ass :-) >So I don't generate paths, I generate "uux - nexthop!rmail user@somewhere" >(with 'somewhere' either a FQDN or a hostname.UUCP), or somewhere!user for the >one site which can't understand the former yet. >Mangling Pathalias output to do the same is real easy via a simple sed script, >which transforms > host: hop1!hop2!hop3!host!%s >into > host: hop1!host!%s >and which is left as an exercise to the reader.) My general strategy, and that of MMDF's, is that anything beyond the first hop in the address is left as an excercise to the next hop, not this hop. The only modification of that strategy which I would allow is to look into the address for FQDN's and route directly to the last one. This might foil somebody who's trying to route around something but still putting FQDN's into their path. >This is based on the simple assumption that the next site along the path >really should know better how to get to the destination than I do, since it's >assumed to be closer to it. You can't control all the sites around you. Nor can you control what happens beyond your neighbors, but what happens out there will still go through your site occasionally. -- <- David Herron, an MMDF weenie, <- Formerly: David Herron -- NonResident E-Mail Hack <- <- Sign me up for one "I survived Jaka's Story" T-shirt!