Securely Sending Email in 2024
summary
Shows actual deployment details and results: DMARC, DKIM, and SPF are configured, signature keys live in DNS, and reporting is functional. One-week data shows 34 million messages protected by DMARC across 84,000 domains yet only 62% of messages and 32% of domains use enforcing DMARC policies. Major providers require SPF+DKIM and bulk senders (>5,000/day) must publish DMARC. Practical advice is concrete: start DMARC at p=none and ingest reports, fix SPF/DKIM, then transition to quarantine or reject for enforcement.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:12Email authentication importance
- 3:40Sender spoofing example
- 5:25Email history and SMTP
- 9:58SMTP design and Postel’s Law
- 12:51How SMTP delivers email
- 15:01Open SMTP relays problem
- 17:06Email envelope vs content
- 18:54Sender spoofing risks
- 21:01SPF prevents spoofing
- 24:34DMARC and DKIM for integrity
- 28:49DMARC enforces authenticity
- 32:22Implement email authentication
- 34:10DMARC deployment guide
- 37:23Configuring SPF and DKIM
- 38:25DMARC adoption trends
- 40:55New Zealand DMARC enforcement
- 42:24Homework and next steps
related talks
44mModern Email Security
42mThe not so simple mail transport protocol
47mHow to Detect Your Domains Being Abused for Phishing Using DNS
19mHow Safe Is Your Domain?
24mEnd-to-End Measurements of Email Spoofing Attacks
22mNot that Simple: Email Delivery in the 21st Century
47mSecure messaging - how to protect yourself & your company
31mHow to Write Terrible Emails Well?