OK, this one is probably to blame on myself.
After reading how to check for config items in the DB I saw an Sogo entry for being an admin.
Curious what secret options would be revealed in the SOGo-webinterface, I added myself to it: config setprop sogod AdminUsers admin AdminUsers rolf
followed by signal event and sogod restart.
After that I couldn’t logon to sogo anymore. Also removing myself from that admin list, and even removing en reinstalling sogo didn’t help.
When looking in sogo.log I see a strange entry:
ROLFBAKKER is my netbios domainname, and HELIUM is the hostname of my server.
This doesn’t look right to me?
Is this related to my actions of adding myself as an sogo-admin?
And how to undo this / so I can log on normally again…
yes, you’re right.
I manually edited sogo.conf and I now can logon again.
Thanks!
So for my understanding: I didn’t actually break it myself by adding myself as admin, but because I had regenerated sogo.conf I introduced the same error as in the referenced posting?
