Content deleted Content added
creating new sections from former arguments |
«+"Security vulnerabilities ==", -"*", -"*", "*" → "=="» |
||
Line 15:
* A few recipients have [[e-mail client]]s that cannot display HTML. This may be mitigated by the inclusion of an automatically generated plain text version, which may be missing important formatting information (e.g. an equation may lose a superscript and take on an entirely new meaning).
* Some senders may excessively rely upon large, colorful, or distracting fonts making all but the shortest messages more difficult to read.
* HTML allows for a link to have a different target than the link's text. This can be a security issue for users, who may be fooled into believing that a link points to the website of an authoritative source (such as a bank) and unintentionally [[phishing|revealing personal details to a scammer]].▼
* The viewing of embedded external content, such as an [[Digital image|image]] in an email, can alert a third party that the e-mail has been opened. This is a potential privacy risk, and the reason for which some e-mail clients do not load external images by default.▼
* Most [[E-mail spam]] is sent in HTML so spam filters (such as [[Spamassassin]]) give high spam scores to HTML messages.▼
* Many HTML-based GUI [[email client]]s automatically convert common plain text characters, e.g. — and ", into non-plain text equivalents. This can cause translation problems in other users' clients.
Line 23 ⟶ 20:
== Multi-part formats ==
Many email clients are configured to send a plain text version of a message along with the HTML version, to ensure that it can be read even by text-only clients, using the <code>[[MIME#Content-Type|Content-Type]]: [[MIME#Alternative|multipart/alternative]]</code>, as specified in RFC 1521.<ref>[http://www.freesoft.org/CIE/RFC/1521/18.htm RFC 1521 7.2.3. The Multipart/alternative subtype]</ref><ref>[http://www.codestone.ltd.uk/software/docs/csmail/tn1010-11-2.pdf TN1010-11-2: Multipart/Alternative – Gracefully handling HTML-phobic email clients.]</ref><ref>[http://www.wilsonweb.com/wmt5/html-email-multi.htm Sending HTML and Plain Text E-Mail Simultaneously]</ref>
Line 32 ⟶ 28:
Additionally, the plain text section of a multi-part message can be retrieved by itself, using [[IMAP]]'s FETCH command.<ref>[http://dsv.su.se/jpalme/ietf/mhtml-discussion.html Do we really want to send web pages in e-mail?]</ref>
== Security vulnerabilities ==
▲
▲
▲
== References==
| |||