I owe an explanation for the recent issues on Postmark. This week we had some pretty terrible performance on our MongoDB cluster, resulting in delayed emails, disabled activity and even disabled bounce API. No emails were lost during the outages, but I do want to explain what happened, what we did, and what we are doing about it.
Continue reading • Chris Nagele wrote in Engineering
Today we were going to have a really important, but low impact maintenance. This morning at 9am the team brought the application offline to migrate to a new, more powerful database. Email sending was not going to be affected during most of the process, we expected about 2-4 minutes of paused sending. Things did not happen as we expected and we had some long outages and delays in sending. I want to explain what happened in detail.
Continue reading • Natalie Nagele wrote in Issues & outages
You know that sending your transactional email through Postmark is the best way to improve your delivery rates. But sometimes, even with the best of tools and intentions, your emails will end up in spam and you won’t know why.
The next time you’re working to troubleshoot why an email is going to your (or your customers’) spam filter in Gmail, you can click on the email itself and look right below the sender and recipient information for more information about why Google thinks that email is spam.
Continue reading • Alex Hillman wrote in Email delivery
A quick exploration of a couple of techniques to help reduce the number of email addresses that lead to bounces and increase customer satisfaction in the process.
Continue reading • Alex Hillman wrote in Email delivery
Hot on the heels of the Node.js example we shared last week, we recently had two new “mitt” libraries contributed to make it easy to process JSON data sent in Postmark Inbound’s webhooks.
Continue reading • Alex Hillman wrote in Product news
