How to disable lazy_expunge for certain mailboxes? My problem is I have a public namespace, whose mail is on a different filesystem than user mails. Some users are allowed to expunge on this shared mailbox, but lazy_expunge is stopping that from working since the mail has to cross a filesystem boundary to make it into the lazy_expunge namespace (location is under the user's home directory). As a workaround can I run a daily cron job to remove messages with the \Deleted flag on them? If so how do I find them? thanks -frank
On Mon, 2009-12-28 at 17:57 -0500, Frank Cusack wrote:> How to disable lazy_expunge for certain mailboxes? > > My problem is I have a public namespace, whose mail is on a different > filesystem than user mails. Some users are allowed to expunge on this > shared mailbox, but lazy_expunge is stopping that from working since > the mail has to cross a filesystem boundary to make it into the > lazy_expunge namespace (location is under the user's home directory).That's not intentional. Even if they were in same filesystem, it shouldn't do that. Fixed: http://hg.dovecot.org/dovecot-1.2/rev/029c3afcfbd0 I don't know what the proper solution would be for lazy-expunge + public namespaces. There probably should be separate lazy-expunge public namespaces or something.. -------------- 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/20091229/3d26a8dd/attachment-0002.bin>
On December 29, 2009 5:20:40 PM -0500 Timo Sirainen <tss at iki.fi> wrote:> That's not intentional. Even if they were in same filesystem, it > shouldn't do that. Fixed: > http://hg.dovecot.org/dovecot-1.2/rev/029c3afcfbd0looks great. i won't be able to test until after the weekend but it sure looks like how i want it to work.
On December 29, 2009 5:20:40 PM -0500 Timo Sirainen <tss at iki.fi> wrote:> That's not intentional. Even if they were in same filesystem, it > shouldn't do that. Fixed: > http://hg.dovecot.org/dovecot-1.2/rev/029c3afcfbd0works for me