This also some of the issues in some forums to me; today I found an answer and solution:
symptom
When you send an email to a user or group with a transfer restriction, the email transmission speed may be slower than expected. In some cases, the message may have to stay in the Exchange Mail Classifier before being transmitted.
the reason
This problem may occur if you configure the transmit restriction on the above users or groups to reject mail based on the communication group or universal security group member. For example, on the Exchange General tab of the user account or a distribution group property, click "From everyone, except" under Mail Limit, and then add a communication group to the exception list.
If you send an email to a recipient, the recipient has been configured with a restriction rule, which refuses to receive mail from a particular distribution group or security group member, then Exchange 2000 Server must expand the group. Check that the sender is a member of the restricted group. Exchange 2000 Server does not caches the results of this group expanded, so you have to perform expansion each time. If you send an email to a group containing many recipients, these recipients have configured a transfer restriction rule, which refuses to receive messages sent by members of the distribution group containing many members, Exchange 2000 Server A restricted distribution group must be expanded separately for each member of the group that sends a message. In addition, if a fault that occurs in this process, Exchange Server stops the group expansion process and then retry this connection after an hour. This will cause mail to stay in the classifier queue and may delay the mail processing process.
alternative method
To resolve this issue, use users you intend to reject its mail separately in a routing group, then create a transfer restriction based on the connector restriction:
1. In the Exchange System Manager, create a new routing group that allows the group to include all users who intend to make messages they send. For additional information about how to create a routing group, click the article number below to see the article in the Microsoft Knowledge Base:
266744 xadm: how to create a routing group
319416 How to: Use routing group connections in Exchange 2000
2. Create a SMTP connector that contains a route group containing non-restricted users to a new route group containing the restricted user. This ensures that mail from non-restricted email recipients is successfully transferred to the restricted user's mailbox. To do this, follow these steps:
a. Under the non-restricted route (such as "first routing group"), right-click "Connector", point to "New", and then click SMTP Connector. b. In the Name box, type a descriptive name. For example, type allow message to rest. c. Click "Transfer all messages for this connector to the following smart host", then type the name or IP address of the smart host belonging to the restricted route group. The IP address must be enclosed in both brackets ([]). d. Under the Local Bridgehead, click Add, click the SMTP virtual server from the non-restricted route group, and then click OK. e. Click the Connection Routing Group tab, and then click Add. f. In the Route Group list, click the restricted routing group, and then click OK. g. Click Apply, and then click OK. 3. Create a SMTP connector from the restricted route group to the non-restricted route group. This is to prevent the restrictions of the mail backlog sent by the restricted user in the restricted path of the "unable to reach the destination" queue. To do this, follow these steps:
a. Under the restricted route, right-click "Connector", point to "New", and then click SMTP Connector. b. In the Name box, type a descriptive name. For example, type Block Messages to Non-RestricTed Users. c. Under the Local Bridge, click Add, click the SMTP virtual server from the restricted routing group, and then click OK. d. Click "Refer to all messages of this connector to the following smart host", then type the name or IP address configured to delete the message or return the message. For example, type the IP address of the server you use as a bridgehead server and enclose the address in square brackets ([]). This is to create a loop, and the message will be returned as a message that cannot be transmitted. Although this method does return mail as an unprepasible message, the unreported report (NDR) code will indicate that the reason for the unable to send mail is the presence loop instead of the transmission limit. e. Click the Connection Routing Group tab, and then click Add. f. On the Route Group list, click the non-restricted routing group, and then click OK. g. Click Apply, and then click OK. 4. Because the route group connector configuration in step 3 prevents you may have to allow NDR mail and transfer status notification (DSN) to be transferred between these routing groups, there is a need to modify the routing group in the restricted path. Connector so that it does not use it for system messages: a. Right-click the new routing group SMTP connector created in the restricted group, and then click Properties. b. Click the Content Limits tab, and then click System Mail check box under Allow Types. c. Click Apply, and then click OK. 5. Create a SMTP connector that allows system messages in the restricted route group:
a. Under the restricted route, right-click "Connector", point to "New", and then click SMTP Connector. b. In the Name box, type a descriptive name. For example, type Allow System Messages. c. Click "Refer to all messages of this connector to the following smart host", then type the name or IP address of the smart host belonging to the non-restricted route group. d. Under the Local Bridgehead, click Add, then add the SMTP virtual server from the restricted routing group. e. Click the Content Limits tab, and then click to clear the "Non-System Mail" checkbox. f. Click the Connection Routing Group tab, and then click Add. g. In the Route Group list, click the non-restricted routing group, and then click OK. h. Click Apply, and then click OK. 6. To make the user in the restricted route group can send an email through the Internet, add a lower SMTP connector with a lower overhead, so that it has the same address space with other connections to the Internet, but put this route Group is used as a connector scope:
a. Under the restricted route, right-click "Connector", point to "New", and then click SMTP Connector. b. In the Name box, type a descriptive name. For example, type Allow Internet Access. c. Under the Local Bridgehead, click Add, then add the SMTP virtual server from the restricted routing group. d. Click the "Address Space" tab, click "Roulet" under the Connector Scope, and then click Add. e. Click "SMTP", click OK, and then click OK again. Note: This step uses the default SMTP address space represented by an asterisk (*). Modify these settings to specify the address space used in your organization. The overhead displayed for this address space must be lower than the overhead of other SMTP connectors you created. f. Click Apply, and then click OK. Note: This workaround solution will only route a means of restriction transmission, and it can be expanded and will not be limited by the number of users in the restricted path group.
source:
Http://support.microsoft.com/default.aspx?scid=kb;zh-cn; 329171
If you have any questions in this article, please go to the nail forum discussion:
http://www.5dmail.net/bbs
