Closed ietf-svn-bot closed 3 years ago
@alexey.melnikov@isode.com changed status from new
to assigned
@alexey.melnikov@isode.com set owner to alexey.melnikov@isode.com
@alexey.melnikov@isode.com set component to smtp
@alexey.melnikov@isode.com commented
Issued 2 weeks WGLC (finishing on February 22nd) to close the ticket, as the change was already implemented.
@alexey.melnikov@isode.com changed status from assigned
to closed
@alexey.melnikov@isode.com set resolution to fixed
keyword_SMTP
owner:alexey.melnikov@isode.com
resolution_fixed
type_defect
| by alexey.melnikov@isode.comSection 3.8 says:
SMTP clients that experience a connection close, reset, or other communications failure due to circumstances not under their control (in violation of the intent of this specification but sometimes unavoidable) SHOULD, to maintain the robustness of the mail system, treat the mail transaction as if a 451 response had been received and act accordingly.
It should say:
SMTP clients that experience a connection close, reset, or other communications failure due to circumstances not under their control (in violation of the intent of this specification but sometimes unavoidable) SHOULD, to maintain the robustness of the mail system, treat the mail transaction as if a 421 response had been received and act accordingly.
Notes:
SMTP clients are told to act as though a 451 response ("Requested action aborted: local error in processing") had been received when context clearly indicates that a 421 response ("Service not available, closing transmission channel") was intended.
Issue migrated from trac:26 at 2022-01-31 12:35:41 +0000