On 2021-11-29 at 20:00:14 UTC-0500 (Mon, 29 Nov 2021 17:00:14 -0800)
Michael Peddemors via mailop <[email protected]>
is rumored to have said:
It does sound like you are arguing for dropping QUIT altogether,
Nope. I didn't say that or anything like that. QUIT is essential. The
response to QUIT is superfluous.
but the protocol was designed for robustness, and there is a reason
for the general use of COMMAND/ACKNOWLEGEMENT.
That reason is not valid at QUIT because the reply MUST always be sent
and MUST always be 220 and neither side has any freedom of action within
the protocol after the QUIT has been sent.
However, he is missing that earlier in the same RFC we see.. (Notice
the MUST NOT, which over reaches the later SHOULD)
Didn't miss it at all. I just read it more tightly.
3.8. Terminating Sessions and Connections
An SMTP connection is terminated when the client sends a QUIT
command. The server responds with a positive reply code, after
which
it closes the connection.
An SMTP server MUST NOT intentionally close the connection under
normal operational circumstances (see Section 7.8) except:
That MUST NOT does not apply to the client side of the SMTP session, it
applies strictly to the server side. The fact that the client may
actually be something we would more loosely call a server (i.e.
Exchange, <shudder>) is irrelevant. In RFCxx21 jargon, there is only one
server in a SMTP conversation, and it doesn't initiate closure.
--
Bill Cole
[email protected] or [email protected]
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
