CODEWITHSUNDEEP
exchangewebservicesews-managed-api
Ralfeus
Ralfeus

Reputation: 815

EWS Item.Copy causes ErrorAccessDenied

I want to copy items between mailboxes used EWS managed API. Here I've met strange situation.

When I try first to get destination folder and then copy item using its ID I get an error ErrorAccessDenied.

this.exchangeService.ImpersonatedUserId = new ImpersonatedUserId(ConnectingIdType.SmtpAddress, "[email protected]");
var folder = Folder.Bind(this.exchangeService, WellKnownFolderName.Inbox);
item.Copy(folder.Id);

This gets an error

If I create a FolderId object instance specifying well known folder name (Inbox) and mailbox name I get no problems. 

var folderId = new FolderId(WellKnownFolderName.Inbox, new Mailbox("[email protected]"));
item.Copy(folderId);

This works

Is such behavior by design? Or I can use destination folder not just well known one?

Upvotes: 0

Views: 531

Answers (1)

Michael Mainer
Michael Mainer

Reputation: 3465

I believe this behavior is by design. In the first example, the calling account (acct1) is impersonating acct2. I think that the request is being processed as acct2 trying to bind to the inbox of acct1 since the credentials of the call are associated with acct1. The context for calls are based on the identifiers which contain the SMTP address of the target mailbox.

Your second example explicitly identifies the mailbox that should be targeted. All subsequent identifiers accessed based on that folder identifier will have the context of [email protected].

I think you can change your first call to this to make it work:

var folder = Folder.Bind(this.exchangeService, new FolderId(WellKnownFolderName.Inbox, new Mailbox("[email protected]")));

I know you are copying to a folder in to [email protected] mailbox. Whose mailbox contains 'item'? I can't recall if it works to use impersonation to copy across mailboxes. I'm interested to know how it works for you.

Upvotes: 0

Related Questions