Process 75242 (in the mail log) was 100 lines of message-id=<> lines
from cleanup.  I'm guessing it's 100 of the messages that are stuck in
my queue and looking for a few of the ID's it seems like a good guess.

Whoooah a lot of output from dtruss (I can't even pipe it to a file)
so I'm not sure what you want me to do with that.  The output from
postcat is (its a little anonymized, so if the IP addresses don't look
right that's why):

*** ENVELOPE RECORDS /var/spool/postfix/maildrop/F423E1976D72 ***
message_size:          444129             556               1
     2          444129
message_arrival_time: Fri Aug  1 15:23:30 2008
create_time: Fri Aug  1 15:23:31 2008
named_attribute: rewrite_context=remote
sender:
named_attribute: log_client_address=10.10.10.1
named_attribute: log_message_origin=unknown[10.10.10.1]
named_attribute: log_helo_name=10.10.10.10
named_attribute: log_protocol_name=ESMTP
named_attribute: client_name=unknown
named_attribute: reverse_client_name=unknown
named_attribute: client_address=10.10.10.10
named_attribute: helo_name=10.10.10.10
named_attribute: client_address_type=2
named_attribute: notify_flags=1
named_attribute: dsn_orig_rcpt=rfc822;my_delivery_mail...@my_system
original_recipient: my_delivery_mail...@my_system
done_recipient: my_delivery_mail...@my_system
*** MESSAGE FILE END /var/spool/postfix/maildrop/F423E1976D72 ***


On Thu, Jan 7, 2010 at 1:37 PM, Victor Duchovni
<victor.ducho...@morganstanley.com> wrote:
> On Thu, Jan 07, 2010 at 01:25:01PM -0600, Wendigo Thompson wrote:
>
>> Woops, I meant to say: message_size_limit is zero.
>>
>> I went all verbose and looking at pickup logs for the specific queue
>> ID I mentioned earlier:
>> Jan  7 13:16:20 se001 postfix/pickup[57270]: warning: C9EBD24E12F23:
>> message has been queued for 521 days
>> Jan  7 13:16:20 se001 postfix/pickup[57270]: C9EBD24E12F23: uid=27
>> from=<> orig_id=F423E1976D72
>> Jan  7 13:16:20 se001 postfix/cleanup[75242]: C9EBD24E12F23:
>> message-id=<11eccdf1ff78c949b5011f37ba264e4619d4d...@10.1.1.1>
>>
>> After that all references to the new queue entry cease, and a minute
>> later the process starts over again with the original queue id
>> appearing to get a new ID, the warning about the message being queued
>> (as little as 2 days and as long as 521, depending on the message).  I
>> never see a delivery message -- which I see plenty of for other
>> messages coming in in real time.
>
> Any subsequent logging from or about process id "75242"? What happens
> if you also send a few messages via sendmail(1). Does the same
> cleanup process handle the new and old mail? In what order?
>
> Can you "dtruss -p 57270" and report a slice of the pickup/cleanup
> interaction after pickup opens the file "F423E1976D72"? It looks
> like this message has been "re-queued", it belongs to "_postfix".
>
> Can you show the envelope records (you can mask sender/recipient
> addresses if you wish):
>
>    # postcat /var/spool/postfix/maildrop/F423E1976D72 |
>        sed -e '/^\*\*\* MESSAGE CONT/,/^\*\*\* HEADER EXTR/d'
>
> Are there any undelivered recipients left in this queue-file?
>
> --
>        Viktor.
>
> Disclaimer: off-list followups get on-list replies or get ignored.
> Please do not ignore the "Reply-To" header.
>
> To unsubscribe from the postfix-users list, visit
> http://www.postfix.org/lists.html or click the link below:
> <mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
>
> If my response solves your problem, the best way to thank me is to not
> send an "it worked, thanks" follow-up. If you must respond, please put
> "It worked, thanks" in the "Subject" so I can delete these quickly.
>

Reply via email to