Re: Corrupt message

2020-02-13 Thread Doug Hardie
> On Feb 13, 2020, at 16:05, Wietse Venema wrote: > > Doug Hardie: >> Thanks. I finally understand it. Interestingly enough, both of >> the corrupt/* files had zero length. > > Did the files have permissions rwx? Then at some point they contained > an email message, before the file system l

Re: Corrupt message

2020-02-13 Thread Wietse Venema
Doug Hardie: > Thanks. I finally understand it. Interestingly enough, both of > the corrupt/* files had zero length. Did the files have permissions rwx? Then at some point they contained an email message, before the file system lost the data. Wietse

Re: Corrupt message

2020-02-13 Thread Doug Hardie
On 13 February 2020, at 03:28, Viktor Dukhovni wrote: > > On Wed, Feb 12, 2020 at 07:43:59PM -0800, Doug Hardie wrote: > >> I seem to have a couple corrupt messages. Restarting postfix gives: >> >> service postfix restart >> postfix/postfix-script: stopping the Postfix mail system >> postfix/

Re: Corrupt message

2020-02-13 Thread Viktor Dukhovni
On Wed, Feb 12, 2020 at 07:43:59PM -0800, Doug Hardie wrote: > I seem to have a couple corrupt messages. Restarting postfix gives: > > service postfix restart > postfix/postfix-script: stopping the Postfix mail system > postfix/postfix-script: warning: damaged message: corrupt/44t83n4KNbz2fjQV >

Corrupt message

2020-02-12 Thread Doug Hardie
/46jP9V452yz2fjRb postfix/postfix-script: starting the Postfix mail system I have tried postsuper -d 44t83n4KNbz2fjQV and it gives no errors, but doesn't remove the corrupt message. I have found both of them in my cur mailbox and they are unimportant so I would like to get rid of them. Clearly I am mi