Technical article 104807

Error: "Your name, 'systemname', is unknown to me" using MMDF on 5.0

OpenServer 5.0.0

Written · Last revised

Problem

Mail from a machine with SCO OpenServer Release 5 is sent
 out without problems, but incoming mail fails.  If sending
 mail from another SCO OpenServer 5 machine, the mail is
 queued correctly, but does not get delivered.  This
 message occurs in /usr/mmdf/log/chan.log on the sending
 machine if logging is set to BTR or FTR in mmdftailor(F):

(421) broncos.sco.com - Your name, 'systemname', is unknown to me

The above message is also displayed if deliver is run manually (using /usr/mmdf/bin/deliver -w -csmtp) on the smtp channel when mail is stuck in this queue.

If the system you are sending mail from is a non-SCO machine,
telnet to the smtp port:
$ telnet <systemname> 25
where <systemname> is the SCO OpenServer 5 machine.  This would
result in the display of the above error message and the telnet(TC)
connection immediately closed.

Cause

If you are running DNS, it may be due to a known problem
 with MX records or to incorrect permissions on the file
/etc/resolv.conf.  If you are not running DNS, it is the
 result of a problem between /etc/hosts and
 /usr/mmdf/table/smtp.chn. SCO is aware of these problems
 and is working to resolve them.
When using DNS:

If using the file /etc/resolv.conf, make sure its permissions are 644, or rw-r--r--.

Check your configuration file for hosts with MX records
set up like the following example.
Host1 is running named and is the primary nameserver for
abc.com.  The DNS configuration has A and MX records like
this:
host1             IN   A      132.147.210.80
                  IN  MX  5   host1.abc.com.
host2             IN   A      132.147.210.200
                  IN  MX  5   host1.abc.com.
Host2 has an /etc/resolv.conf with a nameserver entry pointing
to host1.  In this situation, mail from host2 to host1 will
fail with:

421 host1.abc.com - Your name, 'host2.abc.com', is unknown to me.

When not using DNS:
Compare entries for each host MMDF is configured to send mail
to in /etc/hosts and /usr/mmdf/table/smtp.chn.  hosts(SFF)
explains that the node name of each host should be listed in
the second field of this file, with the fully qualified domain
name (FQDN) in the third field. This is not correct, the FQDN
should be listed in the second field with he node name in the
third field.

When the MMDF Configuration program is run it builds an smtp.chn file with the FQDN of each host. However, when smtpd is called, receiving a request for incoming mail, it only checks the second field (the node name) of /etc/hosts. It then cannot find a match in smtp.chn which causes the mail to fail with the 'system is unknown to me' message.

Solution

If using DNS:

Using the above example, the problem is fixed by commenting out the MX record for host2 pointing to host1.

;host2     IN  MX  5   host1.abc.com.

There is no clean workaround to replace this MX record. If mail from host2 needs to be routed to host1, either aliasing can be used or an MX record for your domain:

abc.com.   IN  MX  5 host1.abc.com.
If not using DNS:
Edit /usr/mmdf/table/smtp.chn so that it has the node name
instead of the fully qualified domain name.  The way each
machine is listed in smtp.chn must match the second column
in /etc/hosts.  Editing smtp.chn is recommended over changing
/etc/hosts, as changing /etc/hosts may have ramifications in
other areas of the system.
/etc/hosts:
132.147.210.80  host1   host1.abc.com
132.147.210.200 host2   host2.abc.com
Original smtp.chn:
host1.abc.com:      132.147.210.80
host2.abc.com:      132.147.210.200
Fixed smtp.chn:
host1:              132.147.210.80
host2:              132.147.210.200

From the Xinuos technical article database, record 104807. Reproduced with permission. The original is at www.sco.com/ta/104807, 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.