Grow with us: Join Postmark's new referral partner program and start earning
x

Blog

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

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

API Update: Manage Servers and Sender Signatures

Some of the most frequent feature requests we get have to do with adding more API endpoints to further automate the Postmark experience. Today I’m happy to announce that we’ve added not one, but two new API endpoints to make automating your Postmark experience even easier!

Continue reading

Archive