My emails go to spam: why it happens and how to fix it
IN SHORT
If your legitimate emails land in spam, it's almost never bad luck: today, in the vast majority of cases, it's a domain authentication issue. Since 2024 and 2025, Gmail, Outlook and Yahoo require your domain to have three records properly set up — SPF, DKIM and DMARC — and they check that before they even read your message. Without them, your email goes to spam or isn't delivered. The good news: it can be diagnosed and fixed.
You send a quote to a client, an invoice, an important email, and hours later you discover they never saw it because it landed in their spam folder. It's one of the most frustrating things that can happen to a business, because you don't find out until you've already lost the sale or look unresponsive. The good news is that, in 2026, this is almost never a mystery or bad luck: there's a concrete cause behind it, and in most cases it's the same one. In this guide we explain why it really happens, how to tell which of the two typical scenarios you're in, and what's done to get your emails back into the inbox where they belong — without needless jargon, and with honesty about what's fixed quickly and what takes time.
Why do your legitimate emails land in spam?
There was a big change many people still don't know about, and it explains almost everything. For years, authenticating your domain was a recommended best practice, but optional. That's over: between 2024 and 2025, the major email providers — Gmail, Microsoft's Outlook, Yahoo — made authentication mandatory and began enforcing it for real. Today, when you send an email, the recipient's server first checks that your domain is properly authenticated, and only then looks at the content. If authentication fails, your message goes straight to spam or, increasingly, is rejected without being delivered. Put another way: it's no longer so much about what you write, but whether your domain can prove the email genuinely came from you. That's why an honest business, with a flawless message, can be landing in spam without understanding why: it's missing, or has misconfigured, that technical proof.
First: does it happen to everyone or just some?
Before touching anything, it's worth pinning down the scenario, because that points to the cause. Ask yourself a simple question: do your emails land in spam with almost every recipient, or only with some? If it happens broadly — to different clients, on Gmail and Outlook alike — or if you just changed your domain or email provider recently, the cause is almost certainly authentication: your domain is missing SPF, DKIM or DMARC, or they're misconfigured. If instead it only happens with some recipients or intermittently, while most receive your mail fine, the source is usually more on the side of reputation, the content of that particular email, or that recipient's own filter. This one distinction already tells you where to start, and it's the first thing we check.
The "trinity" that decides whether you land: SPF, DKIM and DMARC
It's worth understanding, without jargon, these three players, because they decide your fate. Think of them as airport security for your email. SPF is the list of servers authorised to send on your domain's behalf; if an email arrives from a server that isn't on that list, the receiver gets suspicious. DKIM is a digital signature, a kind of tamper-evident seal, that travels with each email and proves two things: that it genuinely came from your domain and that nobody altered it on the way. And DMARC is the one that ties the other two together: it requires them to match the address the recipient sees in the "From" field, and tells the receiving server what to do if something doesn't line up. Here's the detail that catches many people out: having SPF and DKIM isn't enough if they aren't "aligned" with your visible address. That mismatch is one of the most common reasons a well-meaning email keeps landing in spam.
Start here
- Confirm your domain has all three records. SPF, DKIM and DMARC live in your domain's DNS settings. Your professional email provider gives you the exact values to add.
- Check they pass and are "aligned". It's not enough that they exist: they must pass and match your visible address. This is where half-finished setups fail.
- If all of that is fine and you still land in spam, the issue moves to reputation and sending habits (covered below).
- When in doubt, have someone check it. A diagnosis stops you from changing things blindly or switching providers for no reason.
When authentication is fine and you still land in spam
Sometimes all three records are perfect and, even so, some emails land in spam. That's where the second big factor comes in: your domain's reputation. Authentication is getting into the stadium, but reputation decides whether you get a good seat. Providers look at your history: a brand-new domain has none, so it starts with little trust and improves over time. Sending a large volume of emails all at once, when you used to send little, looks suspicious. Spam complaints from people who receive your emails weigh heavily, as does sending to lists with many addresses that bounce because they no longer exist. And if you share sending infrastructure with others, a third party's bad behaviour can splash onto you. None of this is fixed with a button, but all of it improves with healthy practices: authenticate properly, send consistently, keep your lists clean, and write to people who actually want your emails.
Content signals that trip the filter
Content matters less than it used to, but it still counts, especially if your reputation is already shaky. There are patterns filters associate with spam that are worth avoiding. Subject lines and text in sustained capitals, with too many exclamation marks or odd symbols, raise flags. Overly salesy words and promises — "free", "make money", unbelievable offers — do too. Shortened links, or links whose text doesn't match where they go, breed distrust, as does stuffing the email with large images and little text: a balanced email, with clean HTML and clear text, is the safest. And if you send bulk messages, the lack of an easy, visible unsubscribe option pushes people to mark you as spam instead of simply opting out, which damages your reputation. In short: write like one person to another, not like a flyer, and always give a clear exit to anyone who no longer wants to hear from you.
How we fix it
Our approach is orderly and honest. First we diagnose: we check whether your domain has SPF, DKIM and DMARC, whether they pass and are aligned, and we look at the reputation signals and sending habits. With that, we know whether you're in the "authentication is missing or wrong" scenario — the most common and relatively quick to fix — or the "damaged reputation" one, which takes longer to recover. Then we correct it: we configure the three records properly on your domain, fix the alignment, and if it makes sense we set up or migrate to well-built professional email on your own domain. We verify with tools that everything truly passes before declaring victory, and we advise you on sending habits to keep the inbox you've won. We tell you plainly: authentication is solved soon, and reputation is rebuilt with consistency. No magic promises, just a plan that works.
Frequently asked questions
What are SPF, DKIM and DMARC, in plain words?
They're three records you add to your domain's settings (its DNS) that, together, prove to Gmail, Outlook and the rest that an email genuinely came from you and not from an impostor. SPF is like a list of the servers allowed to send on your domain's behalf; if an email arrives from a server that isn't on the list, the receiver gets suspicious. DKIM is a digital signature that travels with every email and proves nobody altered it on the way. And DMARC ties the two together, requires them to match the address the recipient sees in the "From" field, and tells the receiving server what to do if something doesn't line up. Since 2024 and 2025, the big providers have made these three records mandatory: without them, your email goes to spam or isn't even delivered.
I set up SPF, DKIM and DMARC and still land in spam. Why?
It happens, and it usually comes down to two things. The first is a technical detail called alignment: having SPF and DKIM isn't enough if the domain they validate doesn't exactly match the domain shown in your "From" address. That mismatch is one of the most common reasons mail keeps landing in spam, and it's fixed by reviewing the configuration. The second is reputation: authentication is the entry ticket, but providers also look at your history. A new domain has none and starts with little trust; sudden bulk sends, spam complaints, or lists with many invalid addresses all weigh against you. The good news is that almost all of this can be diagnosed and corrected; we check it and tell you what's failing.
Will switching email providers fix the problem?
Rarely on its own, and it's worth knowing before you spend on a move. A good provider (like professional email on your own domain) gives you better infrastructure, but reputation is tied to your domain, not the provider: it follows you wherever you go. If the problem is missing or misconfigured authentication, that same problem reappears at the new provider unless it's corrected. So the sensible thing is to diagnose the real cause first — usually in the domain's records or in sending habits — and fix it. Sometimes moving to well-set-up professional email is worthwhile too, but as part of the solution, not as a magic shortcut.
How long does it take to fix?
It depends on the cause. If the problem is authentication — the most common one — the SPF, DKIM and DMARC records are configured on your domain and start taking effect within hours, though a monitoring period is wise to confirm everything passes and is aligned. If there's also damaged reputation, such as a new domain with no history or earlier spam complaints, that recovers over time: with correct authentication and consistent, healthy sending, trust rebuilds over weeks. We give you a clear diagnosis of which of the two scenarios you're in, so you have realistic expectations instead of empty promises.