Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-06 Thread Elimar Riesebieter
Control: severity -1 normal
Control: tags -1 +moreinfo

* Ben Elliston  [2017-10-06 08:41 +1100]:

> As a workaround, I have switched to using the IMAP server that runs on
> localhost.

This I don't understand...

Elimar
-- 
  Do you smell something burning or is it me?



signature.asc
Description: PGP signature


Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-05 Thread Ben Elliston
As a workaround, I have switched to using the IMAP server that runs on
localhost.


signature.asc
Description: PGP signature


Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-05 Thread Elimar Riesebieter
* Ben Elliston  [2017-10-06 08:04 +1100]:

> On Thu, Oct 05, 2017 at 11:00:10PM +0200, Elimar Riesebieter wrote:
> 
> > How does the corruption looks like?
> 
> One partial message in my mbox, then a From line for the start of the
> next message, and the rest of the mbox is OK.

Did you ever tried maildir instead of mbox?

> 
> > Well, is it possible to open your mbox?
> 
> Yes, but not in mutt.

Hmm, but with which?

> > Maybe your filesystem is full? What tells
> > $ df
> 
> 13% in /var/mail.
ok

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)


signature.asc
Description: PGP signature


Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-05 Thread Ben Elliston
On Thu, Oct 05, 2017 at 11:00:10PM +0200, Elimar Riesebieter wrote:

> How does the corruption looks like?

One partial message in my mbox, then a From line for the start of the
next message, and the rest of the mbox is OK.

> Well, is it possible to open your mbox?

Yes, but not in mutt.

> Maybe your filesystem is full? What tells
> $ df

13% in /var/mail.


signature.asc
Description: PGP signature


Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-05 Thread Elimar Riesebieter
* Ben Elliston  [2017-10-06 07:36 +1100]:

> Hi Ellmar
> 
> > > mutt is corrupting my mbox when writing back the mbox after deleting 
> > > messages
> > > (and quiting mutt).  I have a partial message in the start of the mbox, 
> > > which
> > > makes mutt unable to read any of the messages in the mbox.
> > 
> > The following predication I don't understand?
> 
> mutt is intermittenly corrupting my mbox when it saves out a modified
> mailbox (ie I have deleted some messages).  It happens seemingly
> randomly.

How does the corruption looks like?
Well, is it possible to open your mbox?
Maybe your filesystem is full? What tells
$ df 

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)


signature.asc
Description: PGP signature


Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-05 Thread Ben Elliston
Hi Ellmar

> > mutt is corrupting my mbox when writing back the mbox after deleting 
> > messages
> > (and quiting mutt).  I have a partial message in the start of the mbox, 
> > which
> > makes mutt unable to read any of the messages in the mbox.
> 
> The following predication I don't understand?

mutt is intermittenly corrupting my mbox when it saves out a modified
mailbox (ie I have deleted some messages).  It happens seemingly
randomly.

> Could you please describe more precisely what is corrupting your
> mbox?

I don't know, sorry.  Hence my bug report!

> What tells:
> $ mutt -D | grep mbox_type

mbox_type=mbox

> What sort of messages did you deleted?

Just the usual spam. :-) ie. small plaintext messages.

Thanks,
Ben


signature.asc
Description: PGP signature


Bug#877803: [Pkg-mutt-maintainers] Bug#877803: mutt: corrupting mbox

2017-10-05 Thread Elimar Riesebieter
Hi Ben,

* Ben Elliston  [2017-10-06 06:46 +1100]:

> Package: mutt
> Version: 1.8.3+neomutt20170609-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> mutt is corrupting my mbox when writing back the mbox after deleting messages
> (and quiting mutt).  I have a partial message in the start of the mbox, which
> makes mutt unable to read any of the messages in the mbox.

The following predication I don't understand? 

> This has only just started happening, but that could just be a coincidence.

Could you please describe more precisely what is corrupting your
mbox?

What tells:

$ mutt -D | grep mbox_type

What sort of messages did you deleted?
What is your definition of the "partial message"?

Elimar
-- 
  Do you smell something burning or is it me?