[Dovecot] lazy-expunge acl bug?
Martin Ott
martin.ott at itk-engineering.de
Fri Jun 11 18:40:30 EEST 2010
Am 11.06.2010 17:31, schrieb Timo Sirainen:
> On pe, 2010-06-11 at 17:23 +0200, Martin Ott wrote:
>>> Maybe lazy_expunge_public setting that's equivalent to lazy_expunge
>>> setting, except is used for public namespaces. But ACLs could make it
>>> problematic..
>>
>> Maybe ACLs could be copied to the expunged folder.
>
> ACLs could change, so I don't think copying is ok. Adding some logic to
> always use the original one's ACLs would be better, but I don't know how
> difficult that would be to implement.
>
>> There could also be an
>> option whether the expunged folder inherits the original ACsL or if a global
>> ACL should be applied, such that e.g. only the mailadmin gets write access to
>> the expunged folder.
>
> Some global default ACL might be easier, but that's not very flexible.
>
> Anyway, this is pretty low priority on my todo list.
>
thanks for your points - now I see the arising dificulties
Anyway, for the private namespace lazy_expunge plugins stays a very convenient
method to restore mailboxes and mails from users who accidently expunged them.
thank you!
Martin
More information about the dovecot
mailing list