Select the product you need help with
The ByteEncoderTypeFor7BitCharsets setting does not take effect for the US ASCII character set after you install the hotfix that is mentioned in Microsoft Knowledge Base article 946641Article ID: 958552 - View products that this article applies to. SYMPTOMSYou install the hotfix that is discussed in Microsoft
Knowledge Base article 946641 to set the ByteEncoderTypeFor7BitCharsets key to
control the 7-bit transfer
encoding
method.
However, the ByteEncoderTypeFor7BitCharsets setting does not take effect for the US ASCII character set. For
example, when you set the value to 2, you expect this value to use Base64 encoding for MIME messages.
However, the encoding of MIME messages is still Quoted-Printable
(QP). RESOLUTIONTo resolve this problem, install Update Rollup 7 for
Exchange 2007 Service Pack 1. For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: Description of Update Rollup 7 for Exchange Server 2007 Service Pack 1
For more information about how to obtain the latest Exchange service pack or update rollup, see the following Exchange Help topic:
(http://go.microsoft.com/fwlink/?LinkId=157083)
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007
(http://go.microsoft.com/fwlink/?LinkId=152570)
After you apply this update, Exchange server supports the ByteEncoderTypeFor7BitCharsets option for 7-bit character set US ASCII (20127). The ByteEncoderTypeFor7BitCharsets option supports the following character sets after you install the hotfix:
MORE INFORMATION For more
information, click the following article number to view the article in the
Microsoft Knowledge Base: 836555
(http://support.microsoft.com/kb/836555/
)
Frequently asked questions about MIME and content conversion in Exchange 2000 Server and in Exchange Server 2003
946641
(http://support.microsoft.com/kb/946641/
)
How to change the method for transfer encoding after you apply Exchange 2007 S946641 to the Exchange 2007-based server that is running the Hub Transport role
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. PropertiesArticle ID: 958552 - Last Review: March 18, 2009 - Revision: 1.1 APPLIES TO
|
Back to the top
