Home / Companies / Postmark / Blog / May 2016

May 2016 Summaries

2 posts from Postmark

Filter
Month: Year:
Post Summaries Back to Blog
In a world where littering was once seen as harmless, the phrase "Don't Mess with Texas" was born out of a successful campaign to reduce trash on highways. Today, we're facing a new kind of littering - email clutter. Email inboxes are more personal, making it harder to realize how cluttered they've become. This "email littering" is not just about spam, but also about careless or sloppy emails that deliver no value. The problem with email littering is that it punishes your sending reputation with mailbox providers and ISPs, as recipients show less engagement over time. To avoid this, send emails people expect and want to receive, dig into how customers respond to transactional messages, and prioritize happiness over just delivering the message. By doing so, you'll not only make your customers happier but also improve your sending reputation.
May 24, 2016 580 words in the original blog post.
We've designed a new status page to provide transparency on Postmark's email service provider, giving customers the information they need to make informed sending decisions. The goal is to enable rapid and transparent response to any delivery issues, allowing customers to integrate our status directly into their workflows without having to manually check our status page or Twitter. Customers can use our Status API to get current system status and delivery data for the last 24 hours, as well as poll our API directly on a shorter schedule if needed. This allows customers to rapidly respond to issues and make informed decisions about their email infrastructure. The API also provides incident reports that include details such as the issue type, created and updated timestamps, title, updates, resolved status, and body. Additionally, we're offering free credits to anyone who shares a custom integration with their favorite dashboard service for other Postmark customers to use.
May 19, 2016 1,151 words in the original blog post.