Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. XADM: Messages Generate Immediate NDR When Sent to Certain Sites

XADM: Messages Generate Immediate NDR When Sent to Certain Sites

View products that this article applies to.

This article was previously published under Q180547

↑ Back to the top

Symptoms

Any message sent from the local Exchange Server site to another specific site is immediately rejected with a non-delivery report (NDR). The Event Log typically contains 254, 142, and 290 information and warning events similar to the following: 
   254 - MSExchangeMTA - X.400 Service - "Unable to correctly route the DN
         ... address using information in the gateway address routing
         table.
         The O/R address matches the local site address space

   142 - MSExchangeMTA - X.400 Service - "The MTA was unable to route the
         recipient DN ... the X.400 address ... the message MTSID... Check
         the routing table for a possible incorrect routing configuration.

   290 - MSExchangeMTA -  X.400 Service - "An NDR has been generated for
         MESSID, it was originally destined for DN ... and was to be
         redirected to ."

↑ Back to the top

Cause

One or more recipients in the local site have additional X.400 e-mail addresses defined in their properties that duplicate the address space or spaces of the destination site for the message.

↑ Back to the top

Resolution

There are two ways to resolve this problem, depending on your configuration:

  • If the additional e-mail addresses causing the problem were added in error, you can remove them from whatever recipients have such addresses specified. If the problem occurs suddenly, it is likely that someone has recently created or modified a recipient in the site with an additional e-mail address that duplicates the address space of the other site to which you can no longer send messages. In this case, you can try listing the mailboxes in order of date modified to try to isolate the mailboxes that were changed.
  • If the addresses are X.400 addresses and the address space of the other site is truly shared with the local site (up to OU4), you can enable sharing of X.400 address spaces in the Exchange Administrator program (select the "Share address space with other X.400 systems" check box in the Site Addressing object). This option should be used with care, as it disables the sanity checks and makes it possible to create undetected loops if the organization routing is not configured correctly.

↑ Back to the top

More information

X.400 e-mail addresses for all recipients in a site are scanned each time routing is recalculated, and a compilation of these is stored in a property of the Site Addressing object. This property is consulted when the MTA routes messages; if the destination address space of a message matches an address space in this property, the MTA sends an NDR on the message because routing for the message is ambiguous, unless the sharing of X.400 addresses spaces has been enabled (it is not enabled by default).

This behavior is by design and represents normal sanity checking performed by the MTA.

↑ Back to the top

Keywords: KB180547, kbusage, kbprb

↑ Back to the top

Article Info
Article ID : 180547
Revision : 4
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 370