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
333
334
335
336
337
338
339
|
Network Working Group N. Freed
Request for Comments: RFC 2034 Innosoft
Category: Standards Track October 1996
SMTP Service Extension for
Returning Enhanced Error Codes
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
1. Abstract
This memo defines an extension to the SMTP service [RFC-821, RFC-
1869] whereby an SMTP server augments its responses with the enhanced
mail system status codes defined in RFC 1893. These codes can then
be used to provide more informative explanations of error conditions,
especially in the context of the delivery status notifications format
defined in RFC 1894.
2. Introduction
Although SMTP is widely and robustly deployed, various extensions
have been requested by parts of the Internet community. In
particular, in the modern, international, and multilingual Internet a
need exists to assign codes to specific error conditions that can be
translated into different languages. RFC 1893 defines such a set of
status codes and RFC 1894 defines a mechanism to send such coded
material to users. However, in many cases the agent creating the RFC
1894 delivery status notification is doing so in response to errors
it received from a remote SMTP server.
As such, remote servers need a mechanism for embedding enhanced
status codes in their responses as well as a way to indicate to a
client when they are in fact doing this. This memo uses the SMTP
extension mechanism described in RFC 1869 to define such a mechanism.
Freed Standards Track [Page 1]
^L
RFC 2034 SMTP Enhanced Error Codes October 1996
3. Framework for the Enhanced Error Statuses Extension
The enhanced error statuses transport extension is laid out as
follows:
(1) the name of the SMTP service extension defined here is
Enhanced-Status-Codes;
(2) the EHLO keyword value associated with the extension is
ENHANCEDSTATUSCODES;
(3) no parameter is used with the ENHANCEDSTATUSCODES EHLO
keyword;
(4) the text part of all 2xx, 4xx, and 5xx SMTP responses
other than the initial greeting and any response to
HELO or EHLO are prefaced with a status code as defined
in RFC 1893. This status code is always followed by one
or more spaces.
(5) no additional SMTP verbs are defined by this extension;
and,
(6) the next section specifies how support for the
extension affects the behavior of a server and client
SMTP.
4. The Enhanced-Status-Codes service extension
Servers supporting the Enhanced-Status-Codes extension must preface
the text part of almost all response lines with a status code. As in
RFC 1893, the syntax of these status codes is given by the ABNF:
status-code ::= class "." subject "." detail
class ::= "2" / "4" / "5"
subject ::= 1*3digit
detail ::= 1*3digit
These codes must appear in all 2xx, 4xx, and 5xx response lines other
than initial greeting and any response to HELO or EHLO. Note that 3xx
responses are NOT included in this list.
All status codes returned by the server must agree with the primary
response code, that is, a 2xx response must incorporate a 2.X.X code,
a 4xx response must incorporate a 4.X.X code, and a 5xx response must
incorporate a 5.X.X code.
Freed Standards Track [Page 2]
^L
RFC 2034 SMTP Enhanced Error Codes October 1996
When responses are continued across multiple lines the same status
code must appear at the beginning of the text in each line of the
response.
Servers supporting this extension must attach enhanced status codes
to their responses regardless of whether or not EHLO is employed by
the client.
5. Status Codes and Negotiation
This specification does not provide a means for clients to request
that status codes be returned or that they not be returned; a
compliant server includes these codes in the responses it sends
regardless of whether or not the client expects them. This is
somewhat different from most other SMTP extensions, where generally
speaking a client must specifically make a request before the
extended server behaves any differently than an unextended server.
The omission of client negotiation in this case is entirely
intentional: Given the generally poor state of SMTP server error code
implementation it is felt that any step taken towards more
comprehensible error codes is something that all clients, extended or
not, should benefit from.
IMPORTANT NOTE: The use of this approach in this extension should be
seen as a very special case. It MUST NOT be taken as a license for
future SMTP extensions to dramatically change the nature of SMTP
client-server interaction without proper announcement from the server
and a corresponding enabling command from the client.
6. Usage Example
The following dialogue illustrates the use of enhanced status codes
by a server:
S: <wait for connection on TCP port 25>
C: <open connection to server>
S: 220 dbc.mtview.ca.us SMTP service ready
C: EHLO ymir.claremont.edu
S: 250-dbc.mtview.ca.us says hello
S: 250 ENHANCEDSTATUSCODES
C: MAIL FROM:<ned@ymir.claremont.edu>
S: 250 2.1.0 Originator <ned@ymir.claremont.edu> ok
C: RCPT TO:<mrose@dbc.mtview.ca.us>
S: 250 2.1.5 Recipient <mrose@dbc.mtview.ca.us> ok
C: RCPT TO:<nosuchuser@dbc.mtview.ca.us>
S: 550 5.1.1 Mailbox "nosuchuser" does not exist
C: RCPT TO:<remoteuser@isi.edu>
S: 551-5.7.1 Forwarding to remote hosts disabled
Freed Standards Track [Page 3]
^L
RFC 2034 SMTP Enhanced Error Codes October 1996
S: 551 5.7.1 Select another host to act as your forwarder
C: DATA
S: 354 Send message, ending in CRLF.CRLF.
...
C: .
S: 250 2.6.0 Message accepted
C: QUIT
S: 221 2.0.0 Goodbye
The client that receives these responses might then send a
nondelivery notification of the general form:
Date: Mon, 11 Mar 1996 09:21:47 -0400
From: Mail Delivery Subsystem <mailer-daemon@ymir.claremont.edu>
Subject: Returned mail
To: <ned@ymir.claremont.edu>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="JAA13167.773673707/YMIR.CLAREMONT.EDU"
--JAA13167.773673707/YMIR.CLAREMONT.EDU
content-type: text/plain; charset=us-ascii
----- Mail was successfully relayed to
the following addresses -----
<mrose@dbc.mtview.ca.us>
----- The following addresses had delivery problems -----
<nosuchuser@dbc.mtview.ca.us>
(Mailbox "nosuchuser" does not exist)
<remoteuser@isi.edu>
(Forwarding to remote hosts disabled)
--JAA13167.773673707/YMIR.CLAREMONT.EDU
content-type: message/delivery-status
Reporting-MTA: dns; ymir.claremont.edu
Original-Recipient: rfc822;mrose@dbc.mtview.ca.us
Final-Recipient: rfc822;mrose@dbc.mtview.ca.us
Action: relayed
Status: 2.1.5 (Destination address valid)
Diagnostic-Code: smtp;
250 Recipient <mrose@dbc.mtview.ca.us> ok
Remote-MTA: dns; dbc.mtview.ca.us
Freed Standards Track [Page 4]
^L
RFC 2034 SMTP Enhanced Error Codes October 1996
Original-Recipient: rfc822;nosuchuser@dbc.mtview.ca.us
Final-Recipient: rfc822;nosuchuser@dbc.mtview.ca.us
Action: failed
Status: 5.1.1 (Bad destination mailbox address)
Diagnostic-Code: smtp;
550 Mailbox "nosuchuser" does not exist
Remote-MTA: dns; dbc.mtview.ca.us
Original-Recipient: rfc822;remoteuser@isi.edu
Final-Recipient: rfc822;remoteuser@isi.edu
Action: failed
Status: 5.7.1 (Delivery not authorized, message refused)
Diagnostic-Code: smtp;
551 Forwarding to remote hosts disabled
Select another host to act as your forwarder
Remote-MTA: dns; dbc.mtview.ca.us
--JAA13167.773673707/YMIR.CLAREMONT.EDU
content-type: message/rfc822
[original message goes here]
--JAA13167.773673707/YMIR.CLAREMONT.EDU--
Note that in order to reduce clutter the reporting MTA has omitted
enhanced status code information from the diagnostic-code fields it
has generated.
7. Security Considerations
Additional detail in server responses axiomatically provides
additional information about the server. It is conceivable that
additional information of this sort may be of assistance in
circumventing server security. The advantages of provides additional
information must always be weighed against the security implications
of doing so.
Freed Standards Track [Page 5]
^L
RFC 2034 SMTP Enhanced Error Codes October 1996
8. References
[RFC-821]
Postel, J., "Simple Mail Transfer Protocol", RFC 821,
August, 1982. (August, 1982).
[RFC-1869]
Rose, M., Stefferud, E., Crocker, C., Klensin, J., Freed,
N., "SMTP Service Extensions", RFC 1869, November, 1995.
[RFC-1893]
Vaudreuil, G., "Enhanced Mail System Status Codes", RFC
1893, January, 1996.
[RFC-1894]
Moore, K., Vaudreuil, G., "An Extensible Message Format
for Delivery Status Notifications", RFC 1894, January,
1996.
9. Author Address
Ned Freed
Innosoft International, Inc.
1050 East Garvey Avenue South
West Covina, CA 91790
USA
tel: +1 818 919 3600 fax: +1 818 919 3614
email: ned@innosoft.com
Freed Standards Track [Page 6]
^L
|
