similar to: using Lazy_Expunge to enforce retention policy

I've configured the lazy_expunge plugin exactly like it says on the wiki. I can't seem to configure Mulberry to find the new namespaces. Any hints? I notice that the wiki says to use / as the separator. Mulberry has a setting for this, and the default is '.'. Leaving this as '.' in Mulberry and / in dovecot seems to work fine. (But I still can't access the

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

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

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

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

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

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.

Hi all, Using Dovecot 1.0.3 on RedHat Enterprise 5 (kernel 2.6.18-8.1.6.el5PAE), and NFS storage, we symlinked a Maildir folder: /mailstore/user/Maildir/.Junk -> /junkstore/user/Junkmaildir Everything works fine, until we try to expunge, which produces: A04 NO BUG: Unknown internal error This only happens if "lazy_expunge" is enabled: mail_plugins = quota imap_quota acl

Hello List, do some tests with lazy_expunge i have 2 short questions. is it possible to set folder for expunged messages to read-only so no user is possible to really delete them? i can use mdbox for expunged-folder. but would'nt it be more functional to use maildir to have possibility to delete separate mails? when using mdbox the clean up by cron would effect always multiple messages

Hello, I'm in the process of migrating mailbox from one dovecot server running dovecot 2.1.9 with mailboxes stored in maildir format to a newer one running 2.1.16 with mailboxes stored in mdbox format. To migrate mailboxes I'm using dsync as explained at http://wiki2.dovecot.org/Tools/Dsync. The command I'm running in the newer server is: sudo dsync -o mailbox_list_index=no

Hello all! dovecot 1.1.6 Use lazy_expunge plugin call core on connect. Core: bt full #0 lazy_expunge_mail_expunge (_mail=0x2ac06e9b89e8) at lazy-expunge-plugin.c:103 lt = (struct lazy_expunge_transaction *) 0x2ac06e9b86e0 deststorage = <value optimized out> #1 0x000000000041cefc in imap_expunge (box=0x2ac06e988de8, next_search_arg=0x0) at imap-expunge.c:31 ctx =

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 {

I'm using the dovecot available on Ubuntu Feisty (1.0rc17) and am trying to migrate from courier-imap. A really important feature for me from courier is that expunged messages end up in Trash where they are removed after 7 days. I can get an approximation of this feature as described in the documentation: namespace private { prefix = INBOX. seperator = . inbox = yes } namespace

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 >

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).

Hello Timo, Hello Dovecot Developers, Hello everyone on the list, I think I have some bug, because I haven't found a working configuration till now. I use latest dovecot 2.2.13 from the dovecot-ee repository, with acl and the lazy_expunge plugin. My configuration for shared folders work fine with lazy_expunge disabled. If I enable lazy_expunge and the user (named userA), which I'm

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. 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 >

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: