As you most likely know by now, we are expanding beyond transactional email so that you can send all your communication with your customers through Postmark. We announced this back in May and have been adding customers to our new bulk messaging infrastructure steadily to make sure we get feedback and do it right.
We’ve learned a lot about how to make sure we give you all the tools you need to communicate effectively with your customers via both transactional and bulk messages, while we continue to focus on practices that keep our sending reputation high and respect recipients’ inboxes. We’re now ready to start our final push to make bulk sending via our API and SMTP available to everyone.
Today we are releasing the first in a series of product changes to get us to the point where you can send all your email through Postmark. This release introduces the concept of Message Streams to the Postmark UI, and I want to talk a little bit about that.
A Message Stream is a way to organize and separate your sending within a server. We know that some people use servers as environments, while others use it to separate clients, apps, etc. Message Streams give you an additional way to separate your sending and reduce the proliferation of servers on your dashboard.
As of today, you will see two default Message Streams in each of your servers: a transactional stream and an inbound stream. Here’s what it looks like:
The servers page got a refresh as well, and you will now be able to see, at a glance, any delivery issues you might be having. You will also see some new shortcuts to jump straight to a specific stream’s Stats or Activity page.
When you click on the issue in the Deliverability column, you will see an overlay to help you figure out what to do next:
Once you’re in a server’s specific stream, you can also switch between streams quickly to see the stats or activity of a different stream:
For now, you can’t create or delete streams, but you can change the default stream name on its Settings page. In our next release you will also be able to archive/delete streams you don’t need, to make sure you keep your dashboard tidy.
We’re excited about today’s release because it sets us up for an even bigger change that’s coming in the next couple of months: the ability to create additional, custom Message Streams for any purpose. This can be transactional sending, inbound processing, or — the big one — bulk message sending. Separating different types of email by Message Stream also ensures that we can protect your transactional email reputation, since bulk streams will be on completely different servers and IP pools.
It’s worth noting that you don’t have to make any changes to your code at the moment. The new default Message Streams are completely backwards compatible with our existing API endpoints, so sending will continue as usual. Once we introduce the ability to create custom message streams we’ll also add some additional API calls and endpoints to use for managing and sending with streams.
As always, please let us know what you think of these changes by contacting our support team. We love hearing from you!