Skip to main content

GPX Route Mail App for Exchange 2013 and Exchange Online

As part of my MEC talk last month I presented a Mail App that would show a Map with route layer added based on the content of a GPX attachment on a received message. For example here's a screenshot of the Application that was activated from a GPX file that was exported from the Google Tracks application .


Mail Apps are a new feature of Exchange2013/Exchange Online that gives you a standard way of extending the functionality of Outlook,OWA and OWA for devices. The way this particular Mail app works is first, in the Manifest file there is a filter so it will only show on messages you open/view that have an attachment eg

  1. <Rule xsi:type="RuleCollection" Mode="And">  
  2.     <Rule xsi:type="ItemIs" FormType = "Read" ItemType="Message" />  
  3.     <Rule xsi:type="ItemHasAttachment" />  
  4. </Rule>  

Next if somebody activates the application the next thing it does is uses the new Attachments API that was added in 2013 SP1 to first get the details of the attachments on the message, it then checks if one of them is a GPX attachment. If there is a GPX attachment it then uses an externally hosted controller to make the GetAttachment Call to EWS using a token obtained for authentication to get the Attachment content which is then returned to the MailApp (this is done using a modified version of the following sample). Once the Mail App has the GPX content from the attachment it then uses leaflet which is a open source javascript library that makes mapping easier and also a GPX plugin that was developed for leaflet to add a GPX layer to the map.

Note in this sample I'm using  openstreetmap if you going to use this in your own environment or develop a similar solution using this code you need to be aware of the tile usage policy http://wiki.openstreetmap.org/wiki/Tile_usage_policy of this or any mapping service you decide to use.

To use a Mail App you need to host all the associated the files yourself somewhere see http://msdn.microsoft.com/en-us/library/office/fp161135(v=office.15).aspx for more details. With this particular application you need to host both the Mail App and also the controller service to allow you to get the attachment content.  I've put a download of the hosted code for the Mail App here https://www.dropbox.com/s/6fzzc3hpli8x5sf/HostedFiles.zip the attachment service uses a modified version of http://code.msdn.microsoft.com/office/Mail-apps-for-Office-Get-38babdc9 I've included a copy of the modified controller in the download.

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 Graph is limited to a m

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 need to authorize it in you tenant (eg build a small ap

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
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.