search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

Erratum 1851: Location of text about TCP connection has closure/reset #28

Closed ietf-svn-bot closed 3 years ago

ietf-svn-bot commented 3 years ago

owner:alexey.melnikov@isode.com resolution_fixed type_defect | by alexey.melnikov@isode.com

Alessandro Vesely wrote:

Section 4.1.1.5. says:

There are circumstances, contrary to the intent of this specification, in which an SMTP server may receive an indication that the underlying TCP connection has been closed or reset. To preserve the robustness of the mail system, SMTP servers SHOULD be prepared for this condition and SHOULD treat it as if a QUIT had been received before the connection disappeared.

Notes:

That text seems inappropriate in the RESET (RSET) section. It should presumably be moved to section 4.1.1.10. QUIT (QUIT), or, better yet, to section 3.8. Terminating Sessions and Connections.

Issue migrated from trac:28 at 2022-01-31 12:35:51 +0000

ietf-svn-bot commented 3 years ago

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

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set owner to alexey.melnikov@isode.com

ietf-svn-bot commented 3 years ago

@vesely@tana.it commented

Discussion: https://mailarchive.ietf.org/arch/msg/emailcore/oViYU5qKTK4NkudUJWB6yOh34gc

ietf-svn-bot commented 3 years ago

@julien@trigofacile.com commented

In Section 4.1.1.10, maybe the 4yz response code mentioned would better be 451 (used for transaction abortion)?

If the connection is closed prematurely due to violations of the above or system or network failure, the server MUST cancel any pending transaction, but not undo any previously completed transaction, and generally MUST act as if the command or transaction in progress had received a temporary error (i.e., a 4yz response).

ietf-svn-bot commented 3 years ago

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

ietf-svn-bot commented 3 years ago

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

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Fixed in revision -02.