XCON: Read Receipts Looping in the Message Transfer AgentLast reviewed: February 12, 1998Article ID: Q176127 |
The information in this article applies to:
SYMPTOMSWhen a message is sent to an Enterprise Solutions Limited recipient with a read receipt request, the read receipt is received by the originating message transfer agent (MTA), but is seen looping within the MTA when it is routed to the user. Event logs indicate the following loop detection event:
Source: MSExchange MTA Event: 201 Description: A loop has been detected in the message being transferred in. A non-delivery report was generated with reason code unable-to- transfer and diagnostic code loop-detected. [MTA XFER-IN 17 104] (14)A non-delivery report (NDR) event in the form of Event ID 290 is also generated in the event logs.
STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K Keywords : kbbug5.00 kbfix5.00.sp2 XCON Version : WINDOWS:5.0 Platform : WINDOWS Issue type : kbbug Solution Type : kbfix |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |