[Kolab-devel] Thoughts about an optional alternative to Guam

[Tobias Brunner]

Hi everyone,

> I personally think that Guam is too complicated for the home user.
> It might have its place in an enterprise, with paid subscription and
> support from Kolab Systems.
> But for the open source user that just wants to manage his family
> email, it is overkill.
> Too many dependancies on Erlang and such. A new language that is not mainstream.
> If it breaks, can I fix it myself?

We're using Guam in our commercial Hosted Kolab offering and I must say
it's not only too complicated, it also gives us headaches regarding
debugging, configuration, compatibility with SSL stuff, etc.
At the end, Erlang is - IMHO - not the best decission made here. It
makes Guam a "beast" in terms of installation (dependencies),
configuration (file format) and debugging (logs). It's just not ops
friendly...

Looking at the many Kolab components, they are mostly written in Python,
PHP and some C code. Why use another language? Therefore I'm also not
that happy with the idea of having the IMAP proxy implemented in NodeJS
either (https://github.com/thomascube/imaproxy.js).

I agree that we need something like Guam, or the Groupware folder
filtering should be part of Cyrus, but that seems not so easy to
implement I hear...

Cheers,
Tobias

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 825 bytes
Desc: OpenPGP digital signature
URL: <http://lists.kolab.org/pipermail/devel/attachments/20161031/021861cb/attachment.sig>