#Zimbra outlook conector update

I believe that changed to EAS 16.1 - the protocol was rewritten. And AirSync was specifically designed for groupware/mobile device synchronisation - note I donвЂ™t use the term вЂoutlookвЂ™, but вЂgroupwareвЂ™ - of which there are a number of providers who provide EAS servers. All the publicity states вЂAirSyncвЂ™ - which is the ORIGINAL branding for EAS - and if thatвЂ™s what emClient state is what is supported, then thatвЂ™s what it should provide - which it used to. ThereвЂ™s actually trade description issue though. If you donвЂ™t find my comments helpful, that is OK, I donвЂ™t mind. Of course you are welcome to use any other desktop client that does support the version of EAS that is running on your server. As Randy says it works on his mobile device, and that seems to be only platform on which it is now successfully used and developed. In the end though, whatever the reason, I personally donвЂ™t see eM Client using resources to develop something that is practically dead on the desktop platform.

#Zimbra outlook conector update

Maybe the non-Exchange product itself changed around the time of eM ClientвЂ™s update to 7.0.3x. Thus I am wondering, as eM Client does work with EAS, is the issue maybe with the implementation of that protocol on your server rather than a problem with eM Client itself? You might know if there is a difference between the product that runs on Exchange or a non-Exchange server.

Previously you said it doesnвЂ™t use EAS, now you agree it does. Thanks Richard, I guess you changed your view on.