XADM: Messages Not Rerouted Between Two X.400 Connectors in Same Site

In this scenario, an Exchange site has two servers, and each of them has an X.400 Connector with the same address space but different costs. For example: Messages created on a mailbox on ServerB and addressed to an X.400 recipient are routed this way: If ServerA goes down, then messages created on a mailbox on ServerB and addressed to an X.400 recipient are not locally rerouted to ServerB's X.400 Connector but remain indefinitely in ServerB's MTA queue to ServerA.

NOTE: This happens only with Custom recipients. Messages sent to a one off address are correctly rerouted.

To work around this problem, a manual intervention (modification of the connector cost, recalculation of the routing table) is required to activate the rerouting.

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For more information, please see the following article in the Microsoft Knowledge Base:

Microsoft has confirmed this to be a problem in Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 2.