Blog

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

Troubleshooting email delivery issues

From time to time our customers email us asking to troubleshoot delivery issues to an ISP (Gmail, Yahoo, etc). The steps to troubleshoot the problem are usually the same no matter what the cause. I’d like to share a few tips so you can do this any time you run into an issue.

In most cases, delivery issues come up for three reasons: Infrastructure, Sending Practices and Content.

Continue reading

Archive