Hi,
"rough edges" is a real underestimating term ;)
Here is what came out after a long evaluation and polishing the rough edges.
What was positive:
- It is possible to share AD with a real Windows DC, as long it is 2008
and Samba is a DC (making it everything a bit more complicated). Member
server does not work.
- Autodiscover does work with Outlook and different DNs than the
defaults for users, if you change the hard coded DNs in the python
autodiscover scripts.
- Simple addressbook and calendar stuff for Outlook works.
- Out of office function for Outlook works (but only for external
contacts, as there is no support in SOGo for internal contacts).
What was negative:
- Multiple personal addressbook in Outlook do not work properly.
- If automatic email completion does not work, start from scratch for
the user.
- Outlook stops syncing out of nowhere.
- Outlook crashs for no apparent reason. If it crashs directly after
launch, start from scratch for the user.
- Outlook in a non-english language seems even more unstable.
- Automatic Inbox notification does not work (even after self-compiling
and installing the dovecot plugin. The documentation here is sparse).
- You are never sure, that everthing from Outlook is in sync with the
server.
- Some Outlook problems where only solvable by clearing the SOGo cache
or even worse by recreating the user on the server site. A new Outlook
profile was in most cases not enough.
- Migration from existing user data triggered some obscure behaviour.
- SOGo develops the backend and Zentyl develops OpenChange.
So if you can go with Outlook 2013 and EAS. Avoid OpenChange or plan a
long evaluation phase to catch all problems.
Regards,
Johannes
Am 11.03.16 um 13:08 schrieb Quique:
Hello Martin,
With OpenChange, you will have support from Outlook 2003 to Outlook
2010. There are users in production with OpenChange. There are rough
edges but for a normal usage it will work.
Best,
On 10 March 2016 at 18:20, Martin Simovic <[email protected]
<mailto:[email protected]>> wrote:
Hi Steve,
You are right - my suggestion does not involve openchange at all.
Openchange would be certainly better option, but do you know anyone
who has *working* openchange setup? In production?
Best Regards
Martin.
On 10 Mar 2016, at 17:08, Steve Ankeny <[email protected]
<mailto:[email protected]>> wrote:
Martin . . .
Am I right in understanding your suggestion does not involve
OpenChange? Would that limit a user to Outlook 2013? It appears
to require a lot of resources to implement, and even then, there
appear to be limitations.
pg. 51-55, SOGo Installation and Configuration Guide
From my view, this is certainly preferable to using OpenChange
On 03/10/2016 10:44 AM, Martin Simovic wrote:
Hi,
I recommend you test your setup before the actual migration.
ActiveSync can be very resource demanding, especially with large
mailboxes. At the moment, every EAS connection requires a
separate sogod process, which in your case means you need 32+ GB
RAM - assuming your users use Outlook only (and not the phone,
etc.) Add one more device per user (e.g. Android phone) and
amount of required RAM duplicates.
Best Regards
Martin.
On 10 Mar 2016, at 15:36, EFEKT PAWKI
<<mailto:[email protected]>[email protected]
<mailto:[email protected]>> wrote:
Hello.
I have to migrate from Exchange 2003 to something else.
My users will kill me if I force them to switch from MS Outlook
to something else.
How Sogo behave with account with a lot of data using Active
Sync protocol?
Especially owner of company - he have 5GB of OST and 45 in PST.
Calendar is full of meettings etc...
Will Sogo be able to work fluently with such amount of data?
There will be about 100 mailboxes.
Best regards. Pawel
--
[email protected] <mailto:[email protected]>
https://inverse.ca/sogo/lists
--
[email protected] <mailto:[email protected]>
https://inverse.ca/sogo/lists
--
Quique
Wikipedia: http://es.wikipedia.org/wiki/Usuario:Sixstone
Last.fm: http://www.last.fm/user/sixstone
--
[email protected]
https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists
