An email deliverability field guide
Email reputation explained well
Your mail server says “delivered.” Your customer finds the message in spam. What happened in between?
Sender reputation is how a mailbox provider judges the mail coming from your domain or IP address. If you run a mailing list or build the product that sends the mail, this book explains which signals you can change, from the signup form to the inbox.

What changed for bulk email senders in 2024?
Gmail and Yahoo began enforcing stricter rules for bulk senders in 2024. If you send newsletters at scale, both providers require you to authenticate your domain with SPF, DKIM and DMARC, support one-click unsubscribe, and keep your spam complaint rate below 0.3%.
I wrote this book in 2023 to explain the fundamentals behind those rules. Use it to understand why a reader’s spam report matters even when your mail passes authentication. For the current checklist, go straight to the Gmail sender guidelines and Yahoo sender requirements.
Inside the book
Follow one email from signup to inbox.
01 / Before you send
Keep bad addresses off your list
Spot the difference between a new subscriber, a duplicate and a bot. Decide which addresses to stop mailing when deliveries fail.
02 / At the mail server
Prove who sent the message
Untangle SPF, DKIM and DMARC: what each one checks, how they work together and what passing those checks does not prove.
03 / In the mailbox
Read the signals readers send
Understand why someone marking your email as spam tells a mailbox provider something your delivery report cannot.
04 / Across providers
Know what others see
Learn how providers share information about spam and where to look for warning signs about your own sending resources.
Free companion guides
What are you trying to fix?
- How to set up SPF, DKIM and DMARC
- Start here if you’re connecting a sending service to your domain. Check the DNS records and verify the result on a message you actually received.
- Troubleshoot email delivery and sender reputation
- Start here if mail is bouncing, arriving late or landing in spam. The first clue is whether the receiving server accepted the message.