Displaying 20 results from an estimated 2000 matches similar to: "lazy_expunge and shared folders"
2014 Jun 12
1
lazy_expunge mangles dovecot-acl-list
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.
2014 May 26
1
LDAP: allow pop3, restrict imap
Hello,
I have all userdata in a ldapserver. Every user has the right to use pop3.
There is no explicit attribute allowing that. It's simply possible.
Now I like to add imap. For a starting period I like to restrict, who
may use imap.
http://wiki2.dovecot.org/Authentication/RestrictAccess mention a solution
where I could modify ldap pass_filter. But that require an attribute
2015 Mar 03
2
acl and lazy_expunge plugins are incompatible?
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
2018 May 23
3
lazy_expunge ...
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 = /
2018 May 23
2
lazy_expunge ...
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
2018 May 23
1
lazy_expunge ...
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
>
2017 Sep 04
2
lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32
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 {
2017 Sep 04
2
lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32
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
2014 Aug 12
1
Fatal: lazy_expunge: Unknown namespace: '.EXPUNGED/'
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
2020 Aug 29
2
lazy_expunge and fts_autoindex
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
2007 Apr 16
2
lazy_expunge vs mulberry
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
2011 Sep 16
1
Deleted mailboxes with lazy_expunge
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
2017 Aug 22
2
imapsieve: failed to read mailbox attribute
Hello all,
Hopefully this is something fairly simple.
I've been trying to set up the Sieve Antispam system as detailed at
https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment,
whenever I change mailboxes I get the following message logged:
Aug 22 09:30:45 remy dovecot: imap(darac at darac.org.uk): Error: imapsieve:
mailbox INBOX: Failed to read /shared/imapsieve/script
2014 Jun 11
0
Safe to downgrade 2.2 to 2.1?
Hi,
is it safe to downgrade Dovecot 2.2 to 2.1 (in my case 2.2.13 to 2.1.17 with
mdbox format) or will there be troubles with index files and backup/restore
is recommended?
Unfortunately with 2.2+ it is not to be possible to use acl + lazy_expunge
together anymore, so downgrading is the only option for me...
@Timo, please fix acl + lazy_expunge in 2.2 if you find some time.
Florian
--
2011 Mar 01
1
lazy_expunge, 2 questions
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
2017 Aug 22
2
imapsieve: failed to read mailbox attribute
On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote:
>
>
>On 22.08.2017 13:37, Darac Marjal wrote:
>> Hello all,
>>
>> Hopefully this is something fairly simple.
>>
>> I've been trying to set up the Sieve Antispam system as detailed at
>> https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment,
>> whenever I change mailboxes
2015 Apr 24
0
acl and lazy_expunge plugins are incompatible?
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
>
2015 Feb 18
0
lazy_expunge + mdbox
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
2017 Sep 06
0
lazy_expunge doesn't work since upgrade 2.2.30 to 2.2.32
Any idea why this doesn't setup work anymore in 2.2.32?
thx
Harald
Am 04.09.2017 um 13:52 schrieb Harald Leithner:
> 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
2010 Jul 25
2
using Lazy_Expunge to enforce retention policy
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