similar to: bug in shared folders/lazy_expunge

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

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

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:

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

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

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

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 >

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

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

Hello guys, I have an issue with shared folders: 1) The USERA shares his INBOX with USERB 2) USERB subscribes the USERA share without problems. 3) USERA deletes all his / or some directories from his INBOX (Trash, Drafts and Sent) 4) USERA logouts and makes login, so dovecot recreates the folders. 5) USERB gains access to subscrive those folders (Trash, Drafts and Sent) this is my namespace

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

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

Hello, i have a user, say userA, which has a valid account (/etc/passwd) on my RH 6.1CZ box, as well as samba one (/etc/smbpasswd). userA logs into his win98 box as a userB, which is unknown both to samba and unix. So I put a new record in /etc/smbusers like this: userA = userB afterwards I have restarted samba server, but the user still cannot connect to his samba shares if he use userB as his

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.

Hi All, Is it possible for different users to sync their home directory's (which reside on the same server) using rsync. By that I mean that usera will using rsync to sync /home/usera and userb will sync /home/userb on the same server but usera will not have access to /home/userb. I hope I am making sense. I do not want to use ssh, just rsync. I have RTFMs but they did not answer my question.

On 10/25/2017 12:58 PM, Heiko Schlittermann wrote: > We could create new "role" users, share the password and create an > additional account within the mail client (thunderbird) they use. From > users perspective it is exactly what they want. But I dislike the idea > of sharing the password. For what reason exactly? It not being personalized, too easy to leak, potentially