Glossary - Revision history

Dmarcadmin: /* F */ Add an entry for Failure Reports

2025-05-05T20:40:42Z

‎F: Add an entry for Failure Reports

Dmarcadmin: /* G */ Add entry for GDPR

2025-05-05T20:30:30Z

‎G: Add entry for GDPR

Dmarcadmin: /* D */ Added entry for DKIM Replay

2023-05-22T04:22:52Z

‎D: Added entry for DKIM Replay

Dmarcadmin: /* V */ Fixing VMC anchor

2022-01-28T03:27:44Z

‎V: Fixing VMC anchor

Dmarcadmin: /* M */ Problem with the MVA anchor

2022-01-28T03:27:07Z

‎M: Problem with the MVA anchor

Dmarcadmin: /* B */ Typos in the BIMI anchor

2022-01-28T03:13:30Z

‎B: Typos in the BIMI anchor

Dmarcadmin: /* M */ Adding an entry for the Mark Verifying Authority (BIMI)

2022-01-28T03:00:20Z

‎M: Adding an entry for the Mark Verifying Authority (BIMI)

Dmarcadmin: /* V */ Adding an entry for Verified Mark Certificate (VMC)

2022-01-28T02:48:37Z

‎V: Adding an entry for Verified Mark Certificate (VMC)

Dmarcadmin: /* B */ Tweaking the tense for Blacklist

2022-01-28T02:34:46Z

‎B: Tweaking the tense for Blacklist

Dmarcadmin: /* W */ Updating the entry for Whitelist

2022-01-28T02:33:54Z

‎W: Updating the entry for Whitelist

@@ Line 120: / Line 120: @@
 {{anchor|F}}
 ==F==
 ;{{anchor|FUSSP}}Final Ultimate Solution to the Spam Problem (FUSSP)

← Older revision		Revision as of 20:30, 5 May 2025
Line 134:		Line 134:

	==G==		==G==
		+	;{{anchor\|GDPR}}General Data Protection Regulation (GDPR)
		+	:The [https://gdpr-info.eu General Data Protection Regulation] (GDPR) is a law of the European Union that defines how the data of individuals can be collected and processed, and under what conditions and controls, within the European Union. However because of the global nature of the Internet, it has had a very large impact on data protection standards and practices in much of the world.


		+	{{anchor\|H}}

−	~~{{anchor\|H}}~~
	==H==		==H==

← Older revision		Revision as of 04:22, 22 May 2023
Line 74:		Line 74:

	:DMARC.org and other organizations are developing ways to combat this form of Display Name abuse, and other types of email fraud.		:DMARC.org and other organizations are developing ways to combat this form of Display Name abuse, and other types of email fraud.
		+
		+
		+	;{{anchor\|DKIMReplay}}DKIM Replay Attack
		+	:A [[#DKIM\|DKIM]] Replay Attack occurs when a message with a valid DKIM signature, presumably where the signer has a good reputation, is sent to a different recipient such that the DKIM signature is still intact and valid. The sender may do this by manipulating the envelope recipient ([https://datatracker.ietf.org/doc/html/rfc5321 RFC5321] "RCPT TO:" address), and they may also change headers that were not covered as part of the DKIM signature, like the "Cc:" header. The sender will typically find a way to send a message with malicious content from a source with good reputation to a mailbox elsewhere that they have access to, retrieve the message with the DKIM signature, and then send it from other sources, like a [https://en.wikipedia.org/wiki/Botnet botnet].
		+
		+	:This type of attack was described in section 8.5 of [https://datatracker.ietf.org/doc/html/rfc4871 RFC4871] in 2007, but it became an issue for large scale mail receivers periodically during 2022. [https://proton.me/blog/dkim-replay-attack-breakdown A blog post from ProtonMail] represents an early report of this trend. This wave of activity has prompted a number of technical proposals, re-activation of the [https://ietf.org IETF]'s [https://datatracker.ietf.org/wg/dkim/about DKIM Working Group], and a great deal of discussion at industry forums like [https://www.m3aawg.org M3AAWG].

@@ Line 319: / Line 319: @@
 ==V==
-;{{anchor|Verified_Mark_Certificate}}Verified Mark Certificate (VMC)
+;{{anchor|Verified_Mark_Certificate|VMC}}Verified Mark Certificate (VMC)
 :A '''Verified Mark Certificate''' is a type of X.509 certificate meant to prove the right of an email sender to have a particular image or logo displayed with their messages under the [[#Brand_Indicators_for_Message_Identification|Brand Indicators for Message Indentification (BIMI)]] specification. VMCs are issued by a [[Mark_Verifying_Authority|Mark Verifying Authority]] when an image or logo is presented to them along with documentation proving that the applicant has rights to the trademark associated with the image or logo. The VMC is then hosted by a website, possibly operated by the VMA, and referenced in the BIMI policy record in DNS that is associated with the email messages being sent.

← Older revision		Revision as of 03:27, 28 January 2022
Line 194:		Line 194:


−	;{{anchor\|Mark_Verifying_Authority}}Mark Verifying Authority (MVA)	+	;{{anchor\|Mark_Verifying_Authority\|MVA}}Mark Verifying Authority (MVA)
	:A '''Mark Verifying Authority''' is a role under the [[#Brand_Indicators_for_Message_Identification\|Brand Indicators for Message Identification (BIMI)]] specification filled by a participating [https://en.wikipedia.org/wiki/Certificate_authority certificate authority]. When an organization presents the '''MVA''' with an image or logo, and documentation showing they have the right to use the trademark associated with that image, the '''MVA''' will issue a special X.509 certificate known as a [[#Verified_Mark_Certificate\|Verified Mark Certificate (VMC)]]. The VMC is used by email receivers to validate an email senders right to use an image or logo before displaying that image alongside email that has passed stringent email authentication checks.		:A '''Mark Verifying Authority''' is a role under the [[#Brand_Indicators_for_Message_Identification\|Brand Indicators for Message Identification (BIMI)]] specification filled by a participating [https://en.wikipedia.org/wiki/Certificate_authority certificate authority]. When an organization presents the '''MVA''' with an image or logo, and documentation showing they have the right to use the trademark associated with that image, the '''MVA''' will issue a special X.509 certificate known as a [[#Verified_Mark_Certificate\|Verified Mark Certificate (VMC)]]. The VMC is used by email receivers to validate an email senders right to use an image or logo before displaying that image alongside email that has passed stringent email authentication checks.

← Older revision		Revision as of 03:13, 28 January 2022
Line 45:		Line 45:


−	;{{anchor\|~~Brand Indicators for Message Indentification~~\|BIMI}}Brand Indicators for Message Identification (BIMI)	+	;{{anchor\|Brand_Indicators_for_Message_Identification\|BIMI}}Brand Indicators for Message Identification (BIMI)
	:'''BIMI''' is an emerging specification to allow the use of sender-specified logos or images alongside messages within participating email clients. BIMI relies on [[#DMARC\|DMARC]] and related [[#Email_Authentication\|email authentication]] standards to ensure that only messages authorized by the sender will receive this treatment. The logos are expected to be built from trademarked or similarly registered and protected images, and the system includes the concept of a [[#Verified_Mark_Certificate\|Verified Mark Certificate]] that can be used to prove the right to use said image.		:'''BIMI''' is an emerging specification to allow the use of sender-specified logos or images alongside messages within participating email clients. BIMI relies on [[#DMARC\|DMARC]] and related [[#Email_Authentication\|email authentication]] standards to ensure that only messages authorized by the sender will receive this treatment. The logos are expected to be built from trademarked or similarly registered and protected images, and the system includes the concept of a [[#Verified_Mark_Certificate\|Verified Mark Certificate]] that can be used to prove the right to use said image.

@@ Line 192: / Line 192: @@
 ;{{anchor|Malicious_Content}}Malicious Content
 :Anything in a message that will do harm to the [[#Recipient|Recipient]], or the computer and networks they use, may be referred to as '''Malicious Content'''. This typically includes the various ways of including viruses and similar content in an email message, but sometimes the term may be used to refer to messages which include a mechanism that might lead the [[#Recipient|Recipient]] to take some action that would lead to such content, like a link in the message that leads to a website that delivers code intended to compromise the web browser. '''Malicious Content''' is often referred to as '''malware'''.
@@ Line 204: / Line 210: @@
 {{anchor|N}}
 ==N==

@@ Line 312: / Line 312: @@
 ==V==
 {{anchor|W}}
 ==W==

@@ Line 32: / Line 32: @@
 ;{{anchor|Blacklist}}Blacklist
-:'''Blacklist''' is a commonly used term that refers to a collection of computers, domains, email addresses, ''et cetera'' that will automatically be blocked or disallowed whenever they are encountered. ''See also:'' [[#Whitelist|whitelist]].
+:'''Blacklist''' was a commonly used term that referred to a collection of computers, domains, email addresses, ''et cetera'' that would automatically be blocked or disallowed access whenever they were encountered. ''See also:'' [[#Whitelist|whitelist]].
 :Many organizations have switched to alternate terms like '''blocklist''' to avoid any bias issues associated with the terms '''blacklist''' and '''whitelist'''. This entry is retained due to the historical usage.

@@ Line 317: / Line 317: @@
 ==W==
-;{{anchor|Whitelist|Allowlist}}Whitelist
+;{{anchor|Whitelist}}Whitelist
-:'''Whitelist''' is a commonly used term that refers to a collection of computers, domains, email addresses, ''et cetera'' that will automatically be allowed through whenever they are encountered. Some organizations prefer the term '''allowlist''' and '''blocklist''' to avoid any potential issues associated with the terms '''whitelist''' and '''blacklist'''.
+:'''Whitelist''' was a commonly used term that referred to a collection of computers, domains, email addresses, ''et cetera'' that would automatically be allowed access whenever they were encountered.