Another alternative is to use some other mdbox for the .EXPUNGED namespace, so it will move it from one mdbox to another

Aki

On 24.05.2018 09:00, Matt Bryant wrote:

To a degree I agree .. given mdbox doesnt delete until purge .. but then would be nice if purge took a dovecot search rather than just ditch everything with refcount=0 ... in that way could say purge everything thats been marked as delete according to a specified criteria.

rgds

Matt

completly unrelated moved mailserver back home and listed on cyren so atm getting bounced by dovecot.fi .. have requested de-listing

...

Aki Tuomi <mailto:aki.tuomi@dovecot.fi> 24 May 2018 at 3:35 pm

I am not sure if lazy expunge makes much sense with mdbox, at least if you use the same mdbox storage with it. It might make sense with separate mdbox/sdbox/something for .EXPUNGED.

Aki Matt Bryant <mailto:matt@the-bryants.net> 24 May 2018 at 11:53 am So moving on from earlier issue now looking at converting mail inbox to mdbox and keeping lazy_expunge as mdbox also .. but again seeing some wierdness so questions ....

1. When i purge trash folder I seem to get 2 copies of the message in .EXPUNGED/Trash folder .. however if I set lazy_expunge_only_last_instance = yes then dont seem to get ANY copy .. just nothing.

2. If I go into Trash and delete a message ... then it does not get moved .. I assume that a delete in Trash is not actually an expunge on TB and hence does get caught by the plugin.

3. Since mdbox doesnt delte anything anyway until purged would it be better not to use lazy-expunge but just have a job that moves any messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. does doveadm move work with mdbox_deleted ???

any help appreciated

rgds

Matt