On Wed, 2006-08-09 at 10:29 -0700, Aaron Stone wrote: > On Wed, 2006-08-09 at 18:54 +0200, [EMAIL PROTECTED] wrote: > > Moving this onto the mailing list, because we need some open discussion > and thinking about how to handle this situation: > > > Previously no hierarchical permissions checking was done when creating a > > new mailbox. Now we check to make sure that we have permission to create a > > folder below the parent folder. Your configuration sets all folders to > > read-only -- so they are no longer permitted to have sub-folders created > > within them... > > > > On the one hand, a read-only folder is read-only -- 2.1.7 closes a bug > > where one could create a new folder below a read-only folder... on the > > other hand, it breaks your very useful read-only archive system. > > > > Let's think about a permissions-oriented workaround.
Would something as straightforward as allowing command-line specified mailboxes to be created and delivered regardless of permissions appeal to folks? The infrastructure to know who specified the mailbox has been there for a while, and perhaps this is an additional case to use it for. Aaron
