On the flip side is this:
4.5.3.2.6. DATA Termination: 10 Minutes.
This is while awaiting the "250 OK" reply. When the receiver gets
the final period terminating the message data, it typically performs
processing to deliver the message to a user mailbox. A spurious
timeout at this point would be very wasteful and would typically
result in delivery of multiple copies of the message, since it has
been successfully sent and the server has accepted responsibility for
delivery. See Section 6.1 for additional discussion.
Tony Hansen
tony(_at_)att(_dot_)com
On 8/9/2010 8:30 PM, Dave CROCKER wrote:
On 8/9/2010 5:25 PM, Steve Atkins wrote:
Can folks offer pointers to normative language?
Tail end of section 6.1 of 5321:
"To avoid receiving duplicate messages as the result of timeouts, a
receiver-SMTP MUST seek to minimize the time required to respond to
the final<CRLF>.<CRLF> end of data indicator. "
However the same section also says:
Thanks!
And, yeah, it might be worth reviewing both normative directives.
d/