Skip to main content

Mining the clientinfo property in Messages in Exchange 2013 and Office365 with EWS

Tracking the bewildering array of clients and different Internet browsers that are being used to send email on Exchange can be an interesting challenge especially when your clients are in the cloud. One Mapi property that gets set on the SentItem in the senders Mailbox can help answer some of these questions where logs may not be available. The Named Mapi property clientinfo eg


So if you write a script that accesses this property on messages in the SentItems folder you can build a report of the different sending methods that are being used and also different properties such as the browser version from the agent string being stored eg something like this


I've put a script on GitHub here https://github.com/gscales/Powershell-Scripts/blob/master/GetMailUserAgentsv2.ps1 that can mine the data in the property correctly taking into account the ; used as a separator while also dealing with data enclosed in ( ) (it does this by just doing a character by character parse rather the splitting or using Regex). The script will separate the Primary ClientType and extra client information (eg browser agent string) from the clientinfo property.

The script has a few different options by default it will evaluate every message in the SentItems folder if you use the -days switch you can specify how many days to look back eg

Get-MailUserAgents -Mailbox user@domain -days 14

Will look at messages for the last 14 days, if you want to evaluate messages in the Inbox you can use the -Inbox switch which will change the target folder to the Inbox.

Popular posts from this blog

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is. I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned) #Define Date to Query $StartDate = (Get-Date) $EndDate

Writing a simple scripted process to download attachmentts in Exchange 2007/ 2010 using the EWS Managed API

Every complicated thing in life is made up of smaller simpler building blocks, when it comes to writing a script (or any code really) the more of these little building blocks you have to figure out the more the process of solving a problem can become bewildering. The Internet generally provides you with lots of half eaten sandwiches of information something someone else has taken a bite out but a lot of the time half done, and as with any code its usefulness declines over time as new and better API's and methods are derived. In this post I'm going to go through a simple scripted process that hopefully covers a few more of these smaller building blocks that you might face when asked to come up with a simple costless solution to perform an automated business function with a script. So the process im going to look at is one that comes up a lot and that is you have an Email that comes into to certain mailbox every day with a certain subject in my case "Daily Export" this

EWS Managed API and Powershell How-To series Part 1

I thought I'd start the year with a series of posts that goes back over the basics of using the EWS Managed API from Powershell and provides a modular remarked example that you can easily cut and paste to build your own scripts. Along the way in this series I'll show a whole bunch of examples around specific things. As a starting point for versions this will be Powershell Version 2.0  and the EWS Managed API 1.1 (which will soon change to 1.2 once released) http://www.microsoft.com/download/en/details.aspx?id=13480. The starting point for any EWS script your going to write is connecting to Exchange for which there are three important pieces of information you will need. Firstly you need to know the version of Exchange your running in this script its going to be held in the following variable $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1 Other valid values for Exchange 2007 would be $ExchangeVersion = [Microsoft.Exchange.Web
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.