Guides8 min read

Emails stopped arriving: a Monday morning guide

Your team is posting in Slack that customers aren't getting password reset emails. Your outbound campaign produced zero replies over the weekend. Support tickets are piling up. This is the 90-minute triage for a founder with a browser and no deliverability specialist.

There are two distinct failure modes that look the same from the outside: transactional email broke (users can't log in, receipts missing), or marketing/outbound email broke (replies dropped, campaigns silent). You need to know which you're dealing with before you can triage.

Good news: the first 15 minutes of diagnostics are identical for both. Start here.

First 15 minutes: did anything change?

Nine times out of ten, a sudden email failure correlates with a specific change. Ask your team:

  • Did anyone touch DNS over the weekend?
  • Did we migrate the domain, renew the domain, or change domain registrars?
  • Did we switch ESP? Upgrade a plan? Add a new sending platform?
  • Did we increase send volume recently?
  • Did anyone install a new plugin on the website?
  • Did we run any automated "domain health" tool that modified DNS records?
  • Did the ESP send any recent deliverability or compliance notices?

Write down everything that changed in the last 14 days. Even seemingly unrelated changes (a CDN migration, a new spam filter on the receiving side, a credit card expiration on your ESP account) can cascade into mail failures.

Minute 15: run a seed test

Go to Inbox Check and send your current message (transactional or marketing) through a seed test. In 2–3 minutes you'll know: (a) is mail arriving at all, (b) where is it going, (c) is authentication passing. Free, no signup.

Minutes 15–30: interpret the seed result

Scenario A: Mail is not arriving anywhere

Your domain is probably blacklisted, suspended by your ESP, or has a broken MX/SPF record. Check:

  • Log into your ESP. Is there a warning banner? A suspended sender?
  • Check the domain's payment status. Expired credit cards disable sending on most platforms.
  • Run a blacklist check (several free tools; or see the seed test output).

Scenario B: Mail arrives at some providers, not others

Provider-specific rejection. Most common:

  • Gmail only: reputation dropped or triggered a content filter.
  • Outlook/Microsoft only: SmartScreen or ATP flagged you; check Microsoft SNDS.
  • Enterprise-only: your mail is being quarantined by corporate tenants. Usually due to authentication alignment.

Scenario C: Mail arrives but lands in Spam or Promotions

The mail is technically reaching the provider. Filter decisions are sending it away from Primary. Fix vectors:

  • Authentication (if any FAIL): repair SPF/DKIM/DMARC.
  • Content (if auth is clean): audit for spam triggers, link density, image-to-text ratio.
  • Reputation (if auth and content are clean): reduce volume, warm the domain, wait.

Minutes 30–60: triage by business priority

If it's transactional mail (receipts, password resets, invitations)

This is bleeding revenue and trust. Prioritise in this order:

  1. Communicate to users. Post in your status page or on the login screen: "We're aware of email delivery delays. Please check your spam folder."
  2. Enable SMS or in-app fallback for critical flows (password reset, 2FA) if you have that capability.
  3. Contact your ESP's support. Premium plans often have a priority queue. Free plans rarely.
  4. Check if you can fail over to a second provider. Teams running critical transactional mail should have a backup (e.g. Postmark + SES).

If it's marketing or outbound

Less urgent than transactional — buyers will find you through other channels — but don't keep sending while broken. More volume into a bad-reputation state digs the hole deeper.

  1. Pause all outbound. Stop the active sequences. Stop the newsletter.
  2. Fix the root cause. Authentication first, reputation second.
  3. Resume with reduced volume. When you re-enable, start at 20–30% of previous volume. Ramp over 7–14 days.

Minutes 60–90: if you can't fix it yourself

If the diagnostic points at authentication and you don't manage your own DNS, you need to involve the person who does. Usually that's IT, an agency, or your domain registrar's support.

The escalation message should include:

  • Screenshot of the seed test result showing FAIL on SPF/DKIM/DMARC.
  • The specific record that's failing (the tool shows you).
  • What you tried and what didn't work.
  • The business urgency: "transactional mail is failing, customers are locked out."

Common root causes, ranked by frequency

  1. DMARC policy change, not propagated to senders. Team enables DMARC quarantine/reject without aligning all sending sources. Roughly 30% of "mail suddenly broken" cases in SMB.
  2. Volume ramp on a cold domain. Team started outbound on a new domain without warmup. Gmail/Outlook start filtering by week two.
  3. ESP suspension or rate limit. Expired card, TOS violation, abuse report.
  4. Blacklist. Usually after a list import that hit spam traps, or after an IP-neighbourhood incident.
  5. DNS propagation error after registrar change. MX or authentication records got dropped in the migration.
  6. Content trigger. Rare as a sole cause, but can be last-straw.

What you should do before Monday ever comes

A working Monday morning has two prerequisites:

  • Monitoring: a daily or weekly seed test, with alerts on placement drop. Catches 80% of issues before they hurt.
  • Redundancy: a backup ESP for transactional mail. Even a cold-standby sender saves you when the primary goes down.

Neither is expensive. Both are hours of setup to save days of fire-fighting.

FAQ

My ESP says everything is fine on their side. Is that reassuring?

Only partially. ESPs can only tell you about SMTP handoff (their side of the conversation). They cannot tell you whether the receiving provider inboxed or spam-foldered your mail. A seed test tells you that.

How fast can I get mail back to the inbox after a drop?

Authentication fixes propagate in 1–24 hours. Reputation recovery takes 5–14 days of careful sending. Blacklist removal ranges from automatic (24 hours) to weeks, depending on the list.

Should I switch ESPs as an emergency response?

Usually no. Most email failures are not the ESP's fault — they're authentication, reputation, or content. Switching ESP mid-crisis often makes things worse because you lose the warm reputation you built.

What's the single most common mistake in Monday-morning triage?

Continuing to send while broken. Every message you send to spam folders degrades your reputation further. Pause, diagnose, fix, then resume at lower volume.
Related reading

Check your deliverability across 20+ providers

Gmail, Outlook, Yahoo, Mail.ru, Yandex, GMX, ProtonMail and more. Real inbox screenshots, SPF/DKIM/DMARC, spam engine verdicts. Free, no signup.

Run Free Test →

Unlimited tests · 20+ seed mailboxes · Live results · No account required