[Dovecot] Public folders / namespace documentation
Does Dovecot support public folders?
I thought it may do via namespaces, but having searched the Wiki and the documentation, I can't find how namespaces are defined.
I've probably not looked in the right place - any pointers?
Thanks, Keith
On 27.9.2004, at 14:06, Keith Edmunds wrote:
Does Dovecot support public folders?
I thought it may do via namespaces, but having searched the Wiki and the documentation, I can't find how namespaces are defined.
Hmm. Yes, I suppose that would be possible nowadays with maildir. With mbox the problem is that if you're using multiple UIDs for users the index file permissions get set wrong. Unless you store indexes separately for each user.
namespace public { separator = . prefix = Public. location = maildir:/var/mail/public }
You'll also need to create dovecot-shared file there with permissions and GID you want to use for created indexes and mails.
Anyone have thoughts how to do this best with mboxes?
On Mon, Sep 27, 2004 at 02:43:45PM +0300, Timo Sirainen wrote:
On 27.9.2004, at 14:06, Keith Edmunds wrote:
Does Dovecot support public folders?
I thought it may do via namespaces, but having searched the Wiki and the documentation, I can't find how namespaces are defined.
Hmm. Yes, I suppose that would be possible nowadays with maildir. With mbox the problem is that if you're using multiple UIDs for users the index file permissions get set wrong. Unless you store indexes separately for each user.
namespace public { separator = . prefix = Public. location = maildir:/var/mail/public }
You'll also need to create dovecot-shared file there with permissions and GID you want to use for created indexes and mails.
Anyone have thoughts how to do this best with mboxes?
Personally I think the effort to implement such a thing would be better spent on improving the existing shared folders. Does anyone really need to do shared folders in mbox nowadays? (don't want to sound rude, if anyone does please speak up)
What I'd like to see would be fine grained permission management for the existing shared folders, so one can grant read/write/delete/etc. privileges separately to individual users. The 'dovecot-shared' file could serve as configuration file here. I imagine a simple format like:
user1 RWDC user2 RW default R
User1 would be allowed to read/write/delete/create-subdir, user2 may read/write and default would be read-only.
Just an idea and my 2c :-)
best regards
moe
--On Sunday, October 03, 2004 7:59 PM +0200 Moe Wibble t1lt@bk.ru wrote:
Personally I think the effort to implement such a thing would be better spent on improving the existing shared folders. Does anyone really need to do shared folders in mbox nowadays? (don't want to sound rude, if anyone does please speak up)
Public read-only folders using mbox would be handy for mailing list archives. Esp. if it could use gzipped mbox. I could then put a link to my Mailman archives for IMAP access.
On Sun, Oct 03, 2004 at 11:46:49AM -0700, Kenneth Porter wrote:
--On Sunday, October 03, 2004 7:59 PM +0200 Moe Wibble t1lt@bk.ru wrote:
Personally I think the effort to implement such a thing would be better spent on improving the existing shared folders. Does anyone really need to do shared folders in mbox nowadays? (don't want to sound rude, if anyone does please speak up)
Public read-only folders using mbox would be handy for mailing list archives. Esp. if it could use gzipped mbox. I could then put a link to my Mailman archives for IMAP access.
I'm not sure but I would guess that read-only shared mbox shouldn't be a big problem. Might be mistaken, tho.
On 3.10.2004, at 20:59, Moe Wibble wrote:
What I'd like to see would be fine grained permission management for the existing shared folders, so one can grant read/write/delete/etc. privileges separately to individual users. The 'dovecot-shared' file could serve as configuration file here. I imagine a simple format like:
This is pretty much related to ACLs, and I think I should add support for different kinds of ACLs when I do it. Normal UNIX permissions, Posix ACLs and yes, dovecot-shared file ACLs. It needs some nice ACL API with different implementations and ways to layer them on top of each others so that operating system could force some checks and dovecot-shared file could make them more fine grained.
Anyway, it's all post v1.0 stuff to me.
On Sun, Oct 03, 2004 at 11:38:27PM +0300, Timo Sirainen wrote:
On 3.10.2004, at 20:59, Moe Wibble wrote:
What I'd like to see would be fine grained permission management for the existing shared folders, so one can grant read/write/delete/etc. privileges separately to individual users. The 'dovecot-shared' file could serve as configuration file here. I imagine a simple format like:
This is pretty much related to ACLs, and I think I should add support for different kinds of ACLs when I do it. Normal UNIX permissions, Posix ACLs and yes, dovecot-shared file ACLs. It needs some nice ACL API with different implementations and ways to layer them on top of each others so that operating system could force some checks and dovecot-shared file could make them more fine grained.
Yup, be sure to KISS, tho.
Anyway, it's all post v1.0 stuff to me.
Makes sense. Dovecot should be rock-stable before that stuff comes in because many consider it an enabling feat. for commercial deployment. You don't want to leave a bad first impression on all those PHBs. ;)
For my own use I'm glad that r/w shared folders are finally doable 'cause that's all I need right now. Thanks for that.
participants (4)
-
Keith Edmunds
-
Kenneth Porter
-
Moe Wibble
-
Timo Sirainen