How to Stop Your Emails Going to Spam
A practical checklist for getting your email out of the spam folder — authentication, reputation, content and infrastructure — with the exact fixes that move the needle.
Landing in spam is almost always fixable. Modern filters weigh authentication, sender reputation, infrastructure and content — and most spam-foldered mail fails on the first two. This guide is a practical checklist, ordered by impact, so you fix the things that actually move the needle first.
1. Authenticate: SPF, DKIM, DMARC
This is the single biggest factor. If your mail isn't authenticated, Gmail and Outlook treat it as suspicious by default — and since 2024 they *require* it for bulk senders. Publish all three:
- SPF — a TXT record listing your senders.
- DKIM — a signature proving the message is really from you.
- DMARC — a policy tying them together.
The full walkthrough is how to set up SPF, DKIM and DMARC step by step. Verify a real message in Gmail's Show original — all three should say PASS. Don't skip this; nothing else matters as much.
2. Fix reverse DNS (if you self-host)
If you run your own mail server, a missing or generic PTR record gets you rejected outright. The PTR for your sending IP must point to your mail hostname, and that hostname's A record must point back — forward-confirmed reverse DNS. Full steps: how to set up reverse DNS (PTR) for a mail server.
3. Check you're not on a blocklist
Your IP or domain may be listed on a DNSBL. Check with:
dig +short 10.113.0.203.zen.spamhaus.org(Reverse the IP octets and append the blocklist zone.) An answer means you're listed. Use MXToolbox's blocklist check for a full sweep, then follow each blocklist's delisting process — and fix whatever got you listed (usually a compromised account or open relay).
4. Warm up new IPs and domains
A brand-new sending IP or domain has no reputation, so filters are cautious. Ramp volume gradually over a couple of weeks rather than blasting thousands on day one. Sending from a dedicated IP with no history to a huge list is a classic way to get throttled.
5. Clean your list and honour unsubscribes
Reputation tanks when you hit spam traps, dead addresses (hard bounces) or people who mark you as spam. Remove bounces promptly, never buy lists, and make unsubscribe one click. A high complaint rate is a fast track to the spam folder regardless of perfect DNS.
6. Watch your content and links
Filters still read the message. Avoid:
- All-caps subject lines and "FREE!!!" spammy phrasing.
- A single giant image with almost no text.
- Links to shady or blocklisted domains, or mismatched link text vs destination.
- Broken HTML.
A clean text-to-image ratio and a real physical address in the footer help.
7. Align your From domain
The visible From domain should align with your SPF/DKIM domains (DMARC alignment). Sending as you@example.com but signing with mailer.other.com fails alignment and looks like spoofing. Verifying your domain properly avoids this — see how to verify your domain for email sending.
Quick diagnosis order
- Send a test to mail-tester.com and read the score.
- In Gmail, open Show original — check SPF/DKIM/DMARC.
- Check blocklists for your IP and domain.
- Confirm PTR (self-host) or provider setup (hosted).
Most problems reveal themselves in the first two steps. Related deliverability reading: MX records and email deliverability.
8. Register with postmaster tools and feedback loops
The big receivers give senders visibility if you claim your domain. Google Postmaster Tools shows your domain reputation, spam rate and authentication results as seen by Gmail — invaluable for spotting a reputation dip early. Microsoft SNDS/JMRP does similar for Outlook and provides a feedback loop that tells you when recipients hit "junk." Sign up for both; they turn "my mail vanishes" into an actual dashboard.
9. Engagement is a ranking signal
Modern filters weigh how recipients treat your mail. Opens, replies and "move to inbox" lift you; deletes-without-reading, and especially "mark as spam," sink you. Practical consequences:
- Only email people who want it. Permission-based lists outperform bought or scraped ones every time.
- Send relevant, well-timed mail rather than high frequency. A smaller engaged list beats a big cold one.
- Prune dormant subscribers. Months of ignored emails drag your reputation down; a re-engagement campaign or a clean-out helps.
10. Separate your mail streams
If you send both transactional mail (receipts, password resets) and marketing mail, consider splitting them across different subdomains or sending domains — e.g. mail.example.com for marketing and tx.example.com for transactional. That way a marketing reputation problem never blocks a password-reset email. Each stream keeps its own SPF/DKIM alignment, which is why verifying the domain properly matters — see how to verify your domain for email sending.
A quick diagnostic script
To sanity-check the DNS side of deliverability in one go:
for r in TXT MX; do echo "== $r =="; dig +short example.com $r; done
echo "== DMARC =="; dig +short _dmarc.example.com TXT
echo "== PTR =="; dig -x 203.0.113.10 +shortMissing MX, no SPF, no DMARC, or a blank PTR each explain a chunk of spam-foldering. Fix those first, then look at content and reputation. For the record-by-record setup, circle back to how to set up SPF, DKIM and DMARC step by step.
FAQ
Why do my emails go to spam even with SPF and DKIM?
Common causes: no DMARC alignment, a bad PTR, a poor-reputation IP, a blocklisted domain, or spammy content. Work through the checklist above in order.
Does buying a dedicated IP fix deliverability?
Not by itself — a fresh IP has no reputation and needs warming up. Reputation, authentication and list hygiene matter more than dedicated vs shared.
How do I know if I'm blocklisted?
Query DNSBLs like Spamhaus with your reversed IP, or use MXToolbox's blocklist tool. If listed, fix the root cause and request delisting.
Should I self-host email or use a provider?
Self-hosting gives control but you own reputation, rDNS, patching and blocklist fights. For most people a managed provider deliverability is far easier.
How long does it take to recover a damaged sending reputation?
Usually a few weeks of consistent good behaviour, though it depends how bad the damage was. Reputation is built on recent sending history, so the fastest recovery is to fix the root cause — authentication gaps, a compromised account, a dirty list — then send steadily to engaged recipients who open and reply. Sudden volume spikes or continuing to hit spam traps reset the clock. If you were blocklisted, request delisting only after fixing the cause, or you'll simply be relisted. Google Postmaster Tools lets you watch the reputation graph climb back, which is reassuring during the wait. There's no button to instantly restore trust: it's earned back the same way it was lost — through a sustained pattern of clean, wanted mail.
Deliverability is dramatically easier on managed infrastructure with a clean IP reputation. Try Nxeon business email, or run your own authenticated stack on a fast VPS.