"A configuration error in the e-mail system caused the message to bounce between two servers" NDR Message when you use the wrong smart host address in the SMTP connector

Symptoms

When you send mail to an external destination, the mail may not be delivered to the recipients. Also, in Microsoft Exchange System Manager, the default SMTP virtual server's SmallBusiness SMTP Connector (Remote Delivery) queue shows messages as being queued. These messages remain in the queue, and the sender may receive a non-delivery report (NDR) that is similar to:

The following recipient(s) could not be reached:

'user@microsoft.com' on 7/10/2002 1:34 PM

A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator.


server1.domain.com #5.3.5

Cause

This issue can occur if the SmallBusiness SMTP connector is set to forward mail to itself, or to an incorrect external SMTP smart host.

Resolution

To resolve this issue, follow these steps:
  1. Start Exchange System Manager, and then expand the Connectors container.

    Note By default, the SMTP connector is named "SmallBusiness SMTP Connector" in Small Business Server 2000 and Windows Small Business Server 2003. If you created an SMTP connector, the connector may not have this name. In this case, select the named SMTP connector instead.
  2. Right-click SmallBusiness SMTP Connector, and then click Properties.
  3. On the General tab, click either Use DNS to route to each address space on this connector or Forward all mail through this connector to the following smart hosts.
  4. If you click Forward all mail through this connector to the following smart hosts, verify the following items:
    • Make sure that smart host or hosts that appear in the window are those that are authorized by the Internet service provider (ISP) to relay mail for the Exchange Server e-mail domain. The smart hosts may be listed by fully qualified domain name (such as mailserver.domain.net) or by IP address.
    • Verify the accuracy of the fully qualified domain names (FQDNs) or IP addresses with the ISP.
    • Make sure that the smart hosts do not include the Exchange Server FQDN, its public IP address, or its private IP address.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
속성

문서 ID: 326304 - 마지막 검토: 2007. 12. 2. - 수정: 1

피드백