Skip to content
Writing
·6 min read

Why your email lands in spam, and the DNS fix most people skip

Drafted through my n8n + AI pipeline, edited by me.

By the end of this you'll understand why inboxes started quietly filtering small businesses, and the exact order to fix it so your invoices, reminders, and outreach actually arrive.

The mess

A client told me their booking confirmations 'just stopped arriving.' Nothing had changed on their end. What changed was the rest of the internet: in 2024 Gmail and Yahoo began enforcing rules that used to be optional. There was no bounce and no warning. The mail was simply filtered, and the owner only found out when a customer said 'I never got it.'

The wrong way people solve it

They treat it as a writing problem. They rewrite subject lines, strip the word 'free,' add emojis or remove them, and rephrase the same message five ways. It almost never helps, because the receiving server filtered the message before it read a single word. The problem is not what you said. It is that the server could not prove the mail was really from you.

The system view

Deliverability is an identity check, not a content check. Walking the path makes the fix obvious: you send, the receiver checks SPF and DKIM, it checks DMARC alignment, it weighs your complaint history, and only then does it choose inbox or spam. Your job is to make every one of those checks pass, and to watch the report when one does not.

Trigger (you send) → Decision (do SPF, DKIM, and DMARC pass and align?) → Action (inbox or spam) → Human review (read Postmaster Tools) → Alert (complaint spike) → Record (suppress and clean the list).

What I would build

SPF and DKIM for every service that sends as you: your CRM, your app's transactional mail, your newsletter, your invoicing tool. DMARC published on a monitoring setting first, reports read for two weeks, then tightened, so you never block your own mail by surprise. A working one-click unsubscribe header on anything that resembles bulk. And Google Postmaster Tools connected, so you can see your reputation instead of guessing at it.

What can break

SPF set but DKIM forgotten, the half-fix most people stop at. DMARC tightened to reject too early, so legitimate mail vanishes. A forgotten service quietly sending unsigned mail from your domain and dragging your reputation down. An old, unverified list spiking complaints the moment you send. Each one is avoidable, but only if you do the steps in the right order.

What the business gets

Your real mail in the inbox, a sender reputation you can see and defend, and the end of 'did you get my email?' That means fewer lost bookings, fewer invoices you have to chase twice, and faster replies because people actually receive you.

Deliverability is not about clever words. It is about being a sender the receiving server already trusts before it reads one.

Bring me the workflow that sends your email: invoices, reminders, outreach, all of it. I'll tell you what I'd authenticate and fix first.

Building something this should run inside?

Book a systems call