Technical article 104773

Problems when running MMDF configuration to configure mail over UUCP.

OpenServer 5.0.0

Written · Last revised

Problem

MMDF does not allow you to specify a UUCP host as a smarthost
in the Forwarding screen.  If you specify only the machine name
as listed in /usr/lib/uucp/Systems file, this error occurs:

Bad host name "machine". Host names must be fully-qualified domain names, for example, "sosco.sco.COM

If a fully qualified host name is entered but the host name is only listed in the Systems file, and not in /etc/hosts or nameserver files, an error displays:

Forwarding host "machine.xyz.com" is not known to this site.

Cause

These are errors in the automatic MMDF configuration. This has been reported to SCO Engineering.

Solution

To configure Unknown Host Forwarding and/or Unknown User Forwarding to a UUCP host:

1. Configure UUCP through MMDF Configuration by selecting UUCP as a Network for MMDF.

2. Edit /usr/mmdf/mmdftailor manually and add the badhosts
and/or badusers channels as shown below.  These lines generally
occur at the end of the mmdftailor file.
Adding these two channels tells MMDF to route mail for unknown
hosts and unknown users to the smarthost (often your Internet
provider) entered as host="machine".  The machine listed here
should be the UUCP name of the smarthost as listed in the
Systems file.  In this example, the smarthost is dragon.

MCHN show="Smart-host Routing for hosts", name=badhosts, que=badhosts, tbl=uuchn, pgm=uucp, ap=822, mod=imm, host="dragon"

MCHN show="Smart-host Routing for users", name=badusers, que=badusers, tbl=uuchn, pgm=uucp, ap=822, mod=imm, host="dragon"

3. Check that the MTBL line for uucpdom shows file=uucp.dom instead of local.dom.

Change:
MTBL show="UUCP domain", name=uucpdom, file=local.dom,
flags=domain, flags=partial
To:
MTBL show="UUCP domain", name=uucpdom, file=uucp.dom,
flags=domain, flags=partial

4. Edit /usr/mmdf/table/uucp.dom and change the line that lists your smarthost, the host you defined in the badhosts and badusers channels in mmdftailor.

Change:
dragon:            dragon.UUCP
To:
dragon:            dragon

5. Edit /usr/mmdf/table/uucp.chn and change the line that lists your smarthost.

Change:
dragon.UUCP:       dragon!%s
To:
dragon:            dragon!%s
6. Rebuild the MMDF database:
# cd /usr/mmdf/table
# ./dbmbuild -vn

7. Check that mail to an unknown host will be routed over the badhosts channel using checkaddr(ADM):

# cd /usr/mmdf/bin
# ./checkaddr -w user@sco.com

This returns that this address will be routed using the badhosts channel:

user@sco.com: user@sco.com:  queueing for badhosts: via 'dragon':
'user@sco.com'
OK

8. Send a test message to user@sco.com (or any unknown host or domain) and verify that it gets spooled and delivered.

From the Xinuos technical article database, record 104773. Reproduced with permission. The original is at www.sco.com/ta/104773, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.