On Wednesday 10 January 2007 06:54, Glenn Leavell wrote:
I don't know if the following is related to the above, but I thought I'd include it here just in case. After setting umask = 0007 in dovecot.conf, dovecot-uidlist, dovecot.index, and dovecot.index.log are not created with the new mask; however, the maildir parent directory, cur, new, tmp, and the maildirfolder file *are* created with the new mask:
$ ls -l total 12 drwxrwx--- 2 glenn adm 512 Jan 10 01:37 cur/ -rw------- 1 glenn adm 44 Jan 10 01:37 dovecot-uidlist -rw------- 1 glenn adm 120 Jan 10 01:37 dovecot.index -rw------- 1 glenn adm 24 Jan 10 01:37 dovecot.index.log -rw-rw---- 1 glenn adm 0 Jan 10 01:37 maildirfolder drwxrwx--- 2 glenn adm 512 Jan 10 01:37 new/ drwxrwx--- 2 glenn adm 512 Jan 10 01:37 tmp/
I'm experimenting with using the umask setting for shared folders. In the case of sharing, won't the index files, etc. need to be readable by the sharing group as well?
I concur: the umask is not honoured when Dovecot creates a new Maildir file. This has been the case at least as far back as v0.99.14.
Doesn't this completely defeat use of shared folders? For me this bug is a problem because I want to process Maildirs with a cron process running as uid mail, but group write permission is not set on created message files.
Steve.
-- A verbal contract isn't worth the paper it's written on. -- Samuel Goldwyn