search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

G.2. Repeated Use of EHLO #2

Closed ietf-svn-bot closed 3 years ago

ietf-svn-bot commented 3 years ago

keyword_SMTP resolution_fixed type_defect | by alexey.melnikov@isode.com

While the specification says that an SMTP client's sending EHLO again after it has been issued (starting an SMTP session and treats it as if RSET had been sent (closing the session) followed by EHLO, there are apparently applications, at least some of them involving setting up of secure connections, in which the second EHLO is required and does not imply RSET. Does the specification need to be adjusted to reflect or call out those cases?

Issue migrated from trac:2 at 2022-01-31 12:33:07 +0000

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed title from Repeated Use of EHLO to G.2. Repeated Use of EHLO

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com set component to smtp

ietf-svn-bot commented 3 years ago

@vesely@tana.it commented

Discussion: https://mailarchive.ietf.org/arch/msg/emailcore/0eehumpIbGgOhUmxIyU8kApUFXc

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Part of the above discussion was whether EHLO clears AUTH and/or STARTTLS state. (The conclusion is that it doesn't). As AUTH/STARTTLS are specified in different RFCs, any further clarification of this point will be done if/when these other RFCs are revised.

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com changed status from new 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

This is addressed in -01.