Postmark
Postmark only allows marketing email on a Broadcasts message stream, so you send through one of those rather than the default transactional stream.
Before you start
Section titled “Before you start”- In Postmark, open your server and create a message stream of type Broadcasts. Note its ID, such as
broadcast. - Add your sending domain under Sender Signatures and finish its DNS setup. See From address and domain.
- Copy the server’s Server API token from its API Tokens tab.
Set it up in Rowsend
Section titled “Set it up in Rowsend”- Open Project settings → Sending and choose Postmark.
- Fill in the from name, from email, Server API token and Message stream (the stream’s ID).
- Click Save, then Verify. Rowsend checks that the stream exists and is a Broadcasts stream.

Bounces and deliveries
Section titled “Bounces and deliveries”Nothing to set up. While a campaign is sending and for 24 hours after, Rowsend reads Postmark’s bounces once a minute. Hard bounces, spam complaints and Postmark’s “inactive recipient” errors unsubscribe the contact from everything. This works wherever the companion runs, including on your computer.
Postmark reports deliveries one message at a time, so Rowsend checks sent messages in batches. Deliveries show up on the campaign page a few minutes after sending.
Delivery webhook
Section titled “Delivery webhook”With the companion on your own server or Rowsend Cloud, click Set up delivery webhook. Rowsend creates a webhook in your Postmark server that tells the companion about each delivery as it happens. Running it again updates the same webhook. Changing the server token or the stream turns it off until you set it up again.
The webhook needs a companion that Postmark can reach, so it isn’t offered when the companion runs on your computer.
Can we count your visit?
Google Analytics shows us which pages help. It only sets cookies if you allow it. Privacy policy