Managed infrastructure for SMBs

Why Business Email Lands in Spam (Even With SPF, DKIM and DMARC)

Guides · GlassHosting

EmailDeliverabilityDNSSmall Business

The short answer

SPF, DKIM and DMARC prove that a message really came from your domain. They do not prove that your domain is worth trusting. Mailbox providers such as Gmail and Outlook also look at the reputation of the server and address that sent the mail, whether that server is set up like a real mail server, how people react to what you send, and whether your messages look like the spam they already see. This guide walks through the most common reasons business mail still lands in junk after the basics are done, how to check each one, and a checklist you can work through this week.

1. Your records pass, but they do not line up

DMARC only passes when SPF or DKIM passes for the same domain the reader sees in the From line. A common gap is a newsletter tool, CRM or invoicing system that signs with its own domain, so SPF and DKIM pass for that service but not for yours. Open a message you sent from each tool, view the original headers, and check that at least one of SPF or DKIM shows your own domain and a pass. If not, set up the custom sending domain or DKIM key that the tool offers. Our guide to SPF, DKIM and DMARC for small business covers the records themselves.

2. The sending server does not look like a real mail server

If you run your own mail server or send from a VPS, providers check that the sending address has a reverse DNS (PTR) name, that the name points back to the same address, and that the server introduces itself with that name when it connects. A server that says hello as localhost, or an address whose reverse name is a generic one from the hosting company, looks like a hacked machine. Ask your provider to set the reverse DNS for the address, and set the mail server hostname to match it.

3. You inherited a bad neighbourhood

Reputation is tied to sending addresses and to the network around them. On shared hosting or a cheap VPS, someone else on the same address or range may have sent spam before you arrived. Check your sending address against the public blocklists, and check your domain as well, since some lists track domains and links inside messages. If you are listed, fix the cause first, then use the list's own removal process. If the range keeps getting listed, moving to a cleaner, dedicated address is usually faster than fighting it.

4. Marketing and everyday mail share one reputation

When newsletters, cold outreach and invoices all go out from the same domain and server, a single bad campaign can push your invoices and quotes into junk too. Send bulk and marketing mail from a separate subdomain, such as news.yourcompany.com, with its own SPF, DKIM and DMARC records. Keep person to person mail and transactional mail such as invoices and password resets on the main domain, where the reputation is protected.

5. Sudden volume from a quiet domain

A domain or address that normally sends a few dozen messages a day and then sends thousands in an hour looks exactly like a compromised account. Providers slow it down or junk it. When you start sending from a new domain, a new server or a new tool, increase volume gradually over a few weeks, start with the people most likely to open and reply, and watch the results before each step up.

6. Old lists, bounces and no easy way out

Sending to addresses that no longer exist, or to people who never asked for your mail, quickly hurts reputation. Remove hard bounces straight away, drop contacts who have not opened anything in a long time, and never buy lists. Large mailbox providers now expect bulk senders to include a clear unsubscribe link and the one-click unsubscribe header, and to honour it promptly. If unsubscribing is hard, people press the spam button instead, and that hurts far more.

7. The message itself looks like spam

Content still matters. Link shorteners, links to domains with a poor reputation, a single large image with little text, attachments that arrive unexpectedly and subject lines written in capitals are all common triggers. Use your own domain in links where you can, send a plain text version alongside the HTML version, and keep the message readable without images. If a compromised website on your domain is serving malware, mail that links to it will suffer too, so keep the website patched.

8. Forwarding and mailing lists break the checks

When a message is forwarded automatically or passes through a mailing list, SPF often fails because the forwarding server is not in your record, and a list that edits the subject or footer can break DKIM. This is one reason to rely on DKIM signing for everything you send, and to move DMARC from monitoring to enforcement only after your reports show that your real mail passes. Read the DMARC reports for a few weeks first, so you do not block your own messages.

9. Measure instead of guessing

Sign up for the free sender tools the big providers offer, such as Google Postmaster Tools and Microsoft's Smart Network Data Services, so you can see reputation and complaint signals for your own domain and addresses. Read your DMARC aggregate reports, or use a service that summarises them. Keep a few test inboxes at the main providers and send to them after any change, then check where the message landed and what the headers say.

Email deliverability checklist

  • SPF or DKIM passes for your own From domain on mail from every tool that sends for you.
  • Your sending address has reverse DNS that matches the mail server hostname, and the name points back to the address.
  • Your sending address and domain are not on the public blocklists, and you know how you would check again.
  • Marketing and bulk mail go out from a separate subdomain with its own records.
  • New domains, servers and tools are warmed up gradually instead of sending everything on day one.
  • Hard bounces are removed, old contacts are cleaned out and no bought lists are used.
  • Bulk mail carries a clear unsubscribe link and one-click unsubscribe, and requests are honoured promptly.
  • Messages avoid link shorteners, include a plain text version and read well without images.
  • DMARC reports are read before moving the policy to enforcement.
  • Postmaster tools and test inboxes are checked after every change.

Next steps

GlassHosting is a managed service and infrastructure provider: we run your servers on our own network, so you can run your business. If your invoices and quotes keep landing in junk and you would rather have someone else own the fix, see Mail That Lands, our managed business email and DNS service. Related reading: SPF, DKIM and DMARC for small business and DNS records explained for small business.

Host with GlassHosting

Order a plan or browse the knowledgebase for deeper how-tos.

Order / billing Knowledgebase All guides