Hi Jochen, 1) org.apache.james.mailbox.MessageManager.MetaData is the right place for the ACL's (I think). We could then make the default API to just return something meaningful.
2) I would make the store of group to user mappings an extra interface. As the mailbox api can be used without James Server. Bye, Norman Ps: Maybe server-dev@ would be better for the next steps ... -- Norman Maurer Am Donnerstag, 5. Januar 2012 um 00:10 schrieb Jochen Gazda: > Eric and Norman, > > > - the implementation of RFC4314 in imap code will be great. What about the > > management of the ACL : Made centrally by the server administrator, or via > > the user (such as for example sketched on > > http://www.kombitz.com/wp-content/uploads/2008/10/thunderbird-idle-300x269.jpg > > > > > I do not understand what exactly you mean here. > ACLs can be managed over IMAP by admin or any other user who has the > needed permissions. I see our task just to implement this server part > of IMAP. > How is the thunderbird dialog related to ACL? I see only some general > IMAP settings there. > > > - Not sure if we must limit the group management to the mailbox project or > > extend it also to the server UserRepository frontiers. > > > > > I believe both mailbox and UserRepository API need to be adapted: > > 1. Mailbox needs to store the ACLs. > Is org.apache.james.mailbox.MessageManager.MetaData the right class to > be extended with some kind of getACLs() ? > > 2. We need to pull the information from somewhere, which users belong > to which groups. That kind of information is typically stored in LDAP > or similar. For me, UserRepository is a natural candidate for hosting > group listing methods and methods for querying group memberships. What > is your opinion? > > Best, > > Gazda > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > (mailto:[email protected]) > For additional commands, e-mail: [email protected] > (mailto:[email protected]) > >
