An Exchange 2000 recipient may receive an NDR or an e-mail message that is not formatted correctly

Article translations Article translations
Article ID: 830409 - View products that this article applies to.
Notice
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
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

Symptoms

A Microsoft Exchange 2000 Server recipient may receive an e-mail message that is not formatted correctly. Or, an Exchange 2000 recipient may receive a non-delivery report (NDR) after the recipient sends a message. These problems occur when all the following conditions are true:
  • An Exchange 2000 recipient sends an e-mail message that is relayed from a smart host to a mailbox on another Exchange 2000 server.
  • The e-mail message contains a line of text that has more than 998 characters.
  • The Exchange 2000 server sends messages in Multipurpose Internet Message Extensions (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-JP
    • csISO2022JP
    • UTF-7

Cause

This problem occurs because the extended characters that are used in 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, and the characters are labeled with incorrect 7-bit encoding during transport to the final mailbox server.

Resolution

To resolve this problem, obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup.For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 Update Rollup

More information

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.

The default MIME encoding in Exchange 2000 Server 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.

After you apply this rollup, you can use registry values to set the MIME encoding method in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent\TransferEncodingFor7bit
Use the values that are listed in the following table.
Collapse this tableExpand this table
ValueBehavior
0Always use default 7-bit encoding for both HTML and plain text.
1Always use quoted-printable encoding for both HTML and plain text.
2Always use base64 encoding for both HTML and plain text.
5Use quoted-printable encoding for HTML and plain text, unless plain-text line wrapping is enabled. If plain-text line wrapping is enabled, use quoted-printable encoding for HTML and 7-bit encoding for plain text.
6Use 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.
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 article. The hotfix to resolve this issue permits the administrator to use the registry to select the transfer encoding for all the character sets that are affected. The Administrator must set the encoding method correctly depending on the clients and their encoding capability.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Properties

Article ID: 830409 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Exchange 2000 Enterprise Server
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kbexchange2000presp4fix kbbug KB830409

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com