On Sun, 10 Aug 2008, Pete Resnick wrote: > > Take the following example: > > S: 220 foo.com Simple Mail Transfer Service Ready > C: EHLO bar.com > S: 250-foo.com greets bar.com > S: 250-VRFY > S: 250 HELP > C: VRFY [EMAIL PROTECTED] > S: 250 <[EMAIL PROTECTED]> > C: MAIL FROM:<[EMAIL PROTECTED]> > S: 250 OK > C: VRFY [EMAIL PROTECTED] > S: 250 <[EMAIL PROTECTED]> > C: RCPT TO:<[EMAIL PROTECTED]> > S: 450 Can't send to him right now > C: DATA > S: 354 Start mail input; end with <CRLF>.<CRLF> > C: Blah blah blah... > C: ...etc. etc. etc. > C: . > S: 250 OK > C: QUIT > S: 221 foo.com Service closing transmission channel > > According to 4.2.5 above, since [EMAIL PROTECTED] exists, and foo.com (the > server) > has sent back a 250 to the DATA command, foo.com (the server) now has > responsibility for delivering the message to [EMAIL PROTECTED] (retrying if > necessary) and bar.com (the client) SHOULD NOT attempt to retry delivery to > [EMAIL PROTECTED] Is this the correct interpretation?
I agree with you that this interpretation is wrong. It is also inconsistent with the requirements in the PIPELINING spec RFC 2920. Tony. -- f.anthony.n.finch <[EMAIL PROTECTED]> http://dotat.at/ FITZROY: WEST BACKING SOUTHWEST 4 OR 5, INCREASING 6 OR 7. MODERATE OR ROUGH, OCCASIONALLY VERY ROUGH IN NORTH. RAIN OR SHOWERS. MODERATE OR GOOD, OCCASIONALLY POOR.
