Glen's Exchange and Office 365 Dev Blog

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 ###Code from http://poshcode.org/?show=669    # Creates an RSS feed    # Parameter input is for "site": Path, Title, Url, Description    # Pipeline input is for feed items: hashtable with Title, Link, Author, De

eDiscovery is one of the new features in Exchange 2013 that has been built on the top of new operations added in Exchange Web Services in 2013. While its very useful for ITPro's for handling legal discoveries and compliance issues, it opens up a whole new world for application developers building Apps that search Exchange Mailboxes. Like the AQS querystring that was introduced in Exchange 2010 the eDiscovery operations make use of the Exchange Search service's content indexes. There isn't much documentation around at the moment about how to use eDiscovery in EWS so this is just a dump of what I've learned so far. All up there are four new EWS operations for eDiscovery however the two that you will use most of the time would be. GetSearchableMailboxes Gets a list of mailboxes that the client has permission to search or perform eDiscovery on. SearchMailboxes Searches for items in specific mailboxes that match query keyw

This is a rewrite of an old CDO 1.2 rule.dll script back from 2006 http://gsexdev.blogspot.com.au/2006/10/creating-domain-based-auto-response.html . Creating a Domain based auto response rule allows you to have a custom auto-responder for an email based on the sender's email domain of any newly received email messages. This is useful when you need to cater for a number of different scenarios and where you want to add a more personal touch to these auto responders.  EWS allows you to create Inbox rules via the CreateRule Operation if your after the full spiel have a read of http://msdn.microsoft.com/en-us/library/exchange/hh298418%28v=exchg.140%29.aspx In this script it first uses a ContainsSenderStrings condition to filter on the domain you want the rule to apply to in my example yahoo.com $nrNewInboxRule.Conditions.ContainsSenderStrings.Add("@yahoo.com") Exceptions are created for any messages with subject prefixes of RE and FW to omit these message