Skip to main content

Using Exchange Search and AQS with EWS on Exchange 2010

One of the great new features of Exchange Web Services on Exchange 2010 is the ability to use AQS (Advanced Query Syntax) when querying a mailbox folder. The reason this is helpful is that it provides an easily assessable entrypoint into the Exchange Search Service. The Exchange Search Service has been constantly improving with each new version of Exchange when you consider the size and Item counts of the modern mailbox this has now become a vital component of Exchange and something that those using EWS should consider taking advantage of. For the basics behind the difference between a Store Search and one use that utilizes the Exchange Search Service the Exchange Team blog has a great three part post on the subject.

The main points of interest are that index searches are considerable quicker and can be used to do things such as look at the content of an attachment which a normal store search can not do. Of course there are also a number of things a store search can do that a index search can't because a index search is always limited to searching the properties it indexes.

Using AQS also allows you the opportunity to have more flexible functions and methods when compared with creating search filters in EWS. For example most search filters are hard-coded for a particular property or you create a collection of search filters to apply additional logic. An Example of this would be

SearchFilter sf1 = new SearchFilter.IsEqualTo(ItemSchema.Subject, "Blah");
SearchFilter sf2 = new SearchFilter.IsGreaterThan(ItemSchema.DateTimeReceived, DateTime.Now.AddDays(-1));
SearchFilter sfcol = new SearchFilter.SearchFilterCollection(LogicalOperator.And, sf1, sf2);

While the equivalent AQS query that can be used is

FindItemsResults fiItems = service.FindItems(QueryFolder, "Received:yesterday AND subject:\"blah\"", iv);

Working Out the AQS Syntax

This is perhaps the hardest thing when it comes to using AQS the documentation can be a little confusing and sometimes doesn't show everything you need to know the two articles i would have a look at is firstly

http://msdn.microsoft.com/en-us/library/ee693615.aspx
http://technet.microsoft.com/en-us/library/bb232132.aspx

and

http://msdn.microsoft.com/en-us/library/bb266512(VS.85).aspx

The detail provided in the later is of importance because it provides good detail on what the conditional logic is that can be used with AQS when you need to constructed more advanced searches. For instance if you had to search all messages where a particular name is in the body but where only give part of the first or surname of the person. The COP_WORD_STARTSWITH help do this so you could find say any matches on "Microsoft Exchange" using "body:$<\"Micro Exc\"" this will find any a word starting with micro, followed by a word starting with exc.

Is this useful for SysAdmin's ?

ECP is a exceedingly powerful tool and if you where doing mailbox discoveries then this is what you should be using. However every problem is unique and having this ability availability at the command-line to do this can be very advantages. Using the EWS Managed API allows you to do this in Powershell relatively easily. Eg the following script will take the input of the Mailbox you want it to run against (as primary email address) and AQS query you want to use to search with an return the results to the console

$MailboxName = $args[0]

$dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.0\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)

$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)

$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$sidbind = "LDAP://"
$aceuser = [ADSI]$sidbind

$service.AutodiscoverUrl($aceuser.mail.ToString())


$folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)

$iv = new-object Microsoft.Exchange.WebServices.Data.ItemView(2000)
$fiItems = $service.FindItems($folderid, $args[1], $iv)
foreach ($Item in $fiItems.Items)
{
$Item.Subject
}

With this you can then make queries like

./aqssearch.ps1 gscales@mailbox.com "sent:today"

./aqssearch.ps1 gscales@mailbox.com "sent:thismonth"

find attachment content with

./aqssearch.ps1 gscales@mailbox.com "attachment:Good Movies"

There are a large number of problems you can solve relatively easily just by learning some simple AQS syntax so for both the Admin and developer if your using Exchange 2010 this is something to examine and start using.

I've put a download of the script here.

Popular posts from this blog

Testing and Sending email via SMTP using Opportunistic TLS and oAuth in Office365 with PowerShell

As well as EWS and Remote PowerShell (RPS) other mail protocols POP3, IMAP and SMTP have had OAuth authentication enabled in Exchange Online (Official announcement here ). A while ago I created  this script that used Opportunistic TLS to perform a Telnet style test against a SMTP server using SMTP AUTH. Now that oAuth authentication has been enabled in office365 I've updated this script to be able to use oAuth instead of SMTP Auth to test against Office365. I've also included a function to actually send a Message. Token Acquisition  To Send a Mail using oAuth you first need to get an Access token from Azure AD there are plenty of ways of doing this in PowerShell. You could use a library like MSAL or ADAL (just google your favoured method) or use a library less approach which I've included with this script . Whatever way you do this you need to make sure that your application registration  https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

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 for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Graph is limited to a m
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.