1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
|
MAIL Parameters
(last updated 2008-10-01)
Registry Name: Mail Service Types
Note:
The set of services desired from a mail server are sometimes
characterized by the "hello" keyword used. These are listed here.
Registry:
Keywords Description Reference
-------- -------------------------------- ---------
HELO Simple Mail [RFC821]
EHLO Mail Service Extensions [RFC1869]
LHLO Local Mail [RFC2033]
Registry Name: Mail Encryption Types
Note:
[RFC822] specifies that Encryption Types for mail may be assigned.
There are currently no RFC 822 encryption types assigned. Please use
instead the Mail Privacy procedures defined in [RFC1421], [RFC1422],
[RFC1423].
Registry Name: SMTP Service Extensions
Reference: [RFC5321]
Registration Procedures: Standards-Track or IESG-Approved Experimental RFC
Note:
The Simple Mail Transfer Protocol [RFC5321] specifies a set of commands
or services and a general procedure for extending that set. The table
below lists SMTP service extensions. Both message submission [RFC2476]
and mail transfer [RFC5321] may use these extensions unless otherwise
specified.
As specified in [RFC5321] Section 2.2.2, no entry may be made in this
registry that starts in an "X". Entries may be made only for service
extensions (and associated keywords, parameters, or verbs) that are
defined in Standards-Track or Experimental RFCs specifically approved
by the IESG for this purpose.
The server response to a client EHLO command includes a keyword for
each service extension the server implements.
Registry:
Keywords Description Reference
------------------- ---------------------------------- ---------
SEND Send as mail [RFC821]
SOML Send as mail or terminal [RFC821]
SAML Send as mail and terminal [RFC821]
EXPN Expand the mailing list [RFC821]
HELP Supply helpful information [RFC821]
TURN Turn the operation around [RFC821]
8BITMIME Use 8-bit data [RFC1652]
SIZE Message size declaration [RFC1870]
VERB Verbose [Eric Allman]
ONEX One message transaction only [Eric Allman]
CHUNKING Chunking [RFC3030]
BINARYMIME Binary MIME [RFC3030]
CHECKPOINT Checkpoint/Restart [RFC1845]
DELIVERBY Delivery within prescribed period [RFC2852]
PIPELINING Command Pipelining [RFC2920]
DSN Delivery Status Notification [RFC3461]
ETRN Extended Turn [RFC1985] +
ENHANCEDSTATUSCODES Enhanced Status Codes [RFC2034]
STARTTLS Start TLS [RFC3207]
NO-SOLICITING Notification of no soliciting [RFC3865]
MTRK Message Tracking [RFC3885]
SUBMITTER SMTP Responsible Submitter [RFC4405]
ATRN Authenticated TURN [RFC2645] +
AUTH Authentication [RFC4954]
BURL Remote Content [RFC4468] *
FUTURERELEASE Future Message Release [RFC4865]
UTF8SMTP Internationalized email address [RFC5336]
+ SMTP [RFC5321] only. Not for use on Submit port 587.
* Submit [RFC2476] only. Not for use with SMTP on port 25.
Some of these keywords have parameters. These are listed here (those
keywords not listed here have no parameters).
Service Ext EHLO Keyword Parameters Reference
--------------- ------------- ----------------------- ---------
Size SIZE number [RFC1870]
No Soliciting NO-SOLICITING Soliciting-keywords [RFC3865]
Authentication AUTH SASL mechanism names [RFC4954]
Remote Content BURL Permitted URL prefixes [RFC4468]
MAIL SYSTEM NAMES and ADDRESS TYPES
In some places, an identification of other mail systems is used.
One of these is in "The COSINE and Internet X.500 Schema" (section
9.3.18) [RFC1274]. The mail system names listed here are used as the
legal values in that schema under the "otherMailbox" attribute
"mailboxType" type (which must be a PrintableString).
Another place is in "Mapping between X.400(1988) / ISO 10021 and RFC
822" (section 4.2.2) [RFC1327] (obsoleted by [RFC2156]). The names
listed here are used as the legal values in that schema under the
"std-or-address" attribute "registered-dd-type" type (which must be
a "key-string").
Note that key-string = <a-z, A-Z, 0-9, and "-" >.
Mail System Name Description Reference
---------------- ------------------------ ---------
mcimail MCI Mail
Registry Name: Address Types
Reference: [RFC3461][RFC3464]
Note:
Please see the following:
http://www.iana.org/assignments/dsn-types
Registry Name: Diagnostic Types
Reference: [RFC3461][RFC3464]
Note:
Please see the following:
http://www.iana.org/assignments/dsn-types
Registry Name: MTA Name Types
Reference: [RFC3461][RFC3464]
Note:
Please see the following:
http://www.iana.org/assignments/dsn-types
Registry Name: Mail Transmission Types
Reference: [RFC821][RFC822][RFC5321]
Registration Procedures: Standards-Track or IESG-Approved Experimental RFC
Note:
The Simple Mail Transfer Protocol [RFC821][RFC5321] and the Standard for
the Format of ARPA Internet Text Messages [RFC822] specify that a set of
"Received" lines will be prepended to the headers of electronic mail
messages as they are transported through the Internet.
These received line may optionally include either or both a "via" phrase
and/or a "with" phrase. The legal values for the phrases are listed here.
The via phrase is intended to indicate the link or physical medium over
which the message was transferred. The with phrase is intended to
indicate the protocol or logical process that was used to transfer the
message.
Sub-registry: VIA link types
Registry:
VIA link types Description Reference
-------------- ---------------------------- ---------
UUCP Unix-to-Unix Copy Program [???]
TCP TCP [RFC5321]
Sub-registry: WITH protocol types
Registry:
WITH protocol types Description Reference
------------------- ----------------------------------------- ---------
SMTP Simple Mail Transfer Protocol [RFC5321]
ESMTP SMTP with Service Extensions [RFC5321]
ESMTPA ESMTP with SMTP AUTH [RFC3848]
ESMTPS ESMTP with STARTTLS [RFC3848]
ESMTPSA ESMTP with both STARTTLS and SMTP AUTH [RFC3848]
LMTP Local Mail Transfer Protocol [RFC3848]
LMTPA LMTP with SMTP AUTH [RFC3848]
LMTPS LMTP with STARTTLS [RFC3848]
LMTPSA LMTP with both STARTTLS and SMTP AUTH [RFC3848]
ESMTP ESMTP with NO-SOLICITING [RFC3865]
MMS Multimedia Messaging Service [RFC4356]
UTF8SMTP UTF8SMTP with Service Extensions [RFC5336]
UTF8SMTPA UTF8SMTP with SMTP AUTH [RFC4954][RFC5336]
UTF8SMTPS UTF8SMTP with STARTTLS [RFC3207][RFC5336]
UTF8SMTPSA UTF8SMTP with both STARTTLS and SMTP AUTH [RFC3207][RFC4954][RFC5336]
Sub-registry: Additional-registered-clauses
Reference: [RFC5321]
Registration Procedures: Standards-Track or IESG-Approved Experimental RFC
Registry:
Clause Name Description Syntax Summary Reference
----------- ------------------- ------------------------ ---------
Registry Name: Address Literal Tags
Reference: [RFC5321]
Note:
Please see the following:
http://www.iana.org/assignments/address-literal-tags/address-literal-tags.xhtml
References
----------
[ANSI-X12]
[IS-10646]
[POSTSCRIPT]
Adobe Systems Inc., "PostScript Language Reference
Manual", 2nd Edition, 2nd Printing, January 1991.
[RFC821] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
USC/Information Sciences Institute, August 1982.
[RFC822] Crocker, D., "Standard for the Format of ARPA-Internet Text
Messages", STD 11, RFC 822, UDEL, August 1982.
[RFC1274] Barker, P., and S. Kille, "The COSINE and Internet X.500
Schema", RFC 1274, University College London, November 1991.
[RFC1327] Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO
10021 and RFC 822", RFC 1327, University College London,
May 1992.
[RFC1421] Linn, J., "Privacy Enhancement for Internet Electronic
Mail: Part I: Message Encipherment and Authentication
Procedures", RFC 1421, IAB IRTF PSRG, IETF PEM WG,
February 1993.
[RFC1422] Kent, S., "Privacy Enhancement for Internet
Electronic Mail: Part II -- Certificate-Based Key
Management", BBN, IAB IRTF PSRG, IETF PEM, February 1993.
[RFC1423] Balenson, D., "Privacy Enhancement for Internet Electronic
Mail: Part III -- Algorithms, Modes, and Identifiers",
RFC 1423, TIS, IAB IRTF PSRG, IETF PEM WG, February 1993.
[RFC1505] Costanzo, A., Robinson, D., and R. Ullmann, "Encoding Header
Field for Internet Messages", RFC 1505, AKC Consulting,
Computervision Corporation, August 1993.
[RFC1652] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
Crocker, "SMTP Service Extension for 8bit-MIMEtransport",
RFC 1652, MCI, Innosoft, Dover Beach Consulting, Inc.,
Network Management Associates, Inc., Silicon Graphics, Inc.,
July 1994.
[RFC1830] Vaudreuil, G., "SMTP Service Extensions for Transmission of
Large and Binary MIME Messages", RFC 1830, Octel Network
Services, August 1995.
[RFC1845] Crocker, D., N. Freed, and A. Cargille, "SMTP Service
Extension for Checkpoint/Restart", RFC 1845, Brandenburg
Consulting, Innosoft International, September 1995.
[RFC1869] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D.
Crocker, "SMTP Service Extensions", RFC 1869, MCI, Innosoft,
Dover Beach Consulting, Inc., Network Management Associates,
Inc., Brandenberg Consulting., November 1995.
[RFC1870] Klensin, J., Freed, N., and K. Moore, "SMTP Service
Extension for Message Size Declaration", RFC 1870,
MCI, Innosoft, University of Tennessee, November 1995.
[RFC1985] DeWinter, J., "SMTP Service Extension for Remote Message
Queue Starting", RFC1985, Wildbear Consulting, August 1996.
[RFC2033] Myers, J., "Local Mail Transfer Protocol", RFC 2033,
Carnegie Mellon, October 1996.
[RFC2034] Freed, N., "SMTP Service Extension for Returning Enhanced
Status Codes", RFC Innosoft International, October 1996.
[RFC2156] S. Kille, "MIXER (Mime Internet X.400 Enhanced Relay):
Mapping between X.400 and RFC 822/MIME", RFC 2156, January 1998.
[RFC2183] Troost, R., S. Dorner, and K. Moore, "Communicating
Presentation Information in Internet Messages: The
Content-Disposition Header Field", RFC 2183, New Century
Systems, QUALCOMM Incorporated, University of Tennessee,
August 1997.
[RFC2197] Freed, N., "SMTP Service Extension for Command Pipelining",
RFC 2197, Innosoft, September 1997.
[RFC2487] Hoffman, P., "SMTP Service Extension for Secure SMTP over
TLS", RFC 2487, Internet Mail Consortium, January 1999.
[RFC2645] R. Gellens, "ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic
IP Addresses", RFC 2645, August 1999.
[RFC2852] D. Newman, "Deliver By SMTP Service Extension", RFC 2852,
June 2000.
[RFC2920] N. Freed, "SMTP Service Extension for Command Pipelining",
RFC 2920, September 2000.
[RFC3030] G. Vaudreuil, "SMTP Service Extensions for Transmission of Large
and Binary MIME Messages", RFC 3030, December 2000.
[RFC3207] P. Hoffman, "SMTP Service Extension for Secure SMTP over
Transport Layer Security", RFC 3207, February 2002.
[RFC3461] K. Moore, "Simple Mail Transfer Protocol (SMTP) Service
Extension for Delivery Status Notifications (DSNs)", RFC 3461,
January 2003.
[RFC3848] C. Newman, "ESMTP and LMTP Transmission Types Registration",
RFC 3848, July 2004.
[RFC3865] C. Malamud, "A No Soliciting SMTP Service Extension", RFC 3865,
September 2004.
[RFC3885] E. Allman and T. Hansen, "SMTP Service Extension for Message
Tracking", RFC 3885, September 2004.
[RFC4405] E. Allman and H. Katz, "SMTP Service Extension for Indicating
the Responsible Submitter of an E-mail Message", RFC 4405, April 2006.
[RFC4356] R. Gellens, "Mapping Between the Multimedia Messaging Service (MMS)
and Internet Mail", RFC 4356, January 2006.
[RFC4468] C. Newman, "Message Submission BURL Extension", RFC 4468, May 2006.
[RFC4865] G. White, G. Vaudreuil, "SMTP Submission Service Extension for
Future Message Release", RFC 4865, May 2007.
[RFC4954] Robert Siemborski and Alexey Melnikov, "SMTP Service Extension
for Authentication", RFC 4954, July 2007.
[RFC5336] J. Yao, Ed., W. Mao, Ed., "SMTP extension for internationalized
email address", RFC 5336, September 2008.
[RFC5321] J. Klensin, "Simple Mail Transfer Protocol", RFC 5321, October 2008.
[]
|
