[RESOLVED] You do not have the permission to send the message on behalf of the specified user

We had the same issue. We had a user on a laptop that was using a domain account, but without the (1) correct AD Membership, and (2) there was no email address assigned to the domain account being used on the laptop. We fixed both of these issues.

Details: Laptop was logged in using a "generic" domain account ("CNCUser"); user was using his enterprise email account ("JSmith@OurCompany.com") in Outlook 2019. Outlook did not like that combination. Making the above two changes on the domain server fixed the problem, and the user was able to send emails once again.

Have a new hire, copied AD permissions from another user with the permissions we wanted to duplicate. Added her to the Send As and Full Access permissions of a mailbox in O365 (we are running 2016 Hybrid Exchange) and I keep getting 'No Permission to Send' when trying to reply to an email in the Cloud Mailbox in Outlook. Triple checked - she has the EXACT same permissions as everyone else in her team who access and reply to that mailbox.

I have disabled Cached Mode on her Outlook Profile. I've tried using Powershell to give her Send As permissions and it reported: WARNING: The appropriate access control entry is already present on the object and then shows that:


Identity Trustee AccessControlType AccessRights Inherited
-------- ------- ----------------- ------------ ---------
(cloudmailbox) (local username) Allow {SendAs} False


At a loss as to what to try next. It'

Abstract: You got rights for an additional Exchange mailbox (e.g. your workmade), but when you try to send emails from this mailbox you got an error message.

The full error message you got is:

Subject: Undeliverable: Subject_of_Message
Your message did not reach some or all of the intended recipients.

Subject: Subject_Of_Message
Sent: Date_and_Time

The following recipient(s) cannot be reached:
Recipient_Name on Date_And_Time
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].

or

Subject: Undeliverable: Subject_of_Message
Your message did not reach some or all of the intended recipients.

Subject: Subject_Of_Message
Sent: Date_and_Time
The following recipient(s) cannot be reached:
Recipient_Name on Date_And_Time

This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524].

Possible solution 01:

• You have Full Access and Send On Behalf Of permissions to a shared mailbox in an Exchange Server environment.
• You configure a Microsoft Outlook profile for the shared mailbox and enter your own credentials to access it.
• You send an email message from this Outlook profile.
• You do not have the password to the shared mailbox and do not use it as an additional account.

In this scenario as explained in KB 3045224 you need Send As permissions.

Possible solution 02:

Clean the AutoComplete cache as explained in KB 287623.

Possible solution 03:

It could take some time until the internal Exchange (hold by the Information Store) process updates the content, so that the user can perform these actions. This is due to the reason that MS Exchange update content from the ActiveDirectory every two hours (if not changed). This is controlled by the "Mailbox Cache Age Limit" & "Reread Logon Quotas Interval" entries "HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem". Additional to that time the GAL must be updated as well. So depending on your configuration an additional wait time apply here.

Possible solution 04:

If the delegation isn´t working after a reasonable time passed you should try to update the OAB by hand. If that isn´t solving the issue delete the OAB by hand and fully download it. You can also reset the whole Outlook profile and delete all pending files from the user Outlook Profile folder before you restart Outlook.

Possible solution 05:

Remove the shared mailbox from your Outlook configuration, then restart outlook and re-add the shared mailbox

Possible solution 06:

Delete all email addresses from the "From:" box (which is seen when you send an email). The use the "display name" from the shared box in that field to re-add it. This will force that the client check the GAL and reload the correct permissions.

Possible solution 07:

As explained here, a re-set from the permissions on the shared mailbox seamed to solve the issue for some users. So use:

Add-ADPermission -Identity "YourSharedMailbox" -User "YourADAccessGroup" -AccessRights ExtendedRight -ExtendedRights "Send As"
Add-MailboxPermission -Identity "YourSharedMailbox" -User "YourADAccessGroup" -AccessRights FullAccess -InheritanceType All

Possible solution 08:

If that issue happen when a user was moved from on premise to Exchange Online, check if an LegacyExchangeDN email address was added as explained in KB 3131416. If that isn´t the case add it manually.

Possible solution 09:

As mentioned here, this issue could happen if the account is hidden. So make sure that this isn´t case. If it is unhide it, let the GAL update and retry it.

Possible solution 10:

Make sure the user has only "Send As" and not additional to that "Send on Behalf Of" rights.

Kommentare (19)

Sys

1. vor 4 Jahren
2. #132

This comment was minimized by the moderator on the site

I solved it by disabling Outlook cached mode

1. Antworten

Bastian W.    Sys

1. vor 4 Jahren
2. #133

This comment was minimized by the moderator on the site

Thats a workaround yes, but no solution. The reason why this is working is because of the reason that then no offline address book is used (its only used in cached mode). So something on your side didn´t seamed to be ok with the offline address...

Thats a workaround yes, but no solution. The reason why this is working is because of the reason that then no offline address book is used (its only used in cached mode). So something on your side didn´t seamed to be ok with the offline address book and other users might get the same issues.

Weiterlesen

1. Antworten

Kalle

1. vor 3 Jahren
2. #317

This comment was minimized by the moderator on the site

Turns out a Distribution group had the same Display Name as the user and and the user was "hidden from adressbook" so the user tried "sending as" the distribution list.

1. Antworten

rino19ny

1. vor 3 Jahren
2. #363

This comment was minimized by the moderator on the site

danke! solution #4 worked for me

1. Antworten

Bastian W.    rino19ny

1. vor 2 Jahren
2. #515

This comment was minimized by the moderator on the site

You are welcome

1. Antworten

Jeff

1. vor 3 Jahren
2. #379

This comment was minimized by the moderator on the site

I have a user who can send to anyone in the company, but if anyone in the company sends him a calendar invite, when he accepts and sends a reply, the reply gets the "Error is [0x80070005-0x0004dc-0x000524]"

Any ideas?

1. Antworten

Bastian W.    Jeff

1. vor 2 Jahren
2. #382

This comment was minimized by the moderator on the site

What did you already tried? Do you know KB 3045224?

1. Antworten

Sammy

1. vor 2 Jahren
2. #413

This comment was minimized by the moderator on the site

Works for me, I download the OAB, disable cached mode, test it and it work, then just for curiosity, I enable cached mode then tested it and it works.

Bingo

1. Antworten

Haris Khan

1. vor 2 Jahren
2. #471

This comment was minimized by the moderator on the site

Thanks Sammy, your solution works for me also

1. Antworten

Andy Cashen

1. vor 2 Jahren
2. #513

This comment was minimized by the moderator on the site

Updating the OAB worked for me, It worked from the user account online but not from outlook 2016
Thank you !

1. Antworten

Bastian W.    Andy Cashen

1. vor 2 Jahren
2. #514

This comment was minimized by the moderator on the site

Happy to head the content was helpfull for you

1. Antworten

Timmer

1. vor 1 Jahr
2. #528

This comment was minimized by the moderator on the site

We had the same issue. We had a user on a laptop that was using a domain account, but without the (1) correct AD Membership, and (2) there was no email address assigned to the domain account being used on the laptop. We fixed both of these...

We had the same issue. We had a user on a laptop that was using a domain account, but without the (1) correct AD Membership, and (2) there was no email address assigned to the domain account being used on the laptop. We fixed both of these issues.

Details: Laptop was logged in using a "generic" domain account ("CNCUser"); user was using his enterprise email account ("JSmith@OurCompany.com") in Outlook 2019. Outlook did not like that combination. Making the above two changes on the domain server fixed the problem, and the user was able to send emails once again.

Weiterlesen

1. Antworten

Dave

1. vor 1 Jahr
2. #738

This comment was minimized by the moderator on the site

Have a new hire, copied AD permissions from another user with the permissions we wanted to duplicate. Added her to the Send As and Full Access permissions of a mailbox in O365 (we are running 2016 Hybrid Exchange) and I keep getting 'No...

Have a new hire, copied AD permissions from another user with the permissions we wanted to duplicate. Added her to the Send As and Full Access permissions of a mailbox in O365 (we are running 2016 Hybrid Exchange) and I keep getting 'No Permission to Send' when trying to reply to an email in the Cloud Mailbox in Outlook. Triple checked - she has the EXACT same permissions as everyone else in her team who access and reply to that mailbox.

I have disabled Cached Mode on her Outlook Profile. I've tried using Powershell to give her Send As permissions and it reported: WARNING: The appropriate access control entry is already present on the object and then shows that:


Identity Trustee AccessControlType AccessRights Inherited
-------- ------- ----------------- ------------ ---------
(cloudmailbox) (local username) Allow {SendAs} False


At a loss as to what to try next. It's a brand new outlook profile on a brand new windows profile on that PC. Any suggestions?

Weiterlesen

1. Antworten

Bastian W.    Dave

1. vor 1 Jahr
2. #739

This comment was minimized by the moderator on the site

Is that a brand new user or did you copied it (duplicated the AD account)? If yes then just as an advise, never ever copy an Exchange enabled AD object as this will often cause issue.

1. Antworten

Alexandre

1. vor 1 Jahr
2. #749

This comment was minimized by the moderator on the site

Possible solution 04 worked for me too.

1. Antworten

Bastian W.    Alexandre

1. vor 1 Jahr
2. #750

This comment was minimized by the moderator on the site

Thanks for the Feedback

1. Antworten

There are no comments posted here yet

Lade weitere Kommentare

Einen Kommentar verfassen

1. Posting comment as a guest.

Name (Erforderlich)

E-Mail

Anhänge (0 / 3)

Share Your Location

Zustimmen Nutzungsbedingungen.

Abbrechen Kommentar absenden