Two paper planes. One white and one yellow.

SparkPost Migration Guide

Everything you need to know about moving from SparkPost

Table of Contents

Chapter 1

Introduction#

Key differences between SparkPost and Postmark

Migrating email service providers can be a large undertaking. We want to help relieve some of that stress of moving to Postmark from SparkPost. This guide will detail some of the differences and similarities between SparkPost and Postmark, as well as give some useful tips for migrating to Postmark from SparkPost.

It includes details on differences between Postmark and SparkPost APIs, sending outbound emails, processing inbound emails, UI differences, and webhooks.

Key differences between SparkPost and Postmark #

These are some important differences to be aware of when moving over to Postmark from SparkPost:

  • Postmark does not allow anyone to send marketing or bulk email, whereas SparkPost does. If you were sending your marketing and/or bulk email through SparkPost and want to switch those over to another provider, we highly recommend using Campaign Monitor for any bulk email you need to send. This means that features like list management or suppression lists are not supported.
  • Since Postmark does not allow bulk email (including subscription newsletters), there are no list management features available in Postmark, such as handling unsubscribes or adding unsubscribe links to your emails.
  • Postmark doesn’t offer premium or enterprise options because we provide full support for all of our customers regardless of how much you pay.
  • Postmark does not provide 15,000 free emails each month like SparkPost. We start you with 25,000 free credits when you create your account but you will need to purchase more credits once those are used.
  • Postmark uses a pay as you go credits model instead of subscriptions. You only pay for the credits you use. See our pricing page for more details. One credit is used per email sent/received and credits never expire.
  • We do not recommend using dedicated IPs for most senders but do move senders to dedicated IPs at no additional charge once they reach a significantly large volume. As a result, you are never responsible for warming up an IP. We take full responsibility for managing IP addresses and warming them up.
  • Postmark does not currently support custom domains for click tracking. For security purposes, we use a secure domain: https://click.pstmrk.it.



Chapter 2

Postmark Concepts#

Important concepts to learn when moving over to Postmark

There are a couple important concepts to learn when moving over to Postmark: Servers and Sender Signatures, and Verified Domains. A server and a confirmed sender signature/verified domain are required for sending, so it is important to understand what they are used for.

Servers #

Each Postmark account contains servers. Servers are similar to sub-accounts on SparkPost and can be thought of as folders you create that group together similar email activity. Each server has its own activity (inbound and outbound), stats, server API token(s), a unique inbound email address, and templates. You can create as many servers as you need, there is no limit. 

Some uses of servers are separating your clients’ activity, sending emails for different environments (prod, staging, development), or separating sending for your different domains. When you begin adding more users to your Postmark account, you can also assign them access to specific servers so that they can’t view email activity or change settings across your entire Postmark account.

Sender Signatures and Verified Domains #

In Postmark you need to have either a confirmed sender signature or verified domain for each email address you want to send from. Sender signatures are individual email addresses that are authorized for sending via a confirmation email sent to that address. Adding and verifying a domain using DNS records lets you send from any email address on that domain.

The domain verification option is similar to SparkPost’s domain verification, but Postmark’s sender signatures offer a lower-friction way to verify individual email addresses for sending when verifying an entire domain isn’t practical.

We use sender signatures and verified domains to ensure you own or are authorized to send from the mailboxes you add to your Postmark account. You can have as many signatures and domains as you need, there is not a limit. Sender signatures and domains are associated with your account, not a specific server. This means they can be used for sending across all of your account’s servers.

Postmark does not support verifying domain ownership by emailing abuse@example.com and postmaster@example.com. To verify a domain, you will need the ability to update DNS records.

Tip: You can use any sender signature/verified domain for sending with any Postmark server. It is different from SparkPost where the sending domain and its activity are linked together.


Chapter 3

APIs#

How the Postmark API works

A note on API tokens in Postmark #

Each Postmark account has an account API token. Every server in an account also has its own server API token(s). Server API tokens are used for server-level actions such as sending email, getting statistics, modifying a template, etc… account API tokens are used for account-level actions such as creating a new server or adding a new domain for sending.

Check out our help article on the different API Tokens in Postmark for more information.

APIs Map #

API TypeSparkPost API NamePostmark API Name
Sending EmailsSMTP APIEmail
Managing BouncesMessage EventsBounce
Managing TemplatesTemplatesTemplates
Managing Sending SettingsSending DomainsServer
Managing ServersSubaccountsServers
Managing Sent EmailsMessage EventsMessages
Managing Inbound EmailsMessages
Manage email domains you can send fromInbound DomainsDomains
Manage email addresses you can send fromSending DomainsSender Signatures 
Sending StatisticsMetricsStats
Suppression ListSuppression List
Managing IP PoolsIP Pools

API Libraries #

In addition to the official libraries offered by Postmark, we also include community submitted libraries for additional language/framework options.

Language/Framework SparkPost Official LibraryPostmark Official LibraryPostmark Community Library
C#Postmark .NET
Classic ASPSimple Classic ASP Class for Postmark 
ClojureClojure Binding for Postmark API
ColdFusioncfPostmarkappColdFusion componentA replacement for the stock Coldbox MailService Plugin
DrupalDrupal Library
ElixirSparkPost ElixirEx Postmark
ErlangErlang Library
GoSparkPost GoPostmark GolangPostmark.go
GrailsGrails plugin
GruntPostmark Grunt
HaskellHaskell Library
JavaSparkPost JavaJava librarySpring's MailSender compatible implementation
LaravelLaravel Plugin
MagentoMagento Extension
NodeJSSparkPost NodePostmark.js
Objective-CStandalone Objective-C Class
PerlPerl WWW::Postmark
Pharo SmalltalkPharo SmalltalkPostmark
PHPSparkPost PHPPostmark PHPPHP Community Libraries
PowerShellPostmark PowerShell Snap-in
PythonSparkPost PythonPostmarkerpystmarkPostmark Python library
RubyPostmark Ruby
RailsPostmark Rails
ScalaScala ClientScala Library
WordPress PluginPostmark for WordPress
ZendPostmark drop-in replacement for Zend

Chapter 4

Sending Outbound Emails#

Start sending through Postmark

Similarities to SparkPost #

  • Sending via a REST API and/or SMTP supported
  • Like SparkPost’s sink.sparkpostmail.com domain, you can also send test emails to Postmark’s sink email address, test@blackhole.postmarkapp.com. Messages sent to this domain will be dropped on the receiving end but you will be able to see the delivery confirmation and message in your Activity. Also see our blog post about best practices when testing with your Postmark account.
  • Entire domains can be verified for sending using DKIM and SPF records

Differences from SparkPost #

  • Postmark retains the full content and event history of every message for 45 days whereas SparkPost only maintains event history and only for 10 days.
  • Postmark’s outbound message size limit is 10 MB including attachments, SparkPost’s limit is 20 MB.
  • Postmark messages can have up to 50 recipients in a single message.
  • You must use a Server API Token for both your SMTP username and password when using SMTP with Postmark. You can generate as many Server API Tokens as you need.
  • Postmark does not support scheduling messages to be delivered later. Postmark sends the emails as soon as the request to send is received. If you want to schedule messages to be sent at a later date or time, you would need to do that in your codebase.
  • Templates are not supported with Postmark’s SMTP service and can only be used with the Postmark API.
  • With Postmark, you can verify a single email address, or “Sender Signature,” for sending in place of verifying an entire domain

Verifying Email Addresses and Domains for Sending #

Similar to SparkPost, domains in Postmark are verified for sending using DKIM and SPF records added to your domain’s DNS. Head over to our help article on verifying a domain for sending with Postmark for more detailed steps. Unlike SparkPost, you cannot verify a domain by sending emails to the abuse@ and postmaster@ email addresses for your domain.

Unlike SparkPost, Postmark also includes an additional option for sending from a single email address that you can confirm using an emailed link. You can add individual addresses as Sender Signatures to your account, which does not require that you add DKIM and SPF records to send with that email address, though we always recommend setting up DKIM and SPF to maximize deliverability. 

You can add and manage your sending domains and email addresses from the Sender Signature page in Postmark. Each domain you add has an Authentication page that includes the unique DNS record information for setting up DKIM, SPF, and a custom return-path.

Tip: Postmark does not allow sending from any public domain email addresses, such as Gmail, Yahoo, AOL, Outlook, Live, etc…

Configuration for Sending via SMTP #

Each server you create in Postmark will have its own unique server API token(s). You will need to use a server API token (found in the credentials tab of a server in Postmark) for authenticating SMTP sending.

Tip: You will need to switch over to using port 25, 2525, or 587 when using Postmark SMTP. We recommend using port 2525 or 587, since port 25 is sometimes blocked by ISPs.

Settings SparkPost Postmark
SMTP Endpoint smtp.sparkpostmail.com smtp.postmarkapp.com
Port 587 or 2525 25, 587, or 2525
Username SMTP_injection Server API Token
Password API Key Server API Token
Authentication TLS (STARTTLS) Plain text (unencrypted), CRAM-MD5, TLS

If you need to whitelist the IPs you connect to Postmark SMTP with, whitelist the following ranges:

  • 147.75.195.176/30        [147.75.195.176 - 147.75.195.179]
  • 147.75.202.84/30          [147.75.202.84 - 147.75.202.87]
  • 147.75.205.84/30          [147.75.205.84 - 147.75.205.87] 

You can also view the help doc for the full Postmark IP list.

Sending via API #

Authentication
When authenticating with the Postmark API for sending emails, you will need to use your server API token in an X-Postmark-Server-Token header. As a reminder, you can get your server API token from the server’s credentials tab.

Outbound Sending API JSON Fields Map

Field SparkPost Postmark
From email address(es) content → from → emailFrom
From name content → from → emailFrom
ReplyTo email address content → reply_toReplyTo
ReplyTo name content → reply_toReplyTo
To email address(es) recipients To *
To name recipients To *
Cc email address(es) cc Cc *
Cc name cc Cc *
Bcc email address(es) bcc Bcc *
Bcc name bcc Bcc *
Archive Addresses archive
Metadata metadata Headers
Subject line content → subjectSubject
Custom Tag recipients → tagsTag
HTML Body content → htmlHtmlBody
Text Body content → textTextBody
Custom Headers content → headersHeaders
Template Identifier content → template_idTemplateId
Data to use in Template substitution_data TemplateModel
Open Tracking options → open_trackingTrackOpens
Link Tracking options → click_trackingTrackLinks
Attachments content → attachmentsAttachments
Inline Attachments content → inline_imagesAttachments
Send At Time options → start_time
Send API Request without sending email options → sandboxUse POSTMARK_API_TEST for your X-Postmark-Server-Token header value

Tip: To set a name when adding a To, From, Cc, or Bcc field with the Postmark API, use this format: “Full Name <email@domain.com>”

To start sending quickly with Postmark's API, be sure to check our our official and community API libraries.


Chapter 5

Processing Inbound Email#

Migrating your inbound email handling

For the most part, inbound email processing is implemented similarly between Postmark and SparkPost, but SparkPost refers to it as “Relay Events.” If you were using relay events with SparkPost and will be using Postmark for processing email once you migrate, this section is an important read.

Similarities #

  • Postmark and SparkPost both process inbound emails by converting them to well-formed JSON, which is then posted to a URL that you specify for receiving inbound webhooks. 
  • Both SparkPost and Postmark feature the ability to process emails sent to an entire sub-domain or domain using MX records.
  • You can manage inbound webhook settings using an API (Relay Webhooks API in SparkPost and Servers API in Postmark)

Differences #

  • Postmark will provide the raw content as well as a clean “Stripped Reply” that removes any quoted text and email signatures.
  • Postmark will automatically parse and strip the inbound email address to include a field for the Mailbox Hash 
  • With Postmark, you do not have to use a verified domain for inbound domain forwarding, and Postmark does not require that you set up inbound domain forwarding using an MX record in order to use inbound processing. Each server you create in Postmark will come with a unique inbound email address (ex. yourhash@inbound.postmarkapp.com) that you can use to receive emails inbound at your webhook URL. However, if you want to use inbound domain forwarding, and MX record is required.
  • With SparkPost, attachments are must be extracted from the base64-encoded email content whereas Postmark will send base64-encoded attachments as additional attributes directly in the JSON payload.
  • You can use a wildcard in your MX record to have all sub-domains of your domain point to Postmark for inbound processing.
  • Postmark requires that you enable SMTP (if not enabled already) on your Postmark server to use inbound processing.
  • SparkPost retries inbound message POSTs first at 300 seconds after the initial post, and then repeatedly tries up to 7 times with a back-off algorithm. With Postmark, a total of 10 retries will be made over a 10.5 hour period, with growing intervals from 1 minute to 6 hours. If all of the retries have failed, your inbound activity page will show the message has a processing error.
  • Postmark’s inbound message size limit including attachments is 35 MB, whereas SparkPost’s is 20 MB.
  • Postmark allows you to use filters to block specific domains or email addresses from inbound processing. This save you the processing resources and does not charge you credits for spam or other abuse. These messages are saved for 10 days, and you can bypass the block via the web interface or API.
  • Postmark also offers some SpamAssassin message scoring and filtering for inbound messages.


Inbound Processing JSON Fields Map #

Email Property SparkPostPostmark
Message Identifier for UI/API headers →Message-ID MessageID
HTML Body content → html HtmlBody
Plain Text Body content → text TextBody
Subject Line content → subject Subject
To Email Address content → tofriendly_fromTo, ToFull → Email
From Email Address friendly_from From, FromFull → Email
Cc Email Address content → cc Cc, CcFull → Email
Bcc Email Address Bcc, BccFull → Email
ReplyTo Email Address ReplyTo
Date headers → date Date
Attachment Filename(s) content → email_rfc822 → attachments Attachments → Name
Attachment Content content → email_rfc822 → attachments Attachments → Content
Attachment Content-Type content → email_rfc822 → attachments Attachments → ContentType
Attachment Size content → email_rfc822 → attachments Attachments → ContentLength
Number of Attachments content → email_rfc822 → attachments Attachments (array size)
Headers content →headers Headers
Tag Tag
Mailbox Hash MailboxHash
Stripped Text Reply StrippedTextReply
Sender’s IP Address
DKIM headers → DKIM-Signature Headers → DKIM-Signature
SPF headers → Received-SPF Headers → Received-SPF
SpamAssasssin Score
Headers
SpamAssassin Report
Headers → X-Spam-Tests
SpamAssassin Version Headers → X-Spam-Checker-Version
Character Sets
Identified as Spam Headers → X-Spam-Status
Raw MIME Contentcontent → email_rfc822

Inbound Spam Filtering #

Postmark provides you with some additional control on how spam filtering is handled that is not available in SparkPost. In your inbound settings in the Postmark UI (Settings > Inbound) you can set your Spam Assassin threshold, which is the Spam Assassin score that needs to be reached or exceeded to trigger the spam filter (the higher the Spam Assassin score, the more likely the email is spam).

A screenshot of the slider for the SpamAssassin threshold as well as a text input field for adding rules for filtering spam.
Postmark's inbound spam filtering settings

In the inbound spam filtering settings you can also add rules for blocking inbound messages from specific email addresses and domains.


Chapter 6

Webhooks#

Migrating your webhook handlers to Postmark

Both SparkPost and Postmark allow you to receive notifications as JSON POSTs to URLs you specify when specific events occur. While SparkPost has one main webhook concept with different event types, Postmark splits up event types into multiple distinct webhooks.

Webhook Types Map #

Event Type SparkPostPostmark
Inbound Processing Relay events webhookInbound webhook
Delivery Message events webhookDelivery webhook
Bounces Message events webhook
Bounce webhook
Spam Complaints Message events webhook
Bounce webhook
Open tracking Engagement events webhookOpen tracking webhook
Click tracking Engagement events webhook

There are some values provided by SparkPost's Event Webhooks that do not have comparable fields in Postmark’s webhooks, such as:

  • Whether TLS was used when sending the email
  • IP address used to send the email
  • If there was a certificate error on the receiving mail server when the email was sent
  • Generation and Unsubscribe events (since Postmark does not support sending newsletters)
  • The SMTP message identifier for the sent email. Postmark includes the Postmark MessageID for identifying the email.

Delivery webhook #

Postmark’s delivery webhook allows you to receive notifications when an email is delivered to a recipient. In Postmark, an email is considered successfully delivered when the destination email server returns a 250 OK response after delivery is attempted.

Delivery Webhook Fields Map #

Parameter SparkPost Postmark
Recipient’s email address rcpt_to, raw_rcpt_to, rcpt_metaRecipient
Tag/Category (Message tags in Postmark, Recipient tags in SparkPost)rcpt_tagsTag
Recipient Type (To, Cc, Bcc)rcpt_type
Delivery time timestampDeliveredAt
Receiving mail server’s response
Details
Email Identifier message_idMessageID
Server used to send the email (Server in Postmark, Subaccount in SparkPost)subaccount_idServerID
SubjectsubjectMessageID → Email → Subject
IP address used for sending sending_ip
Recipient Servier IPip_address
IP poolip_pool
Campaign Identifiercampaign_id
Customer Identifiercustomer_id
Delivery Methoddelv_method
Event IDevent_id
Friendly Fromfriendly_fromMessageID → Email → From
Message Frommsg_from
Message Sizemsg_size
Number of Retriesnum_retries
Queue Timequeue_time
Routing Domainrouting_domain
Template IDtemplate_id
Template Versiontemplate_version

Bounce webhook #

Postmark includes some additional information for bounce events that is not present in the SparkPost Event Webhook you should be aware of:

  • Information on whether the recipient’s email address is deactivated and can be reactivated
  • Whether a message dump is available. Postmark stores content for 45 days but retains bounce information indefinitely. If the message was sent less than 45 days ago, you can get a full dump of the message content if this parameter’s value is true

It's also important to note that Postmark's bounce webhook also handles spam complaints and notifications whereas SparkPost uses a separate set of web hooks just for Spam. The fields below denote when an attribute from a SparkPost webhook is only included for spam or bounce requests.

Bounce Webhook Fields Map #

Parameter SparkPost Postmark
Recipient’s email address rcpt_to, raw_rcpt_to, rcpt_meta
Email
Recipient Type (To, Cc, Bcc)rcpt_type
From email address friendly_from, msg_fromFrom
Email subject line subjectSubject
Bounce timestamp timestampBouncedAt
Tag/Category (Message tags in Postmark, Recipient tags in SparkPost) rcpt_tags
Tag
Unique bounce identifier event_idID
Bounce Type bounce_class
(Bounce Hook Only)
Type
Email Identifier message_idMessageID
Server used to send the email (Server in Postmark, Subaccount in SparkPost)subaccount_idServerID
Error Code error_code
(Bounce Hook Only)
Bounce details raw_reason
(Bounce Hook Only)
Details
Description of bounce reason 
(Bounce Hook Only)
Description
Whether the recipient’s email is deactivated Inactive
Whether the recipient’s email address can be reactivated CanActivate
If a message dump is available DumpAvailable
Event Typetype
Campaign IDcampaign_id
Customer IDcustomer_id
Delivery Methoddelv_method
Type of Spam Reportfbtype
(Spam Hook Only)
Details, Description
Report Byreport_by
(Spam Hook Only)
Report Toreport_to
(Spam Hook Only)
Originating IP Addressip_address
Originating IP Poolip_pool
Message Sizemsg_size
Routing Domainrouting_domain
Sending IPsending_ip
Template IDtemplate_id
Template Versiontemplate_version
Transmission IDtransmission_id

Tip: Postmark includes an additional option when setting your bounce webhook URL to include the message content in the JSON sent to your URL. This option lets you receive the full message content when receiving bounce event information.

Open Tracking webhook #

You will notice some open tracking information available with the Postmark open tracking webhook that does not exist in SparkPost's Event webhook or is more difficult to access:

  • The platform the recipient was using (mobile, desktop, webmail). SparkPost only provides the user agent string, and you have to parse it yourself.
  • The email client or browser the recipient was using when they opened the email. SparkPost only provides the user agent string, and you have to parse it yourself.
  • The IP address of the recipient when the email was opened
  • How long the email was opened for
  • Whether this open event was the first time the email was opened

Open Tracking Webhook Fields Map #

Parameter SparkPostPostmark
Recipient’s email address rcpt_to, raw_rcpt_to, rcpt_meta
Recipient
Tag/Category (Message tags in Postmark, Recipient tags in SparkPost) rcpt_tags
Tag
Recipient Type (To, Cc, Bcc)rcpt_type
Timestamp of when open occurred timestamp
ReceivedAt
Email Identifier message_id
MessageID
User Agent user_agent
UserAgent
IP Address of recipient when they opened the email
Geo → IP
Platform Parse from user_agent Platform
Email client used to open the email Parse from user_agent Client
How long the email was opened ReadSeconds
Geographic Location geo_ip Geo
Whether this was the first open for this email FirstOpen
Event Typetype
Campaign IDcampaign_id
Customer IDcustomer_id
Delivery Methoddelv_method
Event IDevent_id
Friendly Fromfriendly_from
IP address to which the message was deliveredip_address
IP Poolip_pool
Message Frommsg_from
Message Sizemsg_size
Number of Retriesnum_retries
Queue Timequeue_time
Routing Domainrouting_domain
Sending IPsending_ip
Subaccount IDsubaccount_id
Template IDtemplate_id
Template Versiontemplate_version
Transmission IDtransmission_id

Chapter 7

UI Overview#

Getting familiar with the Postmark app

When you log into Postmark you are placed in the Servers page, which shows each Server you have created. Each Server has tabs for Statistics, Activity, Templates, Settings, and Credentials.

Servers #

Postmark provides you with the ability to organize your emails by servers. This lets you separate sending based on domains, environments, customers, or any other facet that helps organize the activity of a given application.

A screenshot of Postmark's conceptual servers.
You can use servers in Postmark to group logically related email activity by domains, environments, or other factors.

Statistics #

To view statistics and metrics for a server, click on the server, which will take you to its statistics tab. 

The statistics tab is similar to SparkPost's Reports pages, though each server has its own statistics page rather than an overall account view like SparkPost. Included in the statistics area are the server's sending volume, processed (inbound) volume, link tracking metrics (if enabled), open tracking metrics (if enabled), and bounce metrics.

Screenshot of the detailed statistics for a server report. Emails sent, opened, and clicked filterable by date and tags.
Email activity can be filtered by date and tag to show the levels of engagement for various groups of emails or all emails.

Activity #

To see your inbound and outbound activity in a server, click on the Activity tab. This area will show a detailed event view of that Server’s events, including sent, delivered, open events, spam complaints, bounces, etc... Use the search bar to look for emails by subject or email address.

To see details for a particular event, click on the event. Some events included are sent emails, bounces, spam complaints, clicked links, and opened emails. Events in Activity are color coded to help you tell what occurred at a glance:

  • Email sent - green 
  • Email opened - blue
  • Link clicked - purple
  • Bounce/spam complaint - red
  • Message queued - yellow
Screenshot of an example email activity feed showing emails sent, opened, clicked, bounced, or marked as spam.
The events activity stream will show emails, opens, bounces, clicks, and spam complaints.
Screenshot of the detailed view of an email.
In addition to message events, Postmark stores the full content (both plain text and HTML) of emails for 45 days.
Screenshot of an email with a bounce notification and the option to reactivate.
When an email bounces, Postmark provides a detailed explanation from the server response as well as the option to reactivate delivery. You can also reactivate delivery for bounced addresses using the API.

Templates #

Postmark gives you the ability to create and store templates including a variety of pre-built and well-test templates for common scenarios. From the Templates tab you can create, edit, and delete the server’s templates. Each server contains its own templates but you can easily copy templates from one server to another.

Alternatively, if you'd like to build your own batch of templates, we've created and open-sourced MailMason to help you automate the process of creating, testing, and managing your own templates using partials, variables, SASS, and asset management.

Screenshot of the choice of templates or the option to code your own templates.
Postmark includes a variety of pre-built and well-tested templates to make getting started easier. They include Welcome emails, Password reset, Receipts, Invoices, and more.

Settings #

The Settings tab lets you modify the server’s general, outbound, and inbound settings. This is where you can change the server’s name, color, webhook URLs, open tracking, and link tracking settings.

Screenshot of server settings featuring the server name, a color, and the option to delete the server.
The main server settings let you rename your server as well as change the server's representative color.

Credentials #

The Credentials tab shows you your server API token(s) and the server’s inbound email address. Use this tab to create/delete server API tokens and access your inbound email address.

Screenshot of example server credentials for the server API as well as the automatically generated inbound email address.
The Server credentials tabs provides a unique API token for the server as well as an automatically generated and unique inbound email address.

Managing Account Settings #

The Account page is where you can add emergency contacts in case we need to reach you regarding your account and have not heard back from the owner, set up billing notifications, mange your account API tokens, purchase credits, and other administrative features.

Screenshot of account settings like emergency contacts, billing notification contacts and account-level API token management.
From the account settings, you can add emergency contacts as well as billing notification contacts. You can also manage account-level API tokens.

Users and Permissions #

The Users page is where you add and manage users to your account for tasks such as viewing activity for troubleshooting and tracking purposes, managing server settings, creating templates, etc... Use our different roles to effectively manage the security of your account. See our help article on setting permissions for an overview of what options there are and how to control your users’ permissions.

Screenshot of the users and permissions list with an owner and an admin showing server-level permissions.
Users and permissions can be managed to allow full or read-only access to individual servers.
Screenshot of advanced user permissions management.
You can control whether someone has access to the full account or individual servers, and with each individual server, you can control whether they have full access or read only access.

Chapter 8

Conclusion#

It’s time to switch

Dive Deeper #

For more Postmark specific insight on how to get started and get the most out of Postmark, make sure to look through our “Getting Started Guide” or visit our support center where you can easily search all of our documentation from a single place. API docs. Guides. Blog posts. Help docs. Labs projects. You name it. We probably have something that can help you out.

Status information #

Once you've switched to Postmark, you may want to become familiar with our status page and status API. We believe deeply in transparency, and we go a step further than just system availability and share our inbox rates and delivery speeds for the five most popular inbox providers. We also offer all of the data via an API so you can monitor us and set up automation in the event something does go wrong.

Say hello! #

We love to help. Feel free to reach out via email or  through our contact form, Twitter (@postmarkapp), or even give us a call at 1-855-286-7373. Or, if you have questions or need advice, you can schedule time directly with Rian, the Postmark product manager.

Welcome aboard #

You now have a solid understanding of how to transition over the core features you need in an ESP from SparkPost to Postmark, including how to send outbound and process inbound email, what APIs and webhooks to use for certain functions, and how to view your email activity and statistics. If you have any questions about where to find a setting or how to use a feature in Postmark, get in touch and we can help!

Still have questions?

  • Dana Chaby Dana
  • Marek Loder Marek

Ask us anything! We’re eager to help you with any problem or question you have…