search for: publicmailboxadmin

* Timo Sirainen <tss at iki.fi> 2015.09.08 12:20: > How does the PublicMailboxAdmins group get set? Looks to me like the problem is that it's not getting set to doveadm. Here's an easy way to check if that's the problem or something else: http://hg.dovecot.org/dovecot-2.2/rev/500e8dd7a389 > > If that doesn't help: Show your full doveconf -n, set auth_debug=y...

...H#0111#011PLAIN#011service=imap#011secured#011lip=188.138.0.199#011rip=80.187.102.243#011lport=143#011rport=62388#011resp=<hidden> Mar 23 10:25:45 spectre dovecot: auth: Debug: cache(tlx at leuxner.net,80.187.102.243): hit: <hidden>#011userdb_quota_rule=*:storage=5G#011userdb_acl_groups=PublicMailboxAdmins Mar 23 10:25:45 spectre dovecot: auth: Debug: client out: OK#0111#011user=tlx at leuxner.net Mar 23 10:25:45 spectre dovecot: auth: Debug: master in: REQUEST#0113958898689#0117266#0111#011bfc44f32051961b909e2b458440d645f Mar 23 10:25:45 spectre dovecot: auth: Debug: userdb-cache(tlx at leuxner.net...

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/vmai...

On 31 Dec 2014, at 23:10, Thomas Leuxner <tlx at leuxner.net> wrote: > > 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: How does the PublicMailboxAdmins group get set? Looks to me like the problem is that it's not getting set to doveadm. Here's an easy way to check if that's the problem or something else: http://hg.dovecot.org/dovecot-2.2/rev/500e8dd7a389 If that doesn't help: Show yo...

...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/6c2fdc29/attachment.bin>

Dear all, I am hoping someone can help me with a problem that I have been trying to fix for days. Using postfix and dovecot 2.0.19 on Ubuntu 12.04 with LDAP authentication and virtual users and domains. Basically I want to setup both shared and public mailboxes. The shared part is working fine, ie I can share folders successfully and other uses can see them. However when I try and create sub

On 09/08/2015 02:26 PM, Thomas Leuxner wrote: > * Timo Sirainen <tss at iki.fi> 2015.09.08 12:20: > >> How does the PublicMailboxAdmins group get set? Looks to me like the problem is that it's not getting set to doveadm. Here's an easy way to check if that's the problem or something else: http://hg.dovecot.org/dovecot-2.2/rev/500e8dd7a389 >> >> If that doesn't help: Show your full doveconf -n, set auth_...

Thomas Leuxner: > namespace { > location = virtual:~/mdbox/virtual > prefix = Virtual/ > separator = / > } > > $ cat virtual/Flagged/dovecot-virtual > * > Public/* > flagged once setup correctly it works like expected :-) > Another example, the one I used in the original reply, is 'gluing' > together archives as a single view: > > $