Email playbook
Rules for email that arrives, reads well and stays safe. Authentication, deliverability, unsubscribe, rendering, privacy and security, each with a check.
- Required 44
- Recommended 16
- Optional 6
- Avoid 1
An email playbook for any app or business that sends email, from password resets to newsletters. It covers the message itself, the sending domain, delivery, unsubscribing, layout, privacy, security and automation.
Every rule rests on the standards that mailbox providers enforce, such as the RFCs and the sender rules of Gmail, Yahoo and Microsoft. Each one has a check you can run, often a DNS lookup, a header to read or a test send.
Start with Sending domain and authentication. Without SPF, DKIM and DMARC, large providers reject bulk mail outright.
Chapters
Message basics
Build every message to the internet standards, with the right headers, a plain-text part, UTF-8, a declared language and a size inboxes accept.
- Required 5
- Recommended 3
Sending domain and authentication
Prove each message is yours with SPF, DKIM and DMARC on aligned domains, and send it over checked TLS, or large inboxes reject it.
- Required 6
- Optional 3
Deliverability
Reach the inbox by meeting the big providers' sender rules, keeping complaints low, separating mail streams and sending only to people who asked.
- Required 4
- Recommended 4
Unsubscribe and bounces
Let people leave with one click and honour it within two days. Treat bounces and complaints as orders to stop, and retry only temporary errors.
- Required 8
- Recommended 1
- Optional 1
Layout and accessibility
Build email that every client can show and every reader can use. Semantic HTML, live text, clear contrast, small files and a test send to each major client.
- Required 8
- Recommended 4
Email privacy
Send only what the message needs and track as little as you can. Opens are not reliable, so ask first, keep proof of consent and keep logs lean.
- Required 5
- Recommended 1
Email security
Keep attackers away from your recipients and readers. Send safe links, single-use sign-in links and no secrets, scripts or risky files, and resist phishing.
- Required 5
- Recommended 1
- Optional 1
- Avoid 1
Automation and agents
Make email that machines can use. Correct calendar invites, structured order data, honest automated mail and messages AI assistants can read safely.
- Required 3
- Recommended 2
- Optional 1
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers email playbook: https://agentwranglers.se/playbook/email.