On 8/17/11 11:40 AM, John C Klensin wrote:
--On Tuesday, August 16, 2011 22:58 -0700 "Murray S. Kucherawy"
<msk(_at_)cloudmark(_dot_)com> wrote:
-----Original Message-----
From: owner-ietf-smtp(_at_)mail(_dot_)imc(_dot_)org
[mailto:owner-ietf-smtp(_at_)mail(_dot_)imc(_dot_)org] On Behalf Of Murray S.
Kucherawy Sent: Tuesday, August 16, 2011 10:03 PM
To: ietf-smtp(_at_)imc(_dot_)org
Subject: RE: Mail Data termination
SMTP has always held
that the client is responsible for retrying delivery until
the server gives a 250 or 5xx back after DATA, at which point
the server is now responsible for the message.
Sorry, that's not quite right:
SMTP has always held that the client is responsible for
retrying delivery until the server gives a 250 or 5xx back
after DATA, at which point the server has either accepted or
finally rejected the message; if the message is accepted, the
server is now responsible for its relay or delivery.
Still not quite right.
"...if the message is accepted, the server is now
responsible for its relay, delivery, or rejection via an
NDN ('bounce') message."
(At the risk of opening up a can of worms :-)
How does the 'discard' action of RFC5617 (DKIM ADSP) fit into this
picture? Although RFC5321 and RFC5617 operate on different protocol
layers, in real life the two are often intertwined by way of MTA milter
callouts during SMTP DATA phase.
Maybe we should rephrase the above to:
"...if the message is accepted, the server is now
responsible for its disposition."
/rolf