On Thu, 25 Mar 2004, Cormack, Ken wrote: Hello Ken,
please forgive my ignorance, but what problem is this thread about actually? And why is pipelining a problem with greylisting only? This kicks in whenever the server (temp-) fails a recipient, but accepts the SMTP dialogue in advance (aka pipelining). What do I miss? Actually, if you read the SMTP RFC, the client may always sent the whole message to your server, regardless wether or not it recieved a negative response, it's the duty of the server to act as a bitbucket in this case. However, does this paragraphe RFC2920: "Client SMTP implementations that employ pipelining MUST check ALL statuses associated with each command in a group. For example, if none of the RCPT TO recipient addresses were accepted the client must then check the response to the DATA command -- the client cannot assume that the DATA command will be rejected just because none of the RCPT TO commands worked. If the DATA command was properly rejected the client SMTP can just issue RSET, but if the DATA command was accepted the client SMTP should send a single dot." imply that the client have to wait for the response of DATA? Bye, -- Steffen Kaiser _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
