Since adding Inbound parsing to Postmark over two years ago, we‘ve processed millions of messages for our customers. We‘ve been adding more and more features to inbound over time as well, such as MX Domain Forwarding, retries, and StrippedTextReply. Today we‘re announcing the next set of Inbound features, along with a completely redesigned Server Settings page.
Continue reading • JP Toto wrote in Product news
Our friends over at Word to the Wise recently posted about Cryptography and Email with a great illustrated follow up on Public-key Encryption.
Continue reading • Chris Nagele wrote in Email delivery
Earlier today, around 2:05 PM EDT, our API servers started to drop connections and time out. The entire team dropped everything and started to investigate. After ensuring the API servers and backend databases were healthy, we started to investigate other causes. During this time we decided to redirect traffic to our off-site disaster recovery data center, to avoid lost messages.
Continue reading • Chris Nagele wrote in Issues & outages
Since Postmark’s API and feature set has been growing, we decided it was time to rethink our approach to our documentation. We’re super excited to announce that we’ve completely redesigned our documentation from the ground up.
Continue reading • Derek Rushforth wrote in Product news
When we launched open tracking, we created two ways to enable tracking on emails. You could either enable it with a field in your messages or enable it for a specific tag. While this works for most cases, it still takes some effort. We wanted to make it incredibly easy to start tracking opens in your emails, so today we launched open tracking per server. Now, with the click of a button, you can automatically enable open tracking on all HTML emails sent through a server.
Continue reading • Chris Nagele wrote in Product news
