Tony Finch wrote:
On Tue, 10 Apr 2007, Hector Santos wrote:
I would like to suggest one paragraph wording after the final paragraph in
4.2.1:
Only the final or last reply-code is important in a multiline
response. The client MUST use the final line as the ultimate
server response. It is possible for a server to use a
preliminary reply code 150- as part of multiline response
with a final non-continuation completion code.
Absolutely not. This is way too new and experimental for this revision,
and utterly unsupported by running code.
If you want to define a 150 response, write a proper ESMTP service
extension.
It really has nothing to do with experiments or too new in the field or
whether there are a few running codes exploring this.
The questions are:
- Must all the reply codes be the same?
- If not, the final return code (last line) is valid code?
- 150 SHOULD/MUST NOT be used without extended status codes?
MUST or SHOULD or MUST/SHOULD NOT (pick one) this revision answer these
fundamental specification questions about the multi-line server responses?
Obviously, since you reject, I shouldn't be surprise if the cogs will too.
--
HLS