[Top] [All Lists]

Re: rfc2821bis-01 Issue 14 Continuation of 222 greeting and Issue 15 syntax for multiline replies

2007-04-10 06:16:00

--On Tuesday, 10 April, 2007 05:24 -0400 Hector Santos
<hsantos(_at_)santronics(_dot_)com> 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
    response. The client MUST use the final line as the
    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.

    For example:

    354 Please Start sending....
        [ client uploads message ]
    150-Please Wait...
    150-Please Wait...
    451 Sorry, Rejected, try again later

Hector, in addition to the comments made by others (the codes do
need to be the same, any use of 1yz requires extensions), I note
that this sort of thing would (i) violate well-established
recommendations about getting (final) responses back quickly to
avoid duplicate messages and (ii) would probably result in
clients disconnecting if the sequence were really

     150-Please Wait...
(significant pause)
     150-Please Wait...
(significant pause)
     451 Sorry, Rejected, try again later

As a sometime SMTP implementer, I'd be pretty horrified if I was
told wait... wait.... wait... try later (wait... wait... "5yz Go
away and don't come back" would be a little more plausible).

You might be able to overcome some of these difficulties in an
extension, but it certainly does not belong in the base spec.


<Prev in Thread] Current Thread [Next in Thread>