I guess I'm missing something pretty fundamental here, because I don't see why
any of this is necessary.
We have a model for extending SMTP/LMTP that includes private extensions:
Advertise the extension in the EHLO/LHO response, then enable the extension
either with a new command or parameter. There's essentially no limit on what
an
extension can do, and it certainly includes enabling the use of structured
information in certain replies.
I should also note that the use of an enabling command or parameter here
isn't strictly necessary, especially in the case of LMTP: Since reply text
is normally unstructured, all that's needed is an indicator from the server
that it's going to include structured information in some replies. This
has worked just fine in the case of ENHANCEDSTATUSCODES.
Ned
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp