Mailbox Restore: Recurring Calendar Meeting Update: You do not have permission to send the message on behalf of specified user

We had one of our Exchange mailbox databases become corrupt and it was in a "dirty shutdown" state. We worked with Microsoft however it ended up that we had to restore the mailboxes on that database from backup from the night before.

After the restoration of the mailbox database, whenever users on this database try to send and update to a calendar invite they are receiving an error message that states "You do not have permission to send the message on behalf of specified user".

I have tried setting the "NT AUTHORITY\USER" permission for Full Access and Send As permissions to ensure that the user has full access on their mailbox and items.

Thanks for your assistance!
Lee AndersonVP, CIOAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Lee AndersonConnect With a Mentor VP, CIOAuthor Commented:
It was an issue with the items and their permission level after restoring. Unfortuantly I did not find a fix for this and the items had to be deleted using MFCMAPI and then recreated by the user.
0
 
Adam BrownSr Solutions ArchitectCommented:
NT AUTHORITY\SELF is the permission you would need to have on there. That said, make sure that the users have their reply address set to be the same as the address that those invites are being sent to.
0
 
Lee AndersonVP, CIOAuthor Commented:
Thanks for the reply. In conjunction with this mailbox crash, we did change our email domain due to a name change (lets calls the new email "user@domain2.com"). We kept the old email address (user@domain1.com) attached to each recipient mailbox as an alias and set the "user@domain2.com" as the primary SMTP. So prior to opening this question, I thought that this could have been a cause so I did go into one of the mailboxes affected, and unchecked the "Automatically update email addresses based on email address policy" option and set the "user@domain1.com" as the Primary SMTP address which I believe makes this the Reply To address.

This morning, I did verify that the "user@domain1.com" was still set as the primary email address however, when I ran the test it still failed with the same error.

I did verify that one of the mailboxes in question still contained the "NT AUTHORITY\SELF" for both "Send-As" and "FullAccess" permissions.

The add these permissions, I ran the following in Powershell and then verified in Exchange Management Console

get-Mailbox -server {ServerName} -ResultSize Unlimited | Add-ADPermission -User 'NT AUTHORITY\SELF' -ExtendedRights 'Send-as'
get-Mailbox -server {ServerName} -ResultSize Unlimited | Add-MailboxPermission -User 'NT AUTHORITY\SELF' -AccessRights FullAccess

Open in new window

Also, I should have mentioned that this is Exchange 2007.

Thanks
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
Lee AndersonVP, CIOAuthor Commented:
I just wanted to give an update. It appears that we have a problem with permissions sticking. I just went back into the same mailbox and checked the "Manage Send As Permission" option and now the "NT AUTHORITY\USER" is missing again.

It seems that when I add the permission within about 30 minutes it is removed.
0
 
Simon Butler (Sembee)ConsultantCommented:
Try moving an affected user to a new database.

Simon
0
 
Lee AndersonVP, CIOAuthor Commented:
I tried moving one of the mailboxes to a temporary mailbox DB and it has the same issue.
0
 
Simon Butler (Sembee)ConsultantCommented:
Does the problem occur with a NEW calendar entry?

Simon.
0
 
Lee AndersonVP, CIOAuthor Commented:
No it doesn't. New appointments are not affected.
0
 
Simon Butler (Sembee)ConsultantCommented:
In that case I would have to put it down as a side effect of the recovery operation and the items needs to be recreated. It may well have been a corruption that existing at the point of the backup being taken which wasn't seen.

Simon.
0
 
Lee AndersonVP, CIOAuthor Commented:
There was no solution provided except what we already knew.
0
All Courses

From novice to tech pro — start learning today.