Mail not reaching the inbox?

Your email keeps landing in spam? We fix it.

Deliverability problems are rarely one thing. A missing DKIM key, an SPF record that quietly overflowed, a DMARC policy somebody set to reject without checking first. We work through the signals mailbox providers actually read and fix the ones that are failing.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

mail.log

still failing

What it is

Email deliverability (SPF, DKIM, DMARC) at a glance

Email deliverability is the practice of making sure messages reach the inbox: authenticated with SPF, DKIM and DMARC; sent from a reputable IP; and compliant with Gmail and Yahoo's 2024 bulk-sender rules. The standards live as DNS TXT records.

Receiving mailbox providers combine those signals with content, volume and user behaviour to decide inbox or spam. A domain that sends from several services needs all of them aligned, or at least some of the mail will quietly fall out of the inbox.

Type
Standards and practice
SPF RFC
7208, published 2014
DKIM RFC
6376, published 2011
DMARC RFC
7489, published 2015
Typically used for
Transactional email, marketing campaigns, employee mail, preventing spoofing of your domain

The honest version

Email deliverability (SPF, DKIM, DMARC) pros and cons

No technology is all upside. This is where Email deliverability (SPF, DKIM, DMARC) earns its place and where it tends to cause trouble.

Where Email deliverability (SPF, DKIM, DMARC) is strong

  • The standards are openSPF, DKIM and DMARC are public RFCs that any mail system can implement, with no licence and no vendor in the middle.
  • Free tools to check your workMXToolbox, Google Postmaster Tools and the reports at dmarc.org show you exactly what receivers are seeing, without paying anyone.
  • Any ESP can sign for youSendGrid, Mailgun, Postmark and the rest all publish DKIM selectors you can add to DNS, so authenticated sending is a matter of records, not code.
  • Well-documented winsOnce authentication is lined up and reputation is clean, the improvement in inbox placement is measurable within days, not months.

Where Email deliverability (SPF, DKIM, DMARC) bites

  • SPF has a hidden 10-lookup limitAdd one more sender and the whole record silently turns into a permerror. Receivers then treat your mail as unauthenticated.
  • DKIM selectors differ per senderEach ESP wants its own CNAME records in your DNS, and the names clash, expire or get copied wrong during migrations.
  • DMARC can shoot your own mailMove to p=reject before every legitimate stream is aligned and receipts, newsletters or payroll notices start bouncing.
  • Reputation you did not earnShared sending IPs inherit the behaviour of other customers, and new IPs need weeks of careful warm-up before high-volume sending works.

Sound familiar?

Common Email deliverability (SPF, DKIM, DMARC) problems we fix

The Email deliverability (SPF, DKIM, DMARC) problems that bring people to us, and what you have once each one is fixed.

landing in spam

Mail goes straight to junk

Usually a mix of missing or broken authentication, a sending IP with a weak reputation, and content patterns that look like bulk mail.

Back in the inbox, with proof

SPF permerror: too many DNS lookups

The SPF record overflowed

Every new sender added an include, and the record quietly crossed the 10-lookup limit. Receivers treat it as broken.

SPF flattened and under the limit

550 5.7.26 DMARC policy

Gmail and Yahoo are rejecting your mail

The 2024 bulk-sender rules now require DMARC alignment for domains sending over 5,000 messages a day to Google or Yahoo users.

Aligned, signed and accepted

DKIM signature verification failed

DKIM is failing after a change

A mailing platform was switched, the DNS selector was not updated, or a forwarder is rewriting the body and breaking the signature.

Signatures verifying everywhere

Spamhaus listing: SBL-CSS

Your sending IP is on a blocklist

A compromised mailbox sent spam, or a shared IP picked up another tenant's problem. Delistings require cause and cleanup first.

Delisted, with the cause closed

someone is spoofing our domain

People get phishing from 'you'

Without a DMARC policy, attackers can forge your domain from anywhere. Receivers have no instruction to reject them.

Spoofing stopped at the receiver

Postmaster reputation: Bad

Gmail postmaster shows red

Complaint rates above the threshold, authentication gaps, or a sudden volume spike that looks like a compromised account.

Reputation walked back to green

no DMARC reports anywhere

Nobody knows what's being sent

DMARC is not published, so there is no visibility into which services are sending as your domain or how receivers are treating it.

Reports flowing, every sender known

What we do

Email deliverability help, from rescue to upkeep

Call us for one blocklist, or hand us the whole sending estate.

Rescue
Mail blocked, spoofed or rejected. We get the important streams flowing again, then find the cause.
Authentication
SPF, DKIM and DMARC set up correctly across every sender, with reports feeding back so you can see what is happening.
Reputation
Blocklist removals, Postmaster Tools work, and a warm-up plan for new sending IPs or domains.
Bulk-sender compliance
Getting you aligned with the Gmail and Yahoo 2024 rules so marketing and transactional mail keep landing.
Migrations
Moving between ESPs without a deliverability dip, with DNS and sending patterns handled in the right order.
Managed Tech
DMARC reports read, DNS watched, and a team to call when a new sender needs adding, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Email deliverability (SPF, DKIM, DMARC) alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Email deliverability (SPF, DKIM, DMARC) questions

Something else? Call+1 737 727 7327

Why is our email going to the spam folder?

It is usually several things at once: authentication that does not fully pass, a sending IP or domain with a thin or damaged reputation, content that resembles bulk mail, and sometimes a recipient list with old or unengaged addresses. Fixing one rarely moves the needle; fixing them together does.

What do SPF, DKIM and DMARC actually do?

SPF lists which servers are allowed to send mail for your domain. DKIM adds a cryptographic signature that proves a message was not altered and really came from the claimed domain. DMARC tells receivers what to do when SPF or DKIM fail and asks them to send you reports about it.

Can you set up DMARC without blocking our own mail?

Yes. We start at p=none with reporting on, work through every legitimate sender one at a time, and only move to quarantine and then reject once the reports show the real streams are aligned. Done this way, nothing of yours gets blocked.

How do we get off an email blocklist?

First find the cause: a compromised mailbox, a misconfigured server, a mailing list that was not opted in, or a shared IP with a bad neighbour. Fix that, then submit a delisting request to the specific blocklist with evidence. Listings removed before the cause is closed usually come straight back.

Do we need DKIM now that Gmail and Yahoo are enforcing bulk-sender rules?

If you send any meaningful volume to Gmail or Yahoo addresses, yes. Since February 2024 they require SPF, DKIM, a DMARC record, aligned From addresses and a working one-click unsubscribe for bulk senders. Mail without those is increasingly rejected rather than filtered.

How much does deliverability help cost?

Estimates are free. Tell us what you are sending and what is failing, and you get a price before any work starts.

Free estimate

Email landing in spam?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.