Michael Monnerie wrote:
Dear list, this message was generated by the receiver postfix (2.2.1),
where the sender postfix was 2.3.2 from openSUSE 10.2. The receiver's
disk was temporarily full, which it announced correctly, but the sender
ignored it and continued to try to send. Is this normal behaviour or did
I configure something wrong? I thought it should stop to try after the
452 message.
pipelining in action. the order of commands and responses as you see
them on the console is not the same as what you would have seen on the
ether.
I don't really care about the message, but in this case the problem is,
that the receiver sends this warning mail to root, which is on the same
storage and therefore only adds to the problem. So either the sender
postfix should behave and not continue after 452, or the receiver should
not generate that message. Is there a fix in recent postfix?
mfg zmi
---------- Forwarded message from Mail Delivery System: ----------
Betreff: Postfix SMTP server: errors from
protegate5.zmi.at[212.69.162.205]
Datum: Montag, 22. September 2008
Von: Mail Delivery System <[EMAIL PROTECTED]>
An: Postmaster <[EMAIL PROTECTED]>
Transcript of session follows.
Out: 220 power2u.goelsen.net ESMTP it-management.at hardened Postfix
(2.2.1).
By using this server you agree to be scanned for UCE.
In: EHLO protegate5.zmi.at
Out: 250-power2u.goelsen.net
Out: 250-PIPELINING
Out: 250-SIZE 104857600
Out: 250-ETRN
Out: 250-STARTTLS
Out: 250 8BITMIME
In: STARTTLS
Out: 220 Ready to start TLS
In: EHLO protegate5.zmi.at
Out: 250-power2u.goelsen.net
Out: 250-PIPELINING
Out: 250-SIZE 104857600
Out: 250-ETRN
Out: 250-AUTH LOGIN
Out: 250-AUTH=LOGIN
Out: 250 8BITMIME
In: MAIL FROM:<[EMAIL PROTECTED]> SIZE=13344 BODY=8BITMIME
Out: 452 Insufficient system storage
In: RCPT TO:<[EMAIL PROTECTED]>
Out: 503 Error: need MAIL command
In: DATA
Out: 503 Error: need RCPT command
In: RSET
Out: 250 Ok
In: QUIT
Out: 221 Bye
-------------------------------------------------------
