🌓 Is your email ready for the dark side? Learn how to design emails that look great in both light and dark mode! Check out our latest blog post for best practices.
▸ lttr.ai/AV3MG#darkmode
A user signs up.
“Check your email for a verification code.”
Nothing.
They wait. Resend. Eventually give up.
20 minutes later, it lands in spam.
That's not just an email problem. It's a product experience problem.
Transactional email needs to arrive when it matters.
A basic email API request isn't complicated:
From
To
Subject
HTML/Text
→ Send
Production gets more interesting:
Attachments
CC/BCC
Error handling
Webhooks
Delivery events
Bounces
Sending an email is easy.
Building email reliably into a product is the interesting part.
Developers, it's Friday
Time for email debugging group therapy😅
What's your worst email bug?
We'll start:
• Works locally, fails in prod
• Password resets disappear
• Everything lands in spam
• DNS looks right (it isn't)
• “Delivered” but nowhere to be found
Your turn👇
WordPress: “Email sent successfully.” ✅
Your customer: “I didn't get anything.” ❌
Both can be true.
“Sent” doesn't always mean “delivered.”
When debugging WordPress email, don't stop at:
Did WordPress send it?
Ask:
What happened after WordPress sent it?