Japanese DBCS characters are corrupted when you reply to a message or forward a message in an Exchange Server 2007 SP1 environment

When you reply to a message or forward a message by using a Microsoft Office Outlook client in a Microsoft Exchange Server 2007 Service Pack 1 (SP1) environment, Japanese DBCS characters that appear in any of the following fields become corrupt:

• The display name of the sender
• The display name of the recipients
• The subject
• The file name of an attachment
• The message body

This problem occurs if the field contains one byte Kana.

The problem also occurs if the message is sent by Outlook Web Access (OWA) in an Exchange Server 2007 SP1 environment.

Note This article does not list all conditions under which this problem may occur.

To resolve this problem, install Update Rollup 5 for Exchange 2007 Service Pack 1.
For more information about Update Rollup 5 for Exchange 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base: After you install Update Rollup 5 for Exchange Server 2007 Service Pack 1, you must add a new entry in the Edgetransport.exe.config XML file to enable the hotfix on the server. To do this, follow these steps:

1. On the Exchange 2007-based server that is running the Hub Transport role, open Windows Explorer.
2. Locate the following folder:
   drive :\Program Files\Microsoft\Exchange Server\Bin
3. Make a backup copy of the EdgeTransport.exe.config file by saving a version of the file. Name the backup copy EdgeTransport.exe.config.old.
4. Open the EdgeTransport.exe.config file in Notepad, and then locate the following line between the <appsettings> segment and the </appsettings> segment:

   <add key="PreferredInternetCodePageForShiftJIS" value="50220" />
   

   Note If this line does not exist between the <appsettings> segment and the </appsettings> segment, insert this line.
   
   Note If you set the value of the PreferredInternetCodePageForShiftJIS key to "50222", the problem occurs.
5. Save the changes, and then exit Notepad.
6. Restart the Exchange Transport service.

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