A no fluff response….
We have been slammed with this release because we want it perfect. The extra hours have been intense!
As most of you already know through the community and blog posts, the entire backend has entirely changed. The conversion process was incredibly difficult and we have been testing with customers privately and others who have tested in the community. Thankfully, we have moved past this phase!
In a recent blog post, we explained that our team was in Redmond meeting with their protocol teams. This resulted in significant insight into how we were approaching all protocols: EWS, EAS, WebDAV, and MAPI!
Once they were back, we decided to rewrite all the protocols to use similar synchronization processes and include ALL the properties that Exchange support for emails, calendars, tasks, notes, etc. In turn, this caused us to include even more data in the backend which we want to be done in the most efficient ways possible.
So, we have decided that we are releasing MAPI with a .2 release of SmarterMail 17. This way, we can focus on making the upgrade process from previous versions to SmarterMail 17.x and ensure that all the backend changes and protocols are perfect for customers without introducing MAPI and its intricacies.
So, what will SmarterMail 17 look like on release day...
It will be faster at boot up and while running, it will use less memory, it will use less disk i/o, it will have significantly higher performance and more capable protocols along with many other features and functionality.
The .1 release will be all about any issues that customers have seen after the upgrade, etc.
Within a couple months after release, we will have a .2 version that will include MAPI!
The main takeaway is that we KNOW MAPI support needs to be perfect and have all the functionality of Exchange, and we’re working hard to ensure that, once released, it’s exactly that.