I read blogs, as well as write one. The 'blogroll' on this site reproduces some posts from some of the people I enjoy reading. There are currently 4 posts from the blog 'Postmark.'
Disclaimer: Reproducing an article here need not necessarily imply agreement or endorsement!
Traditionally Postmark has focused on sending only transactional messages with the highest deliverability standards, and that’s produced a ton of loyal fans that boast we’re the best in the business! *blushing* But if we can accommodate more types of messages with the same high-quality sending standards, many of our customers prefer us as their sole email provider.
Our mission 🛰 is to make email painless and enjoyable for development teams, and we're in the unique position to both preserve our world-class 🌎 transactional service and superior deliverability while using that experience to build the ultimate bulk sending environment in parallel♊︎. So I’m pleased to announce that we’ve launched 🚀 brand new infrastructure for managing what we call “API bulk”, that is, similar messages sent to multiple recipients.
Those who’ve been testing it here for the past 6 months have seen truly stellar ✨ and consistently fast deliverability that I’m over-the-moon 🌜about! Of course, the goal is to be more universal 🔭 about the kinds of messages Postmark can support, but so far selected customers have been sending mainly app updates, release notes, daily digests, and event invitations. I’m personally on the lookout for developers willing to go boldly 👩🚀 into more use-cases, so this is where you come in!
Please make contact 👽 if you’re interested in trying out Postmark API Bulk, and my team would love to chat about your specific sending practices and volume requirements. We always want to optimize our tooling and services to best support developers, ensuring your email needs and Postmark are always a match made in heaven 🌤.
We wanted to let you know that on Monday, May 20th we’ll be making 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.
Historically, when Postmark accepted messages over SMTP, we have constructed the To, Cc, and Bcc headers for messages sent to show only the subset of recipients you specify during sending. In some uncommon cases, this behavior meant that not all recipients would be visible in the message that is delivered to your recipients.
With this update, we will ensure that the recipients that are visible in your messages’ To and Cc headers are the same as what will be shown to the final recipients of your messages. We will no longer reconstruct them based on our older behavior, which, in some uncommon cases, could have prevented some recipients from being displayed in the final email that we deliver.
What you need to know:
- This change only changes behavior for SMTP sending; API sending is not affected in any way.
- We will never include the Bcc header in messages we deliver to your recipients. Your recipients will never see a Bcc recipient list in their email client.
- For most senders, this change will not impact you. If you do not explicitly set the To, Cc, or Bcc headers during sending, then your SMTP client is building these headers based on the recipients for your email.
- If you send messages to single recipients, this change will not affect you.
- If you use Postmark to relay mail out of an internal mail server (such as Exchange or Postfix), the To, and Cc headers will now be displayed with all of the original recipients of that message, even if you are only relaying the message to a subset of the recipients via Postmark. Again, these headers will have been set intentionally by your mail client if you have included multiple recipients in a single message.
For the vast majority of our customers, we do not expect this change to affect what is displayed or sent from Postmark on your behalf.
To be clear, this is how recipient headers should work — we shouldn’t be altering these headers from your emails, so we’re correcting that. However, given the sensitivity of displaying recipients in email, we wanted to provide as much context as possible so that you can review your sending integration ahead of our release of this change.
Please let us know if you have any questions.
We're serious about transparency at Postmark, so a useful status page has always been really important to us. We hear feedback from you all the time that you love and appreciate the page, but that you wish it could be possible to see the status of individual services so that it's easier to tell the impact on sending/receiving.
Well, wish no more. We just released an update to the status page that lets you see the status of each individual service, and also drill down into the response times and past incidents for each service.
There is now no more guessing as to how any service issues we might be experiencing are affecting your application email. We've also updated our Slack app and Status API to reflect these changes. Also remember that you can subscribe to status alert emails, or follow our dedicated alerts Twitter account to get real-time updates.
We hope you find these changes helpful, and please keep the feedback coming.
In this customer interview, we talked with Kate Reynier, Customer Success Team Lead at YouCanBook.me, an online scheduling tool for your team that eliminates back and forth emails and allows customer bookings straight into your calendar.Can you tell us a little bit about your experience and the work you do?
YouCanBook.me is an online scheduling tool. We've been operating since 2008 and have customers all over the world. I am part of the Customer team, and I’ve been doing Customer Support and Customer Success for more than six years.How are you using Postmark on projects today?
We send more than a million emails a month. This includes our own transactional emails and also emails to our customers' customers confirming, reminding and following up on their bookings.
The Customer team relies on Postmark for information about email delivery. A customer might not be receiving emails for some reason so we check the activity log for details about the process as well as any issues that mean the email wasn't delivered.
Before moving to Postmark, we used a competitor that was extremely limited in its activity logs. We could only search the last two weeks and there was no easy way to identify specific emails in a group that had gone to an email address. So while we could be reasonably confident that the information was generally correct, we weren't able to point to specific, individual emails and how they performed.
This and other limitations meant we dreaded using their logs and preferred other troubleshooting options. When the team saw the Postmark activity log we sent up a collective cheer! It is clear, easy to read and includes exactly the level of detail we need to troubleshoot issues with confidence.Why did you choose Postmark to deliver your transactional email?
We had been looking for a long time for an alternative to the provider we were using due to their limitations and cost. Postmark has made it easier to help our customers because of its accessible and detailed activity log which means we get better information faster.
This interview has been lightly edited for clarity.