Why your email lands in spam, and why the testers say it is perfect
We spent a week testing what actually decides inbox versus spam, on a real domain, with controlled sends. The answer is not your words. Here is the evidence, and the fix.
Every guide gives you the same checklist. Warm up your domain. Set your SPF, DKIM and DMARC. Run the message through a spam tester. You do all of it, and your mail still lands in spam, while the tester swears the message scores a perfect ten out of ten. So which one is lying?
We spent a week finding out, on a real domain, with controlled tests. The result is not what most guides tell you. Once you see it, the fix stops being a mystery.
The myth that it is your words
The common belief is that spam filters read your message and judge the writing. Sales language, links, urgency, all of it supposedly trips a wire. That belief is mostly wrong, and it sends people rewriting sentences that were never the problem.
The test
We took one domain that had been sending for a while and sent three messages to fresh inboxes that had never received mail from it. Same sender, same kind of recipient, one variable changed each time.
| Message | What changed | Where it landed |
|---|---|---|
| Plain text, no link | nothing | Inbox |
| Plain text, one link | a single link added | Spam |
| Formatted, no link | HTML instead of plain | Spam |
A plain message reached the inbox. Add one link, or switch to formatting, and the same sender, to the same kind of inbox, went to spam. The words never changed. So the words were never the thing being judged.
Why the tester still says ten out of ten
A spam tester scores the message in isolation. What it cannot see is how the receiving mailbox judges your domain based on its history. That judgement lives inside Gmail and Outlook, not inside your message.
The tester checks authentication, scans the content, and looks you up on blocklists. All of that can be genuinely perfect. But none of it measures the one thing that actually decides placement: the receiving provider's running opinion of your domain. That is why a message can score a flawless ten and still land in spam. The tester is not broken. It is measuring the wrong layer.
Reputation is the real gatekeeper
Every mailbox provider keeps a quiet, running opinion of your sending domain, built from how people react to your mail over time. Opens, replies, and people marking you as not spam raise it. Being ignored, deleted, or reported lowers it.
When that opinion is strong, the provider gives your mail the benefit of the doubt. You can send formatted mail full of links all day and it reaches the inbox. When the opinion is weak or unproven, the provider gets strict, and the smallest signal, a link or a formatted layout, is enough to tip you into spam.
That is exactly what our test showed. The plain message had nothing to judge, so it just cleared the bar. The moment we added anything richer, a weak reputation plus a promotional looking signal added up to spam. The link and the formatting were never bad on their own. They were only fatal because the domain had not earned any trust yet.
What actually fixes it
Rewriting your sentences will not move this. Building reputation will. In practice that means:
- Send to people who actually want your mail and will open and reply to it.
- Start small and stay consistent, day after day, with no sudden spikes in volume.
- Earn positive signals: replies, and recipients marking you as not spam or adding you to their contacts.
- Keep anything that must arrive today plain and simple while the reputation is still young.
- Never mix cold, unwanted sending into the domain you rely on. One burst of mail nobody asked for can undo weeks of progress.
Reputation is earned over weeks, not flipped with a setting. But it is the only lever that genuinely moves inbox placement, and once it is built, the links and formatting you were told to fear stop mattering.
The takeaway
The next time a tester hands you a perfect score and your mail still lands in spam, stop editing the message. The message was never the problem. Go build the one thing the tester cannot see.
A clean start helps. Recievet configures your domain so authentication is correct from day one, giving your reputation a trusted base to grow from instead of a hole to climb out of.
Recievet