Skip to main content

How To Series Sample 6 : Show a sorted list of Subject's and number of messages within a mailbox

The following script shows how you can create a summary report of the Subjects of all Messages within a Mailbox. It makes use of the PR_NORMALIZED_SUBJECT http://msdn.microsoft.com/en-us/library/cc815282.aspx. property which contains the subject of a message minus the prefixes such as RE, FW etc. The end result is it will pump out a sorted list of the Number of messages per subject and also create a CSV report. The script is designed to work on Exchange 2010 but you could make it work on 2007 as well by converting the AQS QueryString (which limits the finditems call to just Email) to a search filter. I've put a download of this script here the script looks like
  1. $RptObjColl = @()  
  2. $MailboxName = "user@domain.com"  
  3.   
  4. ## Load Managed API dll    
  5. Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.1\Microsoft.Exchange.WebServices.dll"    
  6.     
  7. ## Set Exchange Version    
  8. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1    
  9.     
  10. ## Create Exchange Service Object    
  11. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  12.     
  13. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  14.     
  15. #Credentials Option 1 using UPN for the windows Account    
  16. $creds = New-Object System.Net.NetworkCredential("user@domain.com","password")     
  17. $service.Credentials = $creds        
  18.     
  19. #Credentials Option 2    
  20. #service.UseDefaultCredentials = $true    
  21.     
  22. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  23.     
  24. [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}    
  25.     
  26. ## 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    
  27.     
  28. #CAS URL Option 1 Autodiscover    
  29. $service.AutodiscoverUrl($MailboxName,{$true})    
  30. "Using CAS Server : " + $Service.url     
  31.      
  32. #CAS URL Option 2 Hardcoded    
  33.     
  34. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  35. #$service.Url = $uri      
  36.     
  37. ## Optional section for Exchange Impersonation    
  38.     
  39. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  40.   
  41. # Bind to the Archive Root folder    
  42. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$MailboxName)     
  43. $MsgRoot = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  44.   
  45. $fvFolderView =  New-Object Microsoft.Exchange.WebServices.Data.FolderView(1000)    
  46. #Deep Transval will ensure all folders in the search path are returned   
  47.    
  48. $fvFolderView.Traversal = [Microsoft.Exchange.WebServices.Data.FolderTraversal]::Deep;    
  49. $ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(1000)    
  50. #The Search filter will exclude any Search Folders   
  51. $psPropertySet = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)    
  52. $PR_NORMALIZED_SUBJECT = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x0E1D,[Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String);     
  53. $psPropertySet.add($PR_NORMALIZED_SUBJECT)  
  54. $PR_FOLDER_TYPE = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(13825,[Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer);    
  55. $sfSearchFilter = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo($PR_FOLDER_TYPE,"1")    
  56. $fiResult = $null    
  57. #The Do loop will handle any paging that is required if there are more the 1000 folders in a mailbox   
  58. $rptHash = @{}  
  59. $AQSString = "kind:email"   
  60. do {   
  61.     $ivItemView = New-Object Microsoft.Exchange.WebServices.Data.ItemView(1000)    
  62.     $ivItemView.PropertySet = $psPropertySet  
  63.     $fiResult = $Service.FindFolders($folderid,$sfSearchFilter,$fvFolderView)    
  64.     foreach($ffFolder in $fiResult.Folders){    
  65.     "Processing Folder : " + $ffFolder.displayName   
  66.     if($ffFolder.UnreadCount -gt 0){  
  67.         $fiResults = $null  
  68.         $updateColl = @()  
  69.         do{    
  70.             $fiResults = $ffFolder.findItems($AQSString,$ivItemView)  
  71.             foreach($Item in $fiResults.Items){    
  72.                 $subject = $null  
  73.                 if($Item.TryGetProperty($PR_NORMALIZED_SUBJECT,[ref]$subject)){  
  74.                     if($subject -ne $null){  
  75.                         "Processing Messsage : " + $subject  
  76.                         if($rptHash.Contains($subject) -eq $false){  
  77.                             $rptHash.add($subject,1);  
  78.                         }  
  79.                         else{  
  80.                             $rptHash[$subject] +=1  
  81.                         }  
  82.                     }  
  83.                 }  
  84.             }    
  85.             $ivItemView.Offset += $fiResults.Items.Count    
  86.         }while($fiResults.MoreAvailable -eq $true)  
  87.     }           
  88.     }   
  89.     $fvFolderView.Offset += $fiResult.Folders.Count  
  90. }while($fiResult.MoreAvailable -eq $true)   
  91.   
  92. $rptHash.GetEnumerator() | Sort-Object value -Descending | ForEach-Object{  
  93.     $rptobj = "" | select Subject, NumberofMessages  
  94.     $rptobj.Subject = $_.Key  
  95.     $rptobj.NumberofMessages = $_.Value  
  96.     $RptObjColl += $rptobj  
  97. }  
  98. $RptObjColl | Export-Csv -NoTypeInformation -path c:\temp\subjectReport.csv  
  99. $RptObjColl  

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

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You ...
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.