I'm wondering about the temper here, you got three responses in four days.
Where is that a lack of attention or "being ignored".

All I see is:
- Paride was asking for more info than "Something is happening to the 
dovecot-index file" which seems fine to me.
- Lucas later marked it invalid after your debugging showed that it doesn't 
appear as a bug in the dovecot code or its packaging.
- Rafael tried to explain options if you want a higher support level. You might 
not want that, but there is nothing bad in him telling you I'd think.

Finally you said " I will just compile it myself" - does that imply there is 
indeed a fix that makes it handle corrupted inboxes more gracefully? If so 
could you point to a commit or upstream discussion.
I'm asking as we are most likely going to bump 2.3.7.2 to 2.3.10 this cycle and 
if your fix is upstream we should get it by that for Ubuntu 20.10 and later. 
But furthermore the questions will then become if there is an isolated fix that 
is SRU-backportable - so if you have identified one please let us know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876537

Title:
  dovecot eating mail indexes /var/dovecot-index/user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1876537/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to