I can see it from both points of view - it's there and works (apparently - although I can't make it do so), so the documentation reflects the current usage. But I've also spent quite a while banging my head against a component that doesn't have any meaningful documentation without consulting the Internet Archive to access openchange.org. That should have been a red-flag I suppose, but the active github repository in Zentyal (which is the build pulled in from the Inverse installation process) would seem to indicate that it's possibly hanging on.
What would be good is a bigger picture road-map (beyond that of bug fixes) of where things are moving to, so that any contributions I/we can make will take things forward along a productive path, rather than down a cul-de-sac. If the openchange component is to go, and EAS is to be the Outlook-compatible tool of choice, then I'm assuming that all the EWS features ( https://msdn.microsoft.com/en-us/library/office/dn144954(v=exchg.140).aspx ) will be lost? -Craig -----Original Message----- On 2017-03-29 5:05 PM, Gordon Messmer ([email protected]) wrote: > I'm afraid I don't understand. Why would people want to test and > contribute to OpenChange if those contributions are going to be > removed from SOGo "soon"? If contributions are interesting and overcome limitations, why would we remove support? I wrote "it is likely" - I didn't write "it will". -- Ludovic Marcotte [email protected] :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence (http://packetfence.org) and Fingerbank (http://fingerbank.org) -- [email protected] https://inverse.ca/sogo/lists
smime.p7s
Description: S/MIME cryptographic signature
