similar to: Getting autoexpunge to work

Displaying 20 results from an estimated 3000 matches similar to: "Getting autoexpunge to work"

2020 Feb 17
3
How does dovecot determine users from /etc/passwd?
We're using dovecot on a help desk ticketing system. The system doesn't perform any cleanup of IMAP mailboxes so we have a regular cronjob doing this: /usr/bin/doveadm flags add -A '\Deleted' SEEN SENTBEFORE 12w && /usr/bin/doveadm expunge -A DELETED MAILBOX '*' Recently, doveadm has been reporting this: doveadm(nobody): Error: User initialization failed:
2020 Feb 19
1
How does dovecot determine users from /etc/passwd?
Thank you, Sami. I've made that change. Regards Philip On Mon, 17 Feb 2020 at 10:50, Sami Ketola <Sami.Ketola at open-xchange.com> wrote: > Hi, > > how about switching to use autoexpunge? > > https://wiki.dovecot.org/MailboxSettings > > Sami > > > On 17 Feb 2020, at 11.01, Philip Colmer <philip.colmer at linaro.org> wrote: > > We're
2019 Dec 23
6
When is a new mail not unseen?
I'm trying to diagnose a really strange situation where certain emails, when submitted to the mailbox by Postfix, are not considered to be unseen by Dovecot. During testing, I've shut down anything else on the server that might want to access the mailbox. I submit the email to the local postfix instance which then says it has delivered it to the mailbox: Dec 23 09:51:35 ip-10-35-194-108
2019 Aug 10
3
Autoexpunge not working for Junk?
On 8 Aug 2019, at 13:03, Amir Caspi <cepheid at 3phase.com> wrote: > IMHO the setting should apply regardless of protocol, but is that actually the case in practice? It seems to be broken. I have namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { autoexpunge = 14 days auto = subscribe special_use = \Junk } ? } and I have messages in my
2020 Mar 03
0
Dovecot autoexpunge
Following a previous suggestion I'd received to turn on autoexpunge (https://dovecot.org/pipermail/dovecot/2020-February/118281.html), I'm now trying to confirm whether or not it is doing what I expect it to do. I've set the expiration to be 12 weeks (as shown below in the config) but a lot of the mailboxes have email in them that is much older. Reading
2020 Mar 17
0
Getting autoexpunge to work
> On 17 Mar 2020, at 16.42, Philip Colmer <philip.colmer at linaro.org> wrote: > > doveadm fetch -u local-finance-support "mailbox date.saved" UID 37 > > mailbox: INBOX > date.saved: 2020-03-17 14:34:12 > > Why on earth is dovecot showing today's date for that message? What > have I misunderstood or misconfigured? Depends a lot on what is your
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 = ? }
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 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
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
2018 Jan 22
1
Autoexpunge is not working with dotlock locking
Hello, Autoexpunge is not working when used with dotlock locking. It seems to been broken since version 2.2.28. When autoexpunge is enabled and mailbox locking is set to dotlock all imap, pop and lmtp connections crash with the same error "file file-lock.c: line 287: unreached". Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR
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
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
2020 Feb 17
0
How does dovecot determine users from /etc/passwd?
Hi, how about switching to use autoexpunge? https://wiki.dovecot.org/MailboxSettings <https://wiki.dovecot.org/MailboxSettings> Sami > On 17 Feb 2020, at 11.01, Philip Colmer <philip.colmer at linaro.org> wrote: > > We're using dovecot on a help desk ticketing system. The system > doesn't perform any cleanup of IMAP mailboxes so we have a regular > cronjob
2019 Aug 08
0
Autoexpunge not working for Junk?
Hi all, Might anyone have any idea about this issue? I can run a cron job if needed but it seems like autoexpunge SHOULD be doing this automatically... Thanks! --- Amir > On Jul 24, 2019, at 10:18 PM, Amir Caspi <Cepheid at 3phase.com> wrote: > > Hi all, > > I set up dovecot a couple of months ago and am having trouble getting autoexpunge=30d to work on my Trash and
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
2017 Jan 18
0
Dynamic autoexpunge for IMAP folders
On 17 Jan 2017, at 13.36, Thorsten Hater <thorsten.hater at gmail.com> wrote: > > 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
2015 Dec 22
2
Dovecot 2.2.20 autoexpunge
> On Dec 22, 2015, at 9:49 AM, Dominik Breu <dominik at dominikbreu.de> wrote: > the autoexpunge feature only removes mails wich have the \Delete Flag so no deletion of mails wich doesn't have this Flag(see https://tools.ietf.org/html/rfc4315#section-2.1 or http://wiki2.dovecot.org/Tools/Doveadm/Expunge) > > you could run a cron job with a doveadm move comando to move the
2016 May 02
2
autoexpunge wildcard mailbox from userdb
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 Trash/* { ... autoexpunge = 10m } everything works.. however if I return =namespace/inbox/mailbox/Trash/*/autoexpunge=10m via userdb - it does not. Logs
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