Hello again. If SOGo is uninstalled using yum remove sogo, the log file (/var/log/sogo/sogo.log) is not properly removed and has invalid permissions. As a result, if re installed, sogod won’t properly start until it’s deleted.
Just FYI
SOGo RPMs are quite bugged.
If you think this is a bug, please report upstream 
Indeed. Turns out that even after deleting the log, SOGo calendars couldn’t be hosted/shared properly anymore.
So basically, NEVER uninstall SOGo if you want it to continue to work properly. 
IMHO, uninstalling and reinstalling a SW is a bad habit that comes form windoze…
if you install anuithing and you have issues, try to diagnose and solve them… if you don’t want to use it anymore, just disable it, but don’t uninstall it…
in this way:
- every kind of data generated/stored by/in that sw won’t be erased/losted
- you can just re-enable it an use it again if you need it
Ok fair enough, but is enough to just disable it when switching to say, WebTop for example? To quote the documentation:
“WebTop and SOGo can’t be installed on the same machine.
Before installing WebTop, make sure SOGo is not present.”
I don’t know… usually I don’t play / make tests on a production server, so, if I were in your shoes, I’d play with more than a virtual machine 
Haha. Touche. 