SCO Unix sendmail initialization problem

[Ronald van der Pol]

rbraun at spdcc.COM (Rich Braun) writes:

>If I reboot my SCO Unix system, incoming SMTP mail gets put into the
>queue (deferred, I think due to a host-name lookup failure) and not
>ever unqueued.  If I kill the sendmail daemon and restart it, the
>queue gets emptied out properly to the appropriate users' mailboxes.

You have to run MMDF's deliver daemon instead of the sendmail daemon.

>SCO ships the system with mmdf, and there may be an interaction problem
>with the mmdfdeliver daemon which is always there sitting in the
>background.  I'd just as soon dump mmdf entirely, though SCO's
>documentation implies that mmdf is superior and one should dump
>sendmail instead.  If mmdf is superior, then my first question is "How
>can I make it communicate with remote sendmail daemons?" and my second
>is "Why doesn't mmdf handle domain name service?"

It (like sendmail) talks to an SMTP daemon at the other side (port 25).
Because SCO (like always) installed an old version (and did it wrong too!).
MMDF supports DNS!
I find MMDF much easier to configure than sendmail. You should get the
official MMDF documentation though!! Don't rely on SCO.

>I'd like to hear from anyone who has had to set up e-mail on a TCP/IP-
>based LAN containing SCO Unix systems mixed with others (AIX, NCR, and
>so on), using a sendmail daemon on a non-SCO system to relay mail to
>the Internet via UUCP.  (I've got my domain name server set up to
>recognize systems on a domain called "kronos.com", and I've got SCO
>sendmail configured to relay all mail addressed to external domains
>to a given system on the LAN that knows how to pass it along to
>the world-wide Internet.)

We run SCO with MMDF and all our mail goes to an IBM-RT with sendmail.
No problems at all (besides working with PC's :-).

>-rich
--
Ronald van der Pol
rvdp at sow.econ.vu.nl
rvdp at cs.vu.nl