XCON: NDR is not Received When Sending to Bad PAB EntryLast reviewed: February 12, 1998Article ID: Q177867 |
The information in this article applies to:
Microsoft Exchange Server, version 4.0
Microsoft Exchange Server, version 5.0
Microsoft Exchange Server, version 5.5
SYMPTOMSWhen a Microsoft Exchange user sends a message to a recipient in their Personal Address Book (PAB), they not receive a Non-Delivery Report (NDR) if the PAB entry is invalid. This problem will only occur in the following circumstance:
as 1984.3. The connector does not have any Connected Sites information. The message to the invalid PAB entry can be tracked by setting the X.400 Service category of the MSExchangeMTA to Maximum logging in the Microsoft Exchange Administrator program. By looking for the 271 and 272 events in the Windows NT Event Viewer Application log, you will see that the message gets sent to the destination Microsoft Exchange Message Transfer Agent (MTA) successfully, a 271 event, then the resulting NDR from this system is received OK, a 272 event, and finally the MTA then passes this on to the Microsoft Exchange Information Store (IS), another 271 event. However, the originator of the message does not receive the NDR. If you turn on maximum logging for the Information Store (IS), specifically:
MSExchangeISPriv/Transport Sending & Transport Delivering MSExchangeISPriv/Transport/General/<all categories>you will see the following error in the Event Log:
Event ID : 2026 Source : MS Exchange Private Type : Information Category : Transport Description : The delivery of a report failed due to error 00000BB8. The report has been deleted. CAUSEThe MTA was not correctly handling Distinguished Name (DN) addresses. The MTA now checks these before sending and will NDR the message back to the originator with the following diagnostic information:
The recipient could not be transferred because it could not be downgraded. WORKAROUNDThe workaround for this is to use versions of the MTA greater than or equal to the following:
Exchange 4.0 : 996.56 Exchange 5.0 : 1459.72 Exchange 5.5 : 2110.00 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 KMicrosoft has confirmed this to be a problem in Microsoft Exchange Server, versions 4.0 and 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.
|
Additional query words: DN NDR 84 GWART X.500 one-off
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |