Article ID: 814036
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
When a message is sent from an Exchange Server 5.5-based Internet Mail Client (IMC) to an Exchange 2000 Server-based computer, MAPI may fail to process the message. When you try to open the message or to mark it as "Read", you may receive the following error message:
CAUSE
This problem is caused by incorrect handling of the Transport Neutral Encapsulation Format (TNEF). This information is contained in the header of the message.
RESOLUTION
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:
824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix 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.
Date Time Version Size File name ----------------------------------------------------------- 04-Feb-2003 13:45 6.0.6412.0 3,915,776 Cdoex.dll 04-Feb-2003 13:37 6.0.6412.0 827,392 Davex.dll 04-Feb-2003 13:12 6.0.6412.0 958,464 Emsmdb32.dll 04-Feb-2003 13:45 6.0.6412.0 3,567,616 Excdo.dll 04-Feb-2003 13:34 6.0.6412.0 258,048 Exmime.dll 04-Feb-2003 13:37 6.0.6412.0 2,129,920 Exoledb.dll 04-Feb-2003 13:31 6.0.6412.0 81,920 Exosal.dll 04-Feb-2003 13:37 6.0.6412.0 303,104 Exprox.dll 04-Feb-2003 13:07 6.0.6412.0 2,265,088 Mdbmsg.dll 04-Feb-2003 12:32 6.0.6412.0 32,768 Mdbrole.dll 31-Jul-2002 22:37 6.0.6300.1 84,480 Spuninst.exe 04-Feb-2003 13:33 6.0.6412.0 4,612,096 Store.exe
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
TNEF is used during Internet messaging. When a message is received, TNEF is used to translate message properties into MAPI properties. TNEF uses Winmail.dat that is sometimes attached to the message to retrieve MAPI properties for the message. This usually occurs before the client receives the message. For additional information about mail formats, click the following article numbers to view the articles in the Microsoft Knowledge Base:
241538 OL2000: How Message Formats Affect Internet Mail
290809 OL2002: How Message Formats Affect Internet Mail
269186 OL2000: The Received Message Is Different from the Message That You Sent
257800 XADM: Winmail.dat Attached to All Internet Messages Regardless of Setting on Client
Additional query words: kbExchange2000preSP4septbarFix
Keywords: kbhotfixserver kbqfe kbexchange2000presp4fix kbenv kberrmsg kbqfe kbfix kbbug KB814036
