Being writtenEmail & identity

Email authentication: SPF, DKIM and DMARC in practice

Getting to an enforced policy without losing legitimate mail on the way.

LevelPractitioner
Material4 modules, 11 lessons
Reading time2 h 3 m
StatusBeing written — not open

This course is not available yet

It is being written. The outline below is what it will cover, and it is unlikely to change much. There is no enrolment and no date — when it is ready it will be on this page. Several of the lessons are built around tools on this site that already work, so you can practise the measurements today.

If you need this capability now rather than later, Advanced email security is the service that covers it, or talk to us.

Who it is for

Whoever owns the domain’s DNS and is being asked to "turn on DMARC" by a customer, an insurer or an auditor.

Practitioner. For people who administer these systems day to day.

Assumed beforehand:

  • Comfortable editing DNS records
  • Access to the domain’s registrar or DNS host

What you will be able to do

  • Build an inventory of every system that sends mail as your domain
  • Count SPF DNS lookups the way a receiver counts them, during evaluation
  • Tell SPF alignment and DKIM alignment apart, and explain why forwarding breaks one and not the other
  • Read an aggregate DMARC report and act on what it shows
  • Move from p=none to p=reject in stages, with a rollback at each step

Outline

4 modules, 11 lessons, 2 h 3 m of material. The times are the sum of the lessons rather than a round figure.

01The inventory nobody has

The reason DMARC enforcement loses mail is never the DNS. It is the system nobody remembered was sending.

Finding every sender14 m

The CRM, the invoicing platform, the ticketing system, the scanner in the corner, and the one marketing tool from three years ago.

Authorising a sender properly12 m

Per-platform: what to add, and why a shared include is not a licence to add ten more.

02SPF, and its one hard limit

Ten DNS lookups, counted during evaluation rather than in the record as written — which is why most checkers get it wrong.

How a receiver evaluates a record12 m

Mechanisms in order, includes followed recursively, and where the count comes from.

Staying under ten12 m

Flattening, subdomain delegation, and the trade each one makes.

~all against -all8 m

What a receiver does with each, and why softfail is where migrations go to die.

03DKIM and alignment

The half that survives forwarding, and the tags that quietly weaken it.

Keys, selectors and rotation12 m

Key length, where the selector lives, and rotating without an outage.

The l= tag and other footguns9 m

Signing part of a body leaves the rest unprotected. Signatures that omit From verify a message whose sender can be replaced.

Relaxed against strict alignment10 m

What each permits, and which one you actually want.

04Enforcement, in stages

p=none teaches you what you have. The next two steps are where care is required.

Reading aggregate reports14 m

The XML, what each failure class means, and separating forwarders from forgers.

Quarantine with a percentage10 m

Partial rollout, what pct= really does, and how long to sit at each stage.

Reject, and what breaks10 m

Mailing lists, forwarded mail, and the ARC headers that let a receiver forgive both.

Format. Written lessons, each with a check you can run against your own domain using this site’s free tools. Delivery mechanism is not built yet.

Would you rather we just did it?

This course exists because the work behind it is work we do. If you need the result rather than the skill, advanced email security is the service that covers it.