index problems after update
aki.tuomi at open-xchange.com
Thu Feb 21 11:51:15 EET 2019
On 21.2.2019 10.53, Hajo Locke via dovecot wrote:
> Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:
>>> On 18 February 2019 09:28 Hajo Locke via dovecot
>>> <dovecot at dovecot.org> wrote:
>>> it seems we need a dovecot developers opinion. May be we hit a
>>> bug or cant help ourselves.
> Thanks for your answer.
>> Core dump with backtrace would help, if possible to acquire. Please
>> refer to https://dovecot.org/bugreport.html for information how to
>> get a core dump.
> Unfortunately its hard to get a backtrace because dovecot is not
> crashing. so it seems to be more a kind of logic problem in code and
> no unexpected situation.
> yesterday evening i had next incident. I upgraded from 188.8.131.52 to
> 184.108.40.206, but same behaviour. Also 220.127.116.11 is tricked by the broken
> index and delivers no new mails. it starts delivering if i delete
> index files. At this point i cant tell if 18.104.22.168 also has same bug
> and writes a damaged index, but very likely. We dont know this
> problems with 2.2.22, between 2.2.22 and 22.214.171.124 a change on
> mbox-index code must happend which leads to this big problem. So imapd
> cant do what he was created for.
> For next incident i prepared a 126.96.36.199 on base of Ubuntu 18.10 and
> will try this. In my opinion this is a major problem and i expect a
> lot of affected people with version > 2.2.22 and classic mbox-storage.
We consider mbox + procmail setup somewhat edge case, and if the core
dump does not point into something more generic, it will probably not
get fixed. It is more likely to have this working if you use
dovecot-lda/lmtp with sieve instead of procmail.
More information about the dovecot