Hello,
I have two postfix systems which generate a lot of double bounces. I was
able to extract such an e-mail using wireshark:
220 erld671x.erlf.siemens.de ESMTP Postfix
EHLO erld604x.erlf.siemens.de
250-erld671x.erlf.siemens.de
250-PIPELINING
250-SIZE 104857600
250-VRFY
250-ETRN
250 8BITMIME
MAIL FROM:<double-bou...@erlf.siemens.de> SIZE=1191
RCPT TO:<postmas...@erld671x.erlf.siemens.de>
DATA
250 Ok
250 Ok
354 End data with <CR><LF>.<CR><LF>
Received: from erld671x.erlf.siemens.de (erld671x.erlf.siemens.de
[194.138.228.10])
.by erld604x.erlf.siemens.de (Postfix) with ESMTP id 9DF6A84657
.for <postmas...@erld671x.erlf.siemens.de>; Tue, 10 Feb 2009 06:32:40 +0100
(CET)
Received: by erld671x.erlf.siemens.de (Postfix)
.id AE06C4569B11; Tue, 10 Feb 2009 06:26:44 +0100 (CET)
Date: Tue, 10 Feb 2009 06:26:44 +0100 (CET)
From: mailer-dae...@erlf.siemens.de (Mail Delivery System)
To: postmas...@erlf.siemens.de (Postmaster)
Subject: Postfix SMTP server: errors from
erld603x.erlf.siemens.de[194.138.228.203]
Message-Id: <20090210052644.ae06c4569...@erld671x.erlf.siemens.de>
Transcript of session follows.
Out: 220 erld671x.erlf.siemens.de ESMTP Postfix
In: EHLO erld603x.erlf.siemens.de
Out: 250-erld671x.erlf.siemens.de
Out: 250-PIPELINING
Out: 250-SIZE 104857600
Out: 250-VRFY
Out: 250-ETRN
Out: 250 8BITMIME
In: MAIL FROM:<double-bou...@erlf.siemens.de> SIZE=1191
Out: 452 Insufficient system storage
In: RCPT TO:<postmas...@erld671x.erlf.siemens.de>
Out: 503 Error: need MAIL command
In: DATA
Out: 503 Error: need RCPT command
In: RSET
Out: 250 Ok
In: QUIT
Out: 221 Bye
.
QUIT
250 Ok: queued as BBB6B4599763
221 Bye
What I don't get here is that the postfix version on erld604x does seem
to ignore the tempfailure on erld671x (452 Insufficient system storage)
and tries to continue with the SMTP dialog. Now it gets an error (503
Error: need MAIL command) but only because it ignores the tempfailure
in the first case and generates a double bounce.
I just deleted 150000 messages on each of our mail relays and 20000 on
erld671x. Can someone explain me what goes wrong here and if it is a
configuration problem or a known problem of postfix version 2.1.1?
Thomas
