home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!uiunix!ahby
- From: ahby@uiunix.ui.org (Shane McCarron)
- Newsgroups: comp.sys.ncr
- Subject: Using SMTP mail under SVR4.0
- Message-ID: <390@uiunix.ui.org>
- Date: 22 Dec 92 16:49:08 GMT
- Organization: UNIX International, Parsippany, NJ 07054
- Lines: 57
-
- We are using SVR4.0 release 2.0 on a 3445. We just recently connected
- to the Internet, and have configured our system, which is our
- mailhost, to use mailsurr/smtpqer/smtp to deliver mail via the
- Internet. We are using DNS, and it is working correctly.
-
- The problem is that the smtp program does not correctly attempt to
- deliver messages to alternate mx forwarders when the primary mx
- forwarder for a given site is unreachable. Specifically, if I attempt
- to send mail to user@pyramid.com (for example), there are several MX
- forwarders available:
-
- pyramid.com preference = 0, mail exchanger = sword.eng.pyramid.com
- pyramid.com preference = 100, mail exchanger = gossip.pyramid.com
- pyramid.com preference = 101, mail exchanger = bertha.pyramid.com
- Authoritative answers can be found from:
- sword.eng.pyramid.com inet address = 129.214.214.10
- gossip.pyramid.com inet address = 129.214.1.101
- bertha.pyramid.com inet address = 129.214.1.100
- NS.UU.NET inet address = 137.39.1.3
- BERT.PYRAMID.COM inet address = 129.214.3.2
-
- Unfortunately, sword.eng.pyramid.com is unreachable:
-
- % ping sword.eng.pyramid.com
- ICMP Host Unreachable from gateway Pyramid-gw.ALTER.NET (137.39.51.2)
- for icmp from dionysus (192.203.65.102) to sword.eng.pyramid.com (129.214.214.10)
-
- However, gossip.pyramid.com is reachable:
-
- % ping gossip.pyramid.com
- gossip.pyramid.com is alive
-
- When /usr/lib/mail/surrcmd/smtp attempts to deliver a message to
- pyramid.com, and run in debug mode, it produces the following output:
-
- buildmxlist got 290
- buildmx rcode 0 ancount 3 qdcount 1 aa 0
- MXsave sword.eng.pyramid.com
- MXsave gossip.pyramid.com
- MXsave bertha.pyramid.com
- add 129.214.214.10 (sword.eng.pyramid.com)
- add 129.214.1.101 (gossip.pyramid.com)
- add 129.214.1.100 (bertha.pyramid.com)
- Try <129.214.214.10.0.25>
- Try <129.214.1.101.0.25>
- Try <129.214.1.100.0.25>
- No route to host
-
- Clearly, the second try above should have succeeded.
-
- Our guess is that the TLI based smtp software is not correctly
- attempting to contact alternate MX forwarders when the primary is
- unavailable. Any assistance in further diagnosing and repairing this
- problem would be greatly appreciated.
- --
- Shane P. McCarron ATT: +1 201 263-8400 x232
- Project Manager UUCP: s.mccarron@ui.org
-