Skip to main content

Text Emoticon Outlook and OWA Compose App

Emojis and emoticons have been around for quite a while but are picking up a bit of steam of late with the release of Windows 10. The Daily mail had a really good article on their use recently which is worth a read.

Like everything these new emoji's have there origins story and text based emoticons (which have many other names) are kind of a interesting sub branch with a slightly retro feel.

In this post I'm going to show you how you can create a Mail App to make using text emoticon's easy in Exchange 2013 and Office365 using the new compose apps feature which was introduced last year at MEC.

Compose apps are one way of easily extending the User interface in OWA and Outlook 2013 (and 2016). So for this example I can do something like the following to make these text emoticons easy to insert into either the Subject or Body of a message (you need to active the app by selecting the Addin Button in OWA or Apps for Office in Outlook)


At this point it should be noted the Unicode support in Email subjects is a relative new thing the RFC came out in 1996 https://tools.ietf.org/html/rfc2047 full Unicode support in Outlook didn't really happen until 2003. So if your sending to someone still rocking old versions be warned actually because of the difference in the implementation of character sets and available between different platforms windows/android/ios etc some of these text base emoticons may only display correctly on some platforms/browsers/mail clients. But you can then have hours of fun filling you mailbox with this type of stuff



Mail Apps are relatively simple to implement and this is a pretty straight forward example the first thing you have is the Manifest file where all the configuration information is held for this Mail App. Eg in my app some of the important relative information is

 <FormSettings>
    <Form xsi:type="ItemEdit">
      <DesktopSettings>
        <SourceLocation DefaultValue=
          "https://gscales.github.io/TextEmoticon/index.html" />
      </DesktopSettings>
      <TabletSettings>
        <SourceLocation DefaultValue=
          "https://gscales.github.io/TextEmoticon/index.html" />
      </TabletSettings>
      <PhoneSettings>
        <SourceLocation DefaultValue=
          "https://gscales.github.io/TextEmoticon/index.html" />
      </PhoneSettings>
    </Form>
  </FormSettings>

This tells us where the Mail App is being hosted is my case just in my GitHub Repo to learn more about the other manifest setting have a read of this. The Mail App itself is just a pretty simple html and javascript app that creates a table and reads in the text emoticons and controls the formatting and takes care of the backend operations by hooking into the JavaScript Api for office.

In the script.js for this app when you select the Subject object and click a text emoticon to insert your chosen Icon it will append this to the current subject (there is no way to do a positional insert based on the current position of the cursor in the subject. For the body you can insert the Icon at the current cursor location using the method from https://msdn.microsoft.com/EN-US/library/office/dn574748.aspx#mod_off15_HowToInsertDataBody_AtCursor

I've posted the code for this up into my GitHub repo at https://github.com/gscales/gscales.github.io/tree/master/TextEmoticon  if you want to test it you can install the app from the manifest at  https://gscales.github.io/TextEmoticon/manifest.xml . Although I'd recommend you clone it yourself and then you can change the text emoticons in the script.js file to whatever you like. If you do clone the repository you need to change the (the source location settings shown above) settings in the Manifest file to ensure its pointing at the files your hosting or you will never see your changes take affect.

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.