Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!apple!snorkelwacker!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.mail.uucp Subject: Re: UUCP path cost reduction Message-ID: Date: 13 Aug 90 21:47:56 GMT References: <42693@mcdchg.chg.mcd.mot.com> <2r-/e2.s9@smurf.sub.org> <1990Aug10.221547.13301@chinet.chi.il.us> Organization: University of Karlsruhe, FRG Lines: 30 In comp.mail.uucp, article <1990Aug10.221547.13301@chinet.chi.il.us>, les@chinet.chi.il.us (Leslie Mikesell) writes: < In article <2r-/e2.s9@smurf.sub.org> urlichs@smurf.sub.org (Matthias Urlichs) writes: < >< One of the questions in the original posting asked whether it was ok < >< to eliminate from the pathalias output all of the paths that began < >< with the system acting as the "smart host". [...] < < >Yes. [...] < < [...] If you get mail for you!smarthost!some.domain!user < you will hand it to smarthost without looking farther down the path, and < smarthost will deliver it without sending it back. What's the problem? Not everyone generates full!bang!paths!to!destination!user. Some people beliebe in generating next!destination!user, i.e. handing off "destination!user" or "user@dest.dom.ain" to machine "next". The latter also happens if you're using BSMTP as your transport, which is a very good idea especially if someone is using weird addresses and/or if you or someone near you is expanding a mailing list. < Mail passing through should already have a next-hop of one of your < direct neighbors unless someone else made a mistake. < I don't quite think so. The view that my site can and should find out for itself where passing-through mail should be going next is, to me, equally valid. (Perhaps even more so, since, according to Pathalias, I'm closer.) -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(Voice)/621227(PEP)