Re: Dovecot 2.4.1 userdb override for autoexpunge on specific mailbox

* Thomas Leuxner via dovecot 2025.05.22 12:07: > namespace/inbox/mailbox/Deleted\_Messages/autoexpunge: 6h [...] May 24 07:31:46 edi dovecot: imap(t...@leuxner.net)<1888518><9cDdB9s12+eyyzNT>: Mailbox Deleted Messages: autoexpunge: uid=18687, msgid=, size=5608 Autoexpunge d

Dovecot 2.4.1 userdb override for autoexpunge on specific mailbox

Hi, I'm trying to override the autoexpunge setting for the "Deleted Messages" mailbox in the INBOX namespace. [...] mailbox "Deleted Messages" { autoexpunge = 2d special_use = "\\Trash" } doveconf -nF # mail_namespace :FILTER settings_filter_na

Re: autoexpunge

> On 19/02/2025 20:22 EET dovecot--- via dovecot wrote: > > > > See > > https://doc.dovecot.org/2.4.0/core/config/namespaces.html#mailbox_autoexpunge > > And while it says "expunge", it really means delete and expunge. > > > > Aki >

Re: autoexpunge

See https://doc.dovecot.org/2.4.0/core/config/namespaces.html#mailbox_autoexpunge And while it says "expunge", it really means delete and expunge. Aki Autoexpunge says you should add 'date.save' to 'mail_always_cache_fields'. However 'mail_cache_fields

Re: autoexpunge

a dovecot > > wrote: > > > >  > >> > >> I have the following in 15-mailboxes.config: > >> mailbox Trash { > >>special_use = \Trash > >>autoexpunge = 30 days > >> } > >> I thought that would empty the dele

Re: autoexpunge

 PM, dovecot--- via dovecot > wrote: > >  >> >> I have the following in 15-mailboxes.config: >> mailbox Trash { >>special_use = \Trash >>autoexpunge = 30 days >> } >> I thought that would empty the deleted emails after 30 days. Howev

Re: autoexpunge

I have the following in 15-mailboxes.config: mailbox Trash { special_use = \Trash autoexpunge = 30 days } I thought that would empty the deleted emails after 30 days. However, I find that in .Deleted Messages/cur there are over 18K messages dating back to the 90's. What do I

Re: autoexpunge

> On Feb 18, 2025, at 06:45, Michael Slusarz > wrote: > >> On 02/18/2025 1:09 AM MST Doug Hardie via dovecot >> wrote: >> >> I have the following in 15-mailboxes.config: >> >> mailbox Trash { >>special_use = \Trash >>autoexpu

Re: autoexpunge

> On 02/18/2025 1:09 AM MST Doug Hardie via dovecot wrote: > > I have the following in 15-mailboxes.config: > > mailbox Trash { > special_use = \Trash > autoexpunge = 30 days > } > > I thought that would empty the deleted emails after 30 days. Howev

Re: autoexpunge

-- Doug > On Feb 18, 2025, at 00:20, Marc via dovecot wrote: > > run cron job with purge? > >> >> I have the following in 15-mailboxes.config: >> >> mailbox Trash { >>special_use = \Trash >>autoexpunge = 30 days >> } >>

RE: autoexpunge

run cron job with purge? > > I have the following in 15-mailboxes.config: > > mailbox Trash { > special_use = \Trash > autoexpunge = 30 days > } > > I thought that would empty the deleted emails after 30 days. However, I > find that in .Deleted M

autoexpunge

I have the following in 15-mailboxes.config: mailbox Trash { special_use = \Trash autoexpunge = 30 days } I thought that would empty the deleted emails after 30 days. However, I find that in .Deleted Messages/cur there are over 18K messages dating back to the 90's. What do I

Dovecot autoexpunge lock errors - Couldn't create dovecot.autoexpunge.lock

Hello, We are seeing lots of errors like this in the logs: "dovecot: imap(user@domain)<31219>: Error: autoexpunge: Couldn't create dovecot.autoexpunge.lock lock: file_create_locked(/home/virtual/domain/user/dovecot.autoexpunge.lock) failed: fstat(/home/vir

Enabling autoexpunge for mailboxes created by sieve rules

d by those sieve rules to automatically set to autoexpunge after 15 days ? I tried this , but it did not work. namespace { type = public separator = / prefix = mypublic/ location = maildir:/var/spool/vmail/dovecot/mail/ subscriptions = no list = children mailbox * { autoe

Re: Getting autoexpunge to work

l_privileged_group = mail mailbox_list_index = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox INBOX { autoexpunge = 12 weeks } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent

Re: Getting autoexpunge to work

> On 17 Mar 2020, at 16.42, Philip Colmer 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? Depen

Getting autoexpunge to work

dovecot 2.2.33.2 (d6601f4ec) on Ubuntu 18.04 The recent announcement that expunge is going to be deprecated and that autoexpunge should be used instead reminded me that my recent switch over to autoexpunge is not working. There has been an active discussion today about getting expunge working so

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 confi

Re: Autoexpunge not working for Junk?

On Aug 14, 2019, at 1:45 PM, Timo Sirainen wrote: > > It's not very helpful to look at the indexes after the problem already > happened. Good point! I guess I'll empty out the mailboxes completely, touch a completely empty file, and see if the problem recurs. I'll

Re: Autoexpunge not working for Junk?

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

Re: Autoexpunge not working for Junk?

On Aug 14, 2019, at 1:26 PM, Timo Sirainen via dovecot 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 >

Re: Autoexpunge not working for Junk?

On 13 Aug 2019, at 5.57, Amir Caspi via dovecot wrote: > > On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot > 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

Re: Autoexpunge not working for Junk?

On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot 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. > > [zla

Re: Autoexpunge not working for Junk?

* 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@disclosure:~]$ date -d @1563154976 Mon Jul 15 03:42:56 CEST 2019 HTH, Thomas

Re: Autoexpunge not working for Junk?

On Aug 12, 2019, at 12:18 AM, Sami Ketola via dovecot 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 mail

Re: Autoexpunge not working for Junk?

On 12 Aug 2019, at 00:18, Sami Ketola wrote: > "1. What's the first mail's saved-timestamp? > doveadm fetch -u user date.saved mailbox Junk 1 > > 2. That timestamp should also be the same in dovecot.list.index: > doveadm mailbox status -u user firstsaved Junk" > > can you check that information?

Re: Autoexpunge not working for Junk?

espace 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 Junk Mail from 16 July 2019 Quoting qu

Re: Autoexpunge not working for Junk?

On 8 Aug 2019, at 13:03, Amir Caspi 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 = 1

Re: Autoexpunge not working for Junk?

On Aug 8, 2019, at 12:52 PM, Reio Remma via dovecot 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 autoe

Re: 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

Re: 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 wrote: > > Hi all, > > I set up dovecot a couple of mo

Re: Autoexpunge not working for Junk?

On 25 Jul 2019, at 7.18, Amir Caspi via dovecot 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 Junk mailboxes. Not sure why not > because I'm not getting error messages in

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 mailbox Junk savedbefore 30d"

Autoexpunge of lazy_expunge namespace

Hi, I'm using autoexpunge to clean my users' Trash and Spam mailboxes. But I'm also using lazy_expunge to keep a copy of deleted messages. Is there any to configure lazy_expunge namespace to be autoexpunged too? My lazy_expunge configuration is the "1 Namespace&

Re: Autoexpunge is not working with dotlock locking

On 22.01.2018 17:01, Jaakko Seppälä wrote: > 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 cras

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Jan 2018, Alexey Murz Korepov wrote: I need to set autoexpunge rule only for one single user and one mailbox (mail folder), so apply it only for user al...@example.com mailbox INBOX. How can I set namespace in dovecot config, that will

Re: 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 al...@example.com::noauthenticate userdb_namespace/inbox/mailbox/INBOX/autoexpunge=31d or nopassword instead of noauthenticate. Please keep replies in-list. Aki On

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

Configure namespace {    mailbox {    } } and return from userdb namespace//mailbox//autoexpunge=value Ak On 23.01.2018 11:57, Alexey Murz Korepov wrote: > I need to set autoexpunge rule only for one single user and one > mailbox (mail folder), so apply it only for user al...@examp

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 al...@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: mur...@gmail.com

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".

Re: home folder for virtual users with autoexpunge setting

fen Kaiser" wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 19 Nov 2017, fe...@kngnt.org wrote: I understand this is correct: as is a virtual user, it does not > have home folder. Is there any way I can set the autoexpunge plugin to > store the lock file in the vi

Re: home folder for virtual users with autoexpunge setting

November 21, 2017 9:08 AM, "Steffen Kaiser" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sun, 19 Nov 2017, fe...@kngnt.org wrote: > >> I understand this is correct: as is a virtual user, it does not > >> have home folder. Is th

Re: home folder for virtual users with autoexpunge setting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 19 Nov 2017, fe...@kngnt.org wrote: I understand this is correct: as is a virtual user, it does not have home folder. Is there any way I can set the autoexpunge plugin to store the lock file in the virtual user email home folder? well

Re: home folder for virtual users with autoexpunge setting

On 19.11.2017 10:57, fe...@kngnt.org wrote: > Hi all, > > I have enabled today the autoexpunge setting for Trash folders, and I am > getting the following error when Dovecot starts: > > imap(): Error: autoexpunge: Couldn't create dovecot.autoexpunge.lock > lock:

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(): Error: autoexpunge: Couldn't create dovecot.autoexpunge.lock lock: User has no home directory I understand this is correct: as is a virtual use

Re: Dynamic autoexpunge for IMAP folders

Excellent, that works for me. Actually, I add one more setting to be on the safe side regarding IMAP capitalisation rules (or non-rules). namespace/inbox/mailbox=bla namespace/inbox/mailbox/bla/name=Bla namespace/inbox/mailbox/bla/autoexpunge=6h Thanks a lot. On Wed, Jan 18, 2017 at 2:01 AM

Re: Dynamic autoexpunge for IMAP folders

t/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 I do not know what folders the user might to configure for > autoexpu

Re: Dynamic autoexpunge for IMAP folders

namespace in the static config, see here http://www.dovecot.org/list/dovecot/2013-August/092053.html As I do not know what folders the user might to configure for autoexpunge, I cannot put the folders into the config. Thorsten On Tue, Jan 17, 2017 at 12:14 PM, Thomas Leuxner wrote: > * Thors

Re: Dynamic autoexpunge for IMAP folders

* Thorsten Hater 2017.01.17 12:04: > userdb { >driver = static >args = namespace/inbox/mailbox/Bla/autoexpunge=6h > } I'm almost sure that 'driver = static' contradicts the concept of userdb overrides: http://wiki.dovecot.org/UserDatabase/ExtraFields I

Re: 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 wrote: > * Thorsten Hater 2017.01.17 10:57: > > > U

Re: Dynamic autoexpunge for IMAP folders

* Thorsten Hater 2017.01.17 10:57: > Unfortunately, this yields the same problem > > Debug: Unknown userdb > setting: plugin/userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h > > userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h 'plugin' is not part of the userdb

Re: 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 wrote: > * Thorsten Hater 2017.01.17 09:40: > > > namespace/inbox/mailbox/Bla/au

Re: Dynamic autoexpunge for IMAP folders

* Thorsten Hater 2017.01.17 09:40: > namespace/inbox/mailbox/Bla/autoexpunge=6h > > from a userdb, which results in > > Debug: Unknown userdb setting: > plugin/namespace/inbox/mailbox/Bla/autoexpunge=6h userdb_namespace/inbox/mailbox/Bla/autoexpunge=6h Regards Thom

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

Re: autoexpunge=30d does not works :(

* Peter Hodur 2016.12.16 11:42: > mailbox Spam { > auto= subscribe > special_use = \Junk > autoexpunge = 30d Hi

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. sepa

RE: autoexpunge clarification

Thanks Philon. In one of my situations, the potential for such old mail in accounts where the user is not receiving new mail or logging in is large. For example, one application is for an emergency auxiliary mail service. It can be heavily used during training, drills and, of course, emergenc

Re: autoexpunge clarification

Hi Michael you are correct I guess based on your assumptions. autoexpunge kicks in on user interaction either by email delivery or a user checking in. If both does not occour then no cleanup will happen. Question would be if there is that much to cleanup in this case. A user not logging in

RE: autoexpunge clarification

y quit. I can guess that the bulletin about LMTP similarly means at the end of each time LMTP delivers mail to the mailbox. Assuming that is true, then the problem I see with autoexpunge is that it doesn't address the case of a user that has not logged in nor received mail in that mailb

Re: autoexpunge clarification

ogram. Philon > Am 30.08.2016 um 14:41 schrieb Michael Fox : > > 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 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=: (v2.2.20+) Automatically at user deinitialization expunge all mails in this ma

Re: autoexpunge wildcard mailbox from userdb

On 02/05/16 21:43, Timo Sirainen wrote: On 02 May 2016, at 16:40, Leon Kyneur wrote: On 02/05/16 16:51, Timo Sirainen wrote: On 02 May 2016, at 03:47, Leon Kyneur wrote: Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24 release. However I'm tryi

Re: autoexpunge wildcard mailbox from userdb

On 02 May 2016, at 16:40, Leon Kyneur wrote: > > > > On 02/05/16 16:51, Timo Sirainen wrote: >> On 02 May 2016, at 03:47, Leon Kyneur wrote: >>> Was excited to see that wildcards are now possible on autoexpunge in the >>> 2.2.24 release. >>> &

Re: autoexpunge wildcard mailbox from userdb

On 02/05/16 16:51, Timo Sirainen wrote: On 02 May 2016, at 03:47, Leon Kyneur 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

Re: autoexpunge wildcard mailbox from userdb

On 02 May 2016, at 03:47, Leon Kyneur 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

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.

Re: Returning custom autoexpunge for user's INBOX

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 29 Feb 2016, Tom Johnson wrote: I want to be able to have custom autoexpunge settings for different users. I have it working for various folders (draft, junk, trash), but I can't seem to get it working for the user's primary in

Re: Returning custom autoexpunge for user's INBOX

I wrote: > I want to be able to have custom autoexpunge settings for different users. > Sorry to follow up on my own post - but will it work if I define the inbox explicitly in 15-mailboxes.conf? Does this syntax properly set autoexpunge for the inbox? namespace inbox { sep

Returning custom autoexpunge for user's INBOX

I want to be able to have custom autoexpunge settings for different users. I have it working for various folders (draft, junk, trash), but I can't seem to get it working for the user's primary inbox. In my user_query (I'm using mysql), I'm returning entries like this in the

Re: Autoexpunge on INBOX? And disabling autoexpunge for a mailbox via userdb_import?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 11 Feb 2016, Tom Johnson wrote: Is it possible to specify an autoexpunge period for the main inbox? And can autoexpunge be turned off via userdb_import? I would make it the other way round: enabled it via userdb_import. I have the

Autoexpunge on INBOX? And disabling autoexpunge for a mailbox via userdb_import?

I have autoexpunge working for various special_use mailboxes, but I'd like it to optionally be used for users for their inbox as well. I'd also like to be able to disable autoexpunge for some users for certain directories. Is it possible to specify an autoexpunge period for the

Re: autoexpunge - different settings for different users

Hi Tom, Looks like you are missing 'mailbox' keyword: namespace/inbox/mailbox/Drafts/autoexpunge=3d Regards, Leon On Tue, Feb 9, 2016 at 12:51 PM Tom Johnson wrote: > > > On Feb 7, 2016, at 10:59 AM, Timo Sirainen wrote: > > > > You can override any mail-rela

Re: autoexpunge - different settings for different users

> On Feb 7, 2016, at 10:59 AM, Timo Sirainen wrote: > > You can override any mail-related setting from userdb. So for example if you > have: > > namespace inbox { > mailbox Trash { >autoexpunge = 30d > } > } > > You can have your userdb return n

Re: autoexpunge - different settings for different users

s if necessary? > > It would mean the same as: > > namespace inbox { > mailbox * { >autoexpunge = 90d > } > } > > So the question is about whether the above configuration works. Currently it > doesn't, but it probably will in future. Does this mean that you can't use autoexpunge on the main inbox for a user at all?

Re: autoexpunge - different settings for different users

> On 08 Feb 2016, at 06:46, Tom Johnson wrote: > >> You can override any mail-related setting from userdb. So for example if you >> have: >> >> namespace inbox { >> mailbox Trash { >> autoexpunge = 30d >> } >> } >> >> You

Re: autoexpunge - different settings for different users

s? Or is this beyond the >> ability of the autoexpunge feature? Should I just use a cron job and use >> "doveadm expunge" on a user-by-user basis? > > You can override any mail-related setting from userdb. So for example if you > have: > > namespace inbox {

Re: autoexpunge - different settings for different users

e 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 is this beyond the > ability of the autoexpunge feature? Should I just use

Re: autoexpunge - different settings for different users

or this? Or is this beyond the ability of the autoexpunge feature? Should I just use a cron job and use "doveadm expunge" on a user-by-user basis? Thanks- I think you’ll need a script for this. At the most basic level you could just create a bash script, add a bunch of expunge comma

Re: autoexpunge - different settings for different users

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

Re: autoexpunge - different settings for different users

e 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 is this beyond the > ability of the autoexpunge feature? Should I just use

autoexpunge - different settings for different users

l from the Trash and Junk folders, and nowhere else. Is there a way to do some sort of lookup for this? Or is this beyond the ability of the autoexpunge feature? Should I just use a cron job and use "doveadm expunge" on a user-by-user basis? Thanks-

Re: 2.2.21 imap crash - autoexpunge related?

> On 22 Jan 2016, at 17:07, Robert Blayzor wrote: > > dovecot --version > 2.2.21 (5345f22) > > > FreeBSD 10.2-RELEASE-p10 FreeBSD 10.2-RELEASE-p10 #0 r294322M: > > > > having repeated core dumps on imap process… autoexpunge issue? Yeah, should be fixed by

2.2.21 imap crash - autoexpunge related?

dovecot --version 2.2.21 (5345f22) FreeBSD 10.2-RELEASE-p10 FreeBSD 10.2-RELEASE-p10 #0 r294322M: having repeated core dumps on imap process… autoexpunge issue? GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public

Re: autoexpunge problems

On 01/04/2016 08:25 PM, Timo Sirainen wrote: On 18 Dec 2015, at 05:26, Olaf Hopp wrote: 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

Re: 2.2.21 imap core dump after enabling autoexpunge

gt; [23] client_destroy(client = 0xbb700, reason = (nil)), line 263 in >> "imap-client.c" >> [24] client_input(client = 0xbb700), line 1121 in "imap-client.c" >> [25] io_loop_call_io(io = 0xb4b90), line 559 in "ioloop.c" >> [26] io_loop_ha

Re: autoexpunge problems

On 18 Dec 2015, at 05:26, Olaf Hopp wrote: > > 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

Re: 2.2.21 imap core dump after enabling autoexpunge

eason = (nil)), line 263 in > "imap-client.c" > [24] client_input(client = 0xbb700), line 1121 in "imap-client.c" > [25] io_loop_call_io(io = 0xb4b90), line 559 in "ioloop.c" > [26] io_loop_handler_run_internal(ioloop = 0xa4830), line 211 in > "ioloop-pol

Re: Dovecot 2.2.20 autoexpunge

On Dec 23, 2015, at 3:17 AM, Timo Sirainen wrote: > > So this keeps finding mails that aren't being automatically deleted? (You > were testing with savedbefore, right?) : > > doveadm search -u user@domain mailbox Trash savedbefore 2w > > If that works, try if it happens to work with mailbox_li

2.2.21 imap core dump after enabling autoexpunge

Hi, I've enabled autoexpunge for Trash and Junk. Now imap process core dumps occasionally. Tomppa program terminated by signal SEGV (no mapping at the fault address) 0xff0dc2e0: o_stream_get_buffer_used_size : ld [%o0 + 20], %o0 Current function is notify_ok (opti

Re: Dovecot 2.2.20 autoexpunge

On 22 Dec 2015, at 22:23, Robert Blayzor wrote: > > On Dec 22, 2015, at 2:56 PM, Teemu Huovila wrote: >> >> The autoexpunge feature does not check the \Deleted flag. >> >> Are any errors logged in "doveadm log errors"? Could you post your c

Re: Dovecot 2.2.20 autoexpunge

On Dec 22, 2015, at 2:56 PM, Teemu Huovila 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

Re: Dovecot 2.2.20 autoexpunge

On 22.12.2015 19:24, Robert Blayzor wrote: >> On Dec 22, 2015, at 9:49 AM, Dominik Breu 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/rf

Re: Dovecot 2.2.20 autoexpunge

> On Dec 22, 2015, at 9:49 AM, Dominik Breu 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/Dovea

Re: Dovecot 2.2.20 autoexpunge

Hi Robert, 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 co

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

limiting autoexpunge to a service

Hello, like described at wiki "Mailbox settings": protocol imap { namespace inbox { mailbox Spam { autoexpunge = 10d } } } I tried to use autoexpunge inside lmtp: 20-lmtp.conf: protocol lmtp { mail_plugins = $mail_plugins sieve postmaster_address = ... info_log_path = /var/l

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

Re: autoexpunge creates special_use folder

On 11 Dec 2015, at 16:00, Tom Sommer wrote: > > namespace inbox { > mailbox Spam { >special_use = \Spam >auto = create >autoexpunge = 30d > } > } > > This creates the "Spam" folder in the filesystem on login/logout, even though > i

autoexpunge creates special_use folder

namespace inbox { mailbox Spam { special_use = \Spam auto = create autoexpunge = 30d } } This creates the "Spam" folder in the filesystem on login/logout, even though it shouldn't. If I remove autoexpunge, the folder is not created. -- Tom Sommer

Re: Autoexpunge and special user namespace

> On 09 Dec 2015, at 23:51, Joseph Tam wrote: > > On Wed, 9 Dec 2015, Timo Siraine wrote: > >>> I'm interested in replacing my cron script that expunges old >>> deleted mail with the new feature announced in 2.2.20 >>>> + Added mailbox

  1   2   >