XADM: Messages Generate Immediate NDR When Sent to Certain Sites

ID: Q180547


The information in this article applies to:


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...

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


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.


RESOLUTION

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


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.

Additional query words: X400 address share routing calculation


Keywords          : kbusage XADM 
Version           : 
Platform          : 
Issue type        : kbprb 

Last Reviewed: March 27, 1999