Resources & Links
Considerations for evaluating transactional email service providers
I put together a detailed guide of considerations and things to look for when trying to choose a transactional email service provider.
Transactional email bounce handling best practices guide
An exhaustive guide to help you understand bounce handling and design a solution to mitigate bounces and empower users to correct issues before they become a bigger problem.
Word to the Wise Blog
Laura Atkins runs one of the most respected companies and blogs for email industry news around authentication and deliverability.
Transactional Email Guides
Everything you need to know about sending great transacctional email.
Products, Services, & Tools
Google Postmaster Tools
Postmaster Tools analyze your email performance, and help Gmail route your messages to the right place.
Test and Optimize your Emails. Identify and fix issues keeping you from the Inbox
Get private, secure, ad-free email hosting for you or your business
Secure Email Based in Switzerland. Secure Your Communications with ProtonMail
Litmus provides a suite of email design and email marketing tools, helping you build, design, test, and analyze your emails.
There’s a better way to talk with your customers. Help Scout is designed with your customers in mind. Provide email and live chat with a personal touch, and deliver help content right where your customers need it, all in one place, all for one low price.
250ok tracks all of the signals critical to your email program. No more depreciated certifications, services blackholes, or insufficient data. Discover insights that drive world-class email performance.
MxToolbox supports global Internet operations by providing free, fast and accurate network diagnostic and lookup tools. Millions of technology professionals use our tools to help diagnose and resolve a wide range of infrastructure issues.
Email marketing, ads, landing pages, and automation tools to grow your business on your terms.
A fake SMTP server to test, view and share emails sent from the development and staging environments without spamming real customers.
How do you manage the necessary but invisible tools in your stack? How should backups work?
Or jump to any of the other topics: