Jerry Seinfield
asked on
Unable to send an email on behalf a shared resource mailbox in Exchange 2016. Permissions "appears to be ok
Hi Experts,
Paty Mason was granted full access to Resource- Benefits, with the ability to send emails as the resource account
She is the co-owner and needs to be on the account's profile to create daily rules, however, she has been unable to send emails as the account.
Troubleshooting done so far:
• Repairing her profile,
• Removed her access and grant her access again
• Removed her Outlook profile and re-added all resource account profiles.
• Was then about to add Mailbox account and view the emails but still cannot send emails.
• Search Error 0x80070005-0x0004dc-0x0005 24 on forums.
• https://www.admin-enclave.com/en/articles/exchange/292-resolved-you-do-not-have-the-permission-to-send-the-message-on-behalf-of-the-specified-user.html\
o See possible 10 solutions.
The user is still unable to send emails as the resource and is unable to use the profile, as she is getting the server error on the attachment. The resource is working as it should for all other users. Other resource accounts to which Patty has access are also working as they should.
User got the NDR whenever she tries to send the email. Refer to screenshots
Can someone please provide instructions step by step to resolve this issue including screenshots?
outlook-issue-2.jpg
Outlook-issue-3.jpg
NDR.jpg
Paty Mason was granted full access to Resource- Benefits, with the ability to send emails as the resource account
She is the co-owner and needs to be on the account's profile to create daily rules, however, she has been unable to send emails as the account.
Troubleshooting done so far:
• Repairing her profile,
• Removed her access and grant her access again
• Removed her Outlook profile and re-added all resource account profiles.
• Was then about to add Mailbox account and view the emails but still cannot send emails.
• Search Error 0x80070005-0x0004dc-0x0005
• https://www.admin-enclave.com/en/articles/exchange/292-resolved-you-do-not-have-the-permission-to-send-the-message-on-behalf-of-the-specified-user.html\
o See possible 10 solutions.
The user is still unable to send emails as the resource and is unable to use the profile, as she is getting the server error on the attachment. The resource is working as it should for all other users. Other resource accounts to which Patty has access are also working as they should.
User got the NDR whenever she tries to send the email. Refer to screenshots
Can someone please provide instructions step by step to resolve this issue including screenshots?
outlook-issue-2.jpg
Outlook-issue-3.jpg
NDR.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Since user is getting error: delegate-settings-not-save d-correctl y in her outlook you may follow below articles for resolution.
https://support.microsoft.com/en-in/help/2593557/the-delegates-settings-were-not-saved-correctly-error-when-you-try-to
https://davidvielmetter.com/tricks/delegate-settings-not-saved-correctly/
To configure Outlook to enable you to add delegates without requiring you to grant the "send on behalf of" permission yourself, follow these steps:
Exit Outlook.
Start Registry Editor. To do this, use one of the following procedures, as appropriate for your situation.
Windows Vista
Click Start, type regedit in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for confirmation, type the password or click Continue.
Windows XP
Click Start, and then click Run.
If you are prompted for an administrator password or for confirmation, type the password or click Continue.
Locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software \Microsoft \Office\x. 0\Outlook\ Preference s
If you use policies, click the following subkey:
HKEY_CURRENT_USER\Software \Policies\ Microsoft\ Office\x.0 \Outlook\P references
Note: x.0 in the above registry key represents your Outlook version. Please use one of the following values.
Outlook 2013: 15.0
Outlook 2010: 14.0
Outlook 2007: 12.0
Outlook 2003: 11.0
After you select the subkey that is specified in step 3, click New on the Edit menu, and then click DWORD Value.
Type IgnoreSOBError, and then press Enter.
Right-click IgnoreSOBError, and then click Modify.
In the Value data box, type 1, and then click OK.
On the File menu, click Exit to exit Registry Editor.
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:
Source: Outlook
Category: None
Event ID: 27
Type: Error
User: N/A
Computer: computer_name
Description:
SOB error ignored
More Information
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:
http://technet.microsoft.com/en-us/library/aa997251.aspx
For more information about how to grant "send on behalf of" permissions in Exchange Server 2007, visit the following Microsoft website:
http://technet.microsoft.com/en-us/library/bb124406(EXCHG.80).aspx
For information about how to grant "send on behalf of" permissions in Exchange Server 2010, visit the following Microsoft website:
http://technet.microsoft.com/en-us/library/bb124255.aspx
For additional history on this problem, please see the original Hotfix articles where the IgnoreSOBError registry value was first introduced.
950794 Error message when you try to add a delegate in Outlook 2007: "The Delegates settings were not saved correctly"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;950794
946208 Error message when you try to add a delegate in Outlook 2003: "The Delegates settings were not saved correctly"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;946208
Back to the top | Give Feedback
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice.
https://support.microsoft.com/en-in/help/2593557/the-delegates-settings-were-not-saved-correctly-error-when-you-try-to
https://davidvielmetter.com/tricks/delegate-settings-not-saved-correctly/
To configure Outlook to enable you to add delegates without requiring you to grant the "send on behalf of" permission yourself, follow these steps:
Exit Outlook.
Start Registry Editor. To do this, use one of the following procedures, as appropriate for your situation.
Windows Vista
Click Start, type regedit in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for confirmation, type the password or click Continue.
Windows XP
Click Start, and then click Run.
If you are prompted for an administrator password or for confirmation, type the password or click Continue.
Locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software
If you use policies, click the following subkey:
HKEY_CURRENT_USER\Software
Note: x.0 in the above registry key represents your Outlook version. Please use one of the following values.
Outlook 2013: 15.0
Outlook 2010: 14.0
Outlook 2007: 12.0
Outlook 2003: 11.0
After you select the subkey that is specified in step 3, click New on the Edit menu, and then click DWORD Value.
Type IgnoreSOBError, and then press Enter.
Right-click IgnoreSOBError, and then click Modify.
In the Value data box, type 1, and then click OK.
On the File menu, click Exit to exit Registry Editor.
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:
Source: Outlook
Category: None
Event ID: 27
Type: Error
User: N/A
Computer: computer_name
Description:
SOB error ignored
More Information
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:
http://technet.microsoft.com/en-us/library/aa997251.aspx
For more information about how to grant "send on behalf of" permissions in Exchange Server 2007, visit the following Microsoft website:
http://technet.microsoft.com/en-us/library/bb124406(EXCHG.80).aspx
For information about how to grant "send on behalf of" permissions in Exchange Server 2010, visit the following Microsoft website:
http://technet.microsoft.com/en-us/library/bb124255.aspx
For additional history on this problem, please see the original Hotfix articles where the IgnoreSOBError registry value was first introduced.
950794 Error message when you try to add a delegate in Outlook 2007: "The Delegates settings were not saved correctly"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;950794
946208 Error message when you try to add a delegate in Outlook 2003: "The Delegates settings were not saved correctly"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;946208
Back to the top | Give Feedback
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice.
ASKER
thank you everyone, can someone please send any solution and articles for Exchange/outlook 2016?
Very basic first:
https://docs.microsoft.com/en-us/exchange/exchange-admin-center
Then what you need is the Send As or Send on Behalf of, see: https://docs.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-permissions-for-recipients
https://docs.microsoft.com/en-us/exchange/exchange-admin-center
Then what you need is the Send As or Send on Behalf of, see: https://docs.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-permissions-for-recipients
Hello Jerry,
Any update on the issue?
Any update on the issue?
Therefore I don't think you've set it properly on the Exchange Server (I only see permissions done on Outlook)