Path: utzoo!attcan!uunet!tektronix!percival!parsely!agora!batie From: batie@agora.UUCP (Alan Batie) Newsgroups: comp.mail.uucp Subject: Re: Another example why not to re-route Message-ID: <1295@agora.UUCP> Date: 13 Dec 88 08:35:01 GMT References: <14430@comp.vuw.ac.nz> <831@mailrus.cc.umich.edu> <38@microsoft.UUCP> Reply-To: batie@agora.hf.intel.com (Alan Batie) Organization: Organization? You've got to be kidding! Lines: 28 In article <38@microsoft.UUCP> w-colinp@microsoft.UUCP (Colin Plumb) writes: >How does this re-routing rule sound: > >If you see a domain-style name (even .uucp) in the bang path, it's okay >to route to that site. Sites without domains are not necessarily distinct, >and should not be routed to, even if they appear before the domain-style name. This is, in fact, an option to smail, but I've added a twist that others may find useful: I doubt the powers that be want internal mail to get sent to Competitor.Com because some butterfingers mistyped an address, or was lazy and didn't put a domain on it. Therefore, I use the "JUSTDOMAIN" option on smail 2.5, so that only a domain form will get routed. Since "user@site" is considered a domain form, if the route routine is called, I check to see if there is a dot in the domain part, and if not, "MYDOM" is tacked on to it. Thus, to get outside routing, you *have* to use "user@site.uucp" or "user@site.domain". Mail passing through should have a bang path already and not be affected, unless a bad path is given, which would be routed and converted into an internal form. This is not desirable, but I don't see an alternative. I can't merge the internal sites into the paths file without domains as there are name conflicts that have to be hidden under a domain. This is on a system without sendmail; I'm having enough problems with sendmail on the other half of the gateway... -- Alan Batie +1 503 640-4013 batie@agora.hf.intel.com "He was born on third base... tektronix!tessi!agora!batie and thought he hit a triple"