Mail clients that are not UTF-8 aware cannot view messages sent from Exchange 2000

When users use Microsoft Internet Explorer 5 or later to gain access to Microsoft Outlook Web Access (OWA) and send a message, recipients who have mail clients that are not Unicode Translation Format-8 (UTF-8) aware cannot view the message.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this problem, turn the feature to use regional characters on. To do this, follow these steps:

1. Click Start, click Run, type Services.msc, and then click OK.
2. Stop the MSExchangeIS service.
3. Stop the W3SVC service.
4. Click Start, and then click Run.
5. In the Open box, type regedit.
6. Locate the following key in the registry:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB
   \OWA\UseRegionalCharset
7. On the Edit menu, click Modify.
8. In the Value Data box, type 1, and then click Exit.
9. On the Registry menu, click Exit.
10. Restart the MSExchangeIS service.
11. Restart the W3SVC service.

Note If the registry key does not exist on the server, you can create it. To create the registry key, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA
3. Click Edit, click Add Value, and then type the following information in the Value box and in the REG_DWORD Data box:
   
   Value: UseRegionalCharset
   REG_DWORD Data: 1
4. Click OK, and then quit Registry Editor.

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.