lazy_expunge + mdbox

[fernando.figaro at uol.com.br]

It appears to me that this issue is related to how lazy_expunge and last_instance work with mdbox - that is different from maildir.
 
With maildir, the message is moved to the expunged namespace only when the last copy is removed (example: from trash folder).

With mdbox, first time when you move message from one folder to another, dovecot creates a copy in the expunge namespace. When you delete messages or expunge them from Trash folder (example, nightly 'doveadm expunge' cronjob) they are simply deleted because they already have copies at expunged namespace.
 
@Timo, is that correct ? This is what I could understand from my tests.
 
Thanks,
Fernando





De: fernando.figaro at uol.com.br
Enviada: Quarta-feira, 4 de Fevereiro de 2015 23:15
Para: dovecot at dovecot.org
Assunto: lazy_expunge + mdbox

Hi,
 
I'm studying an issue related to mdbox and lazy_expunge. If it is active in the imap configuration, when you delete a message (copy to new folder + expunge old folder), a copy is also sent to the expunge namespace.
 
I realize that is something related to mdbox and lazy_expunge_only_last_instance and found almost no references except this one (http://hg.dovecot.org/dovecot-2.2/file/24d6708cea76/TODO):
 
lazy_expunge_only_last_instance=yes + mdbox doesn't work, because refcounts don't update immediately

One other suggestion I found was to disable 'move' capability.

Does anyone has other news regarding this issue ?

Thanks,
Fernando