[Dovecot] RC15 problems with dovecot-shared and umask distilled
I recently posted about problems I've been having with dovecot-shared and umask in RC15 (using Solaris 9). I've now been able to distill what I'm experiencing into these two separate points:
dovecot-uidlist and message files never inherit the dovecot-shared group
With umask=0007 these files are created with mode 600 instead of 660: dovecot-uidlist, dovecot.index, dovecot.index.log, messages files (cur,tmp,new and the parent directory *are* created 770)
(With regard to #1, I originally posted that individual message files were also not inheriting *permissions* from dovecot-shared, but that turned out to be a case of copying a message with maildir_copy_with_hardlinks = yes.)
I can duplicate this consistently; can anyone else? Or has this been fixed in RC16/17?
Thanks, Glenn
On Wed, 2007-01-10 at 16:56 -0500, Glenn Leavell wrote:
- With umask=0007 these files are created with mode 600 instead of 660: dovecot-uidlist, dovecot.index, dovecot.index.log, messages files (cur,tmp,new and the parent directory *are* created 770)
The reason why umask doesn't work correctly is because I've avoided adding code that creates everything with permissions 0666 or 0777. I'm not really sure if I just should do it, or if I should figure out something else. In any case I'd rather not do anything about this to v1.0.
Why do you want to change the umask?
On Thu, Jan 18, 2007 at 07:38:09PM +0200, Timo Sirainen wrote:
On Wed, 2007-01-10 at 16:56 -0500, Glenn Leavell wrote:
- With umask=0007 these files are created with mode 600 instead of 660: dovecot-uidlist, dovecot.index, dovecot.index.log, messages files (cur,tmp,new and the parent directory *are* created 770)
The reason why umask doesn't work correctly is because I've avoided adding code that creates everything with permissions 0666 or 0777. I'm not really sure if I just should do it, or if I should figure out something else. In any case I'd rather not do anything about this to v1.0.
Why do you want to change the umask?
I don't necessarily want to change the umask. I started playing with the umask setting in dovecot.conf when I was first trying to implement shared folders, and some of the things I was experiencing with the use of the dovecot-shared file seemed odd (at the time). So, I decided to play with the umask setting to see how it works and to find out how it affects the use of dovecot-shared.
I now think dovecot-shared completely meets my needs for shared folders (especially with your recent group fix; thanks!), but I reported the behavior above because I wasn't sure if the umask setting was doing what you intended it to do. What's its purpose? In a Maildir environment, it seems to control the permissions of a Maildir directory structure, but not the dovecot-specific files. Is that right?
Thanks very much, Glenn
-- Glenn Leavell glenn@usg.edu Office of Information and Instructional Technology Board of Regents of the University System of Georgia
On 18.1.2007, at 23.47, Glenn Leavell wrote:
I now think dovecot-shared completely meets my needs for shared
folders (especially with your recent group fix; thanks!), but I reported the behavior above because I wasn't sure if the umask setting was doing
what you intended it to do. What's its purpose? In a Maildir
environment, it seems to control the permissions of a Maildir directory structure,
but not the dovecot-specific files. Is that right?
It doesn't really have any thought out purpose. Probably the whole
setting shouldn't even exist. :) I guess I should mark it that way in
dovecot.conf, or even remove it completely..
I did have some vague ideas that it should control the permissions of
all the files created by imap/pop3 processes. But that's not how it
currently works. Maybe some day in future.
participants (2)
-
Glenn Leavell
-
Timo Sirainen