Use shared or custom sending
Start with the eligible CMS Max shared Mailgun service or connect a customer-managed domain, API secret, and validation key.
Transactional email / Native email transport
Deliver CMS Max Transactional Email with Mailgun
Route important website messages through a purpose-built email service with a shared or customer-managed sending configuration.
Mailgun can serve as the active CMS Max outbound mail transport for form notifications, order messages, password resets, and other system email. Eligible sites can use the shared CMS Max configuration or connect a custom Mailgun domain and credentials.
- Shared or custom configuration
- Outbound transactional delivery
- Encrypted custom credentials
- One active CMS Max mail transport
Transactional deliveryMailgun outbound transport
Domain verified
Transactional emailMailgun + CMS MaxNative email transport
TransportMailgun
From domainVerified
PurposeSystem email
Inbound eventsNot connected
01CMS Max eventA system email is prepared
02Transport requestMailgun receives the message
03Mailbox deliveryMailgun attempts provider delivery
04FeedbackReview in Mailgun; no native event sync
What the integration does
A dedicated outbound path for messages customers expect.
Mailgun replaces the active mail transport, not the CMS Max message logic. CMS Max creates the email and Mailgun handles outbound delivery. The current integration does not register inbound Mailgun delivery, bounce, complaint, open, or click webhooks back into CMS Max.
Deliver system email
Use Mailgun as the selected CMS Max transport for operational messages produced by website, form, account, and commerce workflows.
Protect the sending identity
Verify a production domain and its required DNS records before relying on a custom Mailgun configuration.
Integration boundary
Separate message creation, transport, and delivery feedback.
Clear ownership makes transactional email incidents easier to diagnose.
| Area | Primary owner | Supported contract |
|---|---|---|
| Message trigger and content | CMS Max | Creates the system email from the relevant website, form, account, or order workflow. |
| Outbound transport | Mailgun | Accepts the message and attempts delivery through the connected Mailgun configuration. |
| Sending domain and DNS | Business / DNS owner | Verifies the domain and maintains SPF, DKIM, and other provider-required records. |
| Mailbox acceptance | Recipient provider | Applies its own authentication, reputation, policy, filtering, and mailbox rules. |
| Delivery events in CMS Max | Not connected | Current integration does not synchronize Mailgun webhooks into the CMS Max tenant. |
Connected workflow
Build a tested path from CMS Max event to recipient inbox.
Transactional delivery needs representative messages, authenticated identity, and operational ownership.
Inventory
List every system message, trigger, sender, reply-to, recipient type, template, required data, and business criticality.
Configure
Choose shared or custom Mailgun, connect the approved credentials, and set the intended website sender identity.
Authenticate
For a custom domain, publish and verify the Mailgun DNS records and protect domain and account access.
Test
Send representative form, order, account, and exception messages to major providers and inspect content, links, headers, and spam placement.
Operate
Monitor the Mailgun account, domain status, reputation, failures, credentials, billing, and CMS Max support path.
High-value applications
Use Mailgun for operational email generated by the platform.
Transactional messages should be timely, expected, and tied to a customer or administrator action.
Commerce messages
Deliver order confirmations and other configured system notifications created by the CMS Max commerce workflow.
Form notifications
Send customer confirmations or internal notifications produced by approved CMS Max forms and rules.
Account email
Support password reset and other security-sensitive messages with a tested sender and reply path.
Website operations
Route expected administrative or system messages through the selected production transport.
Governance and trust
Protect sender reputation and transactional trust.
A transport can send the message, but the business still owns authentication, recipient expectations, template quality, and incident response.
Authenticated domain
Use a verified custom domain for production when connecting a customer-managed Mailgun account and maintain its DNS records.
Credential security
Store the API secret and validation key in the CMS Max encrypted settings and rotate access under a documented process.
Transactional purpose
Keep operational messages distinct from bulk marketing and send only to recipients who reasonably expect the message.
Feedback ownership
Because provider events are not synchronized into CMS Max, assign someone to monitor Mailgun failures, suppressions, complaints, and domain health.
Search and conversion continuity
Reliable email protects the customer journeys search creates.
Search visibility has little value if a lead, account, or order journey ends with a missing confirmation or an untrusted sender.
Lead continuity
Test that high-value organic landing pages produce the intended form notifications and customer confirmations.
Order confidence
Keep order and account messages aligned with the storefront name, domain, support contacts, and linked CMS Max pages.
Useful destinations
Link email to durable HTTPS pages with current content instead of fragile attachments or temporary campaign URLs.
Brand consistency
Use a recognized sender identity, clear subject, accessible content, and a valid reply or support path.
Implementation sequence
Accept delivery before making Mailgun the active transport.
CMS Max supports one active mail transport at a time, so switchover should be deliberate and reversible.
Prepare
Choose shared or custom service, inventory messages, verify sender identity, collect credentials, and assign owners.
Authenticate
For a custom domain, add the Mailgun DNS records, wait for propagation, and confirm provider verification.
Accept
Test representative triggers, templates, links, reply behavior, inbox placement, failures, and operational monitoring.
Switch
Select Mailgun as the active CMS Max mail transport, monitor the first production messages, and retain a rollback path.
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.
Mailgun 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 email does Mailgun send for CMS Max?
When Mailgun is selected as the active transport, it delivers outbound system email generated by CMS Max workflows such as form notifications, order messages, password resets, and other configured transactional messages.
Can CMS Max provide a shared Mailgun configuration?
CMS Max supports an eligible shared configuration as well as a customer-managed Mailgun account. Confirm current plan eligibility, limits, sender identity, and support expectations during setup.
What is required for a custom Mailgun account?
The CMS Max settings include the Mailgun domain, API secret, and validation key. The Mailgun domain must also be created and verified with the DNS records required by Mailgun.
Can Mailgun, Postmark, and SMTP run at the same time?
CMS Max selects one active email transport. Switching transports should include acceptance testing and a rollback plan.
Does CMS Max receive Mailgun delivery and bounce webhooks?
No. The current integration does not register Mailgun event webhooks in the tenant, so delivery feedback and provider health must be monitored in Mailgun or through separately scoped work.
Does Mailgun replace email templates?
No. CMS Max creates the system message and its website context; Mailgun is the outbound transport. Template content, triggers, recipients, links, sender, and reply behavior must still be reviewed.
Connect with confidence
Give CMS Max transactional email a production-ready Mailgun path.
Bring the sending domain, DNS access, Mailgun account, system-message inventory, sender and reply addresses, test recipients, compliance requirements, and monitoring owner. CMS Max will configure and validate the transport.
Mailgun 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.