2 ms·
> What are the practical cons? 1. Every vulnerability that browsers suffer from, is transferred to e-mails, because a browser is used to view the content. This
by lutusp 14y ago
> What are the practical cons?
1. Every vulnerability that browsers suffer from, is transferred to e-mails, because a browser is used to view the content. This is the primary reason HTML e-mail content has become unpopular. In principle, an HTML e-mail could contain a small Java applet and (with recently reported Java security problems) this could be used to compromise the recipient machine, through the simple act of opening and viewing the e-mail.
2. An embedded, transparent 1x1 pixel graphic can be used to confirm reception, which solves the single most important problem in spamming and phishing attacks -- verifying that a human read the e-mail. All the recipient needs to do is view the e-mail, and the sender detects that it was received and opened, even when it was read and for how long.
3. Embedded links to dangerous sites, an obvious problem.
A better question would be "why is there no nice-looking, but safe, document format for e-mail that has all the aesthetics of HTML but none of the vulnerabilities?" Such a document format would be easy to create, and without linked graphics or hyperlinks, or any kind of plugin vulnerabilities.
- eevilspock 14y agoYour cons are all about the cons of email client supporting HTML. My intended question was, given the existing support for HTML email, is there a reason for a sender to not take advantage of it? Your reasons 1-3 above don't apply because I won't do those things. But what would be a con is if, because of those dangers, enough recipients reject HTML email out-of-hand.