#17160 closed enhancement (fixed)

postfix-3.7.3

Reported by: Bruce Dubbs Owned by: thomas
Priority: normal Milestone: 11.3
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

New point version.

Change History (2)

comment:1 by thomas, 19 months ago

Owner: changed from blfs-book to thomas
Status: newassigned

Fixed in Postfix 3.7.3:

This fixes a bug where some messages were not delivered after "warning: Unexpected record type 'X'.

Such messages were moved to the "corrupt" queue directory, where they may still be found. See below for instructions to deal with these falsely flagged messages.

This problem could happen for messages with 5000 or more recipients, or with fewer recipients on a busy mail server. The problem was first reported by Frank Brendel, and the error conditions were first reproduced by John Alex.

To find out if you have messages flagged as "corrupt", you can use the "postfix check" command.

Execute as root:

postfix check

Look for warnings like this:

postfix/postfix-script: warning: damaged message: corrupt/<filename> A message in the "corrupt" queue directory may be inspected with the "postcat" command.

Execute as root:

postcat /var/spool/postfix/corrupt/<filename>  

If delivery of the file is still desired, the file can be moved back to the "incoming" queue after updating Postfix and executing "postfix reload".

Execute as root:

mv /var/spool/postfix/corrupt/<filename> /var/spool/postfix/incoming/

If bouncing the message is still desired, the message may be moved to the "hold" queue and expired there, so that Postfix will return it to the sender.

Execute as root:

mv /var/spool/postfix/corrupt/<filename> /var/spool/postfix/hold/
postsuper -f <filename>

Note: this does not work with programs such as MailScanner that use the "hold" queue for their own purposes.

comment:2 by thomas, 19 months ago

Resolution: fixed
Status: assignedclosed

Fixed in [c06f7bec5d]

Note: See TracTickets for help on using tickets.