Microsoft KB Archive/169640: Difference between revisions

From BetaArchive Wiki
m (Text replacement - ">" to ">")
m (Text replacement - """ to """)
 
Line 24: Line 24:


<pre>  Internet Mail Service (version 5.0). If possible, change the Message Delivery
<pre>  Internet Mail Service (version 5.0). If possible, change the Message Delivery
   To setting to &quot;Forward all messages to host&quot; instead of &quot;Use DNS,&quot; and enter
   To setting to "Forward all messages to host" instead of "Use DNS," and enter
   the IP address of the Send Mail host to avoid complications with Domain Name
   the IP address of the Send Mail host to avoid complications with Domain Name
   Service (DNS).
   Service (DNS).
Line 44: Line 44:
<pre>  is supposed to connect to. In one instance of this error, the administrator
<pre>  is supposed to connect to. In one instance of this error, the administrator
   was pinging the old IP address of his ISP. This address was changed and the
   was pinging the old IP address of his ISP. This address was changed and the
   new host did not accept his mail and returned the &quot;We do not relay&quot; error
   new host did not accept his mail and returned the "We do not relay" error
   message.
   message.
</pre>
</pre>

Latest revision as of 11:04, 21 July 2020

XFOR: All Outbound IMC Mail NDRs: We do not relay

Article ID: Q169640

The information in this article applies to:

  • Microsoft Exchange Server, versions 4.0, 5.0

SYMPTOMS

You cannot send Simple Mail Transfer Protocol (SMTP) mail to any SMTP domain name. You may receive a non-delivery report (NDR) about two minutes after you send the mail message, which reads:

   Your message did not reach some or all the intended recipients
            The following recipient could not be reached.
            The recipient name is not recognized.
        Microsoft Exchange:IMS:Nwggsc.org:nwggsc.org
        nt4_NWggsc(0000B0981)  751 twili => We do not relay

This problem may occur in a new installation or in a working environment after some changes have been made.

RESOLUTION

1. Check the configuration of the Internet Mail Connector (version 4.0) or

   Internet Mail Service (version 5.0). If possible, change the Message Delivery
   To setting to "Forward all messages to host" instead of "Use DNS," and enter
   the IP address of the Send Mail host to avoid complications with Domain Name
   Service (DNS).

2. Confirm that the Exchange Server computer can successfully ping the Interent

   Service Provider (ISP) host using the IP address.

3. Use the NSLookup utility to confirm the domain name, MX record, and the A-

   record.

4. Telnet to port 25 of the ISP's Mail server to verify that the ISP host is

   accepting communication to port 25.

5. Confirm that the IP address of the ISP really is of the same domain name it

   is supposed to connect to. In one instance of this error, the administrator
   was pinging the old IP address of his ISP. This address was changed and the
   new host did not accept his mail and returned the "We do not relay" error
   message.

This problem was encountered when using an MSDN connection to an ISP. In One circumstance the IMC worked for months, but the same problem can also happen in a new installation.

Keywords          : XFOR 
Version           : 4.0,5.0
Platform          : winnt
Issue type        : kbprb

Last Reviewed: April 14, 1999
© 1999 Microsoft Corporation. All rights reserved. Terms of Use.