Microsoft KB Archive/230650

= XCON: How to Move Messages from One X.400 Connector Queue to Another X.400 Queue =

Article ID: 230650

Article Last Modified on 10/28/2006

-

APPLIES TO


 * Microsoft Exchange Server 4.0 Standard Edition
 * Microsoft Exchange Server 5.0 Standard Edition
 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q230650



SUMMARY
The following scenario describes the situation for how to move messages from one X.400 Connector queue to another:

Server A is in Houston, running Exchange Server 5.5 Service Pack 2, on Windows NT 4.0 Service Pack 3.

It has the following X.400 Connectors:

X.400 Connector to Florida Cost = 1 (connected site only to Florida)

X.400 Connector to Arizona Cost = 100 (connected site only to Arizona)

Houston --128 Kbps---Florida---T-1-Arizona

Arizona is the directory replication hub.

There is no direct link between Houston and Arizona.

There are messages sitting in the queue of the X.400 Connector to Arizona, and they are not getting delivered.

Original:

For example, If there are messages sitting in the queue to x400 connector to the Arizona, and are not getting delivered because of any reason. This article presents a way to move these messages to the other X400 connector to Florida queue on the same server.

In general, this article presents a way to move messages from one X.400 Connector queue to another X.400 Connector queue on the same server, if server has the proper routing information.



MORE INFORMATION
There are two approaches you can take:

Method One

 * 1) On the X.400 Connector from which you want to move messages, change the address space on the X.400 Connector, and make it invalid.
 * 2) Recalculate routing.
 * 3) Stop and restart the Message Transfer Agent (MTA) service.

Method Two

 * 1) Delete the X.400 Connector from which you want to move messages.
 * 2) Recalculate routing.
 * 3) Stop and restart the MTA service.

CAUTION: If the X.400 Connector is also involved in the directory replication topology, you must compensate for it.

Keywords: kbhowto KB230650

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.