Two paper planes. One white and one yellow.

Amazon SES Migration Guide

Everything you need to know about moving from SES to Postmark

Table of Contents

Chapter 1

Introduction#

Key differences between Amazon SES 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 Amazon SES. This guide will detail some of the differences and similarities between SES and Postmark, as well as give some useful tips for migrating to Postmark from SES.

It includes details on differences between the Postmark and SES APIs, sending outbound emails, processing inbound emails, UI differences, and webhooks. For quick reference, we have included tables where possible to equate SES functionality and JSON fields to their comparable functionality and fields in Postmark.

Key differences between SES and Postmark #

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

  • Postmark does not allow anyone to send marketing or bulk email, whereas SES does. If you were sending your marketing and/or bulk email through SES and want to switch those over to another provider, we highly recommend using Campaign Monitor for any bulk email you need to send.
  • Since Postmark does not allow bulk email (including subscription newsletters), there are no list management features available in Postmark, such as creating lists, handling unsubscribes, or adding unsubscribe links to your emails automatically.
  • You do not need to set up your own logging or perform any additional steps to store sent messages. Successfully sent messages are stored for 45 days in Postmark automatically (including the content and delivery events). Sent messages are available to view using our UI or you can pull them with our REST API.  
  • Bounces and spam complaints are also stored indefinitely, for troubleshooting purposes.
  • Postmark uses a pay as you go credits model instead of monthly billing for the previous month’s usage. See our pricing page for more details. One credit is used per email sent/received and credits never expire. Credits are purchased in advance and discounts are offered for large volume credit purchases.
  • Postmark starts you with 25,000 free credits when you create your account but you will need to purchase more credits once those are used. There are no free tier options available.
  • There is not an option to purchase dedicated IPs from the Postmark UI. Most customers use our well-maintained, shared IP ranges. We do not recommend using dedicated IPs for most senders but do move high volume senders to dedicated IPs at no additional charge.  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 have a reseller or affiliate program.
  • Postmark’s account approval process is automatic. There is no ‘moving out of the sandbox’ process like with SES. You may be contacted for more information if we need it when reviewing your account, but odds are you won’t hear anything from us except the approval confirmation within 24 hours.
  • Postmark does not have sending quotas or maximum sending rates that you have to adhere to or request increases on. You can send as many emails as you need to, when you need to send them.

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 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 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.

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.

Tip: You can use any sender signature/verified domain for sending with any Postmark server, from any location. You do not need to verify the same domain multiple times for using with different AWS regions.


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 Type SES API Action(s) Postmark API Name
Sending Emails SendEmail, SendRawEmail Email
Managing Bounces SendBounce Bounce
Managing Templates CreateTemplate, DeleteTemplate, GetTemplate, ListTemplates, SendTemplatedEmail, UpdateTemplate Templates
Managing Sending Settings CreateConfigurationSet, CreateConfigurationSetEventDestination, DeleteConfigurationSet, DeleteConfigurationSetEventDestination, ListConfigurationSets, UpdateConfigurationSetEventDestination Server
Managing Servers
Servers
Managing Sent Emails
Messages
Managing Inbound Emails
Messages
Managing Inbound Processing Settings CreateReceiptFilter, CreateReceiptRule, CreateReceiptRuleSet, DeleteReceiptFilter, DeleteReceiptRule, DeleteReceiptRuleSet, DescribeActiveReceiptRuleSet, DescribeReceiptRule, DescribeReceiptRuleSet, ListReceiptFilters, ListReceiptRuleSets, ReorderReceiptRuleSet, SetActiveReceiptRuleSet, SetReceiptRulePosition, UpdateReceiptRule Server
Manage email domains you can send from GetIdentityDkimAttributes, GetIdentityMailFromDomainAttributes, SetIdentityDkimEnabled, SetIdentityMailFromDomain, VerifyDomainDkim, VerifyDomainIdentity Domains
Manage email addresses you can send from DeleteIdentity, VerifyEmail, ListIdentities, GetIdentityVerificationAttributes Sender Signatures
Sending Statistics GetSendStatistics Stats

Tip: Rather than a single API that has multiple ‘actions’, Postmark has multiple APIs with different endpoints, which are used for the specific operations you need to make.

API Libraries #

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

API Libraries Map #

Language/Framework SES SDK Postmark Official Library Postmark Community Library
C# C# SDK, .NET SDK Postmark .NET
Classic ASP Simple Classic ASP Class for Postmark 
Clojure Clojure Binding for Postmark API
ColdFusion cfPostmarkapp, ColdFusion component, A replacement for the stock Coldbox MailService Plugin
Drupal Drupal Library
ElixirEx Postmark
Erlang Erlang Library
Go Go SDK Postmark Golang, Postmark.go
Grails Grails plugin
Grunt Postmark Grunt
Haskell Haskell Library
Java Java SDK Java library, Spring's MailSender compatible implementation
Laravel Laravel Plugin
Magento Magento Extension
NodeJS Postmark.js
Objective-C Standalone Objective-C Class
Perl Perl WWW::Postmark
Pharo Smalltalk Pharo Smalltalk, Postmark
PHP PHP SDK Postmark PHP PHP Community Libraries
PowerShell Postmark PowerShell Snap-in
Python Python SDK Postmarker, pystmark, Postmark Python library
Ruby Ruby SDK Postmark Ruby
Rails Postmark Rails
Scala Scala Client, Scala Library
WordPress Plugin Postmark for WordPress
Zend Postmark drop-in replacement for Zend

Chapter 4

Sending Outbound Emails#

Start sending through Postmark

Similarities to SES #

  • Sending via an API and/or SMTP supported
  • Like SES’ success@simulator.amazonses.com test address, 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 check out our blog post about best practices when testing with your Postmark account.
  • Entire domains can be verified for sending using DKIM and SPF records.
  • The maximum message size, including attachments, is 10 MB with both SES and Postmark.
  • Postmark messages can also have up to 50 recipients in a single message, which is the same as SES.

Differences from SES #

  • Postmark does not have sending quotas or maximum sending rates that you have to adhere to or request increases on.
  • You only need to verify a domain or individual email address for sending with Postmark once, whereas with SES you may be used to verifying the same domain multiple times for each AWS region.
  • There is only one SMTP endpoint with Postmark (smtp.postmarkapp.com), unlike SES, which has three different endpoints for different regions. We will automatically route you to the nearest data center when connecting to smtp.postmarkapp.com.
  • SES allows sending messages using a raw MIME format, which is not supported by Postmark. Emails must be sent through Postmark’s API or SMTP using the MIME components (To, From, Subject, etc…).
  • 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 for each Server as you need.
  • Templates are not supported with Postmark’s SMTP service and can only be used with the Postmark Templates API.

Verifying Email Addresses and Domains for Sending #

Similar to SES, domains in Postmark can be verified for sending using DKIM and SPF records added to your domain’s DNS. You need to use both an SPF and DKIM record to verify a domain in Postmark, whereas SES just requires a DKIM record for domain verification. Head over to our help article on verifying a domain for sending with Postmark for more detailed steps.

Once you add DKIM and/or SPF for a domain in Postmark, it is applied automatically to all emails sent from that domain, without an option to disable it at the message or sending email address level. Similar to SES, we will also periodically check your DNS to make sure the TXT record for DKIM is still in place. We do not completely remove domains from your account if we do not detect it, though. If we find the DKIM record is not present, we will pause signing with DKIM and send you an email notification so you are aware and can get the record back in your DNS.

With Postmark you only need to verify a domain once, you do not need to complete the process for multiple regions like you do with SES. Sub-domains are also not automatically verified in Postmark once you verify a root domain. Each sub-domain you want to send from will also need to be added to your Postmark account and verified with DKIM/SPF records.

Postmark, like SES, 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. If you need multiple sets of credentials, you can either create multiple Servers in Postmark (since each Server has its own unique token) or generate additional Server API Tokens for your single Server.

Tip: Port 2587 is not supported with Postmark SMTP. If you were using that port with SES, 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 or throttled by ISPs.

Setting SES Postmark
SMTP Endpoint email-smtp.us-east-1.amazonaws.com, email-smtp.us-west-2.amazonaws.com, email-smtp.eu-west-1.amazonaws.com smtp.postmarkapp.com
Port 25, 587, or 2587 25, 587, or 2525
Username SES SMTP Credentials (Username) Server API Token
Password SES SMTP Credentials (Password) Server API Token
Authentication SSL, TLS 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]

This IP list is maintained at http://support.postmarkapp.com/article/800-ips-for-firewalls.

Message Level Options when Sending with SMTP #

Similar to SES, some SMTP sending options are specified in SMTP headers when using Postmark.

Option SES Postmark
Click Tracking X-SES-CONFIGURATION-SET X-PM-TrackLinks header
Open Tracking X-SES-CONFIGURATION-SET X-PM-TrackOpens header
Tags X-SES-MESSAGE-TAGS X-PM-Tag header

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, similar to the X-Amzn-Authorization header in SES. As a reminder, you can get your server API token from a server’s Credentials tab.

Outbound Sending API JSON Fields Map #


Field SES Postmark
From email address Source From
From name Source From
ReplyTo email address ReplyToAddresses ReplyTo
ReplyTo name ReplyToAddresses ReplyTo
To email addresses(es) Destination To *
To name Destination To *
Cc email addresses(es) Destination Cc *
Cc name Destination Cc *
Bcc email address(es) Destination Bcc *
Bcc name Destination Bcc *
Subject line Message Subject
Custom Tag Tags Tag
HMTL Body Message → Body → HTML HtmlBody
Text Body Message → Body → Text TextBody
Custom Headers RawMessage → Data Headers
Template Identifier Template TemplateId
Data to use in Template TemplateData TemplateModel
Open Tracking ConfigurationSetName TrackOpens
Link Tracking ConfigurationSetName TrackLinks
Attachments RawMessage → Data (SendRawEmail Action Only) Attachments
Inline attachments RawMessage → Data (SendRawEmail Action Only) Attachments
Send API Request without sending email Use 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

How inbound email processing is implemented is very different between Postmark and SES. If you were using inbound processing with SES and will be using Postmark for processing email once you migrate, this section is an important read.

Similarities #

  • Both SES and Postmark feature the ability to process emails sent to an entire sub-domain or domain using MX records.
  • Custom settings for blocking incoming email are available in both SES and Postmark.

Differences #

  • Postmark’s inbound message size limit is 35 MB compared to SES's limit of 10 MB.
  • Postmark does not require you to take any actions to preserve inbound messages. We will automatically keep them in your Activity and available through the API for 45 days.
  • Specific actions based on the recipient (Receipt Rules / Receipt Rule Sets in SES) cannot be set in Postmark. Your code for your inbound webhook URL would need to take care of any additional processing tailored for specific recipients.
  • It is not possible to block inbound messages by their source IP. Instead, Postmark provides inbound message blocking based on the sender's email address, sender's domain, and SpamAssassin spam score.
  • 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.  
  • Postmark receives inbound emails, converts them to JSON, and POSTs them to your inbound webhook URL, rather than processing them using Receipt Rules that route the messages to an S3 bucket, Amazon WorkMail, or SNS notification.
  • 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.
  • In the event your inbound webhook URL fails to send a successful response to an inbound message, a total of 10 retries will be made by Postmark, 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.
  • Headers cannot be added to inbound messages in Postmark.


Inbound Processing JSON Fields in Postmark #

Email Property SES Postmark
Message Identifier for UI/API mail→messageId MessageID
HTML Body content HtmlBody
Plain Text Body content TextBody
Subject Line mail→commonHeaders Subject
To Email Address receipt→recipients To, ToFull → Email
From Email Address mail→source From, FromFull → Email
Cc Email Address receipt→recipients Cc, CcFull → Email
Bcc Email Address receipt→recipients Bcc, BccFull → Email
ReplyTo Email Address mail→headers ReplyTo
Date mail→timestamp Date
Attachment Filename(s) mail→content Attachments → Name
Attachment Content mail→content Attachments → Content
Attachment Content-Type mail→content Attachments → ContentType
Attachment Size mail→content Attachments → ContentLength
Attachment Content-ID mail→content Attachments → ContentID
Number of Attachments mail→content Attachments (array size)
Headers mail→headers, mail→commonHeaders Headers
Tag Tag
Mailbox Hash MailboxHash
Stripped Text Reply StrippedTextReply
DKIM receipt→dkimVerdict→status Headers → DKIM-Signature
SPF receipt→spfVerdict→status Headers → Received-SPF
SpamAssasssin Score Headers
SpamAssassin Report Headers → X-Spam-Tests
SpamAssassin Version Headers → X-Spam-Checker-Version
Identified as Spam receipt→spamVerdict→status Headers → X-Spam-Status
Identified as containing a virus receipt→virusVerdict→status
Processing Time receipt→processingTimeMillis


Inbound Spam Filtering Settings
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

Somewhat similar to Event Publishing using Configuration Sets in SES, Postmark allows you to receive notifications as JSON POSTs to URLs you specify when specific events occur using webhooks. With Postmark, you are no longer forced to use CloudWatch, Amazon SNS, or Kinesis Firehose to receive events, since you can use any URL for receiving webhook events with Postmark. Postmark webhooks are sent in real-time as message level events occur, meaning each POST to your webhook URL is for a specific message. Postmark has unique webhooks for each event type (Open, Delivery, Bounce, Inbound message) rather than a single source that specifies the event with an event type parameter.

Tip: Postmark does not yet support receiving events for clicks, but does plan on adding it in the future.

Webhook Types Map #

Event Type SES Postmark
Inbound Processing
Inbound webhook
Delivery eventType → delivery Delivery webhook
Bounces eventType → bounce Bounce webhook
Spam Complaints eventType → complaint Bounce webhook
Open tracking eventType → open Open tracking webhook

Tip: Postmark uses an absolute time (e.g. 2017-06-23T14:14:39.3185236-04:00) for any webhook event timestamps.

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 SES Postmark
Recipient’s email address mail → recipient Recipient
Tag/Metadata Tag
Delivery time mail → timestamp DeliveredAt
Receiving mail server’s response mail → smtpResponse Details
Email Identifier mail → messageId MessageID
Email Source (Server in Postmark, Domain/Address in SES) mail → sourceArn ServerID
MIME Headers mail → headers

Bounce webhook #

Postmark includes some additional information for bounce events that is not present in the SES event notification you should be aware of:

  • The Postmark server used to send the email
  • 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.

Bounce Webhook Fields Map #

Parameter SES Postmark
Bounced recipient’s email address Bounce → bouncedRecipients → emailAddress Email
From email address mail → commonHeaders From
Email subject line mail → commonHeaders Subject
Bounce timestamp Bounce → timestamp BouncedAt
Tag/Metadata Tag
Unique bounce identifier Bounce → feedbackId ID
Bounce Type Bounce → bounceType Type
Email Identifier mail → messageId MessageID
Server used to send the email ServerID
SMTP Status code
Bounce details Bounce → status Details
Description of bounce Description
MIME Headers mail → commonHeaders
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

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 SES Open objects:

  • How long the email was opened for
  • Whether this open event was the first time the email was opened
  • Country, Region, and City where the email was opened
  • Platform, Email client, and OS the recipient was using when they opened the email
Parameter SES Postmark
Recipient’s email address mail → recipient Recipient
Tag/Metadata Tag
Timestamp of when open occurred Open → timestamp ReceivedAt
Email Identifier mail → messageId MessageID
User Agent Open → userAgent UserAgent
IP Address of recipient when they opened the email Open → ipAddress Geo → IP
Country where email was opened Geo → Country, Geo → CountryISOCode
Region where email was opened Geo → Region, Geo → RegionISOCode
City where email was opened Geo → City
Platform Platform
Email client used to open the email Client
OS recipient was using OS
How long the email was opened ReadSeconds
Whether this was the first open for this email FirstOpen



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 the aggregate metrics you can view with SES, though each server has its own statistics page, rather than an overall account view. 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 #

Coming over from SES, you might not be used to being able to quickly view sent and received messages in a friendly UI, without having to do any additional setup. With Postmark, you can quickly search and view your sent and processed messages without any extra effort or development work. Postmark will automatically store and display all successfully sent messages for 45 days and all bounces indefinitely.

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.

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 and how to move from Amazon SES 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…