Article ID: 816135
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Exchange 2000 Conferencing Server Service Pack 3
- Microsoft Exchange 2000 Conferencing Server Service Pack 2
- Microsoft Exchange 2000 Conferencing Server Service Pack 1
- Microsoft Exchange 2000 Conferencing Server
- Microsoft Exchange 2000 Enterprise Server
- Microsoft Exchange Server 2000 Service Pack 3
- Microsoft Exchange 2000 Server Service Pack 2
- Microsoft Exchange Server 2000 Service Pack 1
- Microsoft Exchange 2000 Server Standard Edition
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
In Exchange 2000, the message body of incoming read receipts is replaced by standardized text.
CAUSE
Incoming multipart/report messages are converted to the corresponding MAPI reports.
RESOLUTION
Cumulative Rollup Information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For more 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 Microsoft 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.
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 tool in Control Panel.Component: Information Store
Date Time Version Size File name -------------------------------------------------------------- 03-Jun-2003 15:46 6.0.6472.0 3,915,776 Cdoex.dll 03-Jun-2003 15:40 6.0.6472.0 827,392 Davex.dll 03-Jun-2003 15:38 6.0.6472.0 577,536 Dsaccess.dll 03-Jun-2003 14:47 6.0.6472.0 184,320 Dscmsg.dll 03-Jun-2003 15:46 6.0.6472.0 3,575,808 Excdo.dll 03-Jun-2003 15:38 6.0.6472.0 258,048 Exmime.dll 03-Jun-2003 15:40 6.0.6472.0 2,138,112 Exoledb.dll 03-Jun-2003 15:36 6.0.6472.0 81,920 Exosal.dll 03-Jun-2003 15:40 6.0.6472.0 307,200 Exprox.dll 03-Jun-2003 14:39 6.0.6472.0 49,152 Mdbevent.dll 03-Jun-2003 15:08 6.0.6472.0 2,285,568 Mdbmsg.dll 03-Jun-2003 14:41 6.0.6472.0 32,768 Mdbrole.dll 03-Jun-2003 15:38 6.0.6472.0 24,576 Mdbtask.dll 03-Jun-2003 15:37 6.0.6472.0 4,648,960 Store.exe
Create a New Value in the Registry
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.After you install the hotfix, you must create a new value in the registry.
- Click Start, click Run, type regedit32, and then click OK.
- Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent - On the Edit menu, click Add Value, and then add the following registry value:
Value name: RenderMDNsAsMessages
Data type: REG_DWORD
Value data: 0 = treat read receipts as reports, 1 = treat read receipts as messages. 0 is default. - Quit Registry Editor.
- Restart the Information Store service.
MORE INFORMATION
In Exchange 2000, the body of the read receipt is changed because multipart/report messages are converted to the corresponding MAPI reports (read receipts, delivery receipts, non-delivery receipts). These MAPI reports are made up of a set of special properties; in particular, the rendered text is a standardized and localizable text. The PR_BODY, _RTF_COMPRESSED or the _BODY_HTML message properties are not set on these reports. Therefore, the text/plain body part is not preserved.
When you set the RenderMDNsAsMessages registry value to a value that is greater than zero, Exchange 2000 behaves like Microsoft Exchange Server 5.5. In other words, multipart/report messages are treated as multipart/mixed messages, and therefore they are converted to the IPM.note message type.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Additional query words: kbExchange2000preSP4septbarFix
Keywords: kbhotfixserver kbexchange2000presp4fix kbqfe kbfix kbbug KB816135
