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
|
Network Working Group Julie Sussman
RFC # 630 BBN
NIC # 30237 April 10, 1974
FTP Error Code Usage for More Reliable Mail Service
PURPOSE
A major hindrance to providing reliable mail service is the lack of
well-defined FTP error replies that would enable a mailing process to
decide how to handle a failure. New FTP error codes are currently in
the design stage, and a proposal will be announced soon. In the
interim, we can get some improvement by simply defining how we intend to
use the current FTP codes. The purpose of this RFC is to inform all
sites of how TENEX sites will use and interpret the codes starting in
the near future.
CURRENT CODE DEFINITIONS
The FTP error codes defined for failure to perform a file action
(including mail) are:
450 File not found
451 File access denied to you
452 Data connection closed
453 Insufficient storage
454 Cannot connect to your data socket
450, 451, and 453 are applicable to both the MAIL and MLFL commands,
while 452 and 454 are only meaningful for MLFL.
SHORTCOMING OF CURRENT DEFINITIONS
There are more possible causes of failure to deliver mail than the
ones defined above. Implementors of FTP servers thus had to make
arbitrary assignments of error conditions to defined codes. As a
result, although the text of the reply might distinguish these
conditions for the benefit of human users, the code doesn't distinguish
them for the benefit of processes.
The minimum distinction needed by the TENEX mail-sending processes
is between permanent and non-permanent failures. In the latter case,
the process will repeatedly try to deliver the mail for several days.
Sussman [Page 1]
^L
RFC 630 FTP Error Code Usage for Mail Service April 1974
NEW DEFINITIONS FOR TENEX USE
The following changes will be installed at TENEX sites over the next
couple of months.
FTP SERVER
The TENEX FTP server will continue to use 452 and 454 as specified
for the MLFL command.
For MAIL and MLFL, it will send the other codes as follows:
450 Permanent failures due to the user addressed in the Mail or MLFL
command.
Examples: No such user; No mailbox for that user; Can't access file
(because net users can't write in that mailbox).
451 Permanent failures due to the message itself.
Example: Line sent over TELNET connection is too long (MAIL command
only).
453 Temporary failures
Examples: TELNET connection unexpectedly closed; Mailbox busy;
Unexpected local errors (such as failure to create scratch file).
MAILING PROCESSES
TENEX mailing processes currently interpret all the codes 450-454 as
meaning permanent failure. They will be changed to interpret 452, 453,
and 454 as temporary while leaving 450 and 451 permanent.
COMPATIBILITY WITH NON-TENEX SITES
These interpretations should not adversely affect the interaction of
TENEX and non-TENEX mail processes, since we are simply changing from
one arbitrary set of interpretations to another. Moreover:
--Our interpretation of 450-451 as permanent and 452-454 as temporary is
consistent with their original meanings.
--Our new choice of what codes to use for what failure is no farther
from the original meanings than our old choice was, and conveys more
information.
Sussman [Page 2]
^L
RFC 630 FTP Error Code Usage for Mail Service April 1974
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 10/99 ]
Sussman [Page 3]
^L
|
