On 13 February 2020, at 03:28, Viktor Dukhovni <postfix-us...@dukhovni.org> 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/postfix-script: warning: damaged message: corrupt/44t83n4KNbz2fjQV >> postfix/postfix-script: warning: damaged message: corrupt/46jP9V452yz2fjRb >> postfix/postfix-script: starting the Postfix mail system > > 1. Use "postcat" to check that the partially collected content has > no value: > > # postcat /var/spool/postfix/corrupt/$qid > > SYNOPSIS > postsuper > [-psSv] [-c config_dir] [-d queue_id] > [-h queue_id] [-H queue_id] > > [-r queue_id] [directory ...] > ... > > -d queue_id > Delete one message with the named queue ID from the named mail > queue(s) (default: hold, incoming, active and deferred). > ... > > So postsuper(1) does not look in the "corrupt" directory, but even if > you explicitly try: > > # postsuper -d $qid corrupt > > you'll get an error message, because "corrupt" is not a message queue, > it is just a directory, with detritus, that may or may not be safe to > remove. Therefore, once you're sure you want to remove it: > > 2. # /bin/rm /var/spool/postfix/corrupt/$qid > > -- > Viktor.
Thanks. I finally understand it. Interestingly enough, both of the corrupt/* files had zero length. -- Doug
