Ladies & Gentlemen, in the meantime I could gather some more observations concerning James ACLs and shared folders. All of them are bad news for me. Please correct me if I am wrong:
1. There is no IMAP ACL support in James: parsers for GETACL, SETACL, DELETEACL, LISTRIGHTS and MYRIGHTS in org.apache.james.imap.decode.parser.ImapParserFactory are commented out. Perhaps they used to exist some time ago but not in the current trunk. 2. There is no notion of group in org.apache.james.user.api.UsersRepository or org.apache.james.user.api.model.User 3. There are https://issues.apache.org/jira/browse/IMAP-76 saying that there were no shared folders and https://issues.apache.org/jira/browse/IMAP-80 saying that shared namespace support was added to MailboxSession but the org.apache.james.mailbox.store.SimpleMailboxSession.sharedSpaces field is initialized with an empty ArrayList and not a single element is added to it anywhere in the code. My conclusion is that there are no ACLs, no shared folders and no groups in James. Are there any plans to support any of them? Thanks in advance, Gazda On Wed, Jan 4, 2012 at 10:55 AM, Jochen Gazda <[email protected]> wrote: > Ladies & Gentlemen, > > googling for "Apache James" combined with "ACL" or "permissions" does > not bring anything relevant and querying the similar in james java > sources ditto. > > I guess Apache James 3 just does not support IMAP ACLs, does it? > > Is there another way how to achieve similar results? I.e. that each > user and noone else can access can read/write his own inbox and that > there are some group folders accessible to the group members? > > Thanks in advance, > > Gazda --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
