Skip to main content

Using EWS and AQS to check number of Unread in X days with Graph

It seems that you can never have too many ways of reading the number of Unread messages in a Inbox so here is another method. The following script uses two AQS queries to work out first the number of messages in the Inbox from a prescribed period eg the last 30 days and then the number of these that are then unread. It then works out the percentage of unread using of the two values and then creates a graph to display in the Console using Alt-ASCII characters which produces a pretty nifty output eg


It also produces a CSV output eg


AQS queries will work in Exchange 2010 and 2013 so this script should work okay in those environments as well as ExchangeOnline.

I've created two versions of this script, the first version just reports on one user so you run it with the email of the users you want to report on and the number of days to query back. eg

.\AQSUsr.ps1 gscales1@msgdevelop.onmicrosoft.com 30

the second version reports on all of the users in a CSV file and uses EWS Impersonation to access the Mailboxes. To use the script you need to have configured EWS Impersonation and feed the script a CSV file of the users you want to report on eg the CSV file should look like

smtpaddress
user1@domain.com
user2@domain.com

and you run it like

.\AQSAllUsr.ps1 ./users.csv 30

I've put a download of both scripts here the code look like


  1. ## Get the Mailbox to Access from the 1st commandline argument  
  2.   
  3. $csvFileName = $args[0]  
  4. $DaysBack = $args[1]  
  5.   
  6. ## Load Managed API dll    
  7. Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\2.0\Microsoft.Exchange.WebServices.dll"    
  8.     
  9. ## Set Exchange Version    
  10. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2    
  11.     
  12. ## Create Exchange Service Object    
  13. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  14.     
  15. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  16.     
  17. #Credentials Option 1 using UPN for the windows Account    
  18. $psCred = Get-Credential    
  19. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  20. $service.Credentials = $creds        
  21.     
  22. #Credentials Option 2    
  23. #service.UseDefaultCredentials = $true    
  24.     
  25. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  26.     
  27. ## Code From http://poshcode.org/624  
  28. ## Create a compilation environment  
  29. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  30. $Compiler=$Provider.CreateCompiler()  
  31. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  32. $Params.GenerateExecutable=$False  
  33. $Params.GenerateInMemory=$True  
  34. $Params.IncludeDebugInformation=$False  
  35. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  36.   
  37. $TASource=@' 
  38.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  39.     public class TrustAll : System.Net.ICertificatePolicy { 
  40.       public TrustAll() {  
  41.       } 
  42.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  43.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  44.         System.Net.WebRequest req, int problem) { 
  45.         return true; 
  46.       } 
  47.     } 
  48.   } 
  49. '@   
  50. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  51. $TAAssembly=$TAResults.CompiledAssembly  
  52.   
  53. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  54. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  55. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  56.   
  57. ## end code from http://poshcode.org/624  
  58.     
  59. ## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use    
  60.     
  61. #CAS URL Option 1 Autodiscover    
  62. #$service.AutodiscoverUrl($MailboxName,{$true})    
  63. #"Using CAS Server : " + $Service.url     
  64.      
  65. #CAS URL Option 2 Hardcoded    
  66.     
  67. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  68. #$service.Url = $uri      
  69.     
  70. ## Optional section for Exchange Impersonation    
  71.     
  72.   
  73. $Script:rptCollection = @()  
  74. function Process-Mailbox{    
  75.     param (    
  76.             $SmtpAddress = "$( throw 'SMTPAddress is a mandatory Parameter' )"    
  77.           )    
  78.     process{    
  79.         Write-Host ("Processing Mailbox : " + $SmtpAddress)    
  80.   
  81. # Bind to the Inbox Folder  
  82. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$SmtpAddress)     
  83. $Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  84. $Range = [system.DateTime]::Now.AddDays(-$DaysBack).ToString("MM/dd/yyyy") + ".." + [system.DateTime]::Now.AddDays(1).ToString("MM/dd/yyyy")     
  85. $AQSString1 = "System.Message.DateReceived:" + $Range     
  86. $AQSString2 = "(" + $AQSString1 + ") AND (isread:false)"   
  87. $ivItemView =  New-Object Microsoft.Exchange.WebServices.Data.ItemView(1)    
  88. $allMail = $Inbox.FindItems($AQSString1,$ivItemView)  
  89. $ivItemView =  New-Object Microsoft.Exchange.WebServices.Data.ItemView(1)   
  90. $unread = $Inbox.FindItems($AQSString2,$ivItemView)  
  91. $rptObj = "" | Select MailboxName,TotalCount,Unread,PercentUnread,PercentGraph  
  92.   
  93. #Write-Host ("All Mail " + $allMail.TotalCount)   
  94. #Write-Host ("Unread " + $unread.TotalCount)   
  95. $rptObj.MailboxName = $SmtpAddress  
  96. $rptObj.TotalCount = $allMail.TotalCount  
  97. $rptObj.Unread = $unread.TotalCount   
  98. $PercentUnread = 0  
  99. if($unread.TotalCount -gt 0){  
  100.     $PercentUnread = [Math]::round((($unread.TotalCount/$allMail.TotalCount) * 100))  
  101. }  
  102. $rptObj.PercentUnread = $PercentUnread   
  103. #Write-Host ("Percent Unread " + $PercentUnread)  
  104. $ureadGraph = ""  
  105. for($intval=0;$intval -lt 100;$intval+=4){  
  106.     if($PercentUnread -gt $intval){  
  107.         $ureadGraph += "▓"  
  108.     }  
  109.     else{         
  110.         $ureadGraph += "░"  
  111.     }  
  112. }  
  113. #Write-Host $ureadGraph  
  114. $rptObj.PercentGraph = $ureadGraph  
  115. $rptObj | fl  
  116. $Script:rptCollection +=$rptObj  
  117.   
  118. }  
  119. }  
  120. Import-Csv -Path $csvFileName | ForEach-Object{    
  121.     if($service.url -eq $null){    
  122.         $service.AutodiscoverUrl($_.SmtpAddress,{$true})     
  123.         "Using CAS Server : " + $Service.url     
  124.     }    
  125.     Try{    
  126.         $service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $_.SmtpAddress)   
  127.   
  128.         Process-Mailbox -SmtpAddress $_.SmtpAddress    
  129.     }    
  130.     catch{    
  131.         Write-host ("Error processing Mailbox : " + $_.SmtpAddress + $_.Exception.Message.ToString())    
  132.         $Error.Clear()  
  133.     }    
  134. }    
  135. $Script:rptCollection | ft  
  136. $Script:rptCollection | Export-Csv -NoTypeInformation -Path c:\temp\InboxUnreadReport.csv -Encoding UTF8   

Popular posts from this blog

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 Gr...

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.

Export calendar Items to a CSV file using Microsoft Graph and Powershell

For the last couple of years the most constantly popular post by number of views on this blog has been  Export calendar Items to a CSV file using EWS and Powershell closely followed by the contact exports scripts. It goes to show this is just a perennial issue that exists around Mail servers, I think the first VBS script I wrote to do this type of thing was late 90's against Exchange 5.5 using cdo 1.2. Now it's 2020 and if your running Office365 you should really be using the Microsoft Graph API to do this. So what I've done is create a PowerShell Module (and I made it a one file script for those that are more comfortable with that format) that's a port of the EWS script above that is so popular. This script uses the ADAL library for Modern Authentication (which if you grab the library from the PowerShell gallery will come down with the module). Most EWS properties map one to one with the Graph and the Graph actually provides better information on recurrences then...
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.