XFOR: SNADS: Bad Inbody Addresses Cause the Generation of NDRs to Crash Lsdiamex.exeID: Q215947
|
When you send a message to the Internet through the Microsoft Exchange connectors (SNaDS) with an invalid inbody 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 messges 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
The user improperly created the inbody address and a NDR was generated because the message was not accepted by Exchange Server. Because of the inbody address, there was not a valid return path for the NDR.
A 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.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
Component: Exchange SNADS Connector
File name | Version |
---|---|
Lsdiamex.exe | 5.5.2543.0 |
Q154871 Determining If You Are Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.
Additional query words:
Keywords :
Version : winnt:5.5
Platform : winnt
Issue type : kbbug
Last Reviewed: August 3, 1999