HTML email: Difference between revisions

Content deleted Content added
Security vulnerabilities: «"a security issue for users, who may be" → "used in phishing attacks, in which users are", +", visiting it,", -"", "to a scammer" → "(like bank account numbers) to a scammer", +"revealing", "read"
Security vulnerabilities: «+"Some [[e-mail", "[[E-mail" → "takes advantage of the multi-part message format to trick spam filters into believing that the message is legitimate by including e-mail spam", +" for these reasons", "high" → "
Line 34:
If an email contains inline content from an external server, such as an [[Digital image|image]], the server can alert a third party that the e-mail has been opened. This is a potential privacy risk, revealing that an email address is real (so that it can be targeted in the future) and revealing when the message was read. For this reason, some e-mail clients do not load external images until requested to by the user.
 
Some [[e-mail spam]] takes advantage of the multi-part message format to trick [[spam filter]]s into believing that the message is legitimate, by including innocuous content in the text part of the message and putting the spam in the HTML part (which is what displays to the user).
Most [[E-mail spam]] is sent in HTML, so spam filters (such as [[Spamassassin]]) give high spam scores to HTML messages.
 
Most [[Ee-mail spam]] is sent in HTML for these reasons, so spam filters (such as [[Spamassassin]]) give highhigher spam scores to HTML messages.
 
== References==