search for: lrwstiekxap

...th changeset 9376bf098692 a bit. Right now I'm unsure how to describe a namespace using this feature. Using something like 'Public/*" doesn't seem to work while 'Public*" does, but would also potentially alter non-related mailboxes elsewhere: $ cat global-acl INBOX owner lrwstiekxap Public* group=PublicMailboxAdmins lrwsik Regards Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20140128/6c2fd...

I have a namespace like this: namespace { type = private separator = / prefix = location = maildir:/var/ferrari/users/%d/%n:INDEX=/var/ferrari/indexes/3/4/%u:CONTROL=/var/ferrari/indexes/3/4/%u inbox = no list = yes subscriptions = yes } Where do I store "dovecot-acl" as the default ACL ? /Per Jessen, Z?rich

I have noticed a difference in the behavior of ACLs. When used in a MUA the following global ACL works fine and has the desired effect - new mailboxes can be created by a user being part of the 'PublicMailboxAdmins' group: [ global-acl: ] INBOX owner lrwstiekxap Public/* group=PublicMailboxAdmins lrwsipk Public/* anyone lr Public/* authenticated lrws Creating the same mailbox via doveadm however fails with a permission problem: doveadm(tlx at leuxner.net): Debug: acl vfile: Global ACL file: /var/vmail/conf.d/leuxner.net/global-acl doveadm(tlx at leuxner....