When you use Microsoft Outlook to add or to remove a delegate, the delegate is not added or deleted. Additionally, you receive the following error message:
The Delegates settings were not saved correctly. Unable to activate send-on-behalf-of list. You do not have sufficient permission to perform this operation on this object.
When you add a delegate, Outlook also tries to grant "send on behalf of" permission to the delegate by default. This permission is written to the publicDelegates attribute of your user object in Active Directory.
The issue that is described in "Symptoms" can occur for either (or both) of the following reasons.
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:
322756 How to back up and restore the registry in Windows
Outlook can be configured to enable you to add delegates without requiring you to grant the "send on behalf of" permission.
To have us configure Outlook to enable you to add delegates without requiring you to grant the "send on behalf of" permission, go to the "Here's an easy fix" section. If you prefer to do this yourself, go to the "Let me fix it myself" section.
To configure Outlook to enable you to add delegates without requiring you to grant the "send on behalf of" permission automatically, click the Download button. In the File Download dialog box, click Run or Open, and then follow the steps in the easy fix wizard.
For Windows 7, Windows 8 or Windows 10
For Windows Vista, Windows XP, Windows Server 2008 or Windows Server 2003
After you add the registry value, you can add a delegate without having write permissions to your own user object on the global catalog server. When you do this, a message that resembles the following message is logged in the Windows Application log to help track the event:
Event ID: 27
SOB error ignored
The "send on behalf of" permission is not needed for meeting-related messages. Microsoft Exchange Server specifically does not require that you have "send on behalf of" permissions to send a meeting request on behalf of another user. Therefore, even without the "send on behalf of" permission, delegates can successfully send meeting requests on behalf of the calendar owner.
However, when you use a delegate that does not have the "send on behalf of" permission to send a non-meeting-related message on behalf of the owner, the operation fails. For example, if a delegate tried to send an informational message "from the boss," that operation would fail. This is because the "send on behalf of" permission was not successfully granted.
If you want to grant another user the "send on behalf of" permission on your mailbox, you can do this on the Exchange Server. To do this in Exchange Server 2003, use the Delivery Restrictions button on the Exchange General tab of the Mailbox properties. For more information about the Exchange General tab, visit the following Microsoft website:
For more information about how to grant "send on behalf of" permissions in Exchange Server 2007, visit the following Microsoft website:
For information about how to grant "send on behalf of" permissions in Exchange Server 2010, visit the following Microsoft website:
Article ID: 2593557 - Last Review: 03/25/2016 00:04:00 - Revision: 14.0
r varAutoFirePV = 1; var varClickTracking = 1; var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write("