Inbound Improvements: Better Contacts JSON & New Date Fields
We have introduced some changes to the Postmark Contacts JSON object.
Continue reading • Alex Hillman wrote in Product news
We have introduced some changes to the Postmark Contacts JSON object.
Continue reading • Alex Hillman wrote in Product news
Our friends at Server Density are running a series of deals in the coming months highlighting the useful sysadmin/development tools that they use and love. We’re thrilled to be their first featured deal.
Continue reading • Alex Hillman wrote in Product news
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