Content deleted Content added
Rescuing 2 sources and tagging 0 as dead.) #IABot (v2.0 |
m →Adoption: Punctuation |
||
| (38 intermediate revisions by 28 users not shown) | |||
Line 1:
{{Short description|Type of email}}
{{Use dmy dates|date=
'''HTML email''' is the use of a [[subset]] of [[HTML]] to provide formatting and [[semantic web|semantic]] markup capabilities in [[email]] that are not available with [[plain text]]:<ref>{{Cite web|title = Text Email vs HTML Email – The Pros and Cons {{!}} Thunder Mailer – Mass Emailing Software|url = http://www.thundermailer.com/text-email-vs-html-email-the-pros-and-cons/|website = www.thundermailer.com|access-date = 2016-01-30}}</ref> Text can be linked without displaying a [[URL]], or breaking long URLs into multiple pieces. Text is wrapped to fit the width of the viewing window, rather than uniformly breaking each line at 78 characters (defined in RFC 5322, which was necessary on older [[Data terminal#Text terminals|text terminals]]). It allows in-line inclusion of images, [[Table (information)|table]]s, as well as diagrams or [[mathematical formula]]e as images, which are otherwise difficult to convey (typically using [[ASCII art]]).▼
{{POV|talk=POV|date=December 2021}}
▲'''HTML email''' is the use of a [[subset]] of [[HTML]] to provide formatting and [[semantic web|semantic]] markup capabilities in [[email]] that are not available with [[plain text]]:<ref>{{Cite web|title = Text Email vs HTML Email – The Pros and Cons {{!}} Thunder Mailer – Mass Emailing Software|url = http://www.thundermailer.com/text-email-vs-html-email-the-pros-and-cons/|website =
== Adoption ==
Line 6 ⟶ 8:
Most graphical [[email client]]s support HTML email, and many default to it. Many of these clients include both a [[GUI]] editor for composing HTML emails and a rendering engine for displaying received HTML emails.
Since its conception, a number of people have vocally opposed all HTML email (and even [[MIME]] itself), for a variety of reasons.<ref>[https://subversion.american.edu/aisaac/notes/htmlmail.htm HTML Email: Whenever Possible, Turn It Off!]</ref> For instance, the
While still considered inappropriate in many newsgroup postings and mailing lists, HTML adoption for personal and business mail has only increased over time. Some of those who strongly opposed it when it first came out now see it as mostly harmless.<ref>[http://birdhouse.org/blog/2006/01/15/html-email-the-poll/ HTML Email: The Poll] (Scot Hacker, originator of the much-linked-to ''Why HTML in E-Mail is a Bad Idea'' discusses how his feelings have changed since the 1990s)</ref>
According to surveys by [[online marketing]] companies, adoption of HTML-capable email clients is now nearly universal, with less than 3% reporting that they use text-only clients.<ref>{{Cite web|title=Email Marketing Statistics and Metrics - EmailLabs |url=http://www.emaillabs.com/tools/email-marketing-statistics.html |date=2007-03-29 |access-date=2016-01-30 |quote=HTML has nearly universal adoption among consumers: A Jupiter Research consumer survey found just 3% receive only text email. |url-status=dead |archiveurl=https://web.archive.org/web/20070329012457/http://www.emaillabs.com/tools/email-marketing-statistics.html |archivedate=29 March 2007 }}</ref> The majority of users prefer to receive HTML emails over plain text.<ref>{{Cite web|title = Real-World Email Client Usage: The Hard Data {{!}} ClickZ|url = https://www.clickz.com/clickz/column/2138714/real-world-email-client-usage-the-hard-data|website = www.clickz.com|access-date = 2016-01-30|last = Grossman|date = 2002-07-09|first = Edward|quote = Do you prefer receiving HTML or text email? HTML: 41.95%, Text: 31.52%, No preference: 26.53%}}</ref><ref>{{Cite web|title = The Science of Email Marketing|url = http://www.slideshare.net/HubSpot/the-science-of-email-marketng/32|website = www.slideshare.net|access-date = 2016-01-30|quote = In what format do you prefer to receive email messages from companies? HTML: 88%, Plain text: 12%}}</ref>▼
▲According to surveys by [[online marketing]] companies, adoption of HTML-capable email clients is now nearly universal, with less than 3% reporting that they use text-only clients.<ref>{{Cite web|title=Email Marketing Statistics and Metrics
== Compatibility ==
Email software that complies with [https://tools.ietf.org/html/rfc2822 RFC 2822] is only required to support plain text, not HTML formatting. Sending HTML formatted emails can therefore lead to problems if the recipient's email client does not support it. In the worst case, the recipient will see the HTML code instead of the intended message.
Among those email clients that do support HTML, some do not render it consistently with [[W3C]] specifications, and many HTML emails are not compliant either, which may cause rendering or delivery problems.
In particular, the <code><nowiki><head></nowiki></code> tag, which is used to house CSS style rules for an entire HTML document, is not well supported, sometimes stripped entirely, causing in-line style declarations to be the [[De facto standard|''de facto'' standard]], even though in-line style declarations are inefficient and fail to take good advantage of HTML's ability to [[Separation of content and presentation|separate style from content]].{{
{| class="wikitable"
|+"Email standards project" ''Acid test'' comparison (as of January 2013)
|-
!Clients !! Result (as of)
Line 34 ⟶ 38:
|[[Apple Mail]]
|{{yes|Solid support (28 November 2007)}}
|-
|[[Apple MobileMe]]
Line 72 ⟶ 75:
== Style ==
Some senders may excessively rely upon large, colorful, or distracting [[font]]s, making messages more difficult to read.<ref>{{cite web |last=Shobe |first=Matt |url=http://www.burningdoor.com/matt/archives/000782.html |title=A pretty fair argument against HTML Email |publisher=Burningdoor.com |date=2004-10-12 |accessdate=2012-06-24 |url-status=dead |archiveurl=https://web.archive.org/web/20120424084806/http://www.burningdoor.com/matt/archives/000782.html |archivedate=24 April 2012
== Multi-part formats ==
Many email servers are configured to automatically generate a plain text version of a message and send it along with the HTML version, to ensure that it can be read even by text-only [[email client]]s, using the <code>[[MIME content type|Content-Type]]: [[MIME#
Many{{Citation needed|date=September 2009}} [[Electronic mailing list|mailing list]]s deliberately block HTML email, either stripping out the HTML part to just leave the plain text part or rejecting the entire message.{{Citation needed|date=September 2009}}
The order of the parts is significant. RFC1341 states that: ''In general, user agents that compose multipart/alternative entities should place the body parts in increasing order of preference, that is, with the preferred format last.''<ref>{{cite web|url=http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html|title=RFC1341 Section 7.2 The Multipart Content-Type
== Message size ==
HTML email is larger than plain text. Even if no special formatting is used, there will be the overhead from the tags used in a minimal HTML document, and if formatting is heavily used it may be much higher. Multi-part messages, with duplicate copies of the same content in different formats, increase the size even further. The plain text section of a multi-part message can be retrieved by itself, though, using [[IMAP]]'s FETCH command.<ref>{{cite web|url=http://dsv.su.se/jpalme/ietf/mhtml-discussion.html |title=Do we really want to send web pages in e-mail? |publisher=Dsv.su.se
Although the difference in download time between plain text and mixed message mail (which can be a factor of ten or more) was of concern in the 1990s (when most users were accessing email servers through slow [[modem]]s), on a modern connection the difference is negligible for most people, especially when compared to images, music files, or other common attachments.<ref>[http://www.georgedillon.com/web/html_email_is_evil_still.shtml HTML Email
== Security vulnerabilities ==
HTML allows a link to be
If an email contains inline content from an external server, such as a [[Digital image|picture]],
▲HTML allows a link to be displayed as arbitrary text, so that rather than displaying the full URL, a link may show only part of it or simply a user-friendly target name. This can be used in [[phishing]] attacks, in which users are fooled into believing that a link points to the website of an authoritative source (such as a bank), visiting it, and unintentionally revealing personal details (like bank account numbers) to a scammer.
retrieving it requires a request to that external server which identifies where the picture will be displayed and other information about the recipient. [[Web bug]]s are specially created images (usually unique for each individual email) intended to track that email and let the creator know that the email has been opened. Among other things, that reveals that an email address is real, and can be targeted in the future.
Some phishing attacks rely on particular features of HTML:<ref name=Trend>{{cite web|title=Trend-spotting email techniques: How modern phishing emails hide in plain sight |date=August 18, 2021 |url=https://www.microsoft.com/en-us/security/blog/2021/08/18/trend-spotting-email-techniques-how-modern-phishing-emails-hide-in-plain-sight/ |publisher=Microsoft.com}}</ref>
* Brand impersonation with procedurally-generated graphics (such graphics can look like a trademarked image but evade security scanning because there is no file)
* Text containing invisible [[Unicode]] characters or with a zero-height font to confuse security scanning
* Victim-specific URI, where a malicious link encodes special information which allows a counterfeit site to be personalized (appearing as the victim's account) so as to be more convincing.
Displaying HTML content frequently involves the client program calling on special routines to parse and render the HTML-coded text; deliberately mis-coded content can then exploit mistakes in those routines to create security violations.{{cn|date=June 2024}} Requests for special fonts, etc, can also impact system resources.{{cn|date=June 2024}}
During periods of increased network threats, the US Department of Defense
The multipart type is intended to show the same content in different ways, but this is sometimes abused; some [[email spam]] takes advantage of the format to trick [[spam filter]]s into believing that the message is legitimate. They do this by including innocuous content in the text part of the message and putting the spam in the HTML part (that which is displayed to the user).
Line 102 ⟶ 110:
Most email spam is sent in HTML{{Citation needed|date=December 2013}} for these reasons, so spam filters sometimes give higher spam scores to HTML messages.{{Citation needed|date=December 2013}}
In 2018 a vulnerability ([[EFAIL]]) of the HTML processing of many common email clients was disclosed, in which decrypted text of [[Pretty Good Privacy|PGP]] or [[S/MIME]] encrypted email parts can be caused to be sent as an attribute to an external image address, if the external image is requested. This vulnerability was present in Thunderbird, macOS Mail, Outlook, and later, Gmail and Apple Mail.<ref name="ars">{{cite web|url=https://arstechnica.com/information-technology/2018/05/decade-old-efail-attack-can-decrypt-previously-obtained-encrypted-e-mails/|title=Decade-old Efail flaws can leak plaintext of PGP- and S/MIME-encrypted emails|website=arstechnica.com|date=14 May 2018 }}</ref>
== See also ==
* [[Email production]]
▲* [[Enriched text]] — an HTML-like system for email using MIME
== References ==
{{Reflist
== External links ==
* https://www.caniemail.com/
[[Category:Email]]
| |||