Securing Kolab 16 on Centos 7 howto questions - plus GUAM is broken

[Timotheus Pokorra]

Resending to the list because I realised that I only sent it to the OP...

Hello Josh,

> Any guam developers on this list?
There are only 2 guam developers, Aaron and Jeroen, according to the
commit logs: https://cgit.kolab.org/guam/log/

> It appears that guam completely ignores chained certificates, e.g. free ones obtained from startssl.com, mentioned in a secure-kolab-server.html HOWTO
I have not played with guam yet.
There have been discussions on this mailinglist before, or somewhere
else? I cannot find the ones I think I can remember.

see http://lists.kolab.org/pipermail/users/2016-February/020545.html
see also https://git.kolab.org/T1065
see also https://docs.kolab.org/about/guam/configuration.html

> Could I just remove guam and change imaps from 9993 to 993? What does guam do?
Quoting from https://kolab.org/group-blog/2016/01/31/kolab-16-at-fosdem16/
"Take for example GUAM, our all-new, totally original, "IMAP-protocol
firewall". Guam allows you to, for example, access Kolab from any
client without having to see the special Kolab groupware folders, such
as calendars, todos, contacts, and so on. As Guam is configured
server-side, users do not have to do anything special on their
clients."

Hope this helps,
  Timotheus