Lotus Notes connector stops responding when it receives a message from an X.400 connector

In the following situation, the Microsoft Exchange Connector for Lotus Notes in your Microsoft Exchange 2000 Server may stop responding and you receive an error message from the Dr. Watson utility:

1. An IBM Lotus Notes user sends a message from a Lotus Notes server to another Lotus Notes Server by using Simple Mail Transfer Protocol (SMTP).
2. A reply to this message is sent through an Exchange Notes Connector to an Exchange 2000 computer.
3. The Exchange 2000 computer sends this message to a UNIX server by using an X.400 connector.
4. The UNIX server sends this message to the original sender's Lotus Notes server by using an X.400 connector.
5. The user who originally sent the message receives the recipient's reply message, and then replies to it.
6. The new reply travels back from the originating Lotus Notes server over the X.400 connector to the UNIX server; it then travels over the X.400 connector to the Exchange 2000 computer, and then to the Exchange Notes Connector.
7. On the Exchange 2000 computer, the Lsmexout.exe process quits unexpectedly.

This problem occurs if the country attribute in the X.400 address is larger than the buffer that is allocated for it during the encapsulation of this address. This problem may be caused by a corrupted or an incorrectly formed X.400 domain-defined attribute (DDA). The calling function does not verify the length of the country attribute string before the calling function copies the attribute string into the allocated buffer. As a result, stack corruption occurs, and the Exchange Notes Connector stops responding.

Cumulative Rollup Information

To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Component: Microsoft Exchange Connector for Lotus Notes

The English version of this has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this problem, set the USEX400DDA = NO option in the Exchconn.ini file. To do this, follow these steps:

1. Open the Exchconn.ini file by using a text editor such as Notepad.
   
   By default, this file is located in the following folder:
   C:\Program Files\Exchsrvr\Bin
2. In the [LME] section, type the following information: USEX400DDA = NO
3. Save the file, and then quit the text editor program.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

For additional information about domain-defined attributes, click the following article number to view the article in the Microsoft Knowledge Base:

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.