dovecot - Jan 2009 - dovecot-shared file

Hello Timo,

About the dovecot-shared file, the wiki says :

  "Unless you're using a single UID for all the users, you'll need
to have a
   dovecot-shared file in each shared maildir. The group and the file
permissions
   for new files inside the maildir are taken from the dovecot-shared
file."

but says the following too :

  "With Maildir dovecot-shared file controls if the \Seen flags are shared
or
   private. If you don't have the file, they're shared."

The question is "does it make sense (or is it even possible) not to have
the
file ?". Why would one not have the file and how would it work then ? By
relying on the set-gid bit and umask ?

Finally, the wiki says :

  "If you do have the file, the \Seen flag state is stored only in the
user's
  index files. By making each user have their own private index files, you can
  make the \Seen flag private for the users."

So, my undersanding is that :

  1) you have the file
    1.a) if INDEX points to the same place, flags are shared but are lost if
indexes are lost
    1.b) if INDEX points to some user dependant place, flags are private but
         are lost if indexes are lost

  2) you don't have the file
     flags are shared, whatever INDEX points to and, since they're stored in
filename, survive indexes lost.
    
     but does shared-mailboxes even work if we don't have that file ? maybe
only
     if the set-gid bit and umask does what the file would have done ?

So maybe, if you want to share flags, 2) is safer dans if you want them
private, 1.b) is the only choice ?

thanks

-- 
Thomas Hummel 	    | Institut Pasteur
<hummel at pasteur.fr> | P?le informatique - syst?mes et r?seau

On Fri, 2009-01-30 at 16:49 +0100, Thomas Hummel wrote:
> Hello Timo,
> 
> About the dovecot-shared file, the wiki says :
> 
>   "Unless you're using a single UID for all the users, you'll
need to have a
>    dovecot-shared file in each shared maildir. The group and the file
permissions
>    for new files inside the maildir are taken from the dovecot-shared
file."
> 
> but says the following too :
> 
>   "With Maildir dovecot-shared file controls if the \Seen flags are
shared or
>    private. If you don't have the file, they're shared."
> 
> The question is "does it make sense (or is it even possible) not to
have the
> file ?". Why would one not have the file and how would it work then ?
By
> relying on the set-gid bit and umask ?
Maybe. Or maybe it just wouldn't work. I haven't thought about it.
> So, my undersanding is that :
> 
>   1) you have the file
>     1.a) if INDEX points to the same place, flags are shared but are lost
if indexes are lost
>     1.b) if INDEX points to some user dependant place, flags are private
but
>          are lost if indexes are lost
> 
>   2) you don't have the file
>      flags are shared, whatever INDEX points to and, since they're
stored in filename, survive indexes lost.
Right.
    
>      but does shared-mailboxes even work if we don't have that file ?
maybe only
>      if the set-gid bit and umask does what the file would have done ?
Yes, maybe.
> So maybe, if you want to share flags, 2) is safer dans if you want them
> private, 1.b) is the only choice ?
Yes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20090206/38bb7983/attachment-0002.bin>