Thanks for the update. I see the following alternatives for the ones having the same problem (If you could confirm them or make a suggestion it will be appreciate it):
1. Wait for the upcoming release - ETA 19-jan-2015 2. Have the Apache and the Proxy component running on a supported distribution (CentOS for instance) 3. Have the complete solution running on a supported distribution (again assuming CentOS is supported) Do you have an roadmap of releases for the upcoming weeks that could help us to decide, if we should wait for a specific release This due I notice that quite some updates have been made this last weeks, http://sourceforge.net/projects/sogo-zeg/files/ and the product is certainly active, -----Original Message----- From: users-requ...@sogo.nu [mailto:users-requ...@sogo.nu] On Behalf Of Ludovic Marcotte Sent: jueves, 08 de enero de 2015 2:43 p. m. To: users@sogo.nu Subject: Re: [SOGo] SOGO 2.2.13 - openchange-rpcproxy - Outlook On 07/01/2015 12:30, Walter Barrios | Tible wrote: > Based on this information: > > RPC encapsulated in HTTP - This is native Microsoft Exchange protocol > used for "Outlook Anywhere" provided by (currently missing) > openchange-rpcproxy > Source:https://lists.inverse.ca/sogo/arc/users/2015-01/msg00041.html > > There is an alternative to have an environment on Ubuntu 14.04 and have > Outlook 2013 clients connected to the emails. Yes, install sogo-activesync and use the EAS protocol. > > We are using the ZEG-2.2.13-vmware.vmdk machine, set it up with a valid > domain on https, but does not seem to work. rpc-proxy is not yet available on Debian/Ubuntu. Hopefully, it'll be available next week in v2.2.14. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
