similar to: Bug in the combination of Lazy_expunge and acl plugin

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 a problem I was not able to resolve with my current setup (quite basic, the relevant part appended [1]). When userA shares a folder with userB then userB cannot access his mailbox. It's the same problem others have mentioned in *) http://www.dovecot.org/list/dovecot/2014-August/097449.html *) http://dovecot.org/pipermail/dovecot/2014-May/096355.html Could we please have a

Hi All, I am using Samba 3.0.10 on IBM server with REHL 4 Os. The detailed infromation as below. ----------------------------------------------------------------- [root@ufhkglx02 samba]# uname -a Linux ufhkglx02 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:58:04 EST 2007 i686 i686 i386 GNU/Linux [root@ufhkglx02 samba]# cat /etc/redhat-release Red Hat Enterprise Linux ES release 4 (Nahant Update 6)

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, our dovecot mailservice was running smoothly for a long time. Since last week we get the following error message when connecting from the horde/imp webmailer to the public namespace: Panic: file acl-cache.c: line 294 (acl_cache_update): assertion failed: (obj_cache->my_current_rights != &negative_cache_entry) Dovecot and horde/imp are running on seperate hosts. There are no

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

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

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:

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

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

Everyone, I have finally resolved the new heartburn 3.0.24 on Ubuntu Feisty was giving me and have stumbled upon some information that might help others out there. I was seeing problems with ACL entries getting mangled and disappearing, Excel making files read only and extended attributes doing bizarre things. The solution revolved around what appears to be a change in how ACLs are managed.

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, I may have missed a point, but I could have found an issue between plugins quota and lazy_expunge. I have noticed that the "lazy_expunge"d mails are counted as part of the quota, while the documentation says it should not be. I have first tried to find out if this was a configuration mistake somewhere. Notably, you can notice that the expunged mails are in directory ~/expunged

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, I tried to configure a very simple case of Asterisk using SIP userA --- Asterisk server ---- userB sip.conf [userA] type=friend username=userA host=dynamic nat=no context=test [userB] type=friend username=userB host=dynamic nat=no context=test In extensions.conf [test] exten => 1000,1,Dial(SIP/userA) exten => 2000,1,Dial(SIP/userB) I make a call from userA to userB, it works,

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

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

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