Monday, December 08, 2014

Dumping out the MailTips for all the recipients using EWS and Powershell

MailTip's are a feature in Exchange from 2010 that gives you extra information when sending a message. In a pervious post I showed how you can use these to get the Outlook of Office status for a user using MailTips in EWS. In this Post I have a sample for going through and dumping out all the MailTips for all the Recipients in Exchange (that are feed in using Get-Recipient to include Contacts, Distribution list and any other type of recipeint) and produces an output like
 
 

Because there are no classes in the EWS Managed API to use MailTips so I'm just using Raw SOAP to send the MailTips request and then parse the XML result that comes back. With MailTips you can only request a max of 100 results at a time so there is some code to split the request up in batches of 100 if there are more the 100 entries.

I've put a download of this script here the script looks like

## Get the Mailbox to Access from the 1st commandline argument

$MailboxName = $args[0]

$Script:rptCollection = @()
 

###CHECK FOR EWS MANAGED API, IF PRESENT IMPORT THE HIGHEST VERSION EWS DLL, ELSE EXIT
$EWSDLL = (($(Get-ItemProperty -ErrorAction SilentlyContinue -Path Registry::$(Get-ChildItem -ErrorAction SilentlyContinue -Path 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Web Services'|Sort-Object Name -Descending| Select-Object -First 1 -ExpandProperty Name)).'Install Directory') + "Microsoft.Exchange.WebServices.dll")
if (Test-Path $EWSDLL)
    {
    Import-Module $EWSDLL
    }
else
    {
    "$(get-date -format yyyyMMddHHmmss):"
    "This script requires the EWS Managed API 1.2 or later."
    "Please download and install the current version of the EWS Managed API from"
    "http://go.microsoft.com/fwlink/?LinkId=255472"
    ""
    "Exiting Script."
    exit
    }
 
## Set Exchange Version  
$ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2013_SP1  
  
## Create Exchange Service Object  
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)  
  
## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials  
  
#Credentials Option 1 using UPN for the windows Account  
$psCred = Get-Credential  
$creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())  
$service.Credentials = $creds      
  
#Credentials Option 2  
#service.UseDefaultCredentials = $true  
  
## Choose to ignore any SSL Warning issues caused by Self Signed Certificates  
  
## Code From http://poshcode.org/624
## Create a compilation environment
$Provider=New-Object Microsoft.CSharp.CSharpCodeProvider
$Compiler=$Provider.CreateCompiler()
$Params=New-Object System.CodeDom.Compiler.CompilerParameters
$Params.GenerateExecutable=$False
$Params.GenerateInMemory=$True
$Params.IncludeDebugInformation=$False
$Params.ReferencedAssemblies.Add("System.DLL") | Out-Null

$TASource=@'
  namespace Local.ToolkitExtensions.Net.CertificatePolicy{
    public class TrustAll : System.Net.ICertificatePolicy {
      public TrustAll() { 
      }
      public bool CheckValidationResult(System.Net.ServicePoint sp,
        System.Security.Cryptography.X509Certificates.X509Certificate cert, 
        System.Net.WebRequest req, int problem) {
        return true;
      }
    }
  }
'@ 
$TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)
$TAAssembly=$TAResults.CompiledAssembly

## We now create an instance of the TrustAll and attach it to the ServicePointManager
$TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")
[System.Net.ServicePointManager]::CertificatePolicy=$TrustAll

## end code from http://poshcode.org/624
  
## 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  
  
#CAS URL Option 1 Autodiscover  
$service.AutodiscoverUrl($MailboxName,{$true})  
"Using CAS Server : " + $Service.url 

function DumpMailTips{ 
    param (
         $Mailboxes = "$( throw 'Folder Path is a mandatory Parameter' )"
    )
 process{

$expRequest = @"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header><RequestServerVersion Version="Exchange2010_SP1" xmlns="http://schemas.microsoft.com/exchange/services/2006/types" />
</soap:Header>
<soap:Body>
<GetMailTips xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
<SendingAs>
<EmailAddress xmlns="http://schemas.microsoft.com/exchange/services/2006/types">$MailboxName</EmailAddress>
</SendingAs>
<Recipients>
"@

foreach($mbMailbox in $Mailboxes){
 $expRequest = $expRequest + "<Mailbox xmlns=`"http://schemas.microsoft.com/exchange/services/2006/types`"><EmailAddress>$mbMailbox</EmailAddress></Mailbox>" 
}

$expRequest = $expRequest + "</Recipients><MailTipsRequested>All</MailTipsRequested></GetMailTips></soap:Body></soap:Envelope>"
$mbMailboxFolderURI = New-Object System.Uri($service.url)
$wrWebRequest = [System.Net.WebRequest]::Create($mbMailboxFolderURI)
$wrWebRequest.KeepAlive = $false;
$wrWebRequest.Headers.Set("Pragma", "no-cache");
$wrWebRequest.Headers.Set("Translate", "f");
$wrWebRequest.Headers.Set("Depth", "0");
$wrWebRequest.ContentType = "text/xml";
$wrWebRequest.ContentLength = $expRequest.Length;
$wrWebRequest.CookieContainer = New-Object System.Net.CookieContainer
$wrWebRequest.Timeout = 60000;
$wrWebRequest.Method = "POST";
$wrWebRequest.Credentials = $creds
$bqByteQuery = [System.Text.Encoding]::ASCII.GetBytes($expRequest);
$wrWebRequest.ContentLength = $bqByteQuery.Length;
$rsRequestStream = $wrWebRequest.GetRequestStream();
$rsRequestStream.Write($bqByteQuery, 0, $bqByteQuery.Length);
$rsRequestStream.Close();
$wrWebResponse = $wrWebRequest.GetResponse();
$rsResponseStream = $wrWebResponse.GetResponseStream()
$sr = new-object System.IO.StreamReader($rsResponseStream);
$rdResponseDocument = New-Object System.Xml.XmlDocument
$rdResponseDocument = New-Object System.Xml.XmlDocument
$rdResponseDocument.LoadXml($sr.ReadToEnd());
$Datanodes = @($rdResponseDocument.getElementsByTagName("m:MailTips"))

foreach($nodeVal in $Datanodes){
 $rptObj = "" | Select RecipientAddress,RecipientTypeDetails,PendingMailTips,OutOfOffice,CustomMailTip,MailboxFull,TotalMemberCount,ExternalMemberCount,MaxMessageSize,DeliveryRestricted,IsModerated
 $rptObj.RecipientAddress = $nodeVal.RecipientAddress.EmailAddress
 $rptObj.RecipientTypeDetails = $Script:emAray[$rptObj.RecipientAddress.ToLower()]
 $rptObj.PendingMailTips = $nodeVal.PendingMailTips."#text"
 $rptObj.OutOfOffice = $nodeVal.OutOfOffice.ReplyBody.Message
 $rptObj.CustomMailTip = $nodeVal.CustomMailTip."#text"
 $rptObj.MailboxFull = $nodeVal.MailboxFull."#text"
 $rptObj.TotalMemberCount = $nodeVal.TotalMemberCount."#text"
 $rptObj.ExternalMemberCount = $nodeVal.ExternalMemberCount."#text"
 $rptObj.MaxMessageSize = $nodeVal.MaxMessageSize."#text"
 $rptObj.DeliveryRestricted = $nodeVal.DeliveryRestricted."#text"
 $rptObj.IsModerated = $nodeVal.IsModerated."#text"
 $Script:rptCollection += $rptObj
}

}
}
$mbscn = @()
$Script:emAray = @{}
$rcps = Get-Recipient -ResultSize Unlimited 
$rcps | ForEach-Object {
 $Script:emAray.Add($_.PrimarySMTPAddress.ToString().ToLower(),$_.RecipientTypeDetails)
 $mbscn += $_.PrimarySMTPAddress.ToString()
 if($mbscn.count -gt 100){
  dumpmailtips -Mailboxes $mbscn
  $mbscn = @()
 }
}
if($mbscn.count -gt 0){
 dumpmailtips -Mailboxes $mbscn
}
$Script:rptCollection | Export-Csv -Path c:\temp\MailTipsDump.csv -NoTypeInformation

Tuesday, November 18, 2014

Advanced Search Folder creation with EWS and Powershell

In the past I've posted some examples of creating SearchFolders in Exchange with EWS and Powershell in the following post,  in this post I want to cover some more advanced things you can do with EWS and Search Folders.

The first thing I want to cover is how you change the option on a Search folder from "Show number of unread items" which is the default when you create a search folder in EWS to "Show total number of items". eg




To change this option you need to set the PidTagExtendedFolderFlags property which is documented in http://msdn.microsoft.com/en-us/library/office/cc839880(v=office.15).aspx . This is a binary property and you set this particular option by changing bit 6-7 in this property. Because you also need the SearchFolderGuid in this property the easiest time is to set this is right after you create the folder. eg
  1. $searchFolder.Save($sfRoot.Id);  
  2. $PR_EXTENDED_FOLDER_FLAGS = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x36DA, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Binary)  
  3. $psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)    
  4. $psPropset.Add($PR_EXTENDED_FOLDER_FLAGS)  
  5. $searchFolder.Load($psPropset)  
  6. $exVal = $null  
  7. if($SearchFolder.TryGetProperty($PR_EXTENDED_FOLDER_FLAGS,[ref]$exVal)){  
  8.      $newVal = "010402001000" + [System.BitConverter]::ToString($exVal).Replace("-","")  
  9.      $byteVal = HexStringToByteArray($newVal)  
  10.      $SearchFolder.SetExtendedProperty($PR_EXTENDED_FOLDER_FLAGS,$byteVal)  
  11.      $searchFolder.Update()  
  12. }  
  13. "Folder Created"  

Some other interesting things you can do when using EWS to create search Folders is you can filter on some of the more advanced Item properties you can't access normally using Outlook. For example the PidTagLastVerbExecuted can be used to create a Search folder to find all email where the last action taken on the Message was to reply to the Sender. Eg this would create a SearchFolder with this type of filter
  1. $PR_LAST_VERB_EXECUTED = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition(0x1081, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer)    
  2. $sfItemSearchFilter = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo($PR_LAST_VERB_EXECUTED,102)   
  3. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  4. $SearchFolder = new-object Microsoft.Exchange.WebServices.Data.SearchFolder($service);  
  5. $rfRootFolderId = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$MailboxName)     
  6. $searchFolder.SearchParameters.RootFolderIds.Add($rfRootFolderId);  
  7. $searchFolder.SearchParameters.Traversal = [Microsoft.Exchange.WebServices.Data.SearchFolderTraversal]::Deep;  
  8. $searchFolder.SearchParameters.SearchFilter = $sfItemSearchFilter  
  9. $searchFolder.DisplayName = $SearchFilterName  
  10. $folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::SearchFolders,$MailboxName)     
  11. $sfRoot = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  12. $searchFolder.Save($sfRoot.Id);  

Another interesting Search Folder you can create on 2013/Office365 is using the LatestWordCount property which isn't a documented property but you can use it to produce a SearchFolder of all your wordy emails eg the following would create a SearchFolder of email where this property indicated the word count of the message was greater than 1000 words.
  1. [Guid]$psguid = "23239608-685D-4732-9C55-4C95CB4E8E33"  
  2. $LatestMessageWordCount = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition($psguid,"LatestMessageWordCount", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer)    
  3. $sfItemSearchFilter = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsGreaterThan($LatestMessageWordCount,1000)   
  4. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  5. $SearchFolder = new-object Microsoft.Exchange.WebServices.Data.SearchFolder($service);  
  6. $rfRootFolderId = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::MsgFolderRoot,$MailboxName)     
  7. $searchFolder.SearchParameters.RootFolderIds.Add($rfRootFolderId);  
  8. $searchFolder.SearchParameters.Traversal = [Microsoft.Exchange.WebServices.Data.SearchFolderTraversal]::Deep;  
  9. $searchFolder.SearchParameters.SearchFilter = $sfItemSearchFilter  
  10. $searchFolder.DisplayName = $SearchFilterName  
  11. $folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::SearchFolders,$MailboxName)     
  12. $sfRoot = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  13. $searchFolder.Save($sfRoot.Id);  

I've put a download of full sample scripts for creating search folder for these two examples here

Friday, November 07, 2014

Creating a new folder in EWS and add it to the MyContacts list in OWA in Exchange 2013/Office365

The peoples hub is one of the new features in Exchange 2013 and Exchange Online that is aimed at making your life richer. One little quirk if your creating new folders using EWS is that they won't appear in the My Contacts list inOWA eg if I was creating a folder named aNewContactsFolder you would get


To make the new Folder you just created appear in the MyContacts list rather then other contacts you need to set these two yet to be documented properties

PeopleHubSortGroupPriority 
PeopleHubSortGroupPriorityVersion

Setting the value of these two named properties to 5 and 2 respectively will make the folder appear under My Contacts, if you want to move the folder into other contacts set the values to 10 and 2

Here's a sample script to create a New Folder as a subfolder of a Mailboxes Contacts Folder and set these two properties so the Contact Folder appears under MyContacts

To run the script pass the emailaddress of the mailbox you want to run it against as the first parameter and the foldername as the second parameter eg use something like .\createMyContactsFldv2.ps1 jcool@domain.com newfolderss

I've put a download of this script here the script itself looks like.
  1. ## Get the Mailbox to Access from the 1st commandline argument  
  2. $NewFolderName = $args[1]  
  3. $MailboxName = $args[0]  
  4.   
  5. ## Load Managed API dll    
  6.   
  7. ###CHECK FOR EWS MANAGED API, IF PRESENT IMPORT THE HIGHEST VERSION EWS DLL, ELSE EXIT  
  8. $EWSDLL = (($(Get-ItemProperty -ErrorAction SilentlyContinue -Path Registry::$(Get-ChildItem -ErrorAction SilentlyContinue -Path 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Web Services'|Sort-Object Name -Descending| Select-Object -First 1 -ExpandProperty Name)).'Install Directory') + "Microsoft.Exchange.WebServices.dll")  
  9. if (Test-Path $EWSDLL)  
  10.     {  
  11.     Import-Module $EWSDLL  
  12.     }  
  13. else  
  14.     {  
  15.     "$(get-date -format yyyyMMddHHmmss):"  
  16.     "This script requires the EWS Managed API 1.2 or later."  
  17.     "Please download and install the current version of the EWS Managed API from"  
  18.     "http://go.microsoft.com/fwlink/?LinkId=255472"  
  19.     ""  
  20.     "Exiting Script."  
  21.     exit  
  22.     }  
  23.     
  24. ## Set Exchange Version    
  25. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2    
  26.     
  27. ## Create Exchange Service Object    
  28. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  29.     
  30. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  31.     
  32. #Credentials Option 1 using UPN for the windows Account    
  33. $psCred = Get-Credential    
  34. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  35. $service.Credentials = $creds        
  36.     
  37. #Credentials Option 2    
  38. #service.UseDefaultCredentials = $true    
  39.     
  40. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  41.     
  42. ## Code From http://poshcode.org/624  
  43. ## Create a compilation environment  
  44. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  45. $Compiler=$Provider.CreateCompiler()  
  46. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  47. $Params.GenerateExecutable=$False  
  48. $Params.GenerateInMemory=$True  
  49. $Params.IncludeDebugInformation=$False  
  50. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  51.   
  52. $TASource=@' 
  53.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  54.     public class TrustAll : System.Net.ICertificatePolicy { 
  55.       public TrustAll() {  
  56.       } 
  57.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  58.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  59.         System.Net.WebRequest req, int problem) { 
  60.         return true; 
  61.       } 
  62.     } 
  63.   } 
  64. '@   
  65. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  66. $TAAssembly=$TAResults.CompiledAssembly  
  67.   
  68. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  69. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  70. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  71.   
  72. ## end code from http://poshcode.org/624  
  73.     
  74. ## 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    
  75.     
  76. #CAS URL Option 1 Autodiscover    
  77. $service.AutodiscoverUrl($MailboxName,{$true})    
  78. "Using CAS Server : " + $Service.url     
  79.      
  80. #CAS URL Option 2 Hardcoded    
  81.     
  82. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  83. #$service.Url = $uri      
  84.     
  85. ## Optional section for Exchange Impersonation    
  86.     
  87. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  88.   
  89.   
  90. #PropDefs   
  91. $PeopleHubSortGroupPriority = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::Common, "PeopleHubSortGroupPriority", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer);  
  92. $PeopleHubSortGroupPriorityVersion = New-Object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::Common, "PeopleHubSortGroupPriorityVersion", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Integer);  
  93.   
  94. # Bind to the Contacts Folder  
  95.   
  96. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Contacts,$MailboxName)     
  97. $Contacts = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  98.   
  99. $NewFolder = new-object Microsoft.Exchange.WebServices.Data.Folder($service)    
  100. $NewFolder.DisplayName = $NewFolderName    
  101. $NewFolder.FolderClass = "IPF.Contact"  
  102. $NewFolder.SetExtendedProperty($PeopleHubSortGroupPriority,5);  
  103. $NewFolder.SetExtendedProperty($PeopleHubSortGroupPriorityVersion,2);  
  104. $NewFolder.Save($Contacts.Id)    
  105. "Created Folder"  

Thursday, October 16, 2014

A look into Conversations with EWS and Powershell in a Mailbox

Conversation views in email clients have become par for the course these days, while I'm personally not a great fan it can be a useful feature to use when looking at Mailbox data. With EWS from Exchange 2010 you can use the dedicated EWS operations which are documented http://msdn.microsoft.com/en-us/library/office/dn610351(v=exchg.150).aspx . In Exchange 2013 the conversation operations have been enhanced to offer more functionality such as the ability to use an AQS QueryString to filter the results plus also the ability to apply actions to conversation like applying categories or a specific retention tag.

One interesting thing you can apply these conversation operations to is looking at Mailbox statistics in a different way by looking at the operation of Mailboxes to see how engaged the owners or users of the Mailboxes are, by seeing how engaged in the conversation that are happening in the Mailbox. eg


The FindConversation operation in Exchange will return information such as the MessageCount and Size in a particular folder as well as the GlobalCount and Sizes across all folders in a Mailbox for a conversation.This is sample of a script that uses the findconversation operation to do some statistical sampling of conversation data. So what this does is

  • Does a FindConversation on the Inbox folder to grab the conversation information for the Inbox
  • Does a FindConversation on the SentItems Folder to grab the conversation stats for the Sent Mail
  • Combines the results together to work out the participation rate in the conversation based on the amount of Messages this particular mailbox sent.
  • For Exchange 2013 you can also query based on the received date of the email so you can look at the last 7 days worth or data etc.
So you can run the script like this to examine the whole of the Inbox

 .\converstats.ps1 user@domain.onmicrosoft.com

or you can use a Date to specify how much data you want to look at eg for the last 7 days use

.\converstats.ps1 user@domain.onmicrosoft.com (get-date).AddDays(-7)

In the script itself I've got it set to only report on conversation with a messagecount greater then 3 and sort the conversation by the participation rate you can adjust this by fiddling with the following line

$Script:rptcollection.Values | Where-Object {$_.InboxMessageCount -gt 3} | Sort-Object ParticipationRate -Descending | Export-Csv -NoTypeInformation -Path c:\Temp\$MailboxName-cnvStats.csv

I've put a download this script here the script itself looks like
  1. $MailboxName = $args[0]  
  2. $StartDate = $args[1]  
  3.   
  4.   
  5. ## Get the Mailbox to Access from the 1st commandline argument  
  6.   
  7. ## Load Managed API dll    
  8.   
  9. ###CHECK FOR EWS MANAGED API, IF PRESENT IMPORT THE HIGHEST VERSION EWS DLL, ELSE EXIT  
  10. $EWSDLL = (($(Get-ItemProperty -ErrorAction SilentlyContinue -Path Registry::$(Get-ChildItem -ErrorAction SilentlyContinue -Path 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Web Services'|Sort-Object Name -Descending| Select-Object -First 1 -ExpandProperty Name)).'Install Directory') + "Microsoft.Exchange.WebServices.dll")  
  11. if (Test-Path $EWSDLL)  
  12.     {  
  13.     Import-Module $EWSDLL  
  14.     }  
  15. else  
  16.     {  
  17.     "$(get-date -format yyyyMMddHHmmss):"  
  18.     "This script requires the EWS Managed API 1.2 or later."  
  19.     "Please download and install the current version of the EWS Managed API from"  
  20.     "http://go.microsoft.com/fwlink/?LinkId=255472"  
  21.     ""  
  22.     "Exiting Script."  
  23.     exit  
  24.     }  
  25.     
  26. ## Set Exchange Version    
  27. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2013_SP1  
  28.     
  29. ## Create Exchange Service Object    
  30. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  31.     
  32. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  33.     
  34. #Credentials Option 1 using UPN for the windows Account    
  35. $psCred = Get-Credential    
  36. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  37. $service.Credentials = $creds        
  38.     
  39. #Credentials Option 2    
  40. #service.UseDefaultCredentials = $true    
  41.     
  42. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  43.     
  44. ## Code From http://poshcode.org/624  
  45. ## Create a compilation environment  
  46. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  47. $Compiler=$Provider.CreateCompiler()  
  48. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  49. $Params.GenerateExecutable=$False  
  50. $Params.GenerateInMemory=$True  
  51. $Params.IncludeDebugInformation=$False  
  52. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  53.   
  54. $TASource=@' 
  55.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  56.     public class TrustAll : System.Net.ICertificatePolicy { 
  57.       public TrustAll() {  
  58.       } 
  59.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  60.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  61.         System.Net.WebRequest req, int problem) { 
  62.         return true; 
  63.       } 
  64.     } 
  65.   } 
  66. '@   
  67. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  68. $TAAssembly=$TAResults.CompiledAssembly  
  69.   
  70. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  71. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  72. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  73.   
  74. ## end code from http://poshcode.org/624  
  75.     
  76. ## 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    
  77.     
  78. #CAS URL Option 1 Autodiscover    
  79. $service.AutodiscoverUrl($MailboxName,{$true})    
  80. "Using CAS Server : " + $Service.url     
  81.      
  82. #CAS URL Option 2 Hardcoded    
  83.     
  84. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  85. #$service.Url = $uri      
  86.     
  87. ## Optional section for Exchange Impersonation    
  88.     
  89. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  90. if($StartDate -ne $null){  
  91.     $AQSString = "received:>" + $StartDate.ToString("yyyy-MM-dd")   
  92.     $AQSString  
  93. }  
  94. # Bind to the Inbox Folder  
  95. $Script:rptcollection = @{}  
  96. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)     
  97. $Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  98. # Bind to the SentItems Folder  
  99. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::SentItems,$MailboxName)     
  100. $SentItems = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  101.   
  102. function Process-Folder{    
  103.     param (    
  104.             $FolderId = "$( throw 'SMTPAddress is a mandatory Parameter' )",  
  105.             $IsSentItems = "$( throw 'SMTPAddress is a mandatory Parameter' )"  
  106.           )    
  107.     process{   
  108.         $cnvItemView = New-Object Microsoft.Exchange.WebServices.Data.ConversationIndexedItemView(1000)  
  109.         $cnvs = $null;  
  110.         do  
  111.         {  
  112.             $cnvs = $service.FindConversation($cnvItemView$FolderId,$AQSString);  
  113.             "Number of Conversation returned " + $cnvs.Count  
  114.             foreach($cnv in $cnvs){  
  115.                 $rptobj = $cnv | select Topic,LastDeliveryTime,UniqueSenders,UniqueRecipients,InboxMessageCount,GlobalMessageCount,InboxMessageSize,SentItemsMessageCount,SentItemsMessageSize,ParticipationRate      
  116.                 if($Script:rptcollection.Contains($cnv.Id.UniqueId)-eq $false){  
  117.                     if($IsSentItems){  
  118.                         $rptobj.SentItemsMessageCount = $cnv.MessageCount  
  119.                         $rptobj.SentItemsMessageSize = $cnv.Size  
  120.                         $rptobj.InboxMessageCount = 0  
  121.                         $rptobj.InboxMessageSize = 0  
  122.                         $rptobj.LastDeliveryTime = $cnv.LastDeliveryTime  
  123.                         $rptobj.UniqueSenders = $cnv.GlobalUniqueSenders  
  124.                         $rptobj.UniqueRecipients = $cnv.GlobalUniqueRecipients  
  125.                     }  
  126.                     else{  
  127.                         $rptobj.InboxMessageCount = $cnv.MessageCount  
  128.                         $rptobj.InboxMessageSize = $cnv.Size  
  129.                         $rptobj.SentItemsMessageCount = 0  
  130.                         $rptobj.SentItemsMessageSize = 0  
  131.                         $rptobj.LastDeliveryTime = $cnv.LastDeliveryTime  
  132.                         $rptobj.UniqueSenders = $cnv.GlobalUniqueSenders  
  133.                         $rptobj.UniqueRecipients = $cnv.GlobalUniqueRecipients  
  134.                     }  
  135.                     $Script:rptcollection.Add($cnv.Id.UniqueId,$rptobj)  
  136.                 }  
  137.                 else{  
  138.                     if($IsSentItems){  
  139.                         $Script:rptcollection[$cnv.Id.UniqueId].SentItemsMessageCount = $cnv.MessageCount  
  140.                         $Script:rptcollection[$cnv.Id.UniqueId].SentItemsMessageSize = $cnv.Size  
  141.                     }  
  142.                     else{  
  143.                         $Script:rptcollection[$cnv.Id.UniqueId].InboxMessageCount = $cnv.MessageCount  
  144.                         $Script:rptcollection[$cnv.Id.UniqueId].InboxMessageSize = $cnv.Size  
  145.                     }  
  146.                        
  147.                 }                 
  148.               
  149.             }  
  150.             $cnvItemView.Offset += $cnvs.Count  
  151.         }while($cnvs.Count -gt 0)  
  152.     }  
  153. }  
  154. Process-Folder -FolderId $Inbox.Id -IsSentItems $false  
  155. Process-Folder -FolderId $SentItems.Id -IsSentItems $true  
  156. foreach($value in $Script:rptcollection.Values){  
  157.     if($value.GlobalMessageCount -gt 0 -band $value.SentItemsMessageCount -gt 0){  
  158.         $value.ParticipationRate = [Math]::round((($value.SentItemsMessageCount/$value.GlobalMessageCount) * 100))  
  159.     }  
  160.     else{  
  161.         $value.ParticipationRate = 0  
  162.     }  
  163. }  
  164. $Script:rptcollection.Values | Where-Object {$_.InboxMessageCount -gt 3} | Sort-Object ParticipationRate -Descending | Export-Csv -NoTypeInformation -Path c:\Temp\$MailboxName-cnvStats.csv  
  165.    

Friday, October 03, 2014

Searching based on Categories in EWS

The Categories or Keywords properties on a Mailbox Item is one of the more commonly used Item properties in Exchange. When you want to search for Items with a particular Category set it does present some challenges in EWS.

With EWS you have 3 different search methods, the first being Restrictions (or SearchFilter's if your using the Managed API) that work like MAPI restrictions although you can't build restriction that are 100% equivalent to what you can in MAPI. One particular case is with the Categories property, because this is a Multi-Valued property (or String Array) the IsEqual and Contains Restrictions wont work like the Sproperty restriction in MAPI http://msdn.microsoft.com/en-us/library/office/cc815385(v=office.15).aspx

So the next type of Search you can do is a Search of a Mailbox folder using an AQS querystring which essentially does an Index search. Because the Categories property is an Indexed property this will work fine for Categories. The thrid type of Search you can do is eDiscovery in Exchange 2013 which I'll cover in another post

The following script does a search of the the Inbox folder for a particular Keyword using the AQS query

"System.Category:Categorytolookfor"

It also does a client side validation to ensure no false positives are included. To run the script just pass in the name of the mailbox you want to search and the Category to search for (enclosed in '' if there is a space) eg .\SearchCategory.ps1 glen@domain.com 'green category' . The script will output a CSV report of all the messages founds with that particular Category set.

I've put a download of this script here the code itself looks like

  1. ## Get the Mailbox to Access from the 1st commandline argument  
  2.   
  3. $MailboxName = $args[0]  
  4. $CategoryToFind = $args[1]  
  5.   
  6. ## Load Managed API dll    
  7.   
  8. ###CHECK FOR EWS MANAGED API, IF PRESENT IMPORT THE HIGHEST VERSION EWS DLL, ELSE EXIT  
  9. $EWSDLL = (($(Get-ItemProperty -ErrorAction SilentlyContinue -Path Registry::$(Get-ChildItem -ErrorAction SilentlyContinue -Path 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Web Services'|Sort-Object Name -Descending| Select-Object -First 1 -ExpandProperty Name)).'Install Directory') + "Microsoft.Exchange.WebServices.dll")  
  10. if (Test-Path $EWSDLL)  
  11.     {  
  12.     Import-Module $EWSDLL  
  13.     }  
  14. else  
  15.     {  
  16.     "$(get-date -format yyyyMMddHHmmss):"  
  17.     "This script requires the EWS Managed API 1.2 or later."  
  18.     "Please download and install the current version of the EWS Managed API from"  
  19.     "http://go.microsoft.com/fwlink/?LinkId=255472"  
  20.     ""  
  21.     "Exiting Script."  
  22.     exit  
  23.     }  
  24.     
  25. ## Set Exchange Version    
  26. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2    
  27.     
  28. ## Create Exchange Service Object    
  29. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  30.     
  31. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  32.     
  33. #Credentials Option 1 using UPN for the windows Account    
  34. $psCred = Get-Credential    
  35. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  36. $service.Credentials = $creds        
  37.     
  38. #Credentials Option 2    
  39. #service.UseDefaultCredentials = $true    
  40.     
  41. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  42.     
  43. ## Code From http://poshcode.org/624  
  44. ## Create a compilation environment  
  45. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  46. $Compiler=$Provider.CreateCompiler()  
  47. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  48. $Params.GenerateExecutable=$False  
  49. $Params.GenerateInMemory=$True  
  50. $Params.IncludeDebugInformation=$False  
  51. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  52.   
  53. $TASource=@' 
  54.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  55.     public class TrustAll : System.Net.ICertificatePolicy { 
  56.       public TrustAll() {  
  57.       } 
  58.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  59.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  60.         System.Net.WebRequest req, int problem) { 
  61.         return true; 
  62.       } 
  63.     } 
  64.   } 
  65. '@   
  66. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  67. $TAAssembly=$TAResults.CompiledAssembly  
  68.   
  69. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  70. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  71. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  72.   
  73. ## end code from http://poshcode.org/624  
  74.     
  75. ## 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    
  76.     
  77. #CAS URL Option 1 Autodiscover    
  78. $service.AutodiscoverUrl($MailboxName,{$true})    
  79. "Using CAS Server : " + $Service.url     
  80.      
  81. #CAS URL Option 2 Hardcoded    
  82.     
  83. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  84. #$service.Url = $uri      
  85.     
  86. ## Optional section for Exchange Impersonation    
  87.     
  88. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  89.   
  90. $AQSString = "System.Category:`"" + $CategoryToFind + "`""  
  91. # Bind to the Inbox Folder  
  92. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)     
  93. $Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  94. $rptCollection = @()  
  95. #Define ItemView to retrive just 1000 Items      
  96. $ivItemView =  New-Object Microsoft.Exchange.WebServices.Data.ItemView(1000)      
  97. $fiItems = $null      
  98. do{      
  99.     $fiItems = $service.FindItems($Inbox.Id,$AQSString,$ivItemView)      
  100.     #[Void]$service.LoadPropertiesForItems($fiItems,$psPropset)    
  101.     foreach($Item in $fiItems.Items){  
  102.         #Validate exact Category Match  
  103.         $match = $false  
  104.         foreach($cat in $Item.Categories){  
  105.             if($cat.ToLower() -eq $CategoryToFind.ToLower()){  
  106.                 $match = $true;  
  107.             }  
  108.         }  
  109.         if($match){  
  110.             $rptObj = "" | Select DateTimeReceived,From,Subject,Size,Categories    
  111.             $rptObj.DateTimeReceived = $Item.DateTimeReceived    
  112.             $rptObj.From  = $Item.From.Name    
  113.             $rptObj.Subject = $Item.Subject    
  114.             $rptObj.Size = $Item.Size  
  115.             $rptObj.Categories = [system.String]::Join(",",$Item.Categories)  
  116.             $rptCollection += $rptObj  
  117.         }  
  118.     }      
  119.     $ivItemView.Offset += $fiItems.Items.Count      
  120. }while($fiItems.MoreAvailable -eq $true)   
  121. $rptCollection | Export-Csv -NoTypeInformation -Path c:\temp\$MailboxName-CategoryReport.csv  
  122. Write-Host "Report Saved to c:\temp\$MailboxName-CategoryReport.csv"   

Wednesday, September 17, 2014

Sending a No Reply, No ReplyAll, No Forward Email using EWS and Powershell

I've you haven't seen this before Gavin Smyth from Microsoft Research put together this cool VSTO plugin to allow you to send an Email from Outlook that will disable the Reply, ReplyAll and Forward Buttons on the Outlook ribbon http://research.microsoft.com/en-us/projects/researchdesktop/noreplyall.aspx and the how to posts about the VSTO http://blogs.msdn.com/b/gsmyth/archive/2011/09/18/noreply-vsto-add-in-wrap-up.aspx .

Note this only works in Outlook (not OWA or ActiveSync etc) but basically what a users would see when they receive a message is



How this works is it sets the PidLidVerbStream Property on a message which is mostly documented in the http://msdn.microsoft.com/en-us/library/ee218541(v=exchg.80).aspx protocol document. I say mostly because the format you get when using the methods from the NoReply Addin is a little different from the format documented which is for Voting buttons but its good enough to work with. The Verbs that this property refers to are the standard Verbs that MAPI implements which are documented in http://msdn.microsoft.com/en-us/library/office/cc815879(v=office.15).aspx .

So to use this same property in an EWS script you can just set it using the Extended Properties, the value you use is a little tricky as only the voteoption format is fully documented. But because this is pretty standard you can cut a past the Hex Values which contains the two streams from this property out of an existing message and then just change the bits that either enables or disable the Verbs for what you want to enable or disable on the Message your sending.

So this is what the following script does is allows you to send a message using EWS and set the options to enable and disable each of these verbs.

In the script I've got the following custom object where you can set the verbs on or off
  1. $VerbSetting = "" | Select DisableReplyAll,DisableReply,DisableForward,DisableReplyToFolder  
  2. $VerbSetting.DisableReplyAll = $true  
  3. $VerbSetting.DisableReply = $true  
  4. $VerbSetting.DisableForward = $true  
  5. $VerbSetting.DisableReplyToFolder = $true  

The rest of the script builds the VerbStream value property based on the setting in the custom object and the rest of the script is a standard EWS script to send a message.

I've put a download of this script here the script itself looks like

  1. $MailboxName = $args[0]  
  2. $SentTo = $args[1]  
  3.   
  4. $VerbSetting = "" | Select DisableReplyAll,DisableReply,DisableForward,DisableReplyToFolder  
  5. $VerbSetting.DisableReplyAll = $true  
  6. $VerbSetting.DisableReply = $true  
  7. $VerbSetting.DisableForward = $true  
  8. $VerbSetting.DisableReplyToFolder = $true  
  9.   
  10. ## Load Managed API dll    
  11.   
  12. ###CHECK FOR EWS MANAGED API, IF PRESENT IMPORT THE HIGHEST VERSION EWS DLL, ELSE EXIT  
  13. $EWSDLL = (($(Get-ItemProperty -ErrorAction SilentlyContinue -Path Registry::$(Get-ChildItem -ErrorAction SilentlyContinue -Path 'Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Web Services'|Sort-Object Name -Descending| Select-Object -First 1 -ExpandProperty Name)).'Install Directory') + "Microsoft.Exchange.WebServices.dll")  
  14. if (Test-Path $EWSDLL)  
  15.     {  
  16.     Import-Module $EWSDLL  
  17.     }  
  18. else  
  19.     {  
  20.     "$(get-date -format yyyyMMddHHmmss):"  
  21.     "This script requires the EWS Managed API 1.2 or later."  
  22.     "Please download and install the current version of the EWS Managed API from"  
  23.     "http://go.microsoft.com/fwlink/?LinkId=255472"  
  24.     ""  
  25.     "Exiting Script."  
  26.     exit  
  27.     }  
  28.     
  29. ## Set Exchange Version    
  30. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP2    
  31.     
  32. ## Create Exchange Service Object    
  33. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  34.     
  35. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  36.     
  37. #Credentials Option 1 using UPN for the windows Account    
  38. $psCred = Get-Credential    
  39. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  40. $service.Credentials = $creds        
  41.     
  42. #Credentials Option 2    
  43. #service.UseDefaultCredentials = $true    
  44.     
  45. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  46.     
  47. ## Code From http://poshcode.org/624  
  48. ## Create a compilation environment  
  49. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  50. $Compiler=$Provider.CreateCompiler()  
  51. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  52. $Params.GenerateExecutable=$False  
  53. $Params.GenerateInMemory=$True  
  54. $Params.IncludeDebugInformation=$False  
  55. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  56.   
  57. $TASource=@' 
  58.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  59.     public class TrustAll : System.Net.ICertificatePolicy { 
  60.       public TrustAll() {  
  61.       } 
  62.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  63.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  64.         System.Net.WebRequest req, int problem) { 
  65.         return true; 
  66.       } 
  67.     } 
  68.   } 
  69. '@   
  70. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  71. $TAAssembly=$TAResults.CompiledAssembly  
  72.   
  73. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  74. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  75. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  76.   
  77. ## end code from http://poshcode.org/624  
  78.     
  79. ## 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    
  80.     
  81. #CAS URL Option 1 Autodiscover    
  82. $service.AutodiscoverUrl($MailboxName,{$true})    
  83. "Using CAS Server : " + $Service.url     
  84.      
  85. #CAS URL Option 2 Hardcoded    
  86.     
  87. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  88. #$service.Url = $uri      
  89.     
  90. ## Optional section for Exchange Impersonation    
  91.     
  92. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  93.   
  94.   
  95. function Get-VerbStream{    
  96.     param (    
  97.             $VerbSettings = "$( throw 'VerbSettings is a mandatory Parameter' )"    
  98.           )    
  99.     process{    
  100.       
  101.     $Header = "02010400000000000000"  
  102.     $ReplyToAllHeader = "055265706C790849504D2E4E6F7465074D657373616765025245050000000000000000"  
  103.     $ReplyToAllFooter = "0000000000000002000000660000000200000001000000"  
  104.     $ReplyToHeader = "0C5265706C7920746F20416C6C0849504D2E4E6F7465074D657373616765025245050000000000000000"  
  105.     $ReplyToFooter = "0000000000000002000000670000000300000002000000"  
  106.     $ForwardHeader = "07466F72776172640849504D2E4E6F7465074D657373616765024657050000000000000000"  
  107.     $ForwardFooter = "0000000000000002000000680000000400000003000000"  
  108.     $ReplyToFolderHeader = "0F5265706C7920746F20466F6C6465720849504D2E506F737404506F737400050000000000000000"  
  109.     $ReplyToFolderFooter = "00000000000000020000006C00000008000000"  
  110.     $VoteOptionExtras = "0401055200650070006C00790002520045000C5200650070006C007900200074006F00200041006C006C0002520045000746006F007200770061007200640002460057000F5200650070006C007900200074006F00200046006F006C0064006500720000"  
  111.     if($VerbSetting.DisableReplyAll){  
  112.         $DisableReplyAllVal = "00"  
  113.     }  
  114.     else{  
  115.         $DisableReplyAllVal = "01"  
  116.     }  
  117.     if($VerbSetting.DisableReply){  
  118.         $DisableReplyVal = "00"  
  119.     }  
  120.     else{  
  121.         $DisableReplyVal = "01"  
  122.     }  
  123.     if($VerbSetting.DisableForward){  
  124.         $DisableForwardVal = "00"  
  125.     }  
  126.     else{  
  127.         $DisableForwardVal = "01"  
  128.     }  
  129.     if($VerbSetting.DisableReplyToFolder){  
  130.         $DisableReplyToFolderVal = "00"  
  131.     }  
  132.     else{  
  133.         $DisableReplyToFolderVal = "01"  
  134.     }  
  135.     $VerbValue = $Header +  $ReplyToAllHeader + $DisableReplyAllVal + $ReplyToAllFooter + $ReplyToHeader + $DisableReplyVal +$ReplyToFooter + $ForwardHeader + $DisableForwardVal + $ForwardFooter + $ReplyToFolderHeader + $DisableReplyToFolderVal + $ReplyToFolderFooter + $VoteOptionExtras  
  136.     return $VerbValue  
  137.     }  
  138. }  
  139.   
  140. function hex2binarray($hexString){  
  141.     $i = 0  
  142.     [byte[]]$binarray = @()  
  143.     while($i -le $hexString.length - 2){  
  144.         $strHexBit = ($hexString.substring($i,2))  
  145.         $binarray += [byte]([Convert]::ToInt32($strHexBit,16))  
  146.         $i = $i + 2  
  147.     }  
  148.     return ,$binarray  
  149. }  
  150.   
  151.   
  152.   
  153. $VerbStreamProp = new-object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::Common,0x8520, [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Binary)  
  154.   
  155. $VerbSettingValue = get-VerbStream $VerbSetting  
  156.   
  157. $EmailMessage = New-Object Microsoft.Exchange.WebServices.Data.EmailMessage -ArgumentList $service    
  158. $EmailMessage.Subject = "Message Subject"    
  159. #Add Recipients      
  160. $EmailMessage.ToRecipients.Add($SentTo)    
  161. $EmailMessage.Body = New-Object Microsoft.Exchange.WebServices.Data.MessageBody    
  162. $EmailMessage.Body.BodyType = [Microsoft.Exchange.WebServices.Data.BodyType]::HTML    
  163. $EmailMessage.Body.Text = "Body"   
  164. $EmailMessage.SetExtendedProperty($VerbStreamProp,(hex2binarray $VerbSettingValue))  
  165. $EmailMessage.SendAndSaveCopy()