RFC772 - Mail Transfer Protocol(2)

时间:2005-02-11 来源: 作者: 点击:
S: MRCP TO:Foo@Y CRLF R: 200 OK S: MRCP TO:Raboof@Y CRLF R: 553 No such user here S: MRCP TO:bar@Y CRLF R: 200 OK S: MRCP TO:@Y,@X,fubar@Z CRLF R: 200 OK Note that the failure of "Raboof" has no effe
  

S: MRCP TO:<Foo@Y> <CRLF>
R: 200 OK

S: MRCP TO:<Raboof@Y> <CRLF>
R: 553 No such user here

S: MRCP TO:<bar@Y> <CRLF>
R: 200 OK

S: MRCP TO:<@Y,@X,fubar@Z> <CRLF>
R: 200 OK

Note that the failure of "Raboof" has no effect on the storage of
mail for "Foo", "bar" or the mail to be forwarded to "fubar@Z"
through host "X". Now the message text is furnished, by giving a
MAIL command with no "TO" argument.

S: MAIL FROM:<waldo@A><CRLF>
R: 354 Type mail, ended by <CRLF>.<CRLF>
S: Blah blah blah blah....etc. etc. etc.
S: <CRLF>.<CRLF>
R: 250 Mail sent

The mail text has now been sent to "Foo" and "bar" as well as
forwarded to "fubar@Z".

29

September 1980 RFC772
Mail Transfer Protocol

APPENDIX B

Example of MRSQ T (Text-first)

Using the same message as the previous example to establish that the
receiver implements MRSQ.

S: MRSQ ? <CRLF>
R: 215 T Text first, please

MRSQ is indeed implemented, and the receiver says that it prefers
"T", but that needn't stop the sender from trying something else.

S: MRSQ R <CRLF>
R: 501 Sorry, I really can't do that

It's possible that it could have understood "R" also, but in general
it's best to use the "preferred" scheme, since the receiver knows
which is most efficient for its particular site.

S: MRSQ T <CRLF>
R: 200 OK, using that scheme

Scheme "T" is now selected, and the message text is sent by giving a
mail command with no "TO" argument.

S: MAIL FROM:<WALDO@A><CRLF>
R: 354 Type mail, ended by <CRLF>.<CRLF>
S: Blah blah blah blah....etc. etc. etc.
S: <CRLF>.<CRLF>
R: 250 Mail stored

Now recipients can be specified.

S: MRCP TO:<Foo@Y> <CRLF>
R: 250 Stored mail sent

S: MRCP TO:<Raboof@Y> <CRLF>
R: 553 No such user here

S: MRCP TO:<bar@Y> <CRLF>
R: 250 Stored mail sent

S: MRCP TO:<@Y,@X,fubar@Z> <CRLF>
R: 200 OK

30

RFC772 September 1980
Mail Transfer Protocol

The text has now been sent to "Foo" and "bar" at host "Y" and will be
forwarded to "fubar@Z" through host "X", and still remains stored. A
new message can be sent with another MAIL/MRCP ... sequence, but a
careful sender would reset the state using the exchange below.

S: MRSQ ? <CRLF>
R: 215 T Text first, please

Which resets the state without altering the scheme in effect.
------分隔线----------------------------
顶一下
(0)
0%
踩一下
(0)
0%
------分隔线----------------------------
最新评论 查看所有评论
发表评论 查看所有评论
请自觉遵守互联网相关的政策法规,严禁发布色情、暴力、反动的言论。
评价:
表情:
用户名: 密码: 验证码:
推荐内容