HTML email: Difference between revisions

Revision as of 11:40, 18 March 2023

Revision as of 00:07, 23 June 2024

Line 97:

HTML content requires email programs to use engines to parse, render and display the document. This can lead to more security vulnerabilities, denial of service or low performance on older computers.

During periods of increased network threats, the US Department of Defense convertshas allconverted user's incoming HTML email to text email.<ref>{{cite web|publisher=nextgov.com|url=httphttps://fcwwww.nextgov.com/articlescybersecurity/2006/12/22/dod-bars-use-of-html-emaile-mail-outlook-web-access.aspx/213308/|date=December 22, 2006 |title=DOD bars use of HTML e-mail, Outlook Web Access|publisher=fcw.com|accessdate=20152024-06-2322}}</ref>

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).