Welcome to the November newsletter!
This month we have a really full issue for you. We have a brand new webinar and writers’ program to tell you about, as well as lots of product updates, and an interview with Brad Butner from Take Three Technologies. Let’s get to it!
|
|
✍️ Get paid to write for our blog
We want the Postmark blog to be a resource for developers who want to design, send, and receive better and more reliable emails with their applications.
We’re looking for writers who can contribute technical content that covers broad topics related to transactional email such as delivery, reputation, design, tools, and testing, as well as tutorials for using Postmark with specific languages and systems such as Python, Rails, Laravel, Node, and so on.
|
|
|
If you feel your writing and ideas are a good fit for the Postmark blog and its audience, we encourage you to apply for this paid opportunity. All you have to do is fill out a brief form with your contact information and some writing samples, and then we'll review it and be in touch.
We will respond to all applicants regardless of whether we decide to move forward with an assignment or not. For the full details of how the writing process works, as well as the payment schedule and terms, head over to the application page.
Apply here →
|
|
📺 New webinar: learn how to use Postmark to send more effective emails
Crafting emails is hard. This webinar will dive into the techniques you should apply to your transactional emails to ensure that they’re valuable to recipients. We’ll explain why transactional emails are just another interface to your software that should receive the same attention you’d give to designing any other customer interaction.
If you’re looking to improve the quality of your transactional emails, join us for a free webinar on Thursday, November 29th to learn about:
-
Best practices for sending transactional emails
-
Common mistakes made when sending transactional email
-
How Postmark can help you send effective emails
Register here →
|
|
🚀 What we’ve been up to
Postmark Node.js Library goes to v2
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.
Bounces happen. What can you do?
We know how frustrating it can be to get a notification that an email bounced. The first question you always ask yourself is, “well, what am I supposed to do about that!?” Patrick on our Customer Success team has you covered with a bunch of new help docs with clear information on what the common bounce types mean, along with the right steps to take to get your recipient receiving your emails again. Here’s what’s covered:
Status page improvements
We know how important it is to know the current status of the Postmark services. So we recently added a couple different ways to get status notifications. You can now receive email alerts as well as Slack notifications each time we add or update an incident on our status page. Head over to the subscription page to sign up for email alerts, and check out the Slack app’s Github page for more details on that.
Template improvements
We are currently working on some really big and great improvements to our transactional email templates. In the mean time we have a couple of small improvements to make your life easier.
Back in March, we released template alias support to our API, and now you can manage template aliases from the UI as well. Template aliases make it easier to manage the same template across multiple servers. Check out our help doc for more info.
You can also now search for a template from the UI. No more sifting through pages and pages of templates to find what you’re looking for!
|
|
|
☕ Good/Bad remote worker
In the latest entry in our Good/Bad series we write about our approach to remote work here at Wildbit. Here’s an excerpt:
A good remote worker always thinks about collaboration through the lens of asynchronous communication. Remote work naturally creates great environments for deep, focused work, so it makes sense to optimize for asynchronous communication. This lets everyone get involved when it works best for them — and when they are ready to give something their full attention.
You can read the whole article here.
|
|
🎤 Meet Brad Butner
|
Today we talk to Brad Butner. He is the Lead Application Developer at Take Three Technologies, a platform for mortgage lenders to easily originate
and close loans.
|
|
Can you tell us a little bit about your experience and the work you do?
My background has been in .NET Software development for the past 10 years or so, with PHP development before that. I've been here at Take Three Technologies for a little over two years now, and we specialize in software solutions for the mortgage industry.
How are you using Postmark at Take Three today?
We primarily use Postmark for outbound messaging, but we also use webhooks to identify when messages have been delivered, opened, or bounced. We chose Postmark because we needed service that would deliver our transactional email right. We tried other services, but Postmark was the only service that has delivered what we need.
Before switching to Postmark, mail delivery complaints were daily, but now that we've switched, they're gone. Postmark has also given us more insight into the types of emails our applications are sending out on a daily basis.
If you could give fellow developers one piece of advice about how to implement and manage their transactional email, what would it be?
When building your applications, make sure email is built out early to support services like Postmark and the features they provide, such as templates, tags, and webhooks. It will save you a lot of time caused by reworking your systems down the road.
|
Until next month — happy sending!
The Postmark Team
|
Too many emails?
Unsubscribe 😢
|
|