- Edited
EWS was not "promised" - it was on the roadmap and still is (https://docs.grommunio.com/admin/roadmap.html). Please also take note of the following remark, available since our first roadmap released: https://docs.grommunio.com/admin/roadmap.html#disclaimer
While development has made large steps, the decision has been made that we're not releasing the EWS module to the public (yet). For the full EWS protocol stack to work, 124 SOAP calls need to work well under a variety of scenarios. Unfortunately, tests have revealed that various EWS implementations (clients) are not "clean" and are not following the WSDL specification strictly. grommunio is on track to deliver EWS, week by week, but grommunio is not releasing something with a potential to damage data if used incorrectly and/or not following specifications.
For your consideration, our (highly efficient) EWS contructor code is already 342.910 lines and 16MB in source code alone. Please note that it is incomparibly "easier" to write EWS clients compared to an EWS server service:
wc ewsC.cpp
342910 1254322 16086615 ewsC.cpp
Two final remarks:
- As any organization or company, we prioritize the development based on the feedback, sales and market demand. The reality shows, that EWS has not had the expected priority from the market, the community and the customers, not even in hyperscale installations.
- If you follow the release notes, you will see many other things that have not been previously anounced where the market demand partially has been up to overwhelming, from multi-server API integration to Office, ....
grommunio strives to deliver the best experience, however our understanding "the best" does not include delivering "fast with serious risks" involved. Thanks for your understanding.