We’ve got libraries in most popular languages to make it as easy as possible for you to add Postmark to your projects. Last month, our engineers made improvements to two of our most popular libraries:
We released a new major version (4.0.0) of our Node JS library. This version now relies on newer libraries for improved security. With this release, we no longer support Node versions that have reached end of life, so you’ll need to use Node version v14.0.0 or later. If you use older Node versions for which active and security support ended, you will need to use older library versions (3.x.x).
Check out the Postmark JS library and view all the changes we’ve made.
We have a new engineer on the Postmark team (Welcome Eli! 🙌) and he has given our PHP library some much needed love. You can check out all details in the release notes but in a nutshell:
We closed out all open issues and worked through most open PRs from the community (thanks for your contributions, friends!)
We added Postmark’s new Data Removal API to the library.
We updated the unit test framework.
Check out the Postmark PHP library and view all the changes we’ve made.
If you have any questions or feedback about the changes, we’d love to hear from you.
Postmark's WordPress Plugin now supports tags and we've updated our Java library to fully support newer versions of Java JDK.
Tags are a handy tool to help you categorize your emails in Postmark — and we now added tag support to Postmark’s WordPress plugin! If you’re using the Postmark plugin to send your WordPress emails, you can now apply tags to your messages using one of the following two options:
Set an X-PM-Tag message header, i.e. array_push( $headers, ‘X-PM-Tag: PostmarkPluginTest’ ); where you are calling wp_mail().
Add a filter for ‘postmark_tag’ that hooks into a function that returns the tag you desire.
Please note that using the ‘postmark_tag’ filter will override a tag set via message headers.
A big thank you to our friend DorZuberi for requesting this update and working with Patrick from our Engineering team to get this PR out the door.
Get Postmark’s Wordpress Plugin →
We have updated our Postmark Java library to provide better support for the Jakarta community and to fully support newer versions of Java JDK. Igor from our QA team took care of these requests with the latest updates. Postmark’s Java library now provides full support for Java versions 16, 17, 18, and 19.
We added Message Streams support to Postmark's Zapier Actions. You can now specify which stream you’d like to use to send email through messages triggered from Zapier. If no Message Stream is provided, we'll default to the Outbound Transactional Stream.
Postmark's Zapier Actions support both Send an Email and Send an Email With Template.
We added Message Streams support to the Postmark plugin for Craft CMS so you can now specify which stream you’d like to use to send email through Craft. Previously, Craft would always send over your default transactional Message Stream.
Plus, because the plugin now also supports Broadcast Message Streams, you can now use Postmark to send bulk email via Craft Campaign.
Postmark for WordPress v1.12 is now live! It adds support for Message Streams. You can now specify which stream you want to use in the plugin settings.
This release adds support for our Template Layouts. Find more information about Layouts in our blog post and in our Templates API Docs.
Action Mailbox is a new framework in Rails 6 that routes incoming emails to controller-like mailboxes for processing in Rails. You can get more information about Action Mailbox in the introduction blog post.
You can find implementation instructions in this guide on Action Mailbox Basics, including specific instructions for Postmark.
Our WordPress plugin now supports link tracking! We've also fixed an issue where open and link tracking options were not honored when sending a test email.
We just released an update to the WordPress plugin that adds an optional setting for preserving logs of send attempts. It adds a new Logs tab that can be used to view the last 7 days of plugin sending activity.
Preserving send logs are useful for a couple of reasons:
We heard a lot of feedback from users saying their plugin wasn't working but they had no idea why, and there was not an easy way to tell what was going wrong. Now, you can quickly see what is going on and resolve the more common errors, like trying to send from an address that isn't on your account yet, or trying to send to external recipients before you Postmark account is approved.
Our Postmark JavaScript library just got a huge update. The biggest change is that we added TypeScript support, but there’s way more to it:
We’ve already made a few minor updates based on feedback and additional real-world use, so make sure to grab the latest version. Check out the wiki for more details, including a migration guide for moving from 1.x to 2.x.
