On Tue, 2010-03-09 at 16:40 +0100, Thomas Leuxner wrote:
> With the latest fix from Mercurial it does not crash anymore. The message 
> shows empty and the container in question 'm.59.broken' stays in the 
> 'storage' dir. Is this expected behavior and am I save to delete the broken 
> container, or how would I clean up the corruption?

See if "doveadm force-resync username inbox" helps? If not, see if the
message is still in m.59.broken file. If it's not there either, it
probably never got actually saved.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to