This article has been archived. It is offered "as is" and will no longer be updated.
In Microsoft Office Outlook 2007, you receive a read receipt from an Outlook client who is using a non-Exchange e-mail account. In the message body of the read receipt, the character set in the HTML code differs from the character set of the content-type header.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To resolve this problem for the newly generated read receipts, follow these steps:
Install hotfix 957692.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
957692 Description of the Outlook 2007 hotfix package (Outlook.msp): October 28, 2008
registry entry. To do this, follow these steps:
Exit all 2007 Microsoft Office programs.
Start Registry Editor.
In Windows Vista, click Start, type regedit in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.
In Windows XP, click Start, click Run, type regedit, and then click OK.
Locate and then select one of the following registry subkeys as appropriate:
Note Both these registry keys perform the same function.
On the Edit menu, point to New, and then click DWORD Value.
Type OutlookPlainTextReadReceipts, and then press ENTER.
Right-click OutlookPlainTextReadReceipts, and then click Modify.
In the Value data box, type 1, and then click OK.
On the File menu, click Exit to exit Registry Editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.