similar to: lazy_expunge vs mulberry

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

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

Hi, I've been experimenting with using Lazy_Expunge as a tool to enforce document retention policies (by keeping users from deleting emails forever, instead expiring them after a set time). My problem is, how do I keep the user from deleting/expunging mails *inside the expunge folder itself*? I am using dovecot-1.2.10 built from FreeBSD's ports tree, and I am using the following

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

What are people doing to affect the sort order of mailboxes in outlook? Apple Mail and MS Outlook similarly suck in that they do not sort '~' correctly -- mailboxes starting with '~' are first instead of last. At least I think this is the fault of the client, since Mulberry sorts correctly. At least with Apple Mail I can drag and drop mailboxes into any display order I like, so

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 >

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

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

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

FYI. Does Dovecot implement BODYSTRUCTURE? An eval copy of Mulberry can be downloaded from <http://www.cyrusoft.com/mulberry/>. ------------ Forwarded Message ------------ Date: Tuesday, February 10, 2004 6:56 PM +0100 From: Lennart Petersson <lennart at informatik.gu.se> To: mulberry-discuss at cyrusoft.com Subject: Dovecot and Mulberry I've recently changed my imap-server

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

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 {

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

I use Mulberry 3.1.6 on Windows to read my mails with dovecot 0.99.12 Solaris 9. There are some mail which I cannot read. When I try to open such a mail, dovecot quits and restarts (I can see that with ps, nothing is logged). The Mulberry log just looks like this: | --> #7.2300 Sun Dec 19 12:59:33 2004 | A00009 FETCH 695 (BODY.PEEK[1]) | * 695 FETCH (BODY[1] {61} | | --> #7.2300 Sun Dec 19

Hi! I'm using lazy_expunge to backup that are deleted/expunged, but I would like it to be visible to the user. I tried something like: namespace private { prefix = .EXPUNGED/ separator = / location = maildir:~/Maildir/.Apagadas } namespace private { prefix = .DELETED/ separator = / location = maildir:~/Maildir/.Apagadas } namespace private { prefix = .DELETED/.EXPUNGED/