RE: [SOGo] OpenChange OCSmanager & multidomains
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 (gordon.mess...@gmail.com) 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 lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence (http://packetfence.org) and Fingerbank (http://fingerbank.org) -- users@sogo.nu https://inverse.ca/sogo/lists smime.p7s Description: S/MIME cryptographic signature
Re: [SOGo] OpenChange OCSmanager & multidomains
On 2017-03-29 5:05 PM, Gordon Messmer (gordon.mess...@gmail.com) 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 lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence (http://packetfence.org) and Fingerbank (http://fingerbank.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] OpenChange OCSmanager & multidomains
On 03/29/2017 01:53 PM, Ludovic Marcotte" (lmarco...@inverse.ca) wrote: On 2017-03-29 4:30 PM, Gordon Messmer (gordon.mess...@gmail.com) wrote: Sure, but wouldn't it save people from wasting their time with proof-of-concepts for a component that's being abandoned if the documentation were updated now? But this would allow people to test and contribute to the project if they want to. 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"? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] OpenChange OCSmanager & multidomains
On 2017-03-29 4:30 PM, Gordon Messmer (gordon.mess...@gmail.com) wrote: Sure, but wouldn't it save people from wasting their time with proof-of-concepts for a component that's being abandoned if the documentation were updated now? But this would allow people to test and contribute to the project if they want to. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence (http://packetfence.org) and Fingerbank (http://fingerbank.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] OpenChange OCSmanager & multidomains
On 03/29/2017 11:33 AM, Ludovic Marcotte" (lmarco...@inverse.ca) wrote: The documentation will be updated when the change is carried forward. Sure, but wouldn't it save people from wasting their time with proof-of-concepts for a component that's being abandoned if the documentation were updated now? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] OpenChange OCSmanager & multidomains
On 2017-03-29 1:58 PM, Gordon Messmer (gordon.mess...@gmail.com) wrote: Will the documentation be updated before that happens? https://sogo.nu/files/docs/SOGoNativeOutlookConfigurationGuide.html Removing that component seems like a major change to make "soon" given that the documentation still indicates that this is the recommended configuration. The documentation will be updated when the change is carried forward. How will existing clients react to the removal of native Exchange support? Unfortunately, OpenChange has had limitations that weren't overcome in years, so people rarely went beyond PoC stages. Will they automatically fail over to ActiveSync? No automatically, those are two different account types in Outlook. For Outlook compatibility, you can use ActiveSync if you're using Outlook 2013 or 2013, or you can use the Outlook CalDAV/CardDAV connector (https://sourceforge.net/projects/outlookcaldavsynchronizer/) I presume you mean "or 2016," right? Yes, indeed. Thanks, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence (http://packetfence.org) and Fingerbank (http://fingerbank.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] OpenChange OCSmanager & multidomains
On 03/29/2017 10:36 AM, Ludovic Marcotte" (lmarco...@inverse.ca) wrote: OpenChange is dead. Our code that plays with it is likely set to be removed soon. Will the documentation be updated before that happens? https://sogo.nu/files/docs/SOGoNativeOutlookConfigurationGuide.html Removing that component seems like a major change to make "soon" given that the documentation still indicates that this is the recommended configuration. How will existing clients react to the removal of native Exchange support? Will they automatically fail over to ActiveSync? For Outlook compatibility, you can use ActiveSync if you're using Outlook 2013 or 2013, or you can use the Outlook CalDAV/CardDAV connector (https://sourceforge.net/projects/outlookcaldavsynchronizer/) I presume you mean "or 2016," right? -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] OpenChange OCSmanager & multidomains
On 2017-03-29 12:50 PM, Craig Fisher (craig.fis...@prolateral.com) wrote: Q1. Will Openchange support multipledomains/login via LDAP and pulling information from there? OpenChange is dead. Our code that plays with it is likely set to be removed soon. Q1. If not is Openchange a requirement for Exchange ActiveSync functionality? It seems like a dead development… ☹ Our ActiveSync stack in SOGo does NOT rely in any way with OpenChange - it works on its own and is self-contained. Q2. If not – is there any documentation on what the autodiscover.xml response should look like to tell remote Outlook to use EAS instead of using OCSManager to generate it? For Outlook compatibility, you can use ActiveSync if you're using Outlook 2013 or 2013, or you can use the Outlook CalDAV/CardDAV connector (https://sourceforge.net/projects/outlookcaldavsynchronizer/) Thanks, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence (http://packetfence.org) and Fingerbank (http://fingerbank.org) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] OpenChange OCSmanager & multidomains
Folks, Hi I’ve got SOGO working fine with multiple domains, separated into different OUs in my LDAP (Samba4). I’m using the email address as the login name – which works well for Sogo/dovecot/postfix logins. However – I don’t seem to be able to get OCSManager to authenticate my autodiscover.xml properly. It comes up with an HTTP-AUTH box which seems to connect and work using LDAP correctly initially, but once it gets into the ‘pulling information out of Samba’ part to generate the autodiscover response, the Samba NTLM searches fail as they are searching for the email address. There doesn’t seem to be any documentation for Openchange *anywhere*, beyond the example setup in the SOGo docs. Q1. Will Openchange support multipledomains/login via LDAP and pulling information from there? Q1. If not is Openchange a requirement for Exchange ActiveSync functionality? It seems like a dead development… ☹ Q2. If not – is there any documentation on what the autodiscover.xml response should look like to tell remote Outlook to use EAS instead of using OCSManager to generate it? May thanks in advance… -Craig smime.p7s Description: S/MIME cryptographic signature
