search for: lrwstie

A co-worker edited a dovecot-acl file and accidently introduced a space at the end of a "user=username lrwstie" entry. Fortunately he noticed errors in his own mail client, but I'm not sure what may have happened to other users. Would it be possible to make dovecot more forgiving by ignoring whitespace at the end of ACLS to avoid this issue? Feb 21 12:34:38 hill dovecot: IMAP(username): ACL fi...

...NBOX and some other directories in the mailbox root. I used Access Control Lists (http://wiki.dovecot.org/ACL) to do this: protocol imap { mail_plugins = acl } plugin { # With global ACLs in /etc/dovecot/acls/ directory: acl = vfile:/etc/dovecot/acls } /etc/dovecot/acls/.DEFAULT: owner lrwstie /etc/dovecot/acls/INBOX/.DEFAULT owner lrwstiekxa Actually - its not possible to create/remove directories under the mailbox root - its possible to create directories under INBOX - its NOT possible to remove directories under INBOX (This is my problem.) I tried symlinks like: /var/mail/.../INBOX...

...he creating of subfolders for some special folder for all users. Using ACL plugin for this seems to work at first glance but is not a full solution or is buggy as it allows the creation of sub-subfolders. I'm using the following ACL and namespace separator is "/": $ cat folder owner lrwstie Note: no "k" permission ("k" = create = Mailboxes can be created under this mailbox) Seems to work: a001 create "folder/subfolder" a001 NO Permission denied But: a002 create "folder/subfolder/subsubfolder" a002 OK Create completed....

First of all, I think dovecot is really fantastic and I have thanks for all the hard work. I think it will be the best fit for my ~5000 users when I have it setup completely. We normally have approx 500 concurrent IMAP connections during the day. I am trying to convert from courier-imap to dovecot, but I have an issue with public namespace folders that are not writable by certain users.