On 1/28/2007 9:24 PM, Claus Assmann wrote:
Wrt section "6.4. The Final Response Code":
Why do we need a final reply code? Isn't that code the same as the
minimum over the RCPT reply codes (at least wrt the reply code
severity)? Hence it is not need to send this reply code as it can
be deduced from the existing reply codes.
The final code is where the server says that it is taking responsibility
for the message. The delayed RCPT codes just report on whether or not the
content is acceptable for the associated recipient.
It's possible that the recipients will all accept the message, but the
server is still unable to accept the message for processing for some
reason (server going down, whatever).
PS: "response code" should be replaced by "reply code" in the draft
to match RFC2821.
will add that as well as the clarification above to the next draft
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg