Stuart Rowan
2009-Jun-25 11:07 UTC
[Dovecot] dovecot-acl-list not honouring owner / permissions that are set on dovecot-shared
Hi, I've just upgraded our dovecot installation from 1.0.15 to 1.1.13. This went smoothly and just worked -- thank you very much for writing such a high performance and robust piece of software. However, we have a shared mailbox that people can subscribe to. After upgrading to 1.1.13 ... dovecot tries to create a dovecot-acl-list file in the top level of this ... but it creates it chown'd to the first logged in user with a umask of -rw- --- --- A. -rw------- 1 userA shared 17179 2009-06-25 11:10 /home/imapshared/SharedMaildir/dovecot-acl-list Everyone else who tried to access the shared folder (and hence dovecot tried to read / update the dovecot-acl-list file) caused an error to be logged to the error.log I changed the permissions (once I realised what had gone wrong) to match those on the dovecot-shared file and all was well as everyone can now read/update it. B. -rw-rw---- 1 imapshared shared 17179 2009-06-25 11:19 /home/imapshared/SharedMaildir/dovecot-acl-list -rw-rw---- 1 imapshared shared 0 2008-04-25 13:20 /home/imapshared/SharedMaildir/dovecot-shared Also from time to time the permissions seem to get changed back on dovecot-acl-list inexplicably to those in situation A -- usually following a restart of dovecot but I haven't been able to reproduce this reliably. This seems like a bug to me ... do you agree / is there a sensible work-around? The declaration in dovecot.conf for the shared namespace sets user specific CONTROL and INDEX locations so that users can independently subscribe to folders and mark messages as read on an individual basis. Many thanks, Stu.
Timo Sirainen
2009-Jun-25 17:03 UTC
[Dovecot] dovecot-acl-list not honouring owner / permissions that are set on dovecot-shared
On Thu, 2009-06-25 at 12:07 +0100, Stuart Rowan wrote:> However, we have a shared mailbox that people can subscribe to. After > upgrading to 1.1.13 ... dovecot tries to create a dovecot-acl-list file in > the top level of this ... but it creates it chown'd to the first logged in > user with a umask of -rw- --- --- > > A. > -rw------- 1 userA shared 17179 2009-06-25 11:10 > /home/imapshared/SharedMaildir/dovecot-acl-listSee if setting umask = 0007 to dovecot.conf helps? With v1.2+ this is no longer necessary. -------------- 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/20090625/f9c713cd/attachment-0002.bin>
Stuart Rowan
2009-Jun-25 18:01 UTC
[Dovecot] dovecot-acl-list not honouring owner / permissions that are set on dovecot-shared
Timo Sirainen wrote:> On Thu, 2009-06-25 at 12:07 +0100, Stuart Rowan wrote: >> However, we have a shared mailbox that people can subscribe to. After >> upgrading to 1.1.13 ... dovecot tries to create a dovecot-acl-list file in >> the top level of this ... but it creates it chown'd to the first logged in >> user with a umask of -rw- --- --- >> >> A. >> -rw------- 1 userA shared 17179 2009-06-25 11:10 >> /home/imapshared/SharedMaildir/dovecot-acl-list > > See if setting umask = 0007 to dovecot.conf helps? With v1.2+ this is no > longer necessary. >Well that problem has not reoccurred yet today but I've made the change you suggest anyway. Now we're on to: dovecot: 2009-06-25 18:50:15 Error: IMAP(strr): fchown() failed with file /home/local/strr/Maildir/index/Archive/.junk/dovecot.index.log: Operation not permitted dovecot: 2009-06-25 18:54:15 Error: IMAP(strr): fchown() failed with file /home/local/strr/Maildir/index/Archive/.junk/dovecot.index.log: Operation not permitted Bizarrely the similarly placed .junk-2008 folder has no problems creating the 'strr' specific index files. I've tried deleting the folders / files and chowning/chmodding until I'm blue in the face and since the umask change they are now created with a umask of 0007 ... but the error keeps coming back in the logs. Let me know if you need more information Cheers, Stu.