Your Email Did Nothing Wrong.
Here's Why It's in Spam.
Plain-language explanations of SPF, DKIM, DMARC, sender reputation, Gmail's sorting logic, and what open rates actually tell you now that Apple has changed the picture. No services sold. No jargon left unexplained.
The gap between sending an email and it reaching the inbox is filled with things nobody explains clearly.
Email deliverability is one of those technical areas where the documentation assumes you already know the vocabulary. SPF records live in your DNS. DKIM uses asymmetric cryptography. DMARC policies publish alignment rules. These sentences are accurate. They are also useless to most people who send newsletters.
This site takes the opposite approach. Every concept gets explained from first principles. The technical details are here, but they arrive after you understand why they matter. No email marketing services are sold here, no affiliate links, no platform recommendations with hidden incentives.
Read the First Article
Six areas where understanding the mechanics changes everything.
SPF, DKIM, DMARC
Three authentication standards that tell receiving servers whether your email is legitimate. Each one works differently. Each one failing looks different. Understanding the difference matters when you're troubleshooting.
Understand authenticationGmail's Promotions Tab
Gmail's tabbed inbox isn't random. It uses signals from your email's structure, content patterns, and your sender history to decide where to place incoming mail. Some of those signals you can influence.
Learn the signalsBought Lists and Reputation
Purchasing an email list seems like a shortcut. The damage it does to your sender reputation is lasting and largely invisible until it's severe. This section explains the mechanism, not just the warning.
See the mechanismCleaning a Cold List
A list you haven't emailed in six months behaves differently from an active one. Re-engaging without destroying your deliverability requires a specific sequence that most guides skip over entirely.
See the sequenceOpen Rates After Apple MPP
Apple's Mail Privacy Protection pre-fetches email content, which registers as an open even when no human read anything. Open rates now measure something different from what they measured before 2021.
Read the full pictureTechnical Walkthroughs
Step-by-step explanations of DNS record formats, header analysis, bounce classification, and feedback loops. Written for people who are comfortable reading documentation but didn't grow up in systems administration.
Explore walkthroughs
Why does my newsletter end up in spam when I've never sent anything bad?
The answer almost never involves the content of your email. Spam filters in 2026 are primarily reputation-based systems. They look at your sending domain's history, the alignment of your authentication records, your bounce rate over time, and signals from people who previously received your mail.
Content filters still exist, but they're the last layer. Most deliverability problems are solved before you write a single word of your newsletter.
- How inbox providers build and maintain sender scores
- The difference between a spam complaint and a bounce
- Why shared IP addresses create shared problems
- What "warming up" a sending domain actually means
The path an email takes from your outbox to someone's inbox.
Understanding this sequence makes every other deliverability concept easier to grasp.
Your server sends the email
Your sending server (or your email service provider's server) transmits the message. At this point, the email carries your domain name in the "From" field and in the SMTP envelope.
SPF check happens
The receiving server looks up your domain's SPF record in DNS. It checks whether the IP address that just sent the email is on the list of authorized senders for your domain. Pass or fail gets logged.
DKIM signature is verified
The email carries a cryptographic signature in its headers. The receiving server fetches your public key from DNS and uses it to verify the signature. This confirms the email wasn't altered in transit.
DMARC policy is applied
DMARC ties SPF and DKIM together. It checks whether either one passed and whether the authenticated domain aligns with the visible "From" address. Your DMARC policy tells receivers what to do with failures: nothing, quarantine, or reject.
Reputation scoring adds context
After authentication, the receiving server layers on reputation data: your domain's complaint history, your IP's sending patterns, engagement signals from previous recipients, and third-party blocklist status.
Topics from the archive.
Education without a sales agenda.
Most email deliverability content exists to sell you a tool, a service, or a platform. The explanations are accurate enough to seem helpful but structured to make the paid product feel necessary. This creates a subtle distortion in what gets explained and what gets left vague.
This site doesn't sell email marketing services, deliverability tools, or platform subscriptions. The goal is to explain how these systems work clearly enough that you can make your own informed decisions about your own sending setup.
If you finish reading an article here and understand something you didn't before, that's the entire point.
Questions about something you read?
Cincinnati, OH