[Kroupware] Web interface frontend

[Andreas Jellinghaus]

there is that imap data:
 - list of mailboxes
 - access control lists: who can access this.

you create and change this data usualy with the imap protocol
(the commands are specified in the rfc).

so any configuration tool will need to:
 - speak ldap to create the user in ldap
 - speak imap to create an inbox for that user and give him access 
   to shared folders as necessary

but you want to do everything in ldap.
so you could try:
 - move that configuration into ldap.
 - extract it from ldap and deliver the information to imap.

but at the same time:
user a changes a configuration on shared.something in ldap
user b changes a configuration on shared.something directly with imap
(any client can implement the getact/setacl commands, bynaric did,
others have an incomplete implementation)

so how are you going to merge these two changes.
if you simply export ldap to imap, you will maybe miss the change user b
did or undo it etc. 

the easiest way is not to do everything with ldap, but use three
protocols: ldap, imap and sieve.

there are nice libraries to speak it, so it's not difficult to speak
all three at the same time. even if there was no library: the protocols
are easy: normal text line messages like "LOGIN username password"
and stuff like that.

but if you truly want to manage everything in ldap, including creation
of mailboxes and management of access control lists on mailboxes,
you might have a lot of work integrating that into cyrus.

andreas