Well, good news and bad news.
I backed up the indexes (presumably the ~/.mbox/.imap/*) and started
tinkering:
dovecotadm -u username INBOX
did nothing, it didn't event produce a message in the log, and the
indexes were not updated. I deleted the indexes, and let dovecot rebuild
them. This fixed my inbox (good news), unfortunately, even after copying
the backed-up files back I can no longer reproduce the problem.
I looked around but didn't find any other files that dovecot could be
modifying, or did I miss something? Anyway, I think the problem will get
back soon, as it did many times before.
On Mon, Aug 22, 2016 at 04:18:58PM +0300, Aki Tuomi
wrote:>
>
> On 22.08.2016 15:10, Ladislav Laska wrote:
> > Not really. I tried copying the inbox and wanted to delete half the
> > messages to filter out the problematic one, but opening the copy works
> > fine.
> >
> > What could be the culprit? Does dovecot keep some index that might be
> > corrupted?
> >
> > On Mon, Aug 22, 2016 at 02:43:01PM +0300, Aki Tuomi wrote:
> >> On 21.08.2016 13:59, Ladislav Laska wrote:
> >>> Hi!
> >>>
> >>> dovecot -n and backtrace are both attached in my original
email, due to their
> >>> size. Did the attachments not arrive?
> >>>
> >>> The relevant log does not contain much more than the trace,
but here it is:
> >>>
> >> Any chance to get the offending email somehow?
> >>
> >> Aki
> It is possible. Can you try backing up your current index and running
> doveadm index -u yourusername?
>
> Aki
--
S pozdravem Ladislav "Krakono?" L?ska
http://www.krakonos.org/