|
|
1.1 root 1: @(#) sendmail.hf 4.2 6/7/85
2: cpyr
3: cpyr Sendmail
4: cpyr Copyright (c) 1983 Eric P. Allman
5: cpyr Berkeley, California
6: cpyr
7: cpyr Copyright (c) 1983 Regents of the University of California.
8: cpyr All rights reserved. The Berkeley software License Agreement
9: cpyr specifies the terms and conditions for redistribution.
10: cpyr
11: cpyr @(#)sendmail.hf 4.2 (Berkeley) 6/7/85
12: cpyr
13: smtp Commands:
14: smtp HELO MAIL RCPT DATA RSET
15: smtp NOOP QUIT HELP VRFY EXPN
16: smtp For more info use "HELP <topic>".
17: smtp To report bugs in the implementation contact [email protected]
18: smtp or [email protected].
19: smtp For local information contact postmaster at this site.
20: help HELP [ <topic> ]
21: help The HELP command gives help info.
22: helo HELO <hostname>
23: helo Introduce yourself. I am a boor, so I really don't
24: helo care if you do.
25: mail MAIL FROM: <sender>
26: mail Specifies the sender.
27: rcpt RCPT TO: <recipient>
28: rcpt Specifies the recipient. Can be used any number of times.
29: data DATA
30: data Following text is collected as the message.
31: data End with a single dot.
32: rset RSET
33: rset Resets the system.
34: quit QUIT
35: quit Exit sendmail (SMTP).
36: vrfy VRFY <recipient>
37: vrfy Not implemented to protocol. Gives some sexy
38: vrfy information.
39: expn EXPN <recipient>
40: expn Same as VRFY in this implementation.
41: noop NOOP
42: noop Do nothing.
43: send SEND FROM: <sender>
44: send replaces the MAIL command, and can be used to send
45: send directly to a users terminal. Not supported in this
46: send implementation.
47: soml SOML FROM: <sender>
48: soml Send or mail. If the user is logged in, send directly,
49: soml otherwise mail. Not supported in this implementation.
50: saml SAML FROM: <sender>
51: saml Send and mail. Send directly to the user's terminal,
52: saml and also mail a letter. Not supported in this
53: saml implementation.
54: turn TURN
55: turn Reverses the direction of the connection. Not currently
56: turn implemented.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.