Mail Is Routed Through a Connector That Does Not Have Entire Organization Scope in Other Routing Groups (811706)


The information in this article applies to:

  • Microsoft Exchange 2000 Server
  • Microsoft Exchange 2000 Server SP1
  • Microsoft Exchange 2000 Server SP2
  • Microsoft Exchange 2000 Server SP3

SYMPTOMS

In an environment that has multiple routing groups, and where a local connector for one routing group is not functioning correctly, messages may be rerouted through a connector in another remote routing group. The messages may be rerouted even though the scope setting of the connector in the remote routing group is set to Routing Group or to Local.

WORKAROUND

To work around this behavior, only use scope restrictions in spoke sites.

STATUS

This behavior is by design.

MORE INFORMATION

The following example illustrates this behavior:

An environment has three routing groups: Routing Group 1 (RG1), Routing Group 2 (RG2), and Routing Group 3 (RG3). Each of these routing groups has a Simple Mail Transfer Protocol (SMTP) connector that has the same address space and the same cost properties. The scope of the connectors in RG1 and in RG3 is set to Entire Organization, and the scope of the connector in RG2 is set to Routing Group. RG1 and RG2 are connected by a routing group connector, and RG2 and RG3 are also connected by a routing group connector. The environment is shown in the following diagram: 

SMTP             SMTP             SMTP  
(Entire          (Routing         (Entire
 Organization)    Group)           Organization)  
 |                |                |
 |                |                |
RG 1 <-- RGC --> RG 2 <-- RGC --> RG 3

If a user in RG1 sends a message to an external SMTP address, the categorizer of the local server determines two suitable connectors. The suitable connectors are the local SMTP connector and the SMTP connector in RG3. The connector in RG2 is not chosen because of its scope restriction. If both connectors are functioning correctly, mail is routed through the local connector. But if the local connector is not functioning correctly, the categorizer routes the message to RG2. When the bridgehead in RG2 receives the message, the routing engine determines the next hop. This time, all three connectors might be used because the mail is in RG2; therefore, the scope restriction is not important. Because the connector in RG1 is not functioning correctly, and because the additional hop in the route through the RG3 connector means that the cumulative cost property values in that route are higher than they are in the route through the local SMTP connector, the local SMTP connector is chosen.
Modification Type:MinorLast Reviewed:4/28/2005
Keywords:kbprb KB811706
©2004 Microsoft Corporation. All rights reserved.