You send a client update that's accurate, useful and properly formatted. The client doesn't see it in the inbox. Gmail places it in Promotions, Outlook files it away from Focused Inbox, or the message turns up in Spam hours later. From your side, the campaign appears to have been delivered, so the problem is easy to miss.
That's why improving email deliverability requires more than rewriting subject lines. Mailbox providers assess your sending identity, authentication, domain reputation, recipient engagement, list quality and sending behaviour together. A weakness in one area can undermine the rest.
The practical priorities are clear: authenticate the domain properly, measure inbox placement rather than delivery alone, maintain a disciplined list, and send content in a consistent way that recipients recognise and value. Follow those controls and you'll replace guesswork with evidence.
Table of Contents
- Why Legitimate Email Still Misses the Inbox
- Getting SPF, DKIM and DMARC Working in the Right Order
- Understanding Inbox Placement Beyond the Spam Folder
- List Hygiene and Engagement Signals That Actually Move the Needle
- Content, Subject Lines and Sending Patterns That Build Sender Reputation
- Monitoring and Fixing Problems After Mail Check Retires
- Your 30-Day Deliverability Action Plan
Why Legitimate Email Still Misses the Inbox
A mailbox provider doesn't decide whether your message is legitimate from the wording alone. It checks whether the sending domain is authorised, whether the message carries a valid signature, whether the sender has a trustworthy history and whether recipients normally interact with similar mail.
That explains why a perfectly reasonable invoice reminder can miss the inbox while a less polished message from an established sender arrives immediately. The recipient may have opted in, but the receiving system still has to decide whether the message belongs in the main inbox, a secondary category, junk or nowhere visible at all.
The DMA's Email Benchmarking Report 2025 records a 98% delivery rate in 2024, with B2C campaigns reaching 99.2%. The same report records an overall open rate of 35.9% and a unique click rate of 2.3%. Those figures describe a healthier sending environment, but they don't prove that every accepted message reached the place where a person was likely to notice it.
The four areas that need attention
- Authentication: SPF, DKIM and DMARC tell receiving systems which services may send for your domain and what to do when a message fails those checks.
- Placement: A message can be accepted without appearing in the Primary inbox. Gmail categories and other filtering systems can reduce visibility without creating an obvious bounce.
- List quality: Old, mistyped or uninterested addresses create bounces, complaints and weak engagement signals.
- Content and cadence: Recipients respond to clear, relevant mail sent at a predictable pace. Bursts, misleading subjects and broken layouts reduce those positive signals.
Practical rule: Treat a deliverability problem as a system fault, not bad luck. Check identity, placement, recipients and sending behaviour before changing the copy.
A 98% delivery rate means that 2 in every 100 messages fail to reach the recipient mailbox or are otherwise lost in transit, based on the DMA benchmark. That makes delivery an important baseline, but not the final measure of success. Your real question is whether the intended recipient can find, trust and act on the message.
Getting SPF, DKIM and DMARC Working in the Right Order
Authentication succeeds when you build it in sequence. Publishing three DNS records without mapping how your website, CRM, accounting platform and email service send mail leaves gaps under one domain.
Start with SPF
Sender Policy Framework, or SPF, lists the services authorised to send on your domain's behalf. Identify every legitimate source, remove retired services and keep the record within the DNS lookup limit. A valid SPF record that omits your billing platform remains a production fault, because those messages can fail authentication.
SPF also has a clear limit: forwarding can change the original delivery path. Use DKIM to cover that weakness instead of making SPF carry the entire control.
Add DKIM signing
DomainKeys Identified Mail, or DKIM, adds a cryptographic signature to outgoing messages. Your email provider holds the private key, while DNS publishes the matching public key. Check that each platform signs mail, the selector is correct and the visible From domain aligns with the authenticated domain where required.
Use a strong key managed by the sending platform and document every selector. The recurring operational fault is an overlooked service sending unsigned mail after a system change, not a broken DNS record.
Use DMARC to enforce the result
DMARC instructs receiving servers how to handle messages that fail SPF or DKIM alignment, then sends reports to your organisation. The NCSC DMARC guidance recommends publishing SPF and DKIM first, starting DMARC at p=none, reviewing reports, then moving to p=quarantine or p=reject.
Keep monitoring long enough to identify every legitimate sender. The NCSC recommends reviewing reports for at least 2 weeks after switching to reject, giving you time to catch a forgotten platform or misconfigured sender.
UK businesses often remain at p=none. That policy provides visibility, but it does not block impersonation. UK-focused reporting found that 56% of UK domains remained vulnerable to spoofing, while 44.1% had reached DMARC enforcement at p=reject and 18.9% remained at p=none. The analysis also recorded 93.7% SPF correctness and 20.6% MTA-STS adoption. Basic setup is more common than full enforcement. Read the UK email spoofing analysis for the source data.
For online retailers, follow this SPF DKIM DMARC setup for ecommerce walkthrough. Once reports show legitimate traffic passing reliably, enforce the policy. Quarantine should be the minimum working position, with reject as the end state.
Understanding Inbox Placement Beyond the Spam Folder
“Delivered” only means the receiving system accepted the message. It doesn't tell you whether Gmail put it in Primary, Promotions or Spam, and it doesn't reveal whether Outlook separated it from the messages the recipient checks first.
The distinction matters in the current UK deliverability picture. The 2026 benchmark data records a median spam-folder rate of 8.4%, Promotions placement in Gmail of 38%, and only 53.6% of the median sender's Gmail traffic reaching Primary. Those figures describe visibility loss, not mere rejection.
Read the outcome, not just the bounce report
| Outcome | Where it lands | Visibility to sender | Impact on reputation |
|---|---|---|---|
| Accepted and placed in Primary | Main inbox | Usually visible through engagement reporting | Positive interaction can support sender trust |
| Accepted and placed in Promotions | Gmail Promotions | Often looks delivered unless placement testing is used | Lower visibility can reduce interaction |
| Accepted and placed in Spam | Junk or spam folder | Sometimes visible through complaints or testing | Complaints and weak engagement can damage reputation |
| Rejected or deferred | Outside the mailbox, or delayed | Usually visible through bounce and delivery logs | Repeated failures can indicate an authentication or reputation problem |
Gmail categorisation considers the sender identity, the recipient's history with your mail and the character of the message. Promotional links, discount-heavy language and image-led layouts can reinforce a commercial classification, even when the message is legitimate. That isn't automatically bad, but it changes whether the recipient sees it during their normal inbox routine.
Track inbox placement rate, meaning the share of sent messages that reach the intended inbox location, alongside bounce and complaint data. Use seed accounts across Gmail, Outlook and other relevant providers before important sends, then compare those results with real engagement. A low spam rate can still hide a Primary-tab problem.
List Hygiene and Engagement Signals That Actually Move the Needle
List hygiene isn't a quarterly spring clean. It's a running process that protects your sending reputation every time you import a contact, receive a bounce or process an unsubscribe.
Start with suppression. Confirmed opt-outs must never re-enter a campaign through a second system. Role addresses such as info@ and sales@ deserve separate treatment because they can be shared, monitored inconsistently or unsuitable for marketing. Suppress hard bounces immediately, and don't allow a failed address back into a future send without a clear reason.
Build maintenance into the workflow
- Protect new sign-ups: Use double opt-in and validate capture forms so misspelled or fake addresses don't enter the active list.
- Separate engagement levels: Send priority campaigns to contacts who regularly open, click or reply. Keep inactive groups out of ordinary broadcasts.
- Run a win-back process: Re-engage dormant contacts with a clear choice, then sunset those who remain unresponsive. Don't keep dead weight to make the database look larger.
- Review before major sends: Check suppression lists, recent bounces and segment logic before launching a large campaign.
Mailbox providers use recipient behaviour as evidence of whether your mail is wanted. Opens, clicks, replies and continued interaction help establish that relationship. Spam complaints are much more damaging than a quiet recipient, so sending fewer relevant messages is preferable to repeatedly mailing people who never respond.
Watch the warning signs
Look at list growth alongside attrition, not growth alone. A list that expands while unsubscribes, hard bounces and inactive contacts accumulate may be weakening even if the headline contact count rises.
After each send, compare the inbox-to-spam outcome for inactive segments with your engaged audience. Rising unsubscribe volume often signals content fatigue before the problem becomes a serious complaint pattern. Give recipients a clear unsubscribe route, honour it across every sending system and keep transactional and marketing permissions separate.
Content, Subject Lines and Sending Patterns That Build Sender Reputation
Mailbox providers don't reward attractive design by itself. They respond to what recipients do after the message arrives. If people open, read, click, reply and continue accepting your mail, the sender earns useful engagement signals. If they delete it, ignore it or report it as spam, the system receives the opposite message.
Subject lines should set an accurate expectation. Keep them under 60 characters, use personalisation sparingly and don't stack trigger terms such as “free”, “urgent” and “guarantee”. A short, precise subject usually gives the recipient a better reason to open than a string of sales prompts.
Match the message to the recipient
Separate operational mail from marketing campaigns. An invoice, password notice or service update should use a clear purpose-specific From name, such as “Acme Accounts”. A newsletter can use “Acme News”. This distinction helps recipients recognise the message and gives you cleaner data when you investigate a placement issue.
Keep the content honest and readable. Make sure the body reflects the subject, provide useful text around images, add alt text and test the design on mobile and desktop clients. A broken template doesn't just look untidy. It can reduce the clicks and replies that mailbox systems use to assess recipient interest.
If you're unsure whether a draft contains risky phrasing, use Mailwarm to check your email for spam words. Treat the result as a review aid, not a guarantee of inbox placement. No checker can override poor list quality or a damaged sender reputation.
Send with discipline
Predictable cadence beats sudden bursts. Don't hold a month of campaigns and release them in one afternoon because the content calendar slipped. If you change domain, platform or infrastructure, introduce volume gradually and watch authentication, bounces and complaints before increasing it.
A dedicated IP can make sense for high-volume programmes, but it adds responsibility. Small businesses should first fix identity, list quality and engagement rather than buying infrastructure as a substitute for operational control.
Recipients determine reputation through behaviour. Write for the action you want, then send only to people likely to take it.
Monitoring and Fixing Problems After Mail Check Retires
The NCSC's centralised Mail Check service is being retired in 2026, so UK organisations need their own monitoring process. The change matters because publishing DMARC is only half the job. Someone must review reports, identify an unknown sender and decide whether a failed message is a mistake or an impersonation attempt.
UK-focused reporting also highlights the visibility gap. More than 80% of domains still had no DMARC record or used a non-enforcing policy, and more than 70% of DMARC-enabled domains lacked reporting tags, according to UK DMARC adoption reporting. Without reporting tags, teams can't reliably see which systems are sending, failing alignment or attempting to impersonate the domain.
Replace one service with a working stack
| Tool | What it monitors | Cadence |
|---|---|---|
| Google Postmaster Tools | Gmail domain reputation, spam signals and authentication performance | Review routinely, especially after major campaigns |
| Microsoft SNDS | Microsoft-facing IP reputation and complaint-related signals | Review routinely for Outlook traffic |
| DMARC reporting platform | Authenticated sources, alignment failures and policy outcomes | Weekly |
| GlockApps or Mail Tester | Seed-list placement and message-level checks | Before important sends |
| ESP reporting | Bounces, complaints, unsubscribes and engagement by segment | After every campaign |
Don't treat one seed test as proof that every recipient will see the message in the same place. Test accounts reveal a useful sample, while real mailbox decisions vary according to recipient history and provider-specific filtering.
Use a simple incident response
If reputation drops suddenly, pause non-essential sends. Check recent DNS or ESP changes, inspect DMARC failures, review complaint trends and identify whether one segment or campaign caused the shift.
Resume with a small, engaged audience once the cause is understood. Keep the cadence controlled, then expand only when authentication and engagement return to normal. For organisations that want an engineer to manage the surrounding email filtering, hosting and security controls, Networking2000 is one UK IT support option to consider.
Your 30-Day Deliverability Action Plan
Use this programme yourself or give it to your IT partner. The sequence matters. A clean list cannot fix broken authentication, and correct DNS records cannot overcome recipients ignoring your mail.
Week one, audit and fix
Pull SPF, DKIM and DMARC records for every sending domain. List each legitimate platform, remove obsolete entries, and correct syntax or alignment problems before changing enforcement. Confirm that sending hostnames have matching forward and reverse DNS records. Review DMARC results before moving from observation to stricter enforcement.
Week two, observe placement
Keep DMARC reporting active while checking every authenticated source. Test seed accounts across the mailbox providers your customers use, then record whether messages reach the intended inbox, promotions area or spam folder. Treat the ESP delivery figure as only one signal. Inbox placement is the number that shows whether recipients can find the message.
Week three, clean and segment
Suppress hard bounces, confirmed opt-outs and unsuitable role addresses. Run a focused re-engagement campaign for dormant contacts, then remove people who do not respond. Use this practical guide to clean your email list.
Week four, standardise and report
Set a predictable cadence, separate transactional and marketing identities, review subject lines, and test rendering before launch. Establish weekly DMARC checks, campaign-level bounce and complaint reviews, plus a monthly report covering inbox placement and engagement.
Deliverability needs ongoing control. Keep DNS records, list rules, placement tests and reporting routines documented. Investigate changes before they become lost enquiries or missed invoices.
Networking2000 can help UK businesses review email authentication, filtering, hosting and wider network security. Visit Networking2000 to discuss a practical deliverability and IT support review for your organisation in London, Essex and nearby areas.
