home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!sdd.hp.com!hamblin.math.byu.edu!arizona.edu!mvb.saic.com!mx-list
- Newsgroups: vmsnet.mail.mx
- Subject: RE: Routing mail
- Message-ID: <009636A7.E0B205C0.6829@garnet.nist.gov>
- From: "Jonathan E. Hardis" <hardis@garnet.nist.gov>
- Date: 10 Nov 1992 17:41:55 -0500 (EST)
- Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 29
-
- > MX paths :
- >
- > STROPH $mcp show path
- >
- > Domain-to-path mappings:
- > Domain="stroph.univ-st-etienne.fr", Path=Local
- > Domain="stroph", Path=Local
- > Domain="[161.3.1.11]", Path=Local
- > Domain="UNIV-ST-ETIENNE.FR", Path=Local
- > Domain="rineta.univ-st-etienne.fr", Path=SMTP,
- > Route="rineta.univ-st-etienne.fr"
- > Domain="rineta", Path=SMTP, Route="rineta.univ-st-etienne.fr"
- > Domain="[161.3.1.13]", Path=SMTP, Route="[161.3.1.13]"
- > Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net"
- > Domain="*.BITNET", Path=SMTP, Route="mirsa.inria.fr"
- > Domain="*", Path=SMTP
-
- This method has a hidden premise: if a host (such as rineta.univ...) has
- both MX and A records in the name server, a mailer should give precidence
- to the MX address. That's how remote hosts know to send mail for rineta to
- stroph, even though it could also look up the IP address of rineta itself.
-
- So why should stroph act any differently? When it does the address
- resolution for Route=rineta.univ-st-etienne.fr, it will also use the MX
- record over the A record. In other words, in this application you can't
- use the name server at all (without getting a loop).
-
- As an alternative, try "hard wiring" the IP address into the configuration,
- Domain="rineta...", Path=SMTP, Route="[161.3.1.13]"
-