Set the connection
Provide the approved SMTP host, port, encryption mode, username, and password for the active CMS Max tenant.
Transactional email / Native customer-managed transport
Use Your SMTP Provider for CMS Max Email
Connect an organization-managed mail service while CMS Max continues to create the website, form, account, and commerce messages.
The CMS Max SMTP integration configures the active outbound transport with host, port, encryption mode, username, and encrypted password. The customer-managed SMTP service handles relay and delivery; provider-specific analytics or feedback are not synchronized into CMS Max.
- Custom host and port
- TLS, SSL, or approved no-encryption mode
- Encrypted password storage
- One active CMS Max mail transport
Customer-managed deliverySMTP outbound transport
Connection tested
Transactional emailSMTP + CMS MaxNative customer-managed transport
TransportSMTP
EncryptionTLS
PurposeSystem email
Provider eventsNot connected
01CMS Max eventA system message is created
02SMTP relayThe configured server accepts it
03Mailbox deliveryThe provider attempts delivery
04FeedbackReview with the SMTP provider
What the integration does
Bring an existing mail relay into the CMS Max operating model.
SMTP is a standards-based transport choice for organizations with an approved provider, relay, or internal mail service. The CMS Max integration configures outbound delivery; it does not create provider-specific dashboards, webhooks, templates, suppression tools, or reputation controls.
Send platform messages
Use the configured relay for expected website, form, account, and commerce email generated by CMS Max.
Keep provider ownership
Retain the organization's selected email vendor, domain authentication, account policies, logs, quotas, and support path.
Integration boundary
Make the relay contract observable and supportable.
SMTP problems often sit between application, network, credentials, sender policy, provider quota, and recipient filtering.
| Area | Primary owner | Supported contract |
|---|---|---|
| Message trigger and content | CMS Max | Creates the system email for the relevant platform action. |
| Connection settings | CMS Max tenant | Stores the approved host, port, encryption mode, username, and encrypted password. |
| Relay, authentication, and quotas | SMTP provider | Accepts or rejects the connection and applies account, sender, rate, and policy rules. |
| Domain authentication | Business / DNS owner | Maintains SPF, DKIM, DMARC, sender authorization, and any provider-specific records. |
| Delivery feedback | Provider / operations | No provider-specific event synchronization is included in the generic SMTP integration. |
Connected workflow
Test connectivity and message quality together.
A successful SMTP login does not prove that every customer message is complete, authenticated, and accepted.
Inventory
List system messages, sender and reply identities, recipients, templates, links, attachments, volume, peaks, and business criticality.
Authorize
Confirm the SMTP service allows application relay from CMS Max with the intended sender, port, encryption, and credentials.
Configure
Add the approved connection settings, select SMTP as the active transport, and document account ownership.
Accept
Trigger representative messages and inspect authentication, headers, content, variables, links, replies, mobile layout, and mailbox placement.
Operate
Monitor provider logs, quotas, failures, credentials, domain records, security policy, and escalation ownership.
High-value applications
Use SMTP when a customer-managed relay is the right operational fit.
The transport works best when the organization already has a supported email service and a team responsible for it.
Enterprise mail service
Route CMS Max system email through an approved organization provider or relay.
Regulated operations
Use a reviewed service where account ownership, retention, security, regions, and logs fit internal requirements.
Existing vendor standard
Keep the email provider already supported by IT while CMS Max owns the application triggers and content.
Special sender policy
Use a provider configuration that supports the required domain, sender, reply path, quotas, and authentication model.
Governance and trust
Secure the connection and own the provider relationship.
Generic SMTP offers flexibility, which makes documented settings and operational accountability especially important.
Transport encryption
Use TLS or SSL when required by the provider. Any unencrypted configuration should undergo explicit security review.
Credential lifecycle
Use an application-specific account when possible, limit access, store the password encrypted, and define rotation and revocation.
Sender authentication
Align the From identity with provider authorization and maintain the required SPF, DKIM, and DMARC policy.
Provider monitoring
Assign owners for logs, bounces, complaints, quotas, outages, reputation, billing, and support escalation.
Search and conversion continuity
Keep high-intent website journeys connected after submission.
A customer who finds the right page still needs a reliable confirmation, reset, order message, or staff notification.
Lead acceptance
Test important organic landing pages from form submission through customer and staff email.
Account continuity
Protect password reset and account email with valid HTTPS links and a recognized sender.
Commerce confidence
Align order messages with the storefront identity, support path, account pages, and transaction context.
Accessible templates
Review subjects, text hierarchy, links, mobile layout, reply behavior, and fallback content.
Implementation sequence
Prove the relay under production-like conditions.
CMS Max supports one active transport, so the SMTP switch should include operational acceptance and rollback.
Prepare
Collect provider requirements, host, port, security mode, credentials, sender identities, DNS status, message inventory, and owners.
Connect
Configure SMTP and verify that the provider accepts the intended connection and sender policy.
Accept
Test representative triggers, recipient domains, templates, variables, links, replies, failures, logs, and rate behavior.
Release
Select SMTP as the active transport, monitor initial production email, document escalation, and retain an alternate plan.
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.
SMTP 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.
Which SMTP settings does CMS Max support?
The integration includes host, port, encryption mode, username, and an optional password. The password is stored in encrypted settings.
Which encryption modes are available?
The CMS Max settings support TLS, SSL, or no encryption. Use the mode and port required by the approved provider; an unencrypted connection should receive explicit security review.
What email uses the SMTP transport?
When SMTP is selected, outbound CMS Max system email such as form notifications, order messages, password resets, and other configured transactional messages uses the connection.
Can SMTP run with Mailgun or Postmark?
CMS Max selects one active email transport. Switching requires representative tests and an operational rollback path.
Does CMS Max show delivery and bounce events from my SMTP provider?
The generic SMTP integration does not include provider-specific event synchronization. Use the provider logs and monitoring, or scope a dedicated feedback integration.
Who supports SMTP delivery problems?
CMS Max can verify application configuration and message generation. The organization and SMTP provider own relay access, quotas, sender authorization, domain authentication, provider logs, mailbox acceptance, and account incidents.
Connect with confidence
Connect the SMTP service your organization is ready to operate.
Bring the provider requirements, host, port, encryption, application credentials, sender and reply identities, DNS access, message inventory, test recipients, and support owner. CMS Max will configure and validate the transport.
SMTP 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.