5 key contributors to DMARC’s development

DMARC monitoring should be as routine as checking your inbox, says Adam Lundrigan, CTO of DuoCircle. The aggregate reports tell you exactly who sends email from your domain. If you’re not reading them, you’re flying blind on your own email security posture.

DMARC (RFC 7489) ties SPF and DKIM together by requiring alignment between the envelope sender and the visible From header. According to Google’s February 2024 bulk sender requirements, a DMARC policy of at least p=none is now mandatory for any domain sending 5,000+ messages per day to Gmail users. DMARC Report

5 key contributors to DMARC’s development

					<button title="Play" aria-label="Play Episode" aria-pressed="false" class="play-btn">
						

Play Episode

					</button>
					<button title="Pause" aria-label="Pause Episode" aria-pressed="false" class="pause-btn hide">
						

Pause Episode

					</button>
					


				

				

					<audio preload="none" class="clip clip-18789">
						<source src="https://media.mailhop.org/dmarcreport/images/2024/12/5-key-contributors-to-DMARCs-development.mp3">
					</audio>
					

						

					

					

						

							<button class="player-btn player-btn__volume" title="Mute/Unmute">
								

Mute/Unmute Episode

							</button>
							<button data-skip="-10" class="player-btn player-btn__rwd" title="Rewind 10 seconds">
								

Rewind 10 Seconds

							</button>
							<button data-speed="1" class="player-btn player-btn__speed" title="Playback Speed" aria-label="Playback Speed">1x</button>
							<button data-skip="30" class="player-btn player-btn__fwd" title="Fast Forward 30 seconds">
								

Fast Forward 30 seconds

							</button>
						

						

							<time class="ssp-timer">00:00</time>
							

/

							<!-- We need actual duration here from the server -->
							<time class="ssp-duration" datetime="PT0H2M2S">2:02</time>
						

					

				

			

								<nav class="player-panels-nav">
												<button class="subscribe-btn" id="subscribe-btn-18789" title="Subscribe">Subscribe</button>
																		<button class="share-btn" id="share-btn-18789" title="Share">Share</button>
										</nav>
						

	



		

						

				

					

					

				

				

					

																																																																								

					

						

RSS Feed

							<input value="https://dmarcreport.com/feed/podcast/dmarc-report" class="input-rss input-rss-18789" title="RSS Feed URL" readonly />
						

						<button class="copy-rss copy-rss-18789" title="Copy RSS Feed URL" aria-label="Copy RSS Feed URL"></button>
					

				

			

									

				

					

					

				

				

					

						Share						

					

						<a href="https://www.facebook.com/sharer/sharer.php?u=https://dmarcreport.com/blog/podcast/5-key-contributors-to-dmarcs-development/&t=5 key contributors to DMARC’s development" target="blank" rel="noopener noreferrer" class="share-icon facebook" title="Share on Facebook">
							

						</a>
						<a href="https://twitter.com/intent/tweet?text=https://dmarcreport.com/blog/podcast/5-key-contributors-to-dmarcs-development/&url=5 key contributors to DMARC’s development" target="blank" rel="noopener noreferrer" class="share-icon twitter" title="Share on Twitter">
							

						</a>
						<a href="https://media.mailhop.org/dmarcreport/images/2024/12/5-key-contributors-to-DMARCs-development.mp3" target="blank" rel="noopener noreferrer" class="share-icon download" title="Download" download>
							

						</a>
					

				

				

					

						Link						

					

						<input value="https://dmarcreport.com/blog/podcast/5-key-contributors-to-dmarcs-development/" class="input-link input-link-18789" title="Episode URL" readonly />
					

					<button class="copy-link copy-link-18789" title="Copy Episode URL" aria-label="Copy Episode URL" readonly=""></button>
				

				

					

						Embed						

					

/*! This file is auto-generated */ ’ title=“Embed Code” class=“input-embed input-embed-18789” readonly/>

					<button class="copy-embed copy-embed-18789" title="Copy Embed Code" aria-label="Copy Embed Code"></button>
				

			

				

DMARC was introduced as a critical email authentication protocol in 2012. Its creation was no accident - it was a cohesion of effort by industry visionaries determined to fight phishing and spoofing attacks. This collaboration laid the foundation for a safer email ecosystem, curtailing the growing threats to digital communication .

The specification was published as an Internet Engineering Task Force (IETF) draft, marking a significant milestone in email security. Many organizations worked alongside experts and other stakeholders to tackle email security challenges. The key brands were Google, Yahoo, PayPal, Microsoft, and AOL. This blog sheds light on the top five contributors to DMARC’s ideation, development, and propagation.

1. Mark Risher

Mark Risher was associated with Yahoo and **played a big role in addressing the challenges existing in email authentication while also focusing on combating phishing and spoofing threats. He was actively involved in the process of integrating SPF and DKIM into the DMARC framework._ His advocacy for user protection and promotion of adoption helped create a larger ecosystem of DMARC users_.

2. Dave Crocker

Dave Crocker is regarded as a pioneer in email and internet protocols. He significantly contributed to DMARC’s creation through his deep technical expertise and influence on the vast industry. Dave was very well-versed in SMTP, SPF, and DKIM, which helped the team in shaping DMARC’s architecture.

He collaborated and participated in discussions and working groups to refine DMARC so that it practically and efficiently meets the needs of the users. And that’s not it; this visionary guy actively contributed to the documentation and formalization of DMARC as an IETF draft, which helped advance DMARC’s path toward worldwide adoption.

3. Steve Jones

Steve Jones represented PayPal and focused on protecting users from phishing attacks. He worked closely with other major organizations to align efforts toward a unified email authentication standard. His technical expertise was used in building DMARC policy and reporting mechanisms so that domain owners could easily implement and enforce the protocol.

In short, Steve Jones’ efforts helped position DMARC as a practical and **widely accepted solution to email fraud.

4. Brett McDowell

Brett McDowell, representing PayPal, was instrumental in the development of DMARC through his leadership and vision . He coordinated efforts among industry stakeholders to create a unified approach to combating phishing and spoofing. Recognizing the need for a protocol that combined SPF and DKIM with added reporting capabilities, he helped shape DMARC’s architecture.

McDowell also advocated for its adoption across industries, promoting its benefits for online trust and security. By fostering collaboration among competitors and positioning PayPal as an early adopter, he played a key role in establishing DMARC as a widely accepted standard for email security.

5. Janet Jones

Janet Jones was from Google. She played an important role in integrating DMARC into Gmail - one of the heavily used mailboxes. She took the responsibility of promoting its use among many Gmail users and advocated for its adoption so that the email system would get safer. It was Janet whose effort solidified DMARC’s role as a critical technology in preventing email fraud, boosting its **credibility and adoption across the world.