search

ietf-wg-emailcore / emailcore

3 stars 0 forks source link

G.13. Deprecating HELO #43

Closed ietf-svn-bot closed 3 years ago

ietf-svn-bot commented 3 years ago

resolution_wontfix type_defect | by alexey.melnikov@isode.com

John Klensin wrote:

RFC 5321 (and 2821 before it) very carefully circle around the status of HELO, even recommending its use as a fallback when EHLO is sent and a "command not recognized" response is received. We are just a few months short of 20 years; is it time to deprecate the thing and clean out some or all of that text? And, given a recent (4Q2020) discussion on the EMAILCORE list, should EHLO be explicitly bound to SMTP over TCP with the older transports allowed only with HELO? While those questions may seem independent, separating them is fairly hard given the way the text is now constructed.

Issue migrated from trac:43 at 2022-01-31 12:37:19 +0000

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Discussion thread:

https://mailarchive.ietf.org/arch/msg/emailcore/Zn9T42eVMbqZUtgYU2Ou6UQ4TjA/

ietf-svn-bot commented 3 years ago

@alexey.melnikov@isode.com commented

Resolution:

https://mailarchive.ietf.org/arch/msg/emailcore/UCirIOKEyVxP1bH7mGcCkoDq7Vg/

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 wontfix