Latest updates

The /bounces/tags endpoint is used to return all tags from bounced messages as a string array. This endpoint gets extremely low utilization, so we are deprecating it on December 2nd, 2019. We are reaching out to the few customers who use this endpoint directly to help them transition.

If you do have a need to filter bounces by a specific tag, a better approach is to use the /bounces endpoint with filtering, as outlined in our docs here.

If you have any questions about this, please contact our support team.

Back in March 2018 we released modular webhooks, allowing you to choose which events you’d like to send to each specified hook URL. Up to now this has only been possible through the UI. We’re happy to announce that we just released a brand new /webhooks API endpoint, which brings support for the setup and maintenance of modular webhooks, as well as some of the Message Stream functionality we’ve been working on.

Updated December 3, 2019 with new key dates.

We wanted to let you know about a few changes we’re making to SMTP sending in the coming weeks to make this endpoint more secure. These changes will only affect sending via SMTP. If you use only the Postmark REST API to send, no further action is required on your part.

A small number of customers use our Tags triggers API to track open events on emails sent with specific tags. We’re working on some more powerful features in our other API endpoints, so we are ending support for this feature, and it will be disabled on October 14th, 2019. We ask that customers who currently use this API to track opens based on tags update their applications to instead enable open tracking on a Message Stream level, or for individual messages.

Please let us know if you have any questions about this, or if we can help in any way to make the transition to stream- or message-level tracking.

We have added the following IPs to our SMTP endpoint service. If you send email using SMTP and explicitly whitelist our SMTP endpoint IPs, these will need to be added:

This release adds support for our Template Layouts. Find more information about Layouts in our blog post and in our Templates API Docs.

We released a bunch of improvements to MailMason's workflow. This includes the ability to push your templates up to Postmark as well as general maintenance and package upgrades. We've also made design and accessibility improvements to the starter templates that ship with MailMason.

On Monday, May 20th we made a change to the way we process SMTP headers for emails that are sent with SMTP. Please note that this change does not affect sending via the API.

We will disable support for SSL v3 on March 7th, and going forward our servers will only support encrypted SMTP connections using TLS (1.0 - 1.3). Most customers will not be affected by this change. However, you can double check that your SMTP client is compatible by temporarily sending mail through future-smtp.postmarkapp.com instead of smtp.postmarkapp.com.

future-smtp.postmarkapp.com points to the new servers (and new IPs) and it does not allow SSL v3 connections. If you use connection to test and everything works well, no further action is needed and sending should continue through our current endpoint: smtp.postmarkapp.com.

If you are having trouble connecting over future-smtp.postmarkapp.com you will need to update your SMTP client. Please can let us know if you are not able to resolve or update your SMTP client before the switchover date.

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 Postmark JavaScript library just got a huge update. The biggest change is that we added TypeScript support, but there’s way more to it:

• Migrated library to add TypeScript support
• Revamped the client with a simpler call model
• Added custom error handling
• Added all missing account level and server level API endpoints
• Removed unneeded dependencies

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.

Yes, you're right, our developer docs had a few issues on mobile. We're happy to say that, finally, that is a problem no more. Happy mobile browsing, everyone!

This release includes support for our new metadata feature. You may now include metadata with your outbound messages, and Postmark will include that data in webhook payloads, message details, and message searches. See the full release announcement here.

This release also enables you to specify the BaseURL for each API request, making testing with Guzzle a lot easier.

Finally, you can now enable, or disable SMTP API Error Webhooks for Servers using the Admin Client.

As always, we hope this release helps you get even more value from Postmark, and please feel free to contact us if you have any questions or requests!

Our Swiftmailer Transport for Postmark has been updated with some minor enhancements, and it also now works with SwiftMailer 6.

This release of the official .net client for Postmark includes the addition of the Domains APIs, support for our new custom metadata feature, as well as the “EnableSMTPErrorHook” property to the the Create and Edit Server endpoint methods.

You can now add custom metadata to your emails, and we'll pass that same data back to your system through our webhooks.

Rebound's Javascript API now includes a couple of new features that make it easier to use for email-crucial workflows and single-page apps. We’ve introduced a new method(window.Rebound.check()) for explicitly checking an email address whenever you want instead of only on page load. We’ve also introduced an option to continuously run checks in the background without requiring users to reload the page.

We're constantly improving Postmark and taking care of small issues and annoyances that we find (or you send us!). We wanted to start telling you about these fixes, so from now on we'll update you every few months about the bug fixes and other small tasks we take care of in between our larger feature projects.

We now disable all the third-party scripts that collect data about users visiting our website if the user has Do Not Track enabled. This includes analytics and A/B testing services, as well as less obvious data collectors like live chat.

Rebound prompts your customers to update their email address if an email you sent them hard bounced.

Postmark now offers monthly plans instead of credits, and the new plans will likely save you money. More importantly, if the new pricing doesn’t save you money, nothing changes.You’re grandfathered. You can continue using credits, and your pricing doesn’t change a bit unless you want it to.

Hot off the heels of releasing advanced user roles and permissions, today we’re giving you a way to add extra security to your account by enabling two-factor authentication (2FA).

You can now add emoji to your Postmark subject lines, and they’ll render correctly in your favorite email clients. Of course, emoji are already supported in the message body, so there are no changes there.

Postmark can now notify your application of delivery events via webhooks so you can do a variety of things like feed delivery events into an internal system, provide delivery even notifications to your customers, or aggregate delivery even data to see patterns and respond accordingly.