Hi all,

On vie, 2016-01-29 at 16:53 -0500, Ludovic Marcotte wrote:
> On 2016-01-29 16:12, Chris Coleman wrote:
> > A couple of questions about Inverse, SOGo, Zentyl, and OpenChange....
> >
> > 1. How active is the collaboration between Inverse and Zentyal to fix 
> > bugs, add features, and improve performance of OpenChange and its 
> > implementation of Microsoft's Exchange ActiveSync (EAS) and Exchange 
> > Web Services (EWS) ?
> >
> > I ask because there are some bugs in OpenChange having to do with EAS, 
> > which prevent SOGo's OpenChange ActiveSync features from working as a 
> > full replacement for Exchange server.   Outlook users see some missing 
> > features, some performance problems and some bugs.
> You're mixing a few things here. There's no such thing as OpenChange EAS.
> 
> OpenChange implements the native Exchange protocol (Outlook Anyway is 
> the Exchange protocol over HTTP). OpenChange is pretty much maintained 
> by Zentyal. SOGo provides a backed for OpenChange, so we can link both 
> solutions together.
> 
> The EAS code in SOGo does not require OpenChange at all.

That's true. OpenChange manages natively MAPI RPC, MAPI RPC/Proxy
(Outlook Anywhere) and some EWS (Exchange Web Services) services.

> > 2. Also, what's the roadmap or status on implementing Exchange Web 
> > Services as discussed on the zentyal openchange github repo?
> > https://github.com/openchange/openchange/issues/314
> Ask the OpenChange team.

This has nothing to do with EWS, it is the implementation of the client
MAPI libraries to support to connect openchangeclient CLI tool to an
Exchange 2013 using RPC/Proxy protocol.

> > Many say EWS is a better bet than EAS and much less trouble to debug 
> > than the popular yet arcane and overly complicated EAS.
> EWS isn't better than EAS - those are completely different beasts. EAS 
> is mainly for mobile devices and Outlook 2013. EAS is a protocol 
> oriented towards synchronization of _personal data_.
> > Also.... Outlook 2013 and newer use EWS to talk to exchange server so 
> > this EWS code would be a smart addition to OpenChange and SOGo.
> Outlook 2013 supports the Exchange protocol and EAS. It does not support 
> EWS.

EWS is the mean of communication between Outlook for MAC and Exchange.
It is a beast not managed by now for OpenChange.

Some EWS services are managed by OpenChange server such as
Out-of-office, Availability service (Free/Busy) and Autodiscover. This
is the minimum set for Outlook to work against a RPC server.

Thank you for your interest.

Best regards,
-- 
Enrique J. Hernández - Lead Developer

Zentyal - Active Exchange
www.zentyal.com


-- 
[email protected]
https://inverse.ca/sogo/lists

Reply via email to