Beyond Deliverability Ops

Deliverability work (making sure your email reaches the inbox) often starts as firefighting: something breaks and someone fixes it. Organisations that rely on email are turning it into an ongoing practice called email operations, which looks after the whole email channel. This article explains what that covers, how to tell where you stand, and how to start from zero.

From fixing problems to running a practice

Deliverability work tends to grow through three stages:

1. Firefighting. “We got blocklisted. Fix it.” Someone reacts when mail lands in spam or bounces. Nobody watches for problems in advance.
2. Prevention. You set up authentication, monitoring and alerts, and write down good sending habits. Problems get caught before they grow.
3. Email operations. Deliverability becomes one part of running the email channel as a whole. That includes infrastructure, data, compliance, reporting and business goals.

What email operations covers

Email operations treats email as one connected system. It usually covers five areas.

Infrastructure

• Sending: your mail servers or ESP (email service provider, such as Mailchimp or Amazon SES), your IP addresses and how you warm them up (raise volume slowly so providers learn to trust them), and your domains and DNS records.
• Backup plans: what happens if your ESP has an outage, or you need to move to another one.
• Data systems: where subscriber data lives, how it syncs between tools like your CRM (customer database) and your ESP, and your suppression list (addresses you must never mail again).

Data quality

• Track where each address came from, so you can spot sources that bring bad addresses.
• Validate and clean your lists regularly.
• Score each subscriber by how recently they engaged, and stop mailing people who never do.
• Decide who may add addresses to your system, and what proof of consent you keep.

Compliance

• Follow the laws where your readers live: CAN-SPAM (US), CASL (Canada), GDPR (EU and UK) and CCPA (California).
• Handle data requests, such as “delete my data”, within the legal deadline.
• Meet mailbox provider rules. Gmail and Yahoo require bulk senders (5,000+ messages a day to their users) to have SPF, DKIM and DMARC, one-click unsubscribe, and spam complaints under 0.3%. Microsoft (Outlook.com) has required SPF, DKIM and DMARC for bulk senders since May 2025.

Reporting

• How the mail is doing: delivery rate, bounces, deferrals (temporary “try later” replies), authentication pass rates, and reputation at each provider.
• What the mail earns: revenue per email, revenue per subscriber, and email’s share of total sales.

Working with other teams

• Marketing: plan big campaigns together, choose who gets each email, and review content for risks.
• Engineering: check how infrastructure changes affect delivery, and run incidents together.
• Legal: agree how consent is collected and stored, and how data requests are handled.

Where do you stand? Five maturity levels

A maturity level describes how organised your email work is. Most teams move up one level at a time.

Level 1: Ad hoc

Nobody owns email. Problems get attention only when someone notices them. Authentication may be half set up, and marketing sends without any deliverability check. A single bad campaign can cause a crisis, with no warning.

Level 2: Foundations

You publish SPF, DKIM and DMARC with p=none (monitor only). You use Google Postmaster Tools and check blocklists. Bounces are processed automatically. One person looks after deliverability as part of a bigger job. Gaps remain: monitoring is patchy and responses are slow.

Level 3: Operational

DMARC is enforced with p=quarantine or p=reject, so providers act on mail that fails. Automated alerts watch your key numbers. You have a written incident process and segment by engagement. A named person or team owns deliverability, reports monthly and documents the setup. If email brings in real revenue, aim for at least this level.

Level 4: Optimised

Everything in level 3, plus automation for routine fixes such as slowing down on deferrals and removing bounced addresses. You test send times and segments with data. You plan capacity for growth and review results with other teams each quarter.

Level 5: Strategic

Email operations helps shape business decisions. The team runs constant experiments, uses prediction tools, and shares live dashboards with the whole company. Few organisations need this level.

Building a practice from zero

Spread the work over a few months. Each month builds on the last.

Month 1: Foundations

1. Check your SPF, DKIM and DMARC with the DNS lookup and the test inbox.
2. Sign up for Google Postmaster Tools and Microsoft SNDS (Smart Network Data Services, which shows how your IPs look to Microsoft).
3. Set up blocklist monitoring.
4. Write down every domain, IP address and tool that sends mail for you, and who manages each one.

Month 2: Visibility

1. Build one dashboard with your key numbers.
2. Set alerts for sudden jumps in bounces or complaints.
3. Track results per campaign.
4. Audit your list: where addresses came from and when each person last engaged.

Month 3: Process

1. Write an incident plan: who acts, what they check, who they tell.
2. Create a pre-send checklist.
3. Start segmenting by engagement.
4. Agree a regular report and meeting with marketing.

Month 4 and after: Improvement

1. Automate list cleaning.
2. Write a warm-up plan for new domains and IPs.
3. Test where your mail lands at each provider (inbox placement testing).
4. Keep notes on what works at each provider.

Tools

What you need	What it does	Examples
Reputation monitoring	Shows how providers see you	Google Postmaster Tools, Microsoft SNDS
Blocklist monitoring	Alerts you when you’re listed	MXToolbox, multirbl.valli.org
Inbox placement tests	Shows inbox vs. spam per provider	Validity Everest, GlockApps
Email validation	Finds bad addresses before you send	ZeroBounce, NeverBounce, Kickbox
Authentication checks	Confirms SPF, DKIM and DMARC are right	Mailwel test inbox, DNS lookup, header analyzer
DMARC reporting	Turns DMARC reports into readable charts	dmarcian, Valimail, Postmark
Alerts	Tells the right person fast	PagerDuty, Slack, ESP alerts

Where email operations is heading

These are reasonable expectations, not certainties.

Closer to marketing operations

Email and marketing teams increasingly share the same customer data, consent records and reporting. People in email operations will need to know marketing tools as well as deliverability.

More automation

Routine jobs are likely to become automatic. Examples include rotating DKIM keys (replacing the keys that sign your mail), removing addresses before they go bad, and slowing sending when a provider pushes back. People will spend more time designing systems, handling unusual incidents and making decisions.

More rules

Privacy laws and provider requirements keep growing. Expect more time on consent records, audit trails and checks on the vendors who handle your data.

Ideas from reliability engineering

Some teams borrow habits from site reliability engineering (SRE), the practice software teams use to keep services running:

• Service level objectives (SLOs): a target you measure, such as “99.5% of password-reset emails delivered within 60 seconds”.
• Error budgets: how much failure you accept before you stop and fix things, such as “pause sends if hard bounces pass 0.5%”.
• Severity levels: clear rules for how fast each kind of incident gets attention.
• Post-mortems: a written, no-blame review after each incident, so it doesn’t happen again.

The numbers above are examples to adapt, not industry standards.

Skills for the job

• Technical: DNS and email authentication (SPF, DKIM, DMARC, BIMI, ARC), how SMTP (the protocol servers use to pass email) works, ESPs and APIs, and basic networking.
• Analytical: reading logs, spotting trends, finding root causes, and basic SQL or spreadsheets.
• Communication: explaining technical problems in business terms, and writing clear incident reports.
• Strategic: how email fits into marketing, the privacy laws that apply to you, and choosing vendors.

Email remains one of the most direct ways a business can reach its customers. Running it as an ongoing practice, not a series of fixes, protects that channel.

What to do next

• Find your level in the five maturity levels above.
• Pick the next level’s missing pieces and finish them one at a time.
• Name one owner for email deliverability, even part time.
• Run the month 1 steps if you have no monitoring yet.
• Write a short incident plan before you need it.