Use a Postmark server token
Store the approved Server API token in encrypted CMS Max settings and select Postmark as the active mail transport.
Transactional email / Native email transport
Deliver CMS Max Transactional Email with Postmark
Connect a focused transactional email service to the messages customers and teams rely on.
Postmark can serve as the active CMS Max outbound mail transport. CMS Max generates the form, account, order, and system messages; Postmark accepts those messages through the connected server token and attempts delivery using the verified sender identity.
- Encrypted Server API token
- Outbound transactional delivery
- Verified sender or domain required
- One active CMS Max mail transport
Transactional deliveryPostmark outbound transport
Sender verified
Transactional emailPostmark + CMS MaxNative email transport
TransportPostmark
CredentialServer token
PurposeSystem email
Inbound eventsNot connected
01CMS Max eventA system message is created
02API handoffPostmark receives the message
03Mailbox deliveryPostmark attempts provider delivery
04FeedbackReview in Postmark; no native event sync
What the integration does
A focused transport for expected operational messages.
The native integration configures outbound delivery through Postmark. It does not claim inbound email processing, message-template synchronization, provider analytics inside CMS Max, or Postmark event webhooks back into the tenant.
Route system messages
Send CMS Max transactional email through the connected Postmark server while the platform retains the original workflow and message context.
Verify the sender identity
Confirm the sending address or domain in Postmark and complete recommended DNS authentication before production acceptance.
Integration boundary
Keep content, transport, identity, and feedback ownership visible.
The fastest way to resolve email issues is to know where each responsibility begins and ends.
| Area | Primary owner | Supported contract |
|---|---|---|
| Message trigger and content | CMS Max | Creates the system email for the relevant website, form, account, or commerce action. |
| Outbound API transport | Postmark | Accepts the message using the connected server token and attempts delivery. |
| Sender signature or domain | Business / DNS owner | Verifies the sender and maintains the recommended DKIM and Return-Path configuration. |
| Mailbox acceptance | Recipient provider | Applies authentication, reputation, policy, filtering, and mailbox rules. |
| Postmark events inside CMS Max | Not connected | Current integration does not synchronize provider delivery events into the CMS Max tenant. |
Connected workflow
Move from verified sender to accepted customer message.
A correct token is only the beginning of a production email configuration.
Inventory
List system messages, triggers, recipients, sender and reply identities, templates, required fields, links, and criticality.
Connect
Create or select the intended Postmark server, verify account ownership, and add the approved Server API token to CMS Max.
Authenticate
Verify the sender signature or domain and publish the recommended authentication records.
Test
Trigger representative form, order, account, and exception messages across major mailbox providers and mobile clients.
Operate
Monitor Postmark activity, failures, suppressions, sender health, credentials, billing, and support ownership.
High-value applications
Use Postmark for system email tied to real platform actions.
Transactional email should be expected, specific, and useful to the recipient.
Order communication
Deliver configured CMS Max order and commerce messages through a verified sender.
Form communication
Route customer confirmations and internal notifications generated by approved CMS Max forms.
Account recovery
Support password reset and account messages with tested links, sender identity, and delivery behavior.
Operational alerts
Send expected system notifications to the responsible team through the selected production transport.
Governance and trust
Treat the Server API token and sender identity as production assets.
Secure credentials, authenticated domains, reviewed message content, and a monitored provider account protect customer trust.
Least-privilege access
Limit Postmark and CMS Max administrative access and document who can rotate the server token or change sender settings.
Authenticated identity
Verify the sending signature or domain and maintain DKIM and Return-Path alignment recommended by Postmark.
Transactional purpose
Keep operational messages separate from bulk marketing and send only when the recipient reasonably expects them.
Feedback ownership
Assign a provider owner because Postmark events are not natively synchronized back into CMS Max.
Search and conversion continuity
Protect the conversion journeys that bring customers into the platform.
Reliable confirmations, resets, and notifications preserve confidence after a visitor finds a CMS Max page through search, a campaign, or a direct referral.
Form continuity
Test every high-value landing-page form through submission, notification, confirmation, and follow-up.
Commerce trust
Align order email with the storefront, support identity, HTTPS domain, account, and order-detail experience.
Durable links
Point transactional messages to maintained CMS Max destinations with accurate content and secure actions.
Accessible content
Use descriptive subjects, readable text, meaningful links, valid reply paths, and mobile-friendly templates.
Implementation sequence
Test the whole message path before selecting Postmark.
Because CMS Max uses one active mail transport, the change should be accepted with representative production-like triggers.
Prepare
Inventory messages, create the Postmark server, verify owners, confirm sender identity, and collect the server token.
Authenticate
Verify the sender signature or domain and complete the recommended DNS records.
Accept
Test recipients, templates, variables, links, replies, failures, mailbox placement, mobile rendering, and provider visibility.
Switch
Select Postmark as the active transport, monitor initial messages, document escalation, and retain a rollback option.
Implementation references
Review the platform and provider evidence.
Provider capabilities and requirements change. These links support implementation discovery; the production configuration and acceptance test remain authoritative for your site.
Postmark FAQ
Questions teams ask before they connect.
Final scope depends on account configuration, customer journeys, data policy, compliance requirements, connected systems, ownership, and acceptance criteria.
What credential does CMS Max need for Postmark?
The integration uses a Postmark Server API token, which is stored in encrypted CMS Max settings. Use the token for the intended production server and protect account access.
What email is sent through Postmark?
When selected as the active transport, Postmark delivers outbound system email generated by CMS Max workflows such as form notifications, order messages, password resets, and other configured transactional email.
Must the sender be verified?
Yes. Postmark requires a confirmed sender signature or verified domain. Postmark also recommends domain authentication such as DKIM and a custom Return-Path for production identity and deliverability.
Can Postmark and Mailgun be active together?
CMS Max selects one active email transport. Compare operational needs, test the chosen service, and preserve a rollback path before switching.
Does CMS Max display Postmark delivery events?
No native Postmark event synchronization is represented by the current integration. Provider activity, failures, suppressions, and sender health should be monitored in Postmark or through separate work.
Does the plugin import Postmark templates?
No template synchronization is represented. CMS Max creates the platform message and Postmark transports it through the connected server.
Connect with confidence
Give CMS Max transactional messages a tested Postmark delivery path.
Bring the Postmark server, verified sender or domain, DNS access, message inventory, sender and reply addresses, test recipients, compliance requirements, and monitoring owner. CMS Max will configure and validate the transport.
Postmark is a trademark of its respective owner. CMS Max integration scope is described on this page and may differ from the provider's complete product offering.
Building Relationships with Web Developers and Marketing Agencies that want better results
The world's fastest and most SEO friendly website code.