Glen's Exchange and Office 365 Dev Blog

One of the more challenging things you may want to do when writing code that is going to run against an Exchange 2007 mailbox is to set and modify Folder permissions on a mailbox folder or a public folder. I’d thought I’d share my efforts and what I learnt over the last week of trying to do this (thanks to David Claux for helping me get over my issues with custom permissions). One of the features added to SP1 in Exchange 2007 is the ability to set folder permissions and also folder delegates. This is a pretty cool feature but one you do need to make sure you understand before you dive in. Before you start its a good idea to understand the permissions your want to modify to ensure your code is going to work as expected and avoid any unwanted ACL changes. Let’s start by looking at the permissions that can be set on a folder via EWS CanCreateItems ReadItems DeleteItems EditItems CanCreateSubFolders IsFolderContact IsFolderOwner IsFolderVisible With E...

Auto discovery is one of the new features that are trying to alleviate some of the pain of configuring and maintaining Outlook client setting. Once you have managed to overcome the SSL configuration peculiarities you have a nifty little service that you can authenticate against, supply it with your email address and it will inform you about everything you need to know about connecting to exchange using Outlook, OWA, EWS and or any of the other new services Exchange 2007 provides. If you’re a scripter the information the auto discovery service provides can be retrieved via Active Directory but it not that easy and certain not as convenient as doing with one request. The scripts I’ll talk about in this post are designed to be run from workstation where the Exchange Management Tools aren’t install so they won’t be using any of the Exchange Management Shell cmdlets. The first thing you need to do if you want to use Auto discovery is query Active Directory for the Service Connection Point....

This is another one that came out of the Ether the Out of office functionality was one of the things that received a welcome makeover with Exchange 2007 / Outlook 2007. If you’re moving, migrating or just wondering if people are actually using the Out of Office Assistant then this might be the script for you. This script is broken down into 2 parts the first part of the script takes one command line parameter which is the name of the server you want to export the information from and then it does a ADSI query of Active Directory to get the detail of every account on the server in question. The second part of the script connects to each of the mailboxes the ADSI query found and looks to see if the oof setting is enabled. One of the good things about CDO 1.2 is that it makes getting and setting the oof setting on a mailbox very simple basically once you have logged on you can pull the oof setting from the outofoffice and outofofficetext property of the session object. The format this scr...

Thought this was worth a post its something that pretty easy to do with EWS but not something that maybe initially obvious. If you want to add an X-header to a message your sending via Exchange you need to add this via the PS_INTERNET_HEADERS namespace. With EWS you do this when using the MessageType class by adding an Extended property. Eg if you take the basic send message via EWS example from MSDN http://msdn2.microsoft.com/en-us/library/bb408521.aspx and all you need to do is add the following to add your own custom X-header message.Sensitivity = SensitivityChoicesType.Normal; // Start X-header Code PathToExtendedFieldType epExPath1 = new PathToExtendedFieldType(); epExPath1.DistinguishedPropertySetId = DistinguishedPropertySetType.InternetHeaders; epExPath1.DistinguishedPropertySetIdSpecified = true; epExPath1.PropertyName = "x-myheader"; epExPath1.PropertyType = MapiPropertyTypeType.String; ExtendedPropertyType xhXheaderProp = new ExtendedPropertyType...