Timo Sirainen wrote:
If you think there's still something I should have replied to, please re-send it because I've either missed it or just skipped it for some reason. (Except there are still a couple of mails from this week I've yet to reply to.)
beta 9 still has a permissions problem when a user creates a new folder in a public namespace. The file dovecot-shared is used to assign permissions and ownership for new files, but not for new directories.
In the example below, the public directory .myTest was created by user mark. Other users cannot read it. All users are in the group Everyone. These are real system users.
[root@tesla Maildir]# ls -la /home/public/Maildir/ total 103k drwxrws--- 11 dovecot Everyone 4.1k Jun 20 11:17 ./ drwxrwxrwx 3 root root 4.1k Jun 7 09:15 ../ drwxrws--- 2 dovecot Everyone 13k May 24 14:43 cur/ -rw-rw---- 1 dovecot Everyone 0 May 12 13:46 dovecot-shared drwx--S--- 5 mark Everyone 4.1k Jun 20 11:17 .myTest/ drwxrws--- 2 dovecot Everyone 4.1k May 24 14:44 new/ drwxrws--- 2 dovecot Everyone 4.1k May 19 17:48 tmp/
Note that a message moved into the .myTest directory has correct permissions
[root@tesla Maildir]# ls -la /home/public/Maildir/.myTest/cur/ total 259k drwx--S--- 2 mark Everyone 4.1k Jun 20 11:19 ./ drwx--S--- 5 mark Everyone 4.1k Jun 20 11:17 ../ -rw-rw---- 1 mark Everyone 234k Jun 16 04:02 11508.P2Q3.my.example.com:2,S
Workaround is to set umask=0007 in dovecot.conf, but this gives loose permissions on private mailboxes.
Mark