Email deliverability

Definition
Whether an email actually reaches the primary inbox rather than being dropped or filtered into spam.

Why it matters

The best offer achieves nothing if nobody sees it, and the failure is silent. The sending tool reports an email as sent whether it lands in the inbox or in spam, so a dashboard full of delivered messages tells you very little.

Teams often blame the message or the market when the fault is a missing DNS record or a dirty list. They rewrite subject lines and change the offer, and nothing improves because the problem was never the copy.

Deliverability also compounds. Healthy sending makes the next send easier to place, while a poor run makes everything harder, including the email your customers rely on, such as invoices and password resets. Fixing it first is usually what shows whether the message itself works.

How to apply it

  • Set up SPF, DKIM and DMARC before sending any real volume.
  • Remove hard bounces, which are permanent failures, at once. Soft bounces are temporary and can be retried.
  • Warm up new domains by starting small and growing volume as engagement stays healthy.
  • Watch complaint and open rates for each mailbox provider, since Gmail, Outlook and company systems filter differently.
  • Test a message before a large send, and follow the guidance on list hygiene.

What it is

Delivery and deliverability are different. An email is delivered when the receiving server accepts it. It is deliverable in the sense that matters only if it then lands in the inbox where the person will see it. A message can be accepted and still go straight to spam, and the sending tool will still report it as sent.

Three things decide the outcome. Authentication proves you are who you claim to be, using the DNS records SPF, DKIM and DMARC. Reputation is the history of your sending domain, covered under domain reputation. Content and list quality cover what is in the message and whether the addresses are real and wanted.

Common mistakes

  • Judging success by 'delivered'. That figure only says the server accepted the message. Check placement in the inbox, for example with seed addresses at the main providers.
  • Launching big before authentication is in place. Set up SPF, DKIM and DMARC first. Fixing them afterwards means fixing a reputation too.
  • Using an old or purchased list. Dead addresses and spam traps damage reputation faster than almost anything else.
  • Sending cold and transactional mail from one domain. If outreach goes wrong, invoices and password resets are hit too.
  • Changing everything at once. If you change the copy, the domain and the list together, you cannot tell which change helped. Change one thing at a time.
  • Ignoring complaints and unsubscribes. A rising complaint rate is the clearest warning you will get. Make unsubscribing easy and honour it quickly.
Worked example

Suppose a software company with eight staff starts a cold email campaign from a new sending domain. The first run of 2,000 emails lands mostly in spam, although the sending tool reports every one as sent. The team had skipped the DNS records and mailed an old list. They add SPF, DKIM and DMARC, remove 240 hard bounces and warm the new mailboxes over three weeks with Lemwarm, beginning at about 20 emails a day.

The next campaign reaches the inbox far more often. The copy did not change. The message was never the problem, and the fix sat in the setup, which is why the team now checks deliverability before writing a single subject line.

Tools in the example

Some links are affiliate links: we may earn a commission at no cost to you. It never decides a ranking. How we work with partners

  1. Article

    Domain reputation

    The trust score that deliverability depends on.

  2. Article

    Spam score

    A signal about a single message.

  3. Article

    Reply rate

    Only meaningful once deliverability is healthy.