Article ID: 885419
Article Last Modified on 10/30/2007
APPLIES TO
- Microsoft Exchange Server 2003 Service Pack 1
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you open an e-mail message from your Microsoft Exchange Server 2003 mailbox, the e-mail message is not formatted correctly. The contents may appear scrambled. Or, after you send an e-mail message, you may receive a non-delivery report (NDR) that is similar to the following:
CAUSE
This problem occurs when all the following conditions are true:
- An Exchange 2003 recipient sends an e-mail message that is relayed from a smart host to a mailbox on another Exchange 2003 computer.
- The e-mail message contains a line of text that has more than 998 characters.
- The Exchange 2003 computer sends messages in MIME format by using 7-bit encoding.
- One of the following character sets or code pages are used to compose the e-mail message:
- ISO-2022-KR
- ISO-2022-JP
- csISO2022JP
- UTF-7
This problem occurs because the extended characters that are used in these international character sets are not included in the ASCII 7-bit character range. Therefore, an e-mail message that contains more than 998 characters cannot be wrapped. Additionally, the characters are labeled with incorrect 7-bit encoding during transport to the final mailbox server.
RESOLUTION
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
To install this hotfix, you must be running Exchange Server 2003 Service Pack 1 (SP1). For additional information about how to obtain Exchange Server 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003
Restart requirement
You do not have to restart your computer to install this hotfix. However, the Microsoft Exchange Information Store service and the Microsoft Exchange Event service are automatically restarted during the hotfix installation.
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 tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 26-Oct-2004 20:05 6.5.7232.46 3,230,720 Mdbmsg.dll 08-Oct-2004 02:12 3,304 Redir.asp 26-Oct-2004 20:44 6.5.7232.46 5,139,968 Store.exe
Hotfix installation instructions
After you install this hotfix, you must configure a registry entry to set the MIME encoding method that you want to use. To do this, follow these steps:
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent
- On the Edit menu, point to New, and then click DWORD Value.
- Type TransferEncodingFor7bit as the entry name, and then press ENTER.
- Right-click TransferEncodingFor7bit, and then click Modify.
- In the Base area, click Decimal.
- In the Value data box, type the value that you want, and then click OK.
The values that you can use are listed in the following table:
Note You must set the encoding method correctly. The encoding method depends on the clients and their encoding capability.
The default value of 0 for 7-bit encoding is used if the registry subkey value contains a value that is not listed in this table or if the TransferEncodingFor7bit registry entry is not present.Value Behavior 0 Always use default 7-bit transfer encoding for both HTML and plain text.
Note This is the equivalent of setting Exchange to its pre-hotfix default behavior.
1 Always use Quoted-Printable (QP) encoding for both HTML and plain text. 2 Always use Base64 encoding for both HTML and plain text. 5 Use QP encoding for HTML and plain text, unless plain text line wrapping is enabled. If plain text line wrapping is enabled, use QP encoding for HTML and 7-bit encoding for plain text. 6 Use Base64 encoding for HTML and plain text, unless plain text line wrapping is enabled. If plain text line wrapping is enabled, use Base64 encoding for HTML and 7-bit encoding for plain text. 13 Always use QP encoding for HTML. Always use 7-bit encoding for plain text. 14 Always use Base64 encoding for HTML. Always use 7-bit encoding for plain text. - Quit Registry Editor.
- Restart the Microsoft Exchange Information Store service. To do this, follow these steps:
- Click Start, click Run, type services.msc, and then click OK.
- Right-click Microsoft Exchange Information Store, and then click Restart.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
The default MIME encoding in Exchange 2003 is 7-bit transfer encoding. The MIME encoding in some Asian languages must be set to an encoding method that is different from 7-bit encoding to wrap lines of text that contain more than 998 characters.
For additional information about this same problem in Microsoft Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:
830409 An Exchange 2000 recipient may receive an NDR or an e-mail message that is not formatted correctly
For additional information about a version of this hotfix for the original release version of Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
835992 An e-mail message may not be formatted correctly when a recipient sends the e-mail message from an Exchange Server 2003 computer to another Exchange recipient
For additional information about Microsoft software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
817903 New naming schema for Exchange Server software update packages
Additional query words: XADM
Keywords: kbqfe kbhotfixserver kbexchange2003presp2fix kbfix kbbug KB885419
