Skip to main content

Generating OWA Url's for Mail Items and producing Summary Emails for Public Folders and Mailbox's with Powershell and the EWS Managed API

Its often useful to be able to create a link that will open a specific email within OWA for a variety of different uses (eg RSS feeds, Summary email, Calendar Summary pages etc). With EWS you can get the OWAid which is necessary to form an OWA URL that will be usable by using a covertid operation. Depending on whether you want to show items that are located in mailbox or public folder then you need to use one of two different objects when doing a covertid eg to convert Mailbox Items into the OWA format from a EWS Query

$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternateId
$aiItem.Mailbox = "Blah@Blah.com"
$aiItem.UniqueId = $Item.Id.UniqueId
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::EwsId;
$owaid = $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::OwaId)

If its a public folder use the following

$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternatePublicFolderItemId
$aiItem.FolderId = $PublicFolder.Id
$aiItem.ItemId = $Item.Id
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::EwsId;
$owaid = $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::OwaId)

To make this usefull we need to combine it with a EWS Query of a mailbox or public folder for example if you want to look at all the email from a specific email address within the last day with a paritcular mailbox's inbox. You need a Searchfilter set like the following.

$SenderName = "alerts@domain.com"
$Sfir = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo([Microsoft.Exchange.WebServices.Data.EmailMessageSchema]::Sender,$SenderName)
$Sflt = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsGreaterThan([Microsoft.Exchange.WebServices.Data.ItemSchema]::DateTimeReceived, $MailDate)

$sfCollection = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+SearchFilterCollection([Microsoft.Exchange.WebServices.Data.LogicalOperator]::And);
$sfCollection.add($Sfir)
$sfCollection.add($Sflt)

The rest of the script can then build a HTML body that consists of a HTML table where the subject is hyperlinked with the OWA URI and the mail is sent via SMTP to a configured Hub server.

I've put an example of a script that does this for a public folder and Mailbox and posted this here the public folder version looks lke the following.

Before using this script you need to configure the first 5 varibles

$MailDate = [system.DateTime]::Now.AddDays(-1)
$pfFolder = "/Folder-offroot/Folder1"
$SenderName = "targetAddress@domain.com"

$sendAlertTo = "Sendalerttoaddress@domain.com"
$sendAlertFrom = "Sendalertfromaddress@domain.com"

$SMTPServer = "HubServerName"

Function FindTargetFolder($FolderPath){
$tfTargetFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,[Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::PublicFoldersRoot)
$pfArray = $FolderPath.Split("/")
for ($lint = 1; $lint -lt $pfArray.Length; $lint++) {
$pfArray[$lint]
$fvFolderView = new-object Microsoft.Exchange.WebServices.Data.FolderView(1)
$SfSearchFilter = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo([Microsoft.Exchange.WebServices.Data.FolderSchema]::DisplayName,$pfArray[$lint])
$findFolderResults = $service.FindFolders($tfTargetFolder.Id,$SfSearchFilter,$fvFolderView)
if ($findFolderResults.TotalCount -gt 0){
foreach($folder in $findFolderResults.Folders){
$tfTargetFolder = $folder
}
}
else{
"Error Folder Not Found"
$tfTargetFolder = $null
break
}
}
$Global:findFolder = $tfTargetFolder
}


$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://<SID=" + $windowsIdentity.user.Value.ToString() + ">"
$aceuser = [ADSI]$sidbind

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

FindTargetFolder($pfFolder)
$PublicFolder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$Global:findFolder.Id.UniqueId)

$Sfir = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsEqualTo([Microsoft.Exchange.WebServices.Data.EmailMessageSchema]::Sender,$SenderName)
$Sflt = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+IsGreaterThan([Microsoft.Exchange.WebServices.Data.ItemSchema]::DateTimeReceived, $MailDate)

$sfCollection = new-object Microsoft.Exchange.WebServices.Data.SearchFilter+SearchFilterCollection([Microsoft.Exchange.WebServices.Data.LogicalOperator]::And);
$sfCollection.add($Sfir)
$sfCollection.add($Sflt)


$rpReport = $rpReport + "<table><tr bgcolor=`"#95aedc`">"
$rpReport = $rpReport + "<td align=`"center`" style=`"width:15%;`" ><b>Recieved</b></td>"
$rpReport = $rpReport + "<td align=`"center`" style=`"width:20%;`" ><b>From</b></td>"
$rpReport = $rpReport + "<td align=`"center`" style=`"width:20%;`" ><b>To</b></td>"
$rpReport = $rpReport + "<td align=`"center`" style=`"width:40%;`" ><b>Subject</b></td>"
$rpReport = $rpReport + "<td align=`"center`" style=`"width:5%;`" ><b>Size</b></td>"
$rpReport = $rpReport + "</tr>"

$view = new-object Microsoft.Exchange.WebServices.Data.ItemView(1000)
$fiFindItemsResult = $PublicFolder.FindItems($sfCollection,$view)
foreach($Item in $fiFindItemsResult.items){
$aiItem = New-Object Microsoft.Exchange.WebServices.Data.AlternatePublicFolderItemId
$aiItem.FolderId = $PublicFolder.Id
$aiItem.ItemId = $Item.Id
$aiItem.Format = [Microsoft.Exchange.WebServices.Data.IdFormat]::EwsId;
$CasServer = $service.Url.Host.ToString()
$openType = "ae=Item";
$owaid = $service.ConvertId($aiItem, [Microsoft.Exchange.WebServices.Data.IdFormat]::OwaId)
$Item.load()
$OWAURL = "https://" + $CasServer + "/owa/?" + $openType + "&t=" + $Item.ItemClass + "&id=" + $owaid.ItemId
$rpReport = $rpReport + " <tr>" + " "
$rpReport = $rpReport + "<td>" + $Item.DateTimeReceived.ToString() + "</td>" + " "
$rpReport = $rpReport + "<td>" + $Item.From.Address + "</td>" + " "
$rpReport = $rpReport + "<td>" + $Item.ToRecipients[0].Address + "</td>" + " "
$rpReport = $rpReport + "<td><a href=`"" + $OWAURL + "`">" + $Item.Subject + "</a></td>" + " "
$rpReport = $rpReport + "<td>" + $Item.Size + "</td>" + " "
$rpReport = $rpReport + "</tr>" + " "

}

$rpReport = $rpReport + "</table>" + " "
$SmtpClient = new-object system.net.mail.smtpClient
$SmtpClient.host = $SMTPServer
$MailMessage = new-object System.Net.Mail.MailMessage
$MailMessage.To.Add($sendAlertTo)
$MailMessage.From = $sendAlertFrom
$MailMessage.Subject = "Summary Email"
$MailMessage.IsBodyHtml = $TRUE
$MailMessage.body = $rpReport
$SMTPClient.Send($MailMessage)

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

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filena

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