LUCICHM%LEA1@LEAV-EMH.ARMY.MIL (02/07/90)
From: Mike Lucich, Systems Programmer, Fort Leavenworth, Kansas
We run VM TCP/IP R1.2.1, configured to provide an SMTP/RSCS gateway, without
a name server, since we do not have SQL. When a PROFS user sends mail to a
completely incorrect internet node (ie user@just.plain.wrong.address), SMTP
returns the mail quickly to the sender. But when mail is sent from RSCS to a
bad internet node address that happens to include a valid domain (for example:
user@justplain.army.mil), our SMTP queues the mail to a bogus looking numeric
address (ie 0.16.107.232), and rejects it after 3 days as if the destination
was valid but unreachable. Surely this is not how TCP/IP is meant to work.
We use an up to date HOSTS LOCAL file to generate the HOSTS SITEINFO and HOSTS
ADDRINFO files.
We have not, to date, put down any maintenance on TCP/IP. In the file named
TCPIP DATA, the line with a value for NSinterAddr has been commented out. I
believe this was done as part of the install process to indicate that there
will be no name server.
Any help on this will be greatly appreciated. I also wish to thank all those
who helped me get subscribed to this list.
Sincerely,
Mike Lucich