Article View: comp.mail.misc
Article #5690Re: MMDF, SMTP, & DNS not working
From: Andras Salamon
Date: Wed, 29 Jun 1994 13:15
Date: Wed, 29 Jun 1994 13:15
63 lines
3771 bytes
3771 bytes
<rusty.b.ramser@ksc.nasa.gov> wrote: > The Problem (abridged version): > MMDF isn't delivering SMTP to any addresses that aren't > in my local domain area. > > The Setup: > SCO Open Desktop UNIX v3.0.0 installed and running > TCP/IP installed and running > BIND (a.k.a. DNS) installed and running > MMDF installed and running incorrectly (?) > > The Problem: > I selected to not configure a badhosts or badusers > channel -- the reasoning being, if MMDF properly uses DNS > there will not be any hostname that it can't resolve. > > Attempting > to mail to anyone outside of my domain (ksc.nasa.gov) > results in a failure message of the following type: > johndoe@company.com: (BHST) Unknown host/domain name > in "johndoe@company.com" tls011.ltr talks about an error in the MMDF configuration files; the default mkdev scripts work well when the badhosts channel is used but not otherwise, in my experience. When using a name server with MMDF, the SCO support database recommends running `mkdev mmdf' and then changing the line MTBL rootdom, file="root.dom", show="Root Domain", flags=route to MTBL rootdom, flags=ns, flags=domain, show="Root Domain" and then doing `cd /usr/mmdf/table; su mmdf -c ./dbmbuild'. There are other, different hacks which work; I personally have not tried the above solution but rely on a more complicated setup. One problem to watch out for when using a PPP connection in demand-dialup mode (with SCO UNIX SVR3.2v4.2, TCP/IP 1.2.1, and the net382c SLS patch dated 23 June 1994): the MMDF pseudo-sendmail does not seem to bring the link up to contact name servers but instead times out in about 5s when attempting to resolve the addresses. The `real' sendmail in the patch appears to force the connection up every time it is run (even if only to examine an empty local mail queue), ensuring that name servers are contactable before attempting to do lookups. Hence using sendmail instead of MMDF for delivery of outgoing mail works well. Extrapolating, I suppose that another possible solution would be to use MMDF but to replace the MMDF pseudo-sendmail binary with a wrapper which pings the remote side of the PPP interface and then calls the pseudo-sendmail, to guarantee the link being up. The /etc/if.ignore file does not seem to apply to any of the services being used (if the manual page is correct), so that doesn't look relevant in solving this problem. It seems a lot easier to just ditch MMDF for outgoing mail and use the sendmail supplied in the patch. I can't attest to sendmail doing a good job as an SMTP daemon, but as a delivery agent it seems to work fine. However, the standard setup doesn't set up the queue to be processed periodically, so I had to add `sendmail -q60m' to the startup sequence (a cron entry would be fine also). Comments, anyone? -- Andr\'as Salamon andras@is.co.za
Technical Details
Message-ID:
<2urs59$gqo@apollo.is.co.za>Path:
arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hermes!apollo.is.co.za!not-for-mailReferences:
<2upm5t$80v@niven.ksc.nasa.gov>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f4424,8d3f22a3380814f6 X-Google-Attributes: gidf4424,public X-Google-Thread: f8c9b,8d3f22a3380814f6 X-Google-Attributes: gidf8c9b,public X-Google-Thread: 1122ea,d32d0b1aec0e7126,start X-Google-Attributes: gid1122ea,public X-Google-ArrivalTime: 1994-06-29 06:22:25 PST Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hermes!apollo.is.co.za!not-for-mail From: andras@apollo.is.co.za (Andras Salamon) Newsgroups: comp.mail.misc,comp.unix.questions,biz.sco.general Subject: Re: MMDF, SMTP, & DNS not working Followup-To: comp.mail.misc,biz.sco.general Date: 29 Jun 1994 15:15:21 +0200 Organization: The Internet Solution Lines: 63 Message-ID: <2urs59$gqo@apollo.is.co.za> References: <2upm5t$80v@niven.ksc.nasa.gov> NNTP-Posting-Host: apollo.is.co.za