Clarify the behaviour of SMTP clients when the server closes the connection

ietf-svn-bot commented 3 years ago

resolution_wontfix type_defect | by julien@trigofacile.com

Following the change in #28:

A bit earlier in the same Section 3.8, we have:

After detecting the need to shut down the SMTP service and returning a 421 reply code. This reply code can be issued after the server receives any command or, if necessary, asynchronously from command receipt (on the assumption that the client will receive it after the next command is issued).

Does the part in parenthesis really occur in practice, notably when the closure is asynchronous from command receipt? Maybe it should be reworded this way: "on the assumption that the client will receive it after the next command is issued or read it before closing the connection at its side"?

Another suggestion for the new paragraph:

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,

try to read a possible asynchronous reply from the SMTP server, and
otherwise treat the mail transaction as if a 421 response had been received and act accordingly.

Issue migrated from trac:46 at 2022-01-31 12:37:34 +0000

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com changed status from new to closed

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com set resolution to wontfix

ietf-svn-bot commented 2 years ago

@alexey.melnikov@isode.com commented

Not enough interest to fix this ticket, some participant said that it was too much details and is a transport level issue.

ietf-wg-emailcore / emailcore

Clarify the behaviour of SMTP clients when the server closes the connection #46