I think you are saying, problem will arise when there are multiple hops.
That makes sense.
On Wed, Jan 9, 2019 at 1:10 PM Viruthagiri Thirumavalavan
What happens if my mail server doesn't support markdown?
That's why I'm proposing the MARKDOWN extension. MARKDOWN command should
be presented in the EHLO response only if your server supports markdown.
If your server supports markdown, the mail will be transferred as
text/markdown. Else mail will be transferred as "text/plain" and
"text/html" as usual.
I hope I understood you correctly.
On Wed, Jan 9, 2019 at 1:03 PM <valdis(_dot_)kletnieks(_at_)vt(_dot_)edu>
On Wed, 09 Jan 2019 12:29:43 +0530, Viruthagiri Thirumavalavan said:
I wanna bring Markdown support to SMTP. So instead of transferring both
"text/plain" and "text/html" versions, future mails can use only
Well, right off the top, there's the end to end problem.
Say you support text/markdown, and your mail server accepts it to
happens if my mail server doesn't support markdown? Do you send a
and hope my MUA can deal with it? If you do that, why bother with an SMTP
Also, see RFC1341, and text/richtext. Ask yourself why you never see
e-mails with it.
ietf-smtp mailing list