Build a CSV of bounced emails using the Postmark API

If you send emails, it makes sense that you would want to analyze which email addresses are bouncing. Postmark has a few ways that you can get this information. You can view the information in the Activity section of the website. You can set up a bounce hook so that Postmark will send a POST request to your web server every time we process a bounce. Additionally, you can use our API endpoints to retrieve the data. With this post, I’ll provide a simple example using Ruby to retrieve bounces using the API and saving the data to a CSV.

Continue reading • Nick Canzoneri wrote in Product news

April 9th

Update to Heartbleed vulnerability

We’ve been spending the last two days auditing and responding to the OpenSSL vulnerability that’s known as Heartbleed. This bug is notable because it is widespread (around 70% of the Internet uses Apache and Nginx, and by extension, OpenSSL) and can cause disclosure of sensitive data, including private keys and passwords. The issue has been assigned the following CVE identifier: CVE-2014-0160.

Continue reading • Natalie Nagele wrote in Issues & outages

March 20th

Improvements to date selector in statistics table

Today we released an improvement to our date selector for the stats overview chart. We realized that some filter names were confusing, and others were missing.

The purpose of the filter is to get you the data you want to see quickly. Instead of having to choose a start and end date, you can just click “Last 7 days” and view that time span instantly

Continue reading • Natalie Nagele wrote in Product news

March 4th

Quick explanation of issues today

This is an update to our earlier reported queueing of emails.

At around 10:50am EST our datacenter was doing some IP address mapping on our entire environment (Beanstalk, Postmark and dploy.io). Unfortunately, they set the wrong IP mappings, which caused Postmark to send emails from an IP that is not intended for sending mass emails.

Continue reading • Natalie Nagele wrote in Issues & outages

February 14th

Better bounce categorization in Postmark

Bounces are a big part of troubleshooting delivery issues. We provide our customers a lot of information about bounces:

We provide a specific bounce type so that there is a specific reason the bounce occurred.
We provide the full bounce message, exactly what our servers receive.
We store bounced messages forever because of their value in troubleshooting.

When we detect a Hard Bounce or a Spam Complaint for a particular address, we will deactivate the address. This helps us keep delivery rates high as it gives Postmark a good reputation with ISPs. It also helps our customers so that credits are not spent to send email to addresses that don’t exist. However, it becomes a problem when we incorrectly parse a bounce as a Hard Bounce. Then a legitimate user’s address is deactivated and won’t receive emails.

Continue reading • Nick Canzoneri wrote in Product news

Blog

Build a CSV of bounced emails using the Postmark API

Update to Heartbleed vulnerability

Improvements to date selector in statistics table

Quick explanation of issues today

Better bounce categorization in Postmark

Archive

Product news

2023

2022

2021

2020

Email delivery

2023

2022

Engineering

2023

2022

2021

2019

2018

2017

2016

2015

2023