similar to: 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 = ? }

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

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

On Aug 12, 2019, at 12:18 AM, Sami Ketola via dovecot <dovecot at dovecot.org> wrote: > > "1. What's the first mail's saved-timestamp? > doveadm fetch -u user date.saved mailbox Junk 1 Well... this is giving me strange results. For myself, when I run this command, I get: [~]# doveadm fetch -u cepheid date.saved mailbox Junk 1 date.saved: 2019-07-15 01:42:56

On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot <dovecot at dovecot.org> wrote: > > * Amir Caspi via dovecot, 12.08.19 22:01 > >> [~]# doveadm mailbox status -u cepheid firstsaved Junk >> Junk firstsaved=1563154976 >> >> I can't tell how that timestamp corresponds to a human-readable date, however. > > [zlatko at disclosure:~]$ date -d

On Aug 14, 2019, at 1:26 PM, Timo Sirainen via dovecot <dovecot at dovecot.org> wrote: > > It probably has something to do with using mbox format. Are the IMAP UIDs changing unexpectedly? Errors/warnings logged related to it? Unfortunately it's a rather troublesome mailbox format. There are likely some bugs in Dovecot mbox code, but it's difficult and time consuming to try to

Hello, I also have issues using Dovecot Backup. I am trying to Backup (or possibly Sync - one way) a single user IMAP account from a remote server, unknown type, to my own server. For that purpose, I defined the following parameters : imapc_host = <host name> imapc_user = <user name> imapc_password = <password> imapc_features = rfc822.size (<user name> has format:

On Oct 11, 2019, at 7:26 PM, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > setting the explicit port for SMTP and.or IMAP advanced settings didn?t change the port it actually tried connecting go until I removed the account and re-added it. I'm sure you tried this before deleting/re-adding, but just in case not: you do have to close out of the settings window (or switch

> On 10 Aug 2019, at 3.15, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > 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 = >

On 13 Aug 2019, at 5.57, Amir Caspi via dovecot <dovecot at dovecot.org> wrote: > > On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot <dovecot at dovecot.org> wrote: >> >> * Amir Caspi via dovecot, 12.08.19 22:01 >> >>> [~]# doveadm mailbox status -u cepheid firstsaved Junk >>> Junk firstsaved=1563154976 >>> >>> I

* Amir Caspi via dovecot, 12.08.19 22:01 > [~]# doveadm mailbox status -u cepheid firstsaved Junk > Junk firstsaved=1563154976 > > I can't tell how that timestamp corresponds to a human-readable date, however. [zlatko at disclosure:~]$ date -d @1563154976 Mon Jul 15 03:42:56 CEST 2019 HTH, Thomas

On 14 Aug 2019, at 22.35, Amir Caspi via dovecot <dovecot at dovecot.org> wrote: > > On Aug 14, 2019, at 1:26 PM, Timo Sirainen via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: >> >> It probably has something to do with using mbox format. Are the IMAP UIDs changing unexpectedly? Errors/warnings logged related to it? Unfortunately

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

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

> 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

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

On Aug 8, 2019, at 12:52 PM, Reio Remma via dovecot <dovecot at dovecot.org> wrote: > > I have the autoexpunge settings defined inside protocol imap thus (and it works): It looks like my definitions are outside the protocol, as this is the default in /etc/dovecot/conf.d/15-mailboxes.conf... MUST autoexpunge be declared within the imap protocol, even if the mailboxes themselves are

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

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

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