Earlier this year an online retailer we look after told me some customers weren't getting her emails. She'd been asking people to check their spam folders, but it was hard to tell who was getting them. When she emailed me, the message sat in my junk folder for three or four days with a warning that the sender might be suspicious. So why were her emails going to junk?
She'd had the same address for years and nothing had changed on her end. That's pretty normal. Problems like this usually come from settings nobody has checked since the account was set up.
Why emails go to junk: three records that prove they're from you
When your email arrives, the receiving server checks your domain's DNS records, the settings that tell the internet where your website and email live. Three records do most of the work.
- SPF lists the servers allowed to send email for your domain. If mail comes from a server that isn't on the list, it looks suspicious.
- DKIM adds a digital signature to every email you send, so the receiver can check it wasn't changed on the way.
- DMARC tells the receiver what to do when SPF or DKIM fails, and gives you reports on it.
If any are missing or wrong, Gmail and Outlook have less reason to trust you. Google's sender guidelines spell out what it now expects from anyone sending to Gmail addresses.
A leftover record from the old system
In the retailer's case, her email had moved onto Microsoft 365 some time ago, but her SPF record still pointed at her old host's mail servers.
I replaced it with Microsoft's entry, include:spf.protection.outlook.com, which is what Microsoft says to use for Microsoft 365. The next test email landed straight in my inbox with no warning.
DKIM was the other half. She'd added a DKIM record at her old host, but for Microsoft 365 it's switched on in the Microsoft admin portal, so we switched it on there. She had no DMARC record. For a small sender I'd call that nice to have rather than urgent.
A month later a couple of wholesale customers still weren't getting her emails, even though her records checked out clean. The likely cause then is the recipient's own spam filter, which can take a long time to stop flagging a sender. In the meantime, emails from her second address got through.
Two more from October
Another retailer had emails bounce back from two unrelated Outlook addresses within a day of each other. Their old host had never set up SPF or DKIM, so Outlook's spam protection was rejecting them. We're moving them onto Microsoft 365 with the records set up properly. I told them it can take a month or two before every filter catches up.
A week later, a trade business was setting up ServiceM8. If you don't set up your own email address in job software, invoices go out from the software's own address, and those tend to end up in junk. So we're setting it up to send from their business address.
What to take from this
If customers say they never got your email, or you've ever moved email providers, get your SPF, DKIM and DMARC checked. It's usually the first thing I look at. If you're working out which plan your email should be on, our Microsoft 365 plan guide covers that.
If you only do one thing this week, send a fresh email (not a reply) to a Gmail and an Outlook address you own and see where it lands.