similar to: lazy expunge namespaces

There's a bug in "folder delete" for lazy expunge, type "1 namespace", as descibed on https://wiki2.dovecot.org/Plugins/Lazyexpunge When trying to delete a mailbox that still has messages in it, but that has no EXPUNGED/<name> counterpart, the process hangs after the imap "DELETE" command, and the following appears in the log file after a 60s timeout: Jun

Hello Is it a bug in lazy expunge plugin or am I missing something? Dovecot v2.0.1 (c5111fb65b0b) home = /mail/%Ld/%Ln mail_location = mdbox:/mail/%Ld/%Ln/mdbox sources.list - debian (squeeze) .. deb http://xi.rename-it.nl/debian testing-auto/dovecot-2.0 main Config changes - - - plugin { lazy_expunge = .EXPUNGED/ } namespace { type = private separator = / prefix = inbox = yes

So digging a little deeper it seems this maybe an issue between fts/fts_lucene and lazy_expunge .. if I disable the fts plugin [root at stargate dovecot.rawlog]# doveadm search -u matt at the-bryants.net mailbox .EXPUNGED/Trash from noreply at apress.com 6156a416748c035b5c0b0000ef794dd1 1 search works .. so begs the question whats fts_lucene doing ... rgds Matt > Matt Bryant

There's now a plugin called lazy_expunge in CVS. Instead of EXPUNGE expunging the mails directly, they're moved to a mailbox with same name in another namespace where user can still copy the mails back. Also DELETEd mailboxes are moved to another namespace. See http://wiki.dovecot.org/Plugins/Lazyexpunge for more information. This is similar to Cyrus's two phase expunge:

You should probably exclude the .DUMPSTER folder from quota and FTS plugin { fts_autoindex_exclude = .DUMPSTER quota_ruleN = .DUMPSTER:ignore } Aki On 23.05.2018 13:29, Matt Bryant wrote: > So digging a little deeper it seems this maybe an issue between > fts/fts_lucene and lazy_expunge .. if I disable the fts plugin > > [root at stargate dovecot.rawlog]#? doveadm search -u >

On 23.05.2018 13:46, Matt Bryant wrote: > deeper still looks like culprit was > > fts_enforced = "no" > > which i removed given default anyway .. > > still get error > > [root at stargate dovecot.rawlog]#? doveadm search -u > matt at the-bryants.net mailbox .EXPUNGED/* from noreply at apress.com > doveadm(matt at the-bryants.net): Error: fts: Failed to

deeper still looks like culprit was fts_enforced = "no" which i removed given default anyway .. still get error [root at stargate dovecot.rawlog]# doveadm search -u matt at the-bryants.net mailbox .EXPUNGED/* from noreply at apress.com doveadm(matt at the-bryants.net): Error: fts: Failed to sync mailbox .EXPUNGED: Mailbox doesn't exist: .EXPUNGED 6156a416748c035b5c0b0000ef794dd1

Hello, I wanted to test the lazy expunge plugin together with mdbox. It seems to me that the folder subscriptions file in the mdbox directory was overwritten with only a few folder names every time I added or removed something in the list of subscribed folders, or even if I turned the imap folder subscription feature off and on. Here is my setup: # 2.0.16:

So I decided to configure this plugin and take it for a test drive .. configured using mdbox (main namespace is Maildir) .. So as per Wiki have the following namespaces defined ... location is held within db ... but basically Maildir:~/Maildir for inbox namespace ==== 8< =============== namespace inbox { list = yes type = private inbox = yes prefix = INBOX/ separator = /

Hi, since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon as a user shares a folder. The user the folder is shared to cannot login anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace: '.EXPUNGED/' - When no folder is shared lazy_expunge is working fine, deleted mails are moved to the expunged namespace and can be recovered without any problems. - Sharing

On 14 Dec 2018, at 17:09, Robert L Mathews <lists at tigertech.com> wrote: > https://wiki.dovecot.org/Plugins/Lazyexpunge I have a question about the namespace section. > You create only a single namespace. When a message is expunged from mailbox <name>, it's moved to a mailbox <name> in the expunge namespace. When an entire mailbox <name> is deleted, it's

Hello. Before going into deep testing of 2.2.16 (clean install tbd), I would like to know if someone is using succesfully both ACL and Lazy_expunge plugins. Perhaps I had a config error? Thanks, Paolo > Il 3 marzo 2015 alle 16.36 Paolo Cravero <paolo.cravero at csi.it> ha > scritto: > > > Hello list. > Following two previous unanswered requests >

Hi, I think I found a bug in Dovecot 2.1.17 and 2.2.13. In our setup, sometimes ACLs stop working because "dovecot-acl-list" is replaced by an empty file. We found that lazy_expunge is connected to this. To reproduce, create ACLs for "user1" in a folder. Put a mail in that folder and expunge it, so that the folder will be created in the "expunged" namespace.

Hello list. Following two previous unanswered requests (http://www.dovecot.org/list/dovecot/2014-August/097449.html and http://www.dovecot.org/list/dovecot/2014-May/096261.html), I fell into the same problem: ACL and lazy_expunge plugins do not work together. I had lazy_expunge enabled working OK. Then I activated ACL plugin, and gave dovecot.2 visibily over paolo.cravero's Inbox: the IMAP

Hello, first time here. I am playing with Dovecot because of its mdbox storage, SIS feature and altstorage ability. I authenticate against LDAP (passdb), but I don't fetch operational data from LDAP (mail_locations are static from config files and "user_attrs = =uid=500, =gid=500, =home=/maildata1/home/%d/%1n/%n"). On a daily basis I run "doveadm altmove -A savedbefore

Hi, it seams that the lazy_expunge plugin doesn't work for me after the upgrade... 2.2.32 cry's about plugin { lazy_expunge_only_last_instance=no } is most likely handled as 'yes' - remove the setting completely to disable it. If this is intentional, add quotes around the value: lazy_expunge_only_last_instance="no" I changed it to

I did a debug output of the dsync-server and found out that it queries the userdb parameter but doesn't use it. --- Debug: Loading modules from directory: /usr/lib/dovecot/modules Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib02_lazy_expunge_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so

I used Lazyexpunge. I tried to create .DELETED without any hints and see that the creation was successful. I want to prevent users from creating .DELETED, what should I do? My settings > plugin { > lazy_expunge = .DELETED/ > } > # > > namespace { > prefix = .DELETED/ > hidden = yes > list = no > separator = / > location =

When I try to use it i get undefined symbol: dlopen(/usr/lib/dovecot/pop3/lib02_lazy_expunge_plugin.so) failed: /usr/lib/dovecot/pop3/lib02_lazy_expunge_plugin.so: undefined symbol: namespace_find_prefix Does anyone has this problem or I've compiled it with too agresive flags? Thanx! PS. I've folowed http://wiki.dovecot.org/Plugins/Lazyexpunge word to word. -- FreeB(eer)S(ex)D(rugs)

Hello List, with dovecot version 2.2.13.9, I actually have a problem using lazy_expunge and acl together. Shared/Public Folders work fine with lazy_expunge disabled. If lazy_expunge is enabled and userA got a shared folder form userB, then there is the error shown in subject. My test case to reproduce the error. doveadm mailbox list -u userA at domain --> Output Fine. doveadm acl set -u