XFOR: SNADS: Bad In-body Addresses Cause the Generation of NDRs to Stop Lsdiamex.exe

• Microsoft Exchange Server, version 5.5

SYMPTOMS

When you send a message to the Internet through the Microsoft Exchange connectors (SNADS) with an invalid in-body address, the SNADS connector will attempt to send back a non-delivery report (NDR) to the user and crash while trying to do so. The following messages can be found in the Microsoft Exchange Connector Administrator's log viewer:

LME-SNADS-DIAMEX(002e) 3 00019:The value of the LASTMSGHEADERLINE keyword in the LME-SNADS-DIAMEX section is '/INTERNET'

LME-SNADS-DIAMEX(002e) 4 56155:Foreign ad-hoc recipient: ':user@domain.com'

LME-SNADS-DIAMEX(002e) 2 31200:Exchange Server has returned the condition: 80070057

LME-SNADS-DIAMEX(002e) 2 31201:Microsoft Package ID: Win 32

LME-SNADS-DIAMEX(002e) 2 31203:Extended NT information: The parameter is incorrect.

LME-SNADS-DIAMEX(002e) 2 31081:Cannot create custom Exchange address for user

LME-SNADS-DIAMEX(002e) 2 31200:Exchange Server has returned the condition: 80070057

CAUSE

The user improperly created the in-body address and a NDR was generated because the message was not accepted by Exchange Server. Because of the in-body address, there was not a valid return path for the NDR.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, please see the following article in the Microsoft Knowledge Base:

Q191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.

Additional query words:

Keywords : exc55 EXC55SP3Fix
Version : winnt:5.5
Platform : winnt
Issue type : kbbug