Re: feature request: postsuper -s should delete orphaned defer/ and bounce/ files

From: Meng Weng Wong (no email)
Date: Sat Dec 01 2001 - 20:36:27 EST


On Fri, Nov 30, 2001 at 04:29:15PM -0500, Meng Weng Wong wrote:
| On Fri, Nov 30, 2001 at 03:44:53PM -0500, Wietse Venema wrote:
| | Why do you have so many orphaned files? "postsuper -d" deletes
| | defer/bounce files before deleting the message file.
|
| These orphaned files were generated during the normal course
| of operation, not because postsuper -d failed to delete them.

    20011201-20:04:15 root at granite:/var/tmp/bounce# ls -1 | wc -l
       5433
    20011201-20:06:16 root at granite:/var/tmp/bounce# cat * | sort | uniq -c
       5433
       5433 <unknown>: Message processing aborted: No recipients specified
    20011201-20:06:24 root at granite:/var/tmp/bounce#

it happened again. all the bounce messages were traced to
a single cause:

    20011201-19:52:28 mengwong at dumbo:/shared/logs/syslog/maillogs% ~/src/sql/scripts/tracemail -search='message-id=<>' 20011129/mail.info.*
    Nov 29 11:25:21 granite/granite postfix/cleanup[55074]: 0D1C77DF2A: message-id=<>
    Nov 29 11:25:21 granite/granite postfix/qmgr[55025]: 0D1C77DF2A: from=<>, size=657, nrcpt=1 (queue active)
    Nov 29 11:31:54 granite/granite postfix/smtpd[57133]: 965487DF43: client=localhost[127.0.0.1]
    Nov 29 11:31:54 granite/granite postfix/cleanup[57159]: 965487DF43: message-id=<>
    Nov 29 11:31:54 granite/granite postfix/qmgr[57078]: 965487DF43: from=<>, size=893, nrcpt=1 (queue active)

the successful "to=" delivery lines may have been lost by
syslog. then the bounces begin.

    Nov 29 11:32:41 granite/granite postfix/pickup[57077]: 35A277DFBF: uid=1001 from=<>
    Nov 29 11:32:41 granite/granite postfix/cleanup[57370]: 35A277DFBF: message-id=<>
    Nov 29 11:32:41 granite/granite postfix/cleanup[57370]: 35A277DFBF: to=<unknown>, relay=cleanup, delay=47, status=bounced (Message processing aborted: No recipients specified)

    Nov 29 11:32:45 granite/granite postfix/pickup[57077]: BD1FA7DFF6: uid=1001 from=<>
    Nov 29 11:32:45 granite/granite postfix/cleanup[57368]: BD1FA7DFF6: message-id=<>
    Nov 29 11:32:45 granite/granite postfix/cleanup[57368]: BD1FA7DFF6: to=<unknown>, relay=cleanup, delay=51, status=bounced (Message processing aborted: No recipients specified)

    Nov 29 11:33:41 granite/granite postfix/pickup[57077]: 4F9777DF0A: uid=1001 from=<>
    Nov 29 11:33:41 granite/granite postfix/cleanup[57361]: 4F9777DF0A: message-id=<>
    Nov 29 11:33:45 granite/granite postfix/cleanup[57361]: 4F9777DF0A: to=<unknown>, relay=cleanup, delay=107, status=bounced (Message processing aborted: No recipients specified)

    20011201-20:11:57 root at granite:/var/spool/postfix# postcat maildrop/0D1C77DF2A |less
    *** ENVELOPE RECORDS maildrop/0D1C77DF2A ***
    message_size: 657 135 1
    arrival_time: Thu Nov 29 11:24:56 2001
    sender:
    done:
    *** MESSAGE CONTENTS maildrop/0D1C77DF2A ***
    Received: from mail.goyapr.com (unknown [200.50.31.223])
            by granite.pobox.com (Postfix) with ESMTP id 0D1C77DF2A
            for <>; Thu, 29 Nov 2001 11:24:56 -0500 (EST)
    Received: from sgqvi (localhost [127.0.0.1])
            by mail.goyapr.com (8.9.3/8.9.3) with ESMTP id BAA10828;
            Fri, 30 Nov 2001 01:00:29 -0400
    Date: Fri, 30 Nov 2001 01:00:29 -0400
    From:
    Message-Id: <200111300500 dot BAA10828 at mail dot goyapr dot com>
    Subject: Are you kidding?
    To: undisclosed-recipients:;

    Hi there,

    Want to see some nasty hot action, cum take a look at this amazing site

the only related log entries are

    20011201-20:14:00 mengwong at dumbo:/shared/logs/syslog/maillogs% egrep '965487DF43|0D1C77DF2A' 20011130/mail.*.<11->
    20011130/mail.warning.11:Nov 30 11:00:16 granite/granite postfix/pickup[35995]: warning: maildrop/0D1C77DF2A: Error writing message file
    20011130/mail.warning.11:Nov 30 11:01:16 granite/granite postfix/pickup[35995]: warning: maildrop/0D1C77DF2A: Error writing message file
    20011130/mail.warning.11:Nov 30 11:02:16 granite/granite postfix/pickup[35995]: warning: maildrop/0D1C77DF2A: Error writing message file
    20011130/mail.warning.11:Nov 30 11:03:16 granite/granite postfix/pickup[35995]: warning: maildrop/0D1C77DF2A: Error writing message file
    20011130/mail.warning.11:Nov 30 11:04:16 granite/granite postfix/pickup[2115]: warning: maildrop/0D1C77DF2A: Error writing message file
    20011130/mail.warning.11:Nov 30 11:05:16 granite/granite postfix/pickup[2115]: warning: maildrop/0D1C77DF2A: Error writing message file

a number of other messages have been sitting in maildrop:

    20011201-20:23:58 root at granite:/var/spool/postfix/maildrop# ll
    total 20
    drwx-wx-wt 2 postfix wheel 512 Dec 1 20:23 ./
    drwxr-xr-x 14 root wheel 512 Jan 10 2001 ../
    -rwx------ 1 postfix wheel 2259 Nov 29 11:31 06BE77DF00*
    -rwx------ 1 postfix wheel 821 Nov 29 11:31 0D1C77DF2A*
    -rwx------ 1 postfix wheel 2082 Nov 29 11:31 57B8C7DF01*

    20011201-20:25:33 root at granite:/var/spool/postfix/maildrop# mailq | head
    -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
    0D1C77DF2A 657 Thu Nov 29 11:24:56

    06BE77DF00 2033 Thu Nov 29 11:29:11 bounce-debian-user=lyons=

    57B8C7DF01 1846 Thu Nov 29 11:27:24 bounce-debian-laptop=humming=

    4D3097DF36* 2174 Sat Dec 1 20:25:29
                                             

those messages all appear to be in a done state with no
recipients remaining. shouldn't qmgr just discard them
instead of attempting delivery? very odd.

i've moved them out of maildrop.

mail_version = Snapshot-20010808

i don't think there's any configuration variable that can
affect this particular bit of qmgr logic so i'm omitting
postconf -n.

-
To unsubscribe, send mail to with content
(not subject): unsubscribe postfix-users








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD