The information in this article applies to:
SYMPTOMS
When you use the Microsoft Exchange SNADS connector that comes with Microsoft Exchange Server Version 5.5, if a SNADS user attempts to send a message to a user who meets both of the following conditions, the SNADS system routes the message to the Exchange Server organization.
-and- CAUSEThe receiving message transfer agent (MTA) attempts to route the message to the correct location. At this point, the only other route is out the SNADS connector on the other side so the message is routed there and out. The SNADS system receives the message, routes back in, and a message loop occurs. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later: Component: Foreign Connectors
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. MORE INFORMATION
A new Exchconn.ini entry has been created that allows users to change this behavior. The entry is called AllowUnresolvedAddresses and it should be put under the [LME-SNADS-MEXIN] section in the Exchconn.ini file. Additional query words:
Keywords : exc55 |
Last Reviewed: September 8, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |