similar to: autoexpunge wildcard mailbox from userdb

Displaying 20 results from an estimated 10000 matches similar to: "autoexpunge wildcard mailbox from userdb"

2016 May 02
2
autoexpunge wildcard mailbox from userdb
On 02/05/16 16:51, Timo Sirainen wrote: > On 02 May 2016, at 03:47, Leon Kyneur <leon at f-m.fm> wrote: >> Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24 release. >> >> However I'm trying to configure these from the userdb lookup and it doesn't appear to be working. >> >> if I set in 15-mailboxes.conf >> mailbox
2016 Feb 08
2
autoexpunge - different settings for different users
> On Feb 7, 2016, at 10:59 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 07 Feb 2016, at 04:50, Tom Johnson <tj at terramar.net> wrote: >> >> I have some users where I'd like to expunge their mail at different times. >> .... >> .... >> Is there a way to do some sort of lookup for this? Or is this beyond the ability of the autoexpunge
2016 Jul 10
3
Panic: file mdbox-save.c: line 337: unreached
Recently updated to 2.2.25. Noticed a migration script I've been previously running fine started giving me the errors below. Remove server doesn't log any failure. doveconf -n attached. + /bin/doveadm -o mail_fsync=never backup -R -u user at domain.com imapc: dsync(user at domain.com): Panic: file mdbox-save.c: line 337: unreached dsync(user at domain.com): Error: Raw backtrace:
2016 Feb 07
6
autoexpunge - different settings for different users
I have some users where I'd like to expunge their mail at different times. For example, I may have some users who I want to expunge everything from every folder at 30 days. Others where I'd like to expunge everything at 90 days. And still others where I only want to expunge mail from the Trash and Junk folders, and nowhere else. Is there a way to do some sort of lookup for this? Or
2018 Jan 23
3
How to set autoexpunge rule for single user mailbox in dovecot conf?
I need to set autoexpunge rule only for one single user and one mailbox (mail folder), so apply it only for user alice at example.com mailbox INBOX. How can I set namespace in dovecot config, that will apply only to single user? -- Best regards, Alexey Murz Korepov. Email, Jabber: murznn at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL:
2017 Jan 17
2
Dynamic autoexpunge for IMAP folders
So, returning from the LDAP userdb does not change situation. As I said, I would to set folder names dynamicaly, without setting up a mailbox in advance. Here the problem is discussed http://www.dovecot.org/list/dovecot/2013-August/092023.html but no solution is found apart from defining the namespace in the static config, see here http://www.dovecot.org/list/dovecot/2013-August/092053.html As
2015 Dec 22
2
Dovecot 2.2.20 autoexpunge
I have configured autoexpunge on some folders: namespace inbox { inbox = yes location = mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Trash { auto = subscribe autoexpunge = 2 weeks special_use = \Trash } prefix = separator = / } After adding these and restarting, logging in and out several times, I still see messages
2019 Aug 08
2
Autoexpunge not working for Junk?
Hello! I have the autoexpunge settings defined inside protocol imap thus (and it works): protocol imap { ? mail_plugins = quota notify replication imap_quota imap_sieve ? namespace inbox { ??? location = ??? mailbox Ham { ????? autoexpunge = 365 days ??? } ??? mailbox Spam { ????? autoexpunge = 365 days ??? } ??? mailbox Trash { ????? autoexpunge = 180 days ??? } ??? prefix = ? }
2019 Jul 25
3
Autoexpunge not working for Junk?
Hi all, I set up dovecot a couple of months ago and am having trouble getting autoexpunge=30d to work on my Trash and Junk mailboxes. Not sure why not because I'm not getting error messages in my log. Running "doveadm search -u <user> mailbox Junk savedbefore 30d" shows me many messages (I've got messages back to mid-May, and a couple of other users have them back to
2017 Jan 17
2
Dynamic autoexpunge for IMAP folders
Unfortunately, this yields the same problem Debug: Unknown userdb setting: plugin/userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h Thorsten On Tue, Jan 17, 2017 at 10:16 AM, Thomas Leuxner <tlx at leuxner.net> wrote: > * Thorsten Hater <thorsten.hater at gmail.com> 2017.01.17 09:40: > > > namespace/inbox/mailbox/Bla/autoexpunge=6h > > > > from a userdb,
2017 Jan 17
2
Dynamic autoexpunge for IMAP folders
Dear all, is there a way to allow users to set up something like autoexpunge on an individual IMAP folder basis? The idea I implemented does not seem to work, namely returning namespace/inbox/mailbox/Bla/autoexpunge=6h from a userdb, which results in Debug: Unknown userdb setting: plugin/namespace/inbox/mailbox/Bla/autoexpunge=6h >From older questions on the mailing list I gather that the
2016 Aug 30
2
autoexpunge clarification
I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=<time>: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox whose saved-timestamp is older than <time> (e.g. autoexpunge=30d). This removes the
2016 Jul 09
2
Raw backtrace multiple passwords not allowed
Hi Recently enabled support for encrypted passwords on my proxies - CRAM-MD5, DIGEST-MD5, NTLM and APOP to support some new users. Most users are working perfectly though every so often I see this happening in the logs: Jul 09 06:32:51 auth: Error: ldap(user at domain.com,192.168.10.90,<mOWiFi431eDKOsBS>): Multiple password values not supported Jul 09 06:32:51 auth: Panic: file
2017 Jan 17
2
Dynamic autoexpunge for IMAP folders
I know, but it is not present in the string returned by the userdb, which is set up for testing userdb { driver = static args = namespace/inbox/mailbox/Bla/autoexpunge=6h } On Tue, Jan 17, 2017 at 11:03 AM, Thomas Leuxner <tlx at leuxner.net> wrote: > * Thorsten Hater <thorsten.hater at gmail.com> 2017.01.17 10:57: > > > Unfortunately, this yields the same
2017 Nov 19
4
home folder for virtual users with autoexpunge setting
Hi all, I have enabled today the autoexpunge setting for Trash folders, and I am getting the following error when Dovecot starts: imap(<USER>): Error: autoexpunge: Couldn't create dovecot.autoexpunge.lock lock: User has no home directory I understand this is correct: as <USER> is a virtual user, it does not have home folder. Is there any way I can set the autoexpunge plugin
2015 Dec 18
2
autoexpunge problems
Hello, I tried to use the new autoexpunge for my Trash folders I had in 15-mailboxes.conf mailbox Trash { special_use = \Trash auto = subscribe } (dovecot -n of the original config is below) and added just the line autoexpunge = 1h Just a short period on my test system. But it failed. In the log I see Dec 18 10:54:07 irams2 dovecot: imap(ms2test): Error: Failed to autoexpunge
2015 Dec 22
2
Dovecot 2.2.20 autoexpunge
On Dec 22, 2015, at 2:56 PM, Teemu Huovila <teemu.huovila at dovecot.fi> wrote: > > The autoexpunge feature does not check the \Deleted flag. > > Are any errors logged in "doveadm log errors"? Could you post your complete output of doveconf -n please. That?s what I thought. If I run expunge from doveadm manually, it will work as expected. I just never seem to get
2018 Jan 23
0
How to set autoexpunge rule for single user mailbox in dovecot conf?
You can do passdb { ? driver = passwd-file ? args =? /path/to/some/file ? skip = unauthenticated } and put in this file alice at example.com::::::noauthenticate userdb_namespace/inbox/mailbox/INBOX/autoexpunge=31d or nopassword instead of noauthenticate. Please keep replies in-list. Aki On 23.01.2018 12:31, Alexey Murz Korepov wrote: > So, with using `passwd` driver as userdb - there are
2016 Aug 31
2
autoexpunge clarification
Thanks Philon, I did read the extra bullets, as indicated in my email below. But your "When the user quits and thus closes his mailbox/connection" is more clear than "after the client is already disconnected", since the latter is really anytime, rather than at the time they quit. I can guess that the bulletin about LMTP similarly means at the end of each time LMTP delivers
2016 Dec 16
1
autoexpunge=30d does not works :(
Hello, just upgraded to Dovecot 2.2.27 and altered dovecot.conf to contain autoexpunge directive for Spam mailbox (yes it's migrated from Courier 3 years ago): namespace inbox { prefix = INBOX. separator = . inbox = yes