This post is about emClient’s EAS (Exchange ActiveSync) support and my
(not guaranteed to be 100% correct) understanding of it. The emClient refers to EAS as AirSync, but that is just a far less common and outdated name for the same thing. I’m calling it EAS.
Prior to v7.1, whenever we setup an Outlook.com (MS’ online mail service) account in emClient, EAS was used in the background to do all the syncing. Since version 7.1, emClient still uses EAS to synchronize contacts, calendar and task data, but e-mails are synchronized using IMAP.
The emClient team has done a poor job of explaining why this is. I’ve seen very vague mentions of “reliability issues”. However, considering this is a proven technology that is licensed by MS, and which is used successfully by hundreds of other companies, this “explanation” seems insincere (either that or their development team is incompetent). I’m not buying it. More on that later…
More importantly, along with that change in EAS support, the emClient team also changed how an Outlook.com account is configured. Prior to version 7.1, it was possible to to setup an Outlook.com account and then redirect it to an alternative server. This allowed emClient to authenticate and synchronize not only against Outlook.com, but also against any other EAS based service provider, like Zoho or Shaw. Due to the changes in account configuration, this is no longer possible. For customers who used emClient specifically for the ability to sync with such providers, and payed for it, emClient is now broken. As of yet, I have not seen this addressed by the emClient team. This is frustrating for quite a few people and the emClient’s handling of it just looks dodgy.
I’d appreciate an honest and technically competent answer as to what is going on here.
I suspect these changes were actually made because EAS is a technology that must be licensed from MS. The changes likely allowed the developers to lower or eliminate the licensing costs.
That last paragraph is speculation. Everything else is simply the situation as I currently understand it.
Am I right about all this so far? Corrections? Official statements from the emClient team?
What I’d like to hear is this:
- EAS will return as a fully supported synchronization protocol (i.e. including mail)
- EAS will be configurable for other services besides Outlook.com, like Zoho or Shaw
Since EAS must be licensed from MS, I’d understand the free version not supporting it, but the Pro version really should. It’s what people payed for.
Side note:
A while ago, Outlook.com (MS’ online mail service) and MS Outlook (the Windows application) used EAS to synchronize data between them (just like emClient). Sometime last year that changed. Now Outlook.com and Outlook synchronize data using EWS. EWS is the protocol used by Exchange server, which emClient already supports. When creating a new account in emClient, we can already select “Exchange” (as opposed to outlook, gmail, yahoo, etc) and enter an Outlook.com address. This works perfectly well. The result is an emClient account that syncs with Outlook.com using EWS rather than the clunky EAS+IMAP approach.
Unfortunately, most users with Outlook accounts will end up using the later/inferior approach, as that is the setup we get when we say we want to synchronize with an Outlook.com account. That seems completely backward. I’m hoping this is only temporary and that the emClient team intends to fix this ASAP!