Skip to main content

Accessing the NON_IPM_Subtree folders in Exchange Web Services

One important and potentially frustrating point for anybody who wants to set permissions on the calendar folder in a mailbox with any Exchange API that allows you to modify the folder DACL’s is that you also need add the same ACE your adding (or modifying) to the FreeBusy Data folder which is one the NON_IPM_Subtree Root folders in a mailbox explained in this KB. Exchange Web Services is no exception to this rule and accessing the NON_IPM_Subtree folders isn’t as straight forward as normal mailbox folders but here’s a method for accessing the freebusy folder and modifying the DACL.

The highest level you can get to easily with EWS is the DistinguishedFolderIdNameType.msgfolderroot which in the basically the Root of the IPM_Subtree if you get the parentfolderID of this folder using a GetFolder Operation this will represent the Root of the NON_IPM_Subtree you can then use this ID in FindFolder operation to discover all the NON_IPM_Subtree folder in this case I’ve used a restriction to find the Free Busy folder based on the folderName. Then once you have the FolderID of the Free Busy folder you can Get and Set the ACL via the normal GetFolder and Update Folder operations.

Okay enough said I’ve put a download of the code here the code itself looks like

PermissionSetType fbPermissionSet = new PermissionSetType();
BaseFolderIdType[] bfBaseFolderArray = new BaseFolderIdType[1];
DistinguishedFolderIdType dfRootFolderID = new DistinguishedFolderIdType();
if (intebExchangeServiceBinding.ExchangeImpersonation == null)
{
EmailAddressType mbMailbox = new EmailAddressType();
mbMailbox.EmailAddress = emEmailAddress;
dfRootFolderID.Mailbox = mbMailbox;
}
dfRootFolderID.Id = DistinguishedFolderIdNameType.msgfolderroot;
bfBaseFolderArray[0] = dfRootFolderID;
ListrfRootFolder = GetFolder(bfBaseFolderArray);
BaseFolderIdType[] bfIdArray = new BaseFolderIdType[1];
bfIdArray[0] = rfRootFolder[0].ParentFolderId;
List fbFolder = FindFolder(bfIdArray, "Freebusy Data");
FolderResponseShapeType frFolderRShape = new FolderResponseShapeType();
frFolderRShape.BaseShape = DefaultShapeNamesType.AllProperties;
GetFolderType gfRequest = new GetFolderType();
gfRequest.FolderIds = new BaseFolderIdType[1] { fbFolder[0].FolderId };
intFreeBusyFolderID = fbFolder[0].FolderId;
gfRequest.FolderShape = frFolderRShape;
GetFolderResponseType gfGetFolderResponse = intebExchangeServiceBinding.GetFolder(gfRequest);
FolderType cfCurrentFolder = null;


if (gfGetFolderResponse.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Success)
{
cfCurrentFolder = (FolderType)((FolderInfoResponseMessageType)gfGetFolderResponse.ResponseMessages.Items[0]).Folders[0];
fbPermissionSet = cfCurrentFolder.PermissionSet;
}

public List GetFolder(BaseFolderIdType[] biArray)
{
try
{
List rtReturnList = new List();
GetFolderType gfGetfolder = new GetFolderType();
FolderResponseShapeType fsFoldershape = new FolderResponseShapeType();
fsFoldershape.BaseShape = DefaultShapeNamesType.AllProperties;
DistinguishedFolderIdType rfRootFolder = new DistinguishedFolderIdType();
gfGetfolder.FolderIds = biArray;
gfGetfolder.FolderShape = fsFoldershape;
GetFolderResponseType fldResponse = intebExchangeServiceBinding.GetFolder(gfGetfolder);
ArrayOfResponseMessagesType aormt = fldResponse.ResponseMessages;
ResponseMessageType[] rmta = aormt.Items;
foreach (ResponseMessageType rmt in rmta)
{
if (rmt.ResponseClass == ResponseClassType.Success)
{
FolderInfoResponseMessageType firmt;
firmt = (rmt as FolderInfoResponseMessageType);
BaseFolderType[] rfFolders = firmt.Folders;
rtReturnList.Add(rfFolders[0]);
}
else
{
//Deal with Error
}

}
return rtReturnList;
}
catch (Exception exException)
{
Console.WriteLine(exException.ToString());
throw new GetFolderException("Get Folder Exception");
}

}
public List FindFolder(BaseFolderIdType[] biArray, String fnFolderName)
{
try
{
List rtReturnList = new List();
FindFolderType fiFindFolder = new FindFolderType();
fiFindFolder.Traversal = FolderQueryTraversalType.Shallow;
FolderResponseShapeType rsResponseShape = new FolderResponseShapeType();
rsResponseShape.BaseShape = DefaultShapeNamesType.AllProperties;
fiFindFolder.FolderShape = rsResponseShape;
fiFindFolder.ParentFolderIds = biArray;
RestrictionType ffRestriction = new RestrictionType();
IsEqualToType ieToType = new IsEqualToType();
PathToUnindexedFieldType fnFolderNameField = new PathToUnindexedFieldType();
fnFolderNameField.FieldURI = UnindexedFieldURIType.folderDisplayName;

FieldURIOrConstantType ciConstantType = new FieldURIOrConstantType();
ConstantValueType cvConstantValueType = new ConstantValueType();
cvConstantValueType.Value = fnFolderName;
ciConstantType.Item = cvConstantValueType;
ieToType.Item = fnFolderNameField;
ieToType.FieldURIOrConstant = ciConstantType;
ffRestriction.Item = ieToType;
fiFindFolder.Restriction = ffRestriction;

FindFolderResponseType findFolderResponse = intebExchangeServiceBinding.FindFolder(fiFindFolder);
ResponseMessageType[] rmta = findFolderResponse.ResponseMessages.Items;
foreach (ResponseMessageType rmt in rmta)
{
if (((FindFolderResponseMessageType)rmt).ResponseClass == ResponseClassType.Success)
{
FindFolderResponseMessageType ffResponse = (FindFolderResponseMessageType)rmt;
if (ffResponse.RootFolder.TotalItemsInView > 0)
{
foreach (BaseFolderType suSubFolder in ffResponse.RootFolder.Folders)
{
rtReturnList.Add(suSubFolder);
}

}
else
{
throw new FindFolderException("Find Folder Exception No Folder");
}
}
else
{
throw new FindFolderException("Find Folder Exception Seach Error");
}

}

return rtReturnList;
}
catch (Exception exException)
{
Console.WriteLine(exException.ToString());
throw new FindFolderException("Get Folder Exception");
}
}

Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

For an updated article on this problem please have a read of https://glenscales.substack.com/p/application-is-over-its-mailboxconcurrency If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around...
Read more

Sending a MimeMessage via the Microsoft Graph using the Graph SDK, MimeKit and MSAL

One of the new features added to the Microsoft Graph recently was the ability to create and send Mime Messages (you have been able to get Message as Mime for a while). This is useful in a number of different scenarios especially when trying to create a Message with inline Images which has historically been hard to do with both the Graph and EWS (if you don't use MIME). It also opens up using SMIME for encryption and a more easy migration path for sending using SMTP in some apps. MimeKit is a great open source library for parsing and creating MIME messages so it offers a really easy solution for tackling this issue. The current documentation on Send message via MIME lacks any real sample so I've put together a quick console app that use MSAL, MIME kit and the Graph SDK to send a Message via MIME. As the current Graph SDK also doesn't support sending via MIME either there is a workaround for this in the future my guess is this will be supported.
Read more

Outlook Addin for exporting Email to EML from Outlook on the Web

One of the more interesting announcements from the recent Microsoft Build conference was the ability to get the MimeContent of Messages in the Microsoft Graph API  https://developer.microsoft.com/en-us/graph/blogs/mime-format-support-for-microsoft-graph-apis-preview/ . This is a much needed feature as it was something that a lot of people use in EWS application, it still comes with a few limitations the Graph has a 4GB underlying limit for REST  https://docs.microsoft.com/en-us/graph/api/post-post-attachments?view=graph-rest-1.0&tabs=javascript and its export only at the moment so you can't import messages using it. One other thing is that its only in the Graph endpoint not the Outlook Rest endpoint so its not that easy to use from a Mail Add-in (without additional security config). One thing I do a bit when developing code for Exchange and Outlook is to look at the MimeContent of Messages as well as the MAPI properties using a MAPI editor like OutlookSpy of MFCMapi. T...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.