similar to: lazy_expunge ...

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

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

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

Hi list, I have both lazy_expunge and fts_autoindex activated (with fts-xapian), as follows: plugin { lazy_expunge = EXPUNGED/ } plugin { fts = xapian fts_xapian = partial=2 full=20 attachments=1 verbose=0 fts_autoindex = yes fts_enforced = yes fts_autoindex_exclude = EXPUNGED fts_autoindex_exclude2 = EXPUNGED/* } However, I still see "indexer-worker...: Info: Indexed 1 messages in

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

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, 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:

On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner <leithner at itronic.at> wrote: > Any idea why this doesn't setup work anymore in 2.2.32? > > thx > > Harald > > I just ran into the same thing myself. For me, when I added this to the "location" in the expunged namespace, it started working again: ...:LISTINDEX=expunged.list.index I can't tell you why

On Fri, Sep 15, 2017 at 1:42 PM, Harald Leithner <leithner at itronic.at> wrote: > Am 2017-09-15 21:25, schrieb Mark Moseley: > >> On Wed, Sep 6, 2017 at 2:01 AM, Harald Leithner <leithner at itronic.at> >> wrote: >> >> Any idea why this doesn't setup work anymore in 2.2.32? >>> >>> thx >>> >>> Harald >>>

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.

To a degree I agree .. given mdbox doesnt delete until purge .. but then would be nice if purge took a dovecot search rather than just ditch everything with refcount=0 ... in that way could say purge everything thats been marked as delete according to a specified criteria. rgds Matt completly unrelated moved mailserver back home and listed on cyren so atm getting bounced by dovecot.fi .. have

Ok thx for the info, anyway there are no mail copied to #EXPUNGED/ namespace. Am 04.09.2017 um 13:40 schrieb Aki Tuomi: > Hi! > > On 04.09.2017 14:38, Harald Leithner wrote: >> Hi, >> >> it seams that the lazy_expunge plugin doesn't work for me after the >> upgrade... >> >> 2.2.32 cry's about >> >> plugin {

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

I'm messing around with lazy expunge and I just had a couple of questions. If I delete messages or folders with messages, I see them being moved to the expunge namespace, but if I delete an empty folder, all traces of it seem to disappear. Is there a way to move empty folders to the expunge namespace also? My second question is in regards to restoring folders. If I try to execute the imap

Maybe try fts_autoindex_exclude = \EXPUNGED On 2020-08-29 14:34, Gregory Heytings wrote: > Hi list, > > I have both lazy_expunge and fts_autoindex activated (with fts-xapian), > as follows: > > plugin { > lazy_expunge = EXPUNGED/ > } > > plugin { > fts = xapian > fts_xapian = partial=2 full=20 attachments=1 verbose=0 > fts_autoindex = yes >

Hi, I tried to migrate my dovecot 2.2 to a new server with a other storage configuration and dovecot 2.3. New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location =

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

Hello, I'm trying to configure lazy_expunge plugin (as a way to provide easy backup for mails). This is my configuration (as explained in dovecot wiki): # Default namespace namespace { prefix = separator = / inbox = yes } # namespaces for lazy_expunge plugin: namespace { prefix = .EXPUNGED/ separator = / location = maildir:~/Maildir/expunged } namespace

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