Email deliverability can feel mysterious: you hit “send,” your dashboard says “delivered,” and yet customers say they never saw it. On Windows, you can do a few simple checks to confirm where your emails are actually landing and what’s most likely pushing them toward spam.
This guide focuses on practical signals you can verify yourself, before you change tools or rewrite everything.
First, separate “sent,” “delivered,” and “inbox placement”
Most email platforms report “delivered” when the receiving server accepted the message. That does not guarantee it reached the primary inbox.
What you’re trying to confirm is inbox placement: Primary/Focused vs Promotions/Other vs Spam/Junk.
- Sent: your platform attempted to hand off the email.
- Delivered: the recipient’s mail server accepted it.
- Inbox placement: where the email is filed after filtering.
- Opened: tracking pixel fired (not always reliable).
Run a fast “seed test” with real inboxes (10 minutes)
A seed test is just sending your campaign to a small set of addresses you control, then checking where it lands.
Create 6–10 test recipients across common providers (Outlook/Hotmail, Gmail, Yahoo, iCloud). Include at least one address on your own domain if you have it.
- Send the exact email you plan to send (same subject, links, and from-address).
- Check Inbox, Promotions/Updates, and Spam/Junk.
- Forward one received copy to another inbox to see if it worsens (forwarding sometimes breaks authentication alignment).
- Repeat with a plain-text version if your platform supports it (useful for comparison).
If 2–3 providers put it in spam, it’s usually a reputation or authentication issue—not “one weird inbox.”
On Windows, view message headers and look for authentication results
Headers are the “receipt” of how the message traveled and what checks it passed. You don’t need to read every line—just find the authentication summary.
In Outlook for Windows, open the message and look for Internet headers (the path varies by Outlook version). In webmail (Outlook.com/Gmail), use the menu for Show original or View message source.
In the header text, search for:
- Authentication-Results: look for SPF=pass/fail, DKIM=pass/fail, DMARC=pass/fail.
- From: the domain customers see.
- Return-Path / Mail-From: the sending domain used for SPF.
- DKIM-Signature: indicates DKIM signing is present.
A very common deliverability problem is “SPF passes but DMARC fails” (or DKIM missing), which can happen when your visible From domain and your sending domain don’t align.
Understand SPF, DKIM, DMARC (what they do and what “good” looks like)
These are DNS-based checks that tell mailbox providers whether your sender is authorized and whether the message was altered.
- SPF: “Is this server allowed to send for this domain?” (checks the envelope sender / return-path domain)
- DKIM: “Is this message cryptographically signed by the domain?”
- DMARC: “Do SPF or DKIM pass, and do they align with the visible From domain?”
Healthy baseline for marketing email:
- SPF: pass
- DKIM: pass
- DMARC: pass (alignment is the key)
If you use a sending service, they usually provide SPF/DKIM records to add. The important part is ensuring you’re authenticating the same domain customers see in the From address (or a properly aligned subdomain).
Check your domain reputation and list hygiene signals (the quiet “filters”)
Even with perfect authentication, mailbox providers watch engagement and complaints over time.
- Low engagement: many recipients don’t open or read → more filtering.
- Spam complaints: even a small spike matters.
- Bounces: sending to invalid addresses looks careless.
- Sudden volume jumps: going from 1,000 to 50,000 overnight can trigger throttling/spam.
- Old lists: addresses collected long ago tend to underperform and complain.
If you’re unsure, segment and send to your most engaged subscribers first. That alone often improves placement while you fix the underlying issue.
A prioritized fix order (what to change first)
When deliverability is bad, it’s tempting to rewrite the entire email. Usually, you get more mileage by fixing fundamentals first.
- 1) Authentication: ensure SPF + DKIM are set and DMARC passes with alignment.
- 2) From-domain consistency: avoid frequently changing From domains and From names.
- 3) List hygiene: remove hard bounces, suppress unengaged recipients, use confirmed opt-in where possible.
- 4) Sending pattern: ramp volume gradually; keep cadence predictable.
- 5) Content tuning: only after the above—reduce URL shorteners, keep image-to-text reasonable, ensure a clear unsubscribe link.
One practical rule: if DMARC is failing, treat content tweaks as secondary until DMARC passes.
Takeaway: confirm placement, read the header, then fix alignment
On Windows, you can get surprisingly far with a small seed test and a quick header check. If you confirm spam placement across providers, look first at SPF/DKIM/DMARC pass status and domain alignment—then clean your list and stabilize your sending pattern.