dovecot - May 2006 - public folders aren't public

I'm testing dovecot as a replacement for an aging UW-IMAP server.  I 
have the basic IMAP setup working but I'm stuck on public folders (which 
my users are addicted to). I set up public folders generally a described 
in the wiki. The problem is that when a user creates a new public 
folder, the folder is owned by the user with permissions drwx------ 
which prevents other users from viewing the contents.

Here is part of dovecot.conf:

namespace public {
   separator = /
   prefix = Public/
   location = maildir:/home/public/Maildir
}

and here is the Maildir directory

[root at tesla Maildir]# ls -la
total 70k
drwxrwxrwx 7 dovecot Everyone 4.1k May 12 14:33 ./
drwxrwxrwx 3 root    root     4.1k May 12 13:43 ../
drwxrwS--- 2 dovecot Everyone 4.1k May 12 13:48 cur/
drwx------ 5 david   Everyone 4.1k May 12 14:33 .davi/
-rw-rw-r-- 1 dovecot Everyone    0 May 12 13:46 dovecot-shared
drwxrwS--- 2 dovecot Everyone 4.1k May 12 13:48 new/
-rw------- 1 mark    Everyone    6 May 12 14:07 subscriptions
drwxrwS--- 2 dovecot Everyone 4.1k May 12 13:48 tmp/
drwx------ 5 mark    Everyone 4.1k May 12 14:30 .tryit/

The directories .davi/ and .tryit/ were created by users david and mark 
respectively.

These are real system users.  They are both members of the Everyone group.

Any suggestions appreciated.  Thanks,
Mark

Mark Nienberg wrote:
> I'm testing dovecot as a replacement for an aging UW-IMAP server.  I 
> have the basic IMAP setup working but I'm stuck on public folders
(which
> my users are addicted to). I set up public folders generally a described 
> in the wiki. The problem is that when a user creates a new public 
> folder, the folder is owned by the user with permissions drwx------ 
> which prevents other users from viewing the contents.
Further testing shows that "umask = 0007"  can be used to fix this. 
I'm
surprised that it is a global setting.  I would have thought that you 
would want a different umask for private and public mailboxes. This 
makes the messages in a user's home directories readable and writeable 
by members of the group.  But I guess they don't really have access to 
the directory in the first place.  Or am I doing something wrong here?

Mark