[Kolab-devel] Is IMAP still the right choice?

Georg C. F. Greve greve at kolabsys.com
Wed Nov 30 13:58:30 CET 2011

On Wednesday 30 November 2011 12.32:22 Jeroen van Meeuwen wrote:
> I think there may be one exception,  Exchange 2010 EWS ;-)

Okay, I stand corrected. ;)

Although I *could* try to weasel out saying "I said _virtually_ every..." ;)

> I can give you the most complex LDAP ACL to use in a Cyrus IMAP ACE and
> it'll all be dandy to the user. It's called dynamic groups.

That is of course true.

But then the difference to the user of having the admin set up a group to which 
then objects can be assigned, or doing that assignment through the location in 
which you store something, e.g. "Calendar/WorkingGroup" is one of usability 
more than efficiency.

And unless you wanted to store the entire groupware payload in LDAP, which I 
am sure noone is advocating, it would mean we'd then have to implement our own 
ACL control mechanism based on that.

The chance of us making a mistake there that does not get detected quickly 
enough seems much higher than the chance of such a mistake in Cyrus having 
gone undetected for a very long time.

So using the IMAP folder concept for this allows us to rely upon the ACL 
control of Cyrus, which is a good thing, imho.

Best regards,

Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Zürich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20111130/19982c3c/attachment.sig>

More information about the devel mailing list