Skip to main content

MEC is back again this year

MEC the Microsoft Exchange Conference is on again this year in April and is shaping up to be a not to be missed event if your interested in Exchange. Unlike other conferences MEC doesn't come around every year which adds to the charm and freshness of the content you can expect to hear. Also the Exchange community are pretty awesome so it is not just the technology that makes this event but rather the people you can meet and listen to.

If your a developer or interested in coding on Exchange there is an Exchange Extensibility track http://www.mecisback.com/Sessions.aspx which covers among other things some of the new things you can do with Exchange 2013 and Exchange Online.  As with many of the sessions at MEC a lot these are being delivered by the people at Microsoft who are responsible for designing and delivering these features, so its one of the only places you can get those hard questions answered or put some feedback forward. The future look sessions also look pretty interesting to get glimpse of the near future.

I'm also really excited about the session I'll be giving at MEC on "Using Exchange as a platform for Innovation" http://www.mecisback.com/SessionDetail.aspx?id=14161 . My session content will be a bit out of the box and different, it might be a bit of an 11 on the technical side as i have a pretty broad scope to cover, I'll be talking on both hardware and software and how you can build Mailbox centric solutions on unconventional devices. So if your interested in what you can do with a Raspberry Pi connecting to an Exchange Mailbox with EWS or interesting in learning how the Maker movement may start interfacing with Exchange then this is the session for you. I hope to have a least 3 unique prototypes to show and a little bit of usually blog type scripts at the end.

You can get all the other details on MEC at http://www.mecisback.com/

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

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.

EWS-FAI Module for browsing and updating Exchange Folder Associated Items from PowerShell

Folder Associated Items are hidden Items in Exchange Mailbox folders that are commonly used to hold configuration settings for various Mailbox Clients and services that use Mailboxes. Some common examples of FAI's are Categories,OWA Signatures and WorkHours there is some more detailed documentation in the https://msdn.microsoft.com/en-us/library/cc463899(v=exchg.80).aspx protocol document. In EWS these configuration items can be accessed via the UserConfiguration operation https://msdn.microsoft.com/en-us/library/office/dd899439(v=exchg.150).aspx which will give you access to either the RoamingDictionary, XMLStream or BinaryStream data properties that holds the configuration depending on what type of FAI data is being stored. I've written a number of scripts over the years that target particular FAI's (eg this one that reads the workhours  http://gsexdev.blogspot.com.au/2015/11/finding-timezone-being-used-in-mailbox.html is a good example ) but I didn't have a gene...
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.