Skip to main content

Create an RSS feed of Exchange Items using any of the How To Series scripts

If you've missed my HowTo Series this year I've been demonstrating many different way's of getting, filtering and searching for Exchange data using Powershell and the EWS Managed API see the full list here . One of the fun things to do with scripting is to link this together with the other plethora of script's out in the world to do different things. Here one example of linking the How-To series script with an RSS feed script from the PoshCode repository http://poshcode.org/?show=669

The following script grabs the last 50 Items in the Inbox and creates an RSS feed of theses Item including Links to OWA for the Item and the Item's Body as HTML in the Feed details.

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

  1. ###Code from http://poshcode.org/?show=669  
  2. # Creates an RSS feed  
  3. # Parameter input is for "site": Path, Title, Url, Description  
  4. # Pipeline input is for feed items: hashtable with Title, Link, Author, Description, and pubDate keys  
  5. Function New-RssFeed  
  6. {   
  7.     param (  
  8.             $Path = "$( throw 'Path is a mandatory parameter.' )",  
  9.             $Title = "Site Title",  
  10.             $Url = "http://$( $env:computername )",  
  11.             $Description = "Description of site"  
  12.     )  
  13.     Begin {  
  14.             # feed metadata  
  15.             $encoding = [System.Text.Encoding]::UTF8  
  16.             $writer = New-Object System.Xml.XmlTextWriter( $Path, $encoding )  
  17.             $writer.WriteStartDocument()  
  18.             $writer.WriteStartElement( "rss" )  
  19.             $writer.WriteAttributeString( "version", "2.0" )  
  20.             $writer.WriteStartElement( "channel" )  
  21.             $writer.WriteElementString( "title", $Title )  
  22.             $writer.WriteElementString( "link", $Url )  
  23.             $writer.WriteElementString( "description", $Description )  
  24.     }  
  25.     Process {  
  26.             # Construct feed items  
  27.             $writer.WriteStartElement( "item" )  
  28.             $writer.WriteElementString( "title",    $_.title )  
  29.             $writer.WriteElementString( "link",             $_.link )  
  30.             $writer.WriteElementString( "author",   $_.author )  
  31.             $writer.WriteStartElement( "description" )  
  32.             $writer.WriteRaw( "<![CDATA[" ) # desc can contain HTML, so its escaped using SGML escape code  
  33.             $writer.WriteRaw( $_.description )  
  34.             $writer.WriteRaw( "]]>" )  
  35.             $writer.WriteEndElement()  
  36.             $writer.WriteElementString( "pubDate", $_.pubDate.toString( 'r' ) )  
  37.             $writer.WriteElementString( "guid", $homePageUrl + "/" + [guid]::NewGuid() )  
  38.             $writer.WriteEndElement()  
  39.     }  
  40.     End {  
  41.             $writer.WriteEndElement()  
  42.             $writer.WriteEndElement()  
  43.             $writer.WriteEndDocument()  
  44.             $writer.Close()  
  45.     }  
  46. }  
  47. ### end code from http://poshcode.org/?show=669  
  48.   
  49. ## Get the Mailbox to Access from the 1st commandline argument  
  50.   
  51. $MailboxName = $args[0]  
  52.   
  53. ## Load Managed API dll    
  54. Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.2\Microsoft.Exchange.WebServices.dll"    
  55.     
  56. ## Set Exchange Version    
  57. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1    
  58.     
  59. ## Create Exchange Service Object    
  60. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)    
  61.     
  62. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials    
  63.     
  64. #Credentials Option 1 using UPN for the windows Account    
  65. $psCred = Get-Credential    
  66. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())    
  67. $service.Credentials = $creds        
  68.     
  69. #Credentials Option 2    
  70. #service.UseDefaultCredentials = $true    
  71.     
  72. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates    
  73.     
  74. ## Code From http://poshcode.org/624  
  75. ## Create a compilation environment  
  76. $Provider=New-Object Microsoft.CSharp.CSharpCodeProvider  
  77. $Compiler=$Provider.CreateCompiler()  
  78. $Params=New-Object System.CodeDom.Compiler.CompilerParameters  
  79. $Params.GenerateExecutable=$False  
  80. $Params.GenerateInMemory=$True  
  81. $Params.IncludeDebugInformation=$False  
  82. $Params.ReferencedAssemblies.Add("System.DLL") | Out-Null  
  83.   
  84. $TASource=@' 
  85.   namespace Local.ToolkitExtensions.Net.CertificatePolicy{ 
  86.     public class TrustAll : System.Net.ICertificatePolicy { 
  87.       public TrustAll() {  
  88.       } 
  89.       public bool CheckValidationResult(System.Net.ServicePoint sp, 
  90.         System.Security.Cryptography.X509Certificates.X509Certificate cert,  
  91.         System.Net.WebRequest req, int problem) { 
  92.         return true; 
  93.       } 
  94.     } 
  95.   } 
  96. '@   
  97. $TAResults=$Provider.CompileAssemblyFromSource($Params,$TASource)  
  98. $TAAssembly=$TAResults.CompiledAssembly  
  99.   
  100. ## We now create an instance of the TrustAll and attach it to the ServicePointManager  
  101. $TrustAll=$TAAssembly.CreateInstance("Local.ToolkitExtensions.Net.CertificatePolicy.TrustAll")  
  102. [System.Net.ServicePointManager]::CertificatePolicy=$TrustAll  
  103.   
  104. ## end code from http://poshcode.org/624  
  105.     
  106. ## 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    
  107.     
  108. #CAS URL Option 1 Autodiscover    
  109. $service.AutodiscoverUrl($MailboxName,{$true})    
  110. "Using CAS Server : " + $Service.url     
  111.      
  112. #CAS URL Option 2 Hardcoded    
  113.     
  114. #$uri=[system.URI] "https://casservername/ews/exchange.asmx"    
  115. #$service.Url = $uri      
  116.     
  117. ## Optional section for Exchange Impersonation    
  118.     
  119. #$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)   
  120.   
  121. # Bind to the Contacts Folder  
  122.   
  123. $folderid= new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$MailboxName)     
  124. $Inbox = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)  
  125. $psPropset = new-object Microsoft.Exchange.WebServices.Data.PropertySet([Microsoft.Exchange.WebServices.Data.BasePropertySet]::FirstClassProperties)    
  126. #Define ItemView to retrive just 50 Items      
  127. $ivItemView =  New-Object Microsoft.Exchange.WebServices.Data.ItemView(50)      
  128. $fiItems = $service.FindItems($Inbox.Id,$ivItemView)      
  129. [Void]$service.LoadPropertiesForItems($fiItems,$psPropset)    
  130. $feedItems = @()  
  131. foreach($Item in $fiItems.Items){      
  132.      "processing Item " + $Item.Subject  
  133.      $PostItem = @{}  
  134.      $PostItem.Add("Title",$Item.Subject)  
  135.      $PostItem.Add("Author",$Item.Sender.Address)  
  136.      $PostItem.Add("pubDate",$Item.DateTimeReceived)  
  137.      $PostItem.Add("link",("https://" + $service.Url.Host +  "/owa/" + $Item.WebClientReadFormQueryString))  
  138.      $PostItem.Add("description",$Item.Body.Text)  
  139.      $feedItems += $PostItem         
  140. }      
  141. $feedItems | New-RssFeed -path "c:\temp\Inboxfeed.xml" -title ($MailboxName + " Inbox")  


Labels:

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

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

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