Article ID: 2458423
In Microsoft Outlook 2010, when you disable the Do Not Forward command, Exchange Message Classifications commands are also disabled unexpectedly. These commands are in the Permission drop-down that is located on the Options tab of a new mail message.
Microsoft Office 2010 provides a feature to disable elements of the ribbon by using Group Policy settings. When you disable the Do Not Forward command, the Exchange Message Classifications feature is also disabled. This is because all items on the Permission drop-down list are managed together.
To disable the Do Not Forward command on the Permission drop-down list without also disabling Message Classification, apply the following update:
(https://support.microsoft.com/kb/2405793/ )Description of the Outlook 2010 hotfix package (outlook-x-none.msp): October 26, 2010
Registry key informationImportant 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:
322756After you install the hotfix package, follow these steps to enable the hotfix:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
You may also want to disable the Manage Credentials command on the Permission menu. To do this, apply the same Outlook 2010 Group Policy template file (outlk14.adm or outlk14.admx) that you used to disable the Do Not Forward command. The Control ID (also known as TCID) for the Manage Credentials control is 15831.
For more information about how to disable Office 2010 user interface items by using Group Policy settings, see the following topic in the TechNet library:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2458423 - Last Review: February 8, 2012 - Revision: 4.0