You follow the steps in article 907977 in the Microsoft Knowledge Base to implement the resolution for handling Rich Text Format (RTF) e-mail messages correctly. Then, you send an RTF e-mail message that includes an HTML-based attachment to a Microsoft Exchange Server 2003 server that is running the Microsoft Exchange Server 2003 Connector for Lotus Notes. However, the LME-NOTES-MEXNTS process of the Exchange Connector for Lotus Notes service stops responding on the Exchange server. Additionally, an event that resembles the following is logged on the Exchange server.

Event Type: Error
Event Source: MSExchangeNOTES
Event ID: 8225
Description: Process LME-NOTES-MEXNTS terminated unexpectedly

After you restart the Exchange Connector for Lotus Notes service, the Rich Text e-mail message is sent to the Badmail folder on the Exchange server.

Back to the top

To resolve this problem, install the latest version of the Exchange Server 2003 Connector for Lotus Notes. To obtain the latest version of the Exchange Server 2003 Connector for Lotus Notes, visit the following Microsoft Web site:

Back to the top

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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.

Prerequisites

Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2 to be installed on the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, the following services are automatically stopped and then restarted when you apply this hotfix:

•	The Microsoft Exchange Connectivity Controller service
•	The Exchange Connector for Lotus Notes service and all dependent services

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

File name	File version	File size	Date	Time
Lsmexif.dll	6.5.7903.0	233,984	21-Feb-2007	16:50

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

Call stack output

When this problem occurs, the following call stack is generated:

 # ChildEBP RetAddr  Args to Child               
00 000afb38 61e357d3 00de0000 00000000 00000088 ntdll!RtlAllocateHeap+0x1f5 (FPO: [Non-Fpo]) (CONV: stdcall)  01 000afb58 61e35820 00000001 00de0000 000afba0 mapi32!MAPIAllocateBufferExt+0x34 (FPO: [Non-Fpo]) (CONV: stdcall)  02 000afb6c 61e38dcf 00000080 000afba0 000afba4 mapi32!MAPIAllocateBuffer+0x26 (FPO: [Non-Fpo]) (CONV: stdcall)  03 000afb7c 61e416b9 00df0490 00000080 000afba0 mapi32!UNKOBJ_ScAllocate+0x11 (FPO: [Non-Fpo]) (CONV: stdcall)  04 000afba4 61e41828 00df0490 000afc70 000afbc4 mapi32!ScCreateSPV+0x38 (FPO: [Non-Fpo]) (CONV: stdcall)  05 000afbd4 61e4fd97 000afc70 0000000a 000afc20 mapi32!IPDAT_SetProps+0x11f (FPO: [Non-Fpo]) (CONV: stdcall)  06 000afcfc 61e41459 00d6e37d 00000000 000afbec mapi32!NewOOP+0x483 (FPO: [Non-Fpo]) (CONV: stdcall)  07 000afd38 003a5260 00de2178 00000060 00000000 mapi32!IAB_OpenEntry+0x12b (FPO: [Non-Fpo]) (CONV: stdcall)  08 000afd90 00366b04 00000000 000afe5c 00f2e5e4 lsmexif!MEXEConvertFLATENTRYLISTtoAddressList+0x109 (FPO: [Non-Fpo])  (CONV: cdecl)
09 000afe78 00367cc9 0040866c 00ec1f28 00000000 lsmexhc!MEXHCMessage::GetIPMProperty+0x2e9 (FPO: [Non-Fpo]) (CONV:  thiscall) 
0a 000afe9c 00403bac 00000001 001015d8 0010146c lsmexhc!MEXHCMessage::parse+0x160 (FPO: [Non-Fpo]) (CONV: thiscall)  0b 000afee8 0029f651 00000000 00408150 00000000 lsmexnts!recvFromExchange+0x160 (FPO: [Non-Fpo]) (CONV: cdecl)  0c 000aff08 0040201b 001015d8 00000000 00000000 lscps!EventManager::process+0x53 (FPO: [Non-Fpo]) (CONV: thiscall)  0d 000aff3c 004021aa 000affc0 00406d1f 00000004 lsmexnts!runApp+0x501 (FPO: [Non-Fpo]) (CONV: cdecl)  0e 000aff44 00406d1f 00000004 006753b8 00672920 lsmexnts!main+0x19 (FPO: [Non-Fpo]) (CONV: cdecl)  0f 000affc0 77e523cd 00000000 00000000 7ffde000 lsmexnts!mainCRTStartup+0x12f (FPO: [Non-Fpo]) (CONV: cdecl)  10 000afff0 00000000 00406bf0 00000000 78746341 kernel32!BaseProcessStart+0x23 (FPO: [Non-Fpo]) (CONV: stdcall)

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top