Yes I know that. Look this is the mailer-daemon sent by postfix (bold
line at the end of the message). In the notification only "552
Requested ..." must appear, why 250-PIPELINING too?
"Received: by relay.com (Postfix, from userid 500)
id 9E06D8E87A; Wed, 20 Jun 2012 11:33:58 +0200 (CEST)
Received: by relay.com (Postfix)
id 91CD88E87B; Wed, 20 Jun 2012 11:33:58 +0200 (CEST)
Date: Wed, 20 Jun 2012 11:33:58 +0200 (CEST)
From: Mail Delivery Service <postmas...@relay.com>
Subject: Undelivered Mail Returned to Sender
To: +33612345678/TYPE=p...@destination.com
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="884C98E87A.1340184838/relay.com"
Message-Id: <20120620093358.91cd88e...@relay.com>
This is a MIME-encapsulated message.
--884C98E87A.1340184838/relay.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii
This is the mail system at host relay.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<+33612374185/TYPE=p...@origin.com>: host mms11.toto.fr[81.52.180.21] said:
250-PIPELINING 552 Requested mail action aborted: exceeded storage
allocation (in reply to MAIL FROM command)"
Le mercredi 20 juin 2012 à 10:10 -0400, Wietse Venema a écrit :
> Wael MANAI:
> > What do you mean "security software"? It's postfix which adds
> > 250-PIPELINING...
>
> You are mistaken.
>
> The "security" software sends
>
> 250 whatever
> 250-PIPELINING
> 552 whatever
>
> The 250-PIPELINING is NOT PART OF THE EHLO RESPONSE.
>
> In RFC 5321, section "4.2.1. Reply Code Severities and Theory"
>
> The format for multiline replies requires that every line, except the
> last, begin with the reply code, followed immediately by a hyphen,
> "-" (also known as minus), followed by text. The last line will
> begin with the reply code, followed immediately by <SP>, optionally
> some text, and <CRLF>. As noted above, servers SHOULD send the <SP>
> if subsequent text is not sent, but clients MUST be prepared for it
> to be omitted.
>
> Wietse
