Article ID: 900087 - Last Review: October 25, 2007 - Revision: 3.3 The body of an e-mail message is garbled when the header field and body field are set to different character sets in Exchange Server 2003
NoticeImportant 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
(http://support.microsoft.com/kb/256986/
)
Description of the Microsoft Windows registry On This PageSYMPTOMSConsider the following scenario.
For example, a message has UTF-8 specified in the From field or in the To field. Additionally, the body of the message is encoded as ISO-8859-1. When you try to view it by using Outlook, the body of the message contains garbled characters. CAUSEThis problem occurs because Microsoft Exchange Server 2003 sets the PR_INTERNET_CPID property to the UTF-8 character set. The PR_INTERNET_CPID property is a superset for any header field character set and body field character set.
When a message uses two different language groups, Outlook tries to display the body of the message in UTF-8. Therefore, the body of the message is garbled. RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
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.PrerequisitesBecause of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:836993
(http://support.microsoft.com/kb/836993/
)
How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.Date Time Version Size File name ---------------------------------------------------------- 25-Aug-2005 01:55 6.5.7233.45 3,270,144 Mdbmsg.dll 04-Jun-2005 01:56 3,304 Redir.asp 25-Aug-2005 02:29 6.5.7233.45 5,177,856 Store.exe STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONWarning 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 this hotfix, you must create the following registry key. To do this, follow these steps:
| Article Translations
|
Back to the top
