Email standards for better messages · Email Spec

What a good
email does.

A sourced specification for every technical detail that matters: from From:and MIME to DMARC, one-click unsubscribe, accessible HTML, and dark mode. Written for humans and agents.

34 topics10 areasBuilt in the open ↗
Anatomy of a good email

One email. All of these responsibilities.

Email evolves.
So does the spec.

Full changelog →

Every detail.
A reason behind it.

Ten areas, grounded in email standards.
Pick the part of your email you’re working on.

Read it.
Check it.
Make it better.

Open the checklist →

Every topic explains what it is, why it matters, and how to implement it. Every item in the checklist is a yes/no.

Required23
Leaving it out breaks delivery, authentication, or access for some recipients.
Recommended9
What modern mailbox providers, clients, and recipients expect.
Optional1
Useful when the context calls for it.
Avoid1
Outdated, harmful, or unsafe.

Audit a delivered message. Fix what’s missing, send a test, then re-check.

Same spec.
Another pair of eyes.

Let your agent query the same specification through a read-only MCP server. Search topics, fetch guidance, build checklists, or ask what changed.

34 topicsOne specification
For peopleHTML ↗

Standards, not folklore. Primary sources on every topic.

Provider agnostic. Use any ESP, MTA, or template system.

Test the delivered message. Verify what actually arrives.