[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-14 Thread Rafael David Tinoco
There is a very similar (to yours) problem described here: https://dovecot.org/pipermail/dovecot/2014-May/095998.html one of the developers tell end-user to move away from mbox, and there seems to exist a correct answer stating that mbox is a supported format and there is no current documentation

Re: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-12 Thread Robert Dinse
At this point this is what I know.  There was manual intervention on behalf of a user that ended up with an extra space in the box.  This caused dovecot to blow up with no real intelligent error.  It should have given some error like mail header corrupt or some such.  Second, it seems to be doing s

[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-12 Thread Lucas Kanashiro
Hi Robert, Sorry if you felt ignored here but it was not the case, we are just trying to make sure your bug report is actionable. I did not quite understand your problem considering you mentioned in Comment #3 it was an issue due to a manual intervention in your mailbox. Are you talking about a f

Re: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-11 Thread Robert Dinse
On Mon, 11 May 2020, Christian Ehrhardt  wrote: > Date: Mon, 11 May 2020 11:38:01 - > From: Christian Ehrhardt  <1876...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user > > I'm wonde

[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-11 Thread Christian Ehrhardt 
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 yo

Re: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-08 Thread Robert Dinse
1876537] Re: dovecot eating mail indexes /var/dovecot-index/user > > Hello Robert, > > This is a community supported bug system and sometimes bugs don't get > expected visibility for many reasons. If you're looking for support > services, with different support levels an

[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-07 Thread Rafael David Tinoco
Hello Robert, This is a community supported bug system and sometimes bugs don't get expected visibility for many reasons. If you're looking for support services, with different support levels and expected servicing times, you can always look for Ubuntu Advantage options: https://ubuntu.com/legal/

Re: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-05 Thread Robert Dinse
o.com > Subject: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user > > ** Changed in: dovecot (Ubuntu) > Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.lau

[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-05 Thread Lucas Kanashiro
** Changed in: dovecot (Ubuntu) Status: Incomplete => Invalid -- 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 notif

Re: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-04 Thread Robert Dinse
ay 2020 16:08:54 - > From: Paride Legovini > Reply-To: Bug 1876537 <1876...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user > > Thanks Robert for taking the time to report this bug. There isn

[Bug 1876537] Re: dovecot eating mail indexes /var/dovecot-index/user

2020-05-04 Thread Paride Legovini
Thanks Robert for taking the time to report this bug. There isn't really enough information here for a developer to confirm this issue is a bug, or to begin working on it. Could you try to dig a bit more and try to understand if anything useful gets logged? Best of all would be to have some steps t