As I’ve mentioned before, I mainly run my Neth box for my family. When I reasonably can, I like to give options. So there are five packages for Neth that do webmail: Roundcube, Rainloop, Horde, WebTop, and Sogo. Right now I have Roundcube and Horde installed, and will probably play with Rainloop shortly. I’d be glad to go ahead and install Sogo and WebTop as well, but I see that they both do ActiveSync. Is there going to be any conflict between these? Or can I have them both installed without causing any problems? Any gotchas I should be aware of?
I’m not personally interested in ActiveSync at all, as long as the one system doesn’t break the other. I guess I’ll try it with the defaults, and if something starts to look broken, probably disable ActiveSync in both apps.
BTW, there’s a bug on the WebTop doc page in the section where it tells you how to configure Google and Dropbox integration. It says (in two places) to run
Does that mean it isn’t production-ready? Or only that I won’t get it (without manually enabling the nethforge repo) if I have a subscription on my server?
Sogo treats (e-smith props) ActiveSync and Dav in the same manner.
IMHO it’s a nice feature be able to remove all rewrite rules to (what-ever) web-service; Just a matter of preference: close the most in front possible door.
Define “(not) production-ready”
I am running SOGo for about half year now on NethServer. (before that I ran SOGO2.x on Linuxschools) and it hasn’t failed me yet.
Although I must say, I barely use the web interface. Most use of my mailserver is through Thunderbird.
I am currently using sogo on a production environment, before setting up the environment I had staging environment for a bout two weeks, sogo and webtop did not do so well, I have multiple conflicts, which in some cases caused me to have to re-build the whole installation. so I would not install the two at the same time, if you have had luck let me know, I try again on one of my staging servers.
as promised, I tried rebuilding the server and replicating the steps that I followed initially to see the erro, but its seems like there is an update that fixed the error.
Initially, I had tried more than three times with the same error.