Happy June, everyone!
We have another really good newsletter for you this month. After we go over some interesting news and tools, we talk about our brand new CLI tool, how we’re expanding into bulk email (and why this won’t affect our stellar transactional email delivery rates), and some more updates from our team.
Enjoy the newsletter, and as always, let me know if you have feedback! I read every response, promise 🤞
Rian
|
|
📰 Industry news and useful tools
In this guide the Vero team takes a look at transactional emails and explores different types, best practices, and examples from companies delivering delightful customer experiences. This goes really well with our own guide on transactional email best practices.
This is a very interesting webinar from the Litmus team. They explain what email metrics brands track, and provide actionable advice on how you can turn bare stats into strategies and tactics that drive results.
Speaking of Litmus, they just updated their always-interesting “State of Email” report for 2019. It includes up-to-date insights on AMP for Email, updates on GIF support in Outlook, and industry news from the first few months of 2019.
What is a blacklist and how do you avoid being put on one? Read this article to find out. As a reminder, as a Postmark user, you don’t have to worry about reaching out to blacklists. We handle a lot of it proactively — and if you notice something weird and reach out to us, we take care of it as well.
|
|
💻 Introducing the Postmark CLI
|
|
We’re really excited to let you know that Postmark now has an official command-line interface. Version 1 supports pushing and pulling templates, sending emails, and fetching server lists, all from the command line. This means that you can now host your templates on Github, and use a CI/CD tool like Travis CI or CircleCI to trigger pushes from git commits.
We’d love for you to check out the announcement blog post, and give it a try.
(🕹 Btw, if you’re feeling adventurous, try the postmark cheats command…)
|
|
📥 We’re looking for senders to help us test “API bulk”
We announced some big news last week. In her blog post API Bulk: The Final Frontier, Anna explains what we’re up to:
Our mission 🛰 is to make email painless and enjoyable for development teams, and we're in the unique position to both preserve our world-class 🌎 transactional service and superior deliverability while using that experience to build the ultimate bulk sending environment in parallel♊︎. So I’m pleased to announce that we’ve launched 🚀brand new infrastructure for managing what we call “API bulk”, that is, similar messages sent to multiple recipients.
If you’d be interested in testing out this new functionality, read Anna’s post, and then get in touch with us! You might ask, won’t this affect the delivery of my transactional mail? The short answer is, nope! The longer answer is:
Based on our experience, we have always recommended separating bulk and transactional traffic using different sending IPs and From domains. They have entirely different origins as well as vulnerabilities, and so following our own advice we’ve chosen to create a separate but parallel infrastructure for them. That means transactional and bulk traffic do not mix in Postmark, including when it comes to IP ranges. This follows best practices for separating email reputation as recommended by inbox providers
like Gmail.
|
|
🎉 What else we’ve been up to
🎨 Do you use Craft for your projects? If you do, we have an official mail adapter for Craft CMS in the plugin store. It’s free and integrates seamlessly with your projects.
📺 Want to learn how DKIM and custom return-path authentication work, along with how to add the records to your DNS? We have a brand new, 7-minute video for that.
|
Until next month — happy sending!
|
|
|
Rian van der Merwe
Product Manager
|
|
Too many emails?
Unsubscribe 😢
|