On Sat, 23 Nov 2019 07:35:00 -0500, John C Klensin said:
(4) Now, assume that you were confident you could really gather
community consensus that a change would be a good idea for use
in specific contexts. The way to do that would be to define an
SMTP extension for longer local parts in the kinds of
applications you cite, imposing whatever new restrictions you
thought appropriate. By contrast to (3), that would be easy.
No modification to 5321 would be needed and legacy embedded
applications would either not recognize the extension mechanism
or would not offer or request the extension.
Figuring out what to do with an email that contains a 158 character username
when you attempt delivery to a server that doesn't support the extension is
left as an exercise for the reader. :)
(HInt: The proper action is probably different for sender and recipient
fields...)
pgpuE5x86MbEk.pgp
Description: PGP signature
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp