similar to: Plugin "lazy_expunge" and subfolder

Hi all, on my system ("AIX 6.1" with "xlc -q64") the "configure" script for "dovecot-2.0.2" breaks with: checking whether fd passing works... no configure: error: fd passing is required for Dovecot to work in config.log: configure:19524: ./conftest configure:19524: $? = 1 configure: program exited with status 1 It seems, that the last

Hi all, on my system ("AIX 6.1" 64bit) after "doveadm stop" there are some processes still alive: vmail 3997878 1 0 16:54:26 - 0:00 dovecot/imap dovenull 4915236 1 0 16:54:26 - 0:00 dovecot/imap-login root 6029330 1 0 16:54:20 - 0:00 dovecot/ssl-params root 6553702 1 0 16:52:01 - 0:00 dovecot/log

Hi all, we use dovecot 2.0.11 with local (LDAP based) users and see (occasionally) error messages like "Mar 15 09:29:26 MailServ local3:err|error dovecot: imap(xxxx): Error: creat(/dovecot.mailbox.log) failed: Permission denied (euid=1985(xxxx) egid=219(yyyy) stat() failed: No such file or directory, euid is not dir owner) but all (filesystem) permissions are correct and the user

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

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

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

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

I'm seeing a crash in 1.1alpha2 when trying to expunge a folder when "lazy_expunge" is enabled: namespace private { separator = . prefix = .EXPUNGED/ location = maildir:/mailstore/%u/Expunged hidden = yes } ... lazy_expunge = .EXPUNGED/ .EXPUNGED/ .EXPUNGED/ Commenting out "lazy_expunge" prevents the crash and mail is expunged. It happens with and without

It appears to me that this issue is related to how lazy_expunge and last_instance work with mdbox - that is different from maildir. With maildir, the message is moved to the expunged namespace only when the last copy is removed (example: from trash folder). With mdbox, first time when you move message from one folder to another, dovecot creates a copy in the expunge namespace. When you delete

Hi, I'm using autoexpunge to clean my users' Trash and Spam mailboxes. But I'm also using lazy_expunge to keep a copy of deleted messages. Is there any to configure lazy_expunge namespace to be autoexpunged too? My lazy_expunge configuration is the "1 Namespace" described at https://wiki2.dovecot.org/Plugins/Lazyexpunge -- Angel L. Mateo Mart?nez Secci?n de

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

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 {

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 >

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

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