Summarize this blog post with: ChatGPT | Perplexity | Claude | Grok

You already know that Cloudways can host your WordPress website, WooCommerce store, or web application, but its email setup works differently from the bundled inboxes supplied by many traditional hosts. The missing distinction is whether you need a business mailbox, automated website delivery, or both. In this guide, you will learn how every Cloudways Email option works, how to configure it, and how to build a reliable sending and receiving architecture.

Freshness note: Cloudways pricing, interface labels, email limits, DNS values, and provider policies were checked against available official documentation on August 2, 2026. Verify configuration-sensitive values inside your Cloudways and email-provider dashboards before implementation.

For a wider overview of servers, applications, backups, security, and platform management, read the complete Cloudways tutorial.

Key Takeaways

• Cloudways Email refers to several mailbox and email-delivery integrations rather than one bundled email-hosting service.
• Rackspace Email provides custom-domain mailboxes for sending and receiving person-to-person business email.
• Elastic Email and custom SMTP handle automated messages such as password resets, order confirmations, invoices, and form notifications.
• Mailbox hosting and transactional email solve different problems, and many Cloudways websites need both.
• SPF, DKIM, and DMARC strengthen sender authentication and make delivery problems easier to diagnose, but they cannot guarantee inbox placement.
• Server-level SMTP settings normally affect every application on that Cloudways server unless an application-level plugin or configuration overrides the route.
• Pricing, sending limits, storage allowances, ports, and DNS records should be rechecked before implementation because providers can change them.

What Is Cloudways Email and How Does It Work?

Cloudways Email is a group of mailbox and email-delivery integrations used with websites and applications hosted on Cloudways. Cloudways separates human business correspondence from application-generated messages, allowing you to use Rackspace Email for mailboxes and Elastic Email or custom SMTP for automated outgoing email.

Cloudways does not operate a conventional mailbox server as part of its standard hosting infrastructure. Instead, the platform connects your website and domain to specialized providers that handle receiving, storing, sending, authenticating, and tracking email. ailbox Email?

Mailbox email is person-to-person communication sent and received through an inbox such as support@example.com. Employees, customers, suppliers, and clients use these addresses for conversations that require replies, folders, contacts, search, and message storage.

For example, a five-person company may create:

• sales@example.com
• support@example.com
• accounts@example.com
• john@example.com
• sarah@example.com

Rackspace Email, Google Workspace, Microsoft 365, Zoho Mail, Fastmail, and Proton Mail belong to the mailbox-provider category.

What Is Transactional Email?

Transactional email is an automated message triggered by an action inside a website or application. Typical examples include WooCommerce order confirmations, WordPress password resets, SaaS login codes, invoices, shipping updates, contact-form notifications, and account alerts.

Transactional email usually needs:

• Authenticated SMTP or an email API
• Verified sending domains
• Bounce and complaint handling
• Delivery logs
• Stable sender reputation
• Volume-appropriate limits
• SPF and DKIM authentication

Elastic Email, Amazon Simple Email Service, Postmark, Mailgun, SendGrid, Brevo, and SMTP2GO belong primarily to the transactional-delivery category.

The Recommended Two-Layer Architecture

A complete Cloudways email setup may use one provider for employee mailboxes and a separate transactional provider for website-generated messages. This separation prevents customer conversations from sharing the same infrastructure, limits, and sender reputation as automated website traffic.

For example:

Domain: example.com

Incoming business email
Customer → Rackspace/Google Workspace MX servers → support@example.com

Outgoing business email
Employee mailbox → Rackspace/Google Workspace SMTP → Customer

Automated website email
WooCommerce → Elastic Email/Postmark SMTP → Order customer

Authentication and monitoring
SPF + DKIM + DMARC + provider logs

[Insert image: Custom architecture diagram showing Cloudways hosting connected separately to a mailbox provider and a transactional email provider | Alt text: “Map Cloudways Email mailbox and transactional architecture”]

Why Does Choosing the Correct Cloudways Email Setup Matter?

Choosing the correct Cloudways Email setup matters because mailbox communication and automated application email have different technical requirements, sending patterns, limits, and failure risks. Combining both functions without a deliberate architecture can cause missing orders, failed password resets, DNS conflicts, spam placement, blocked messages, and difficult troubleshooting.

A business mailbox is optimized for interactive communication. Transactional infrastructure is optimized for repeatable automated delivery, authentication, logging, bounce analysis, and potentially higher volume.

For example, a WooCommerce store may send hundreds of order, refund, password-reset, and shipping messages during a promotion. Sending that traffic through an employee’s ordinary mailbox can trigger limits or damage the reputation used for important customer replies.

Problems Caused by the Wrong Email Route

An unsuitable configuration can cause:

• WooCommerce order notifications to disappear
• Password-reset emails to fail
• Contact Form 7 notifications to enter spam
• Replies to reach an unmonitored address
• Duplicate or conflicting SPF records
• DKIM verification failures
• SMTP authentication errors
• Mailbox rate limits
• Unexplained bounces
• PHP mail dependency
• Automated traffic mixed with employee correspondence
• Applications on the same server using an unintended provider

Why Direct PHP Mail Is Often Unreliable

PHP mail sends messages through the server’s local mail function without providing the specialized authentication, reputation management, and diagnostic tooling offered by a dedicated delivery provider. Cloudways recommends using a transactional email service instead of dispatching important application email directly from the cloud server. a WordPress site may report that wp_mail() completed successfully even though the destination provider later rejected or filtered the message. An SMTP provider’s log can reveal whether the message was authenticated, accepted, deferred, bounced, or blocked.

Does Cloudways Include Email Hosting With Its Hosting Plans?

Cloudways hosting plans do not include conventional email inboxes on the web server. Cloudways supports email through paid mailbox add-ons and external transactional integrations, but customers must deliberately add Rackspace Email, connect another mailbox provider, or configure Elastic Email or custom SMTP. on is important:

• Not included: You do not automatically receive mailboxes with a standard Cloudways server.
• Supported: You can connect specialized mailbox and outgoing-delivery providers.
• Separately billed: Mailbox licenses and transactional volume may create additional charges.
• Separately configured: DNS, domain authentication, and client settings require setup.

This difference is one of the costs to evaluate alongside server resources, backups, bandwidth, security add-ons, and support. The Cloudways pricing and additional costs guide explains how optional services affect total ownership cost.

For an overall assessment of the platform’s advantages, limitations, performance, and suitability, read the full Cloudways review.

What Is the Difference Between Cloudways Rackspace Email, Elastic Email, and Custom SMTP?

Rackspace Email provides inboxes, while Elastic Email and custom SMTP primarily deliver automated outgoing messages from Cloudways applications. Google Workspace, Microsoft 365, Zoho Mail, and similar services can replace Rackspace when an organization needs mailboxes plus calendars, meetings, documents, identity controls, or collaboration features. imary purpose | Sends email | Receives email | Best for | Main limitation |
|—|—|—:|—:|—|—|
| Rackspace Email | Business mailbox | Yes | Yes | Person-to-person custom-domain email | Not designed for high-volume automated traffic |
| Elastic Email | Transactional delivery | Yes | No conventional inbox | WordPress, WooCommerce, Magento, Laravel, and web applications | Requires server binding and domain verification |
| Custom SMTP | External delivery provider | Yes | Depends on provider | Businesses already using Gmail SMTP, Postmark, Mailgun, SendGrid, or another gateway | Provider pricing, limits, and authentication rules apply |
| Google Workspace | Mailbox and productivity suite | Yes | Yes | Teams needing Gmail, Drive, Calendar, Meet, and administration | Higher per-user cost than a basic mailbox |
| Microsoft 365 | Mailbox and productivity suite | Yes | Yes | Microsoft-centric organizations | External licensing and administration |
| Zoho Mail | Hosted business mailbox | Yes | Yes | Cost-conscious organizations | Advanced collaboration features depend on the plan |

“You can only use one transactional email add-on per server—either Elastic Email or SMTP.”

— Syed Abuzar Mehdi, Cloudways Help Center author, Which Email Add-on Should I Use?, 2025

This server-level rule means all applications using the default server mail route share the selected transactional provider. An application-level plugin such as WP Mail SMTP can create a separate route for an individual WordPress installation when different behavior is necessary. se Rackspace Email and Elastic Email Together?

Rackspace Email and Elastic Email can be used together because they perform different functions. Rackspace can receive customer replies and employee correspondence, while Elastic Email delivers automated messages generated by WordPress, WooCommerce, Magento, Laravel, or another application.

For example:

• support@example.com can be a Rackspace mailbox.
• WooCommerce can send from orders@example.com through Elastic Email.
• Replies can be directed to support@example.com.
• SPF can authorize both Rackspace and Elastic Email in one consolidated record.
• DMARC can monitor whether the visible From domain aligns correctly.

→ Explore Elastic Email Delivery

Which Cloudways Email Option Should You Choose?

The correct Cloudways Email option depends first on whether you need to receive messages and second on whether your website sends automated messages. Choose a mailbox provider for incoming correspondence, a transactional provider for application-generated email, and both systems when the business needs reliable human communication and automated delivery.

Simple Cloudways Email Decision Tree

Do you need to receive email at your domain?
│
├── Yes → Choose Rackspace Email, Google Workspace,
│         Microsoft 365, Zoho Mail, Fastmail, or Proton Mail.
│
└── No → A mailbox may not be necessary.

Will your website or application send automated messages?
│
├── Yes → Configure Elastic Email or custom SMTP.
│
└── No → A transactional provider may not be necessary.

Do you need both business correspondence and automated email?
│
└── Yes → Use a mailbox provider plus a transactional provider.

Use-Case Recommendation Matrix

Agencies should document ownership, DNS access, sender domains, credentials, billing responsibility, and handover procedures for each client. The Cloudways for agencies guide expands this operational model.

Primary Recommendations by Requirement

Choose Rackspace Email for Cloudways mailboxes when you need affordable addresses that send and receive person-to-person mail.

Choose Elastic Email for Cloudways transactional delivery when a website or application must send automated messages through Cloudways-managed integration.

Choose custom SMTP when you already use a provider with specific APIs, analytics, templates, compliance controls, dedicated IP options, or regional infrastructure.

Choose Google Workspace for business collaboration or Microsoft 365 for Microsoft-based teams when mailboxes are part of a broader productivity and identity-management requirement.

Cloudways customers evaluating the hosting platform itself can compare current Cloudways plans before adding mailbox and transactional-email costs.

→ Evaluate Cloudways Email Options

How Do You Set Up Rackspace Email on Cloudways?

Rackspace Email is set up by activating the add-on in Cloudways, creating a mailbox, publishing the required DNS records, waiting for propagation, and testing incoming and outgoing delivery. The add-on currently costs $1 per mailbox per month and provides a fixed 25GB mailbox according to Cloudways documentation verified on August 2, 2026. ecord Your Current Email DNS

Before changing anything, document:

• Existing MX records
• Current SPF TXT record
• DKIM selectors
• DMARC policy
• Autodiscover records
• Verification CNAME or TXT records
• Current TTL values
• Existing mailbox provider
• Current forwarding and aliases

This record creates a rollback path if incoming email stops after the migration.

Step 2: Activate Rackspace Email

1. Sign in to the Cloudways Platform.
2. Open Integrations.
3. Select Rackspace Email or open View All.
4. Navigate to Mailboxes.
5. Select Add Mailbox.
6. Enter the custom-domain email address.
7. Create a strong, unique password.
8. Save the mailbox.

Cloudways allows multiple mailboxes to be added from the Rackspace Email interface. : Cloudways Integrations screen with Rackspace Email selected and the Add Mailbox button visible | Alt text: “Activate Cloudways Rackspace Email mailbox”]

Step 3: Add the Rackspace MX and SPF Records

Use the lowest practical TTL during a planned migration. Restore a normal TTL after the new route has been tested.

Do not replace an existing SPF record with a second SPF record. Merge every authorized sender into one valid SPF policy, as explained later in this guide.

[Insert image: DNS provider panel showing the two Rackspace MX records, consolidated SPF record, and autodiscover CNAME | Alt text: “Configure Cloudways Rackspace Email DNS records”]

Step 4: Wait for DNS Propagation

DNS changes may take time to become visible across recursive resolvers. Cloudways notes that propagation can take 24–48 hours, although many changes appear sooner depending on previous TTL values and resolver caching. the old mailbox provider immediately. Keep the previous service active until:

• New MX records are visible globally
• Incoming mail reaches the new mailbox
• Outgoing mail passes authentication
• Historical messages have been migrated
• All employee devices are configured
• The rollback window has closed

Step 5: Access Rackspace Webmail

Rackspace webmail provides browser-based access using the full mailbox address and password. The current Rackspace login page presents fields for the email address and password. : Rackspace Webmail login screen with the email-address and password fields highlighted | Alt text: “Access Cloudways Rackspace webmail login”]

Step 6: Send and Receive Test Messages

Test both directions:

1. Send from Rackspace to Gmail.
2. Reply from Gmail to Rackspace.
3. Send from Rackspace to Outlook.
4. Reply from Outlook to Rackspace.
5. Inspect the received message headers.
6. Confirm SPF, DKIM, and DMARC results.
7. Verify the visible From, Reply-To, and Return-Path values.
8. Test attachments.
9. Test aliases and forwarding.
10. Confirm messages appear on all synchronized devices.

Step 7: Create Aliases and Forwarding Rules

An alias is an additional address that delivers to an existing mailbox without creating another paid inbox. For example, hello@example.com and contact@example.com can both deliver to owner@example.com.

Cloudways states that aliases do not create an additional charge and permits multiple aliases under the same domain. Cloudways also documents forwarding to up to four addresses through its Rackspace add-on interface. umentation states that the Rackspace catch-all feature reached end-of-life and should not be recommended for new configurations. Use explicit mailboxes and aliases instead. lan Mailbox Migration

Watch: Set Up and Manage Rackspace Email on Cloudways

This official Cloudways walkthrough demonstrates how to create a Rackspace mailbox and configure aliases and email forwarding from the Cloudways Platform.

Video: “How to Set Up Rackspace Email Add-On on Cloudways” by Cloudways.

Cloudways currently documents an assisted migration charge of $10 per mailbox. Confirm availability, scope, eligibility, and current pricing before relying on the service. tion process is:

1. Lower DNS TTL before the migration.
2. Export or back up old messages.
3. Create new mailboxes.
4. Copy historical email.
5. Add accounts to employee devices.
6. Change MX records.
7. Test both providers during the transition.
8. Keep the old service active temporarily.
9. Document final settings.
10. Remove the old service only after validation.

How Do You Configure Elastic Email on Cloudways?

Elastic Email is configured by subscribing to a Cloudways package, binding the package to the correct server, verifying every sending domain through DNS, setting the application’s From address, sending test messages, and reviewing delivery logs. Cloudways states that both server binding and domain verification are mandatory. astic email to your server & Verifying your domain is mandatory.”

— Syed Abuzar Mehdi, Cloudways Help Center author, How to Activate the Elastic Email Add-on, 2026

The requirement prevents an application from sending through the integration before Cloudways and Elastic Email can associate the server with a verified domain. It also reduces sender-domain mismatches that commonly produce failed authentication or spam placement. ctivate an Elastic Email Package

1. Sign in to Cloudways.
2. Open Integrations.
3. Select View All.
4. Choose Elastic Email.
5. Select a package based on expected monthly volume.
6. Subscribe to the package.

Cloudways currently advertises Elastic Email from $0.10 per 1,000 emails, but the complete package structure, overages, permitted content, and billing rules should be verified inside the platform before purchase. : Cloudways Elastic Email package-selection interface showing volume choices and subscription controls | Alt text: “Select Cloudways Elastic Email package”]

Step 2: Bind Elastic Email to the Correct Server

1. Open Servers.
2. Select the target server.
3. Open SMTP under Server Management.
4. Select Elastic Email.
5. Choose Enable.

Cloudways states that one Elastic Email package can be bound to multiple Cloudways servers. Once enabled at the server level, applications using the default server mail route do not require separate activation. nce also creates an operational risk. An agency must verify that the correct domains, servers, and client applications are connected to the intended package.

[Insert image: Cloudways Server Management SMTP screen with Elastic Email selected | Alt text: “Bind Elastic Email to Cloudways server”]

Watch: Configure Elastic Email and Verify Your Sending Domain

This walkthrough demonstrates how to activate Elastic Email, bind it to a Cloudways server, publish the required authentication records, and connect WordPress email delivery. Start around 04:10 for the Elastic Email configuration process.

Video: “How to setup Emails on Cloudways using Elastic Email + Rackspace + WordPress | Cloudways Tutorial” by Hamza – GoTechUG.

Step 3: Verify the Sending Domain

Cloudways’ current workflow requires domain-verification records that can include:

• SPF TXT record
• DKIM TXT record
• Tracking CNAME
• DMARC TXT record
• Provider-specific ownership records

Copy the exact values from the Cloudways dashboard. Do not reuse DKIM keys or tracking values from another domain or tutorial.

Cloudways currently documents the Elastic Email SPF authorization as include:_spf.elasticemail.com, but that mechanism must be merged into an existing SPF record rather than published as a second independent policy. re manages DNS, Cloudways instructs users to disable proxying for the Elastic Email tracking CNAME. Mail-related records should follow provider instructions rather than being indiscriminately proxied. : Cloudways Elastic Email domain-verification screen showing SPF, DKIM, tracking, and DMARC status indicators | Alt text: “Verify Cloudways Elastic Email sending domain”]

Step 4: Configure the Sender Address

The application’s visible From address should use a verified domain. For example:

From Name: Example Store
From Email: orders@example.com
Reply-To: support@example.com

Avoid sending through Elastic Email with a public Gmail or Yahoo address as the visible From address. Cloudways’ WP Mail SMTP guidance requires a verified custom domain for Elastic Email configurations. onnect WordPress or WooCommerce

Cloudways supports Elastic Email through the server-level route, but a WordPress SMTP plugin can improve application-level control over the From address, mailer settings, email logs, and testing.

A typical workflow is:

1. Install WP Mail SMTP.
2. Open the plugin’s mailer settings.
3. Select the appropriate Elastic Email or SMTP configuration.
4. Enter the verified From email.
5. Force the From address only when necessary.
6. Configure the From name.
7. Save the configuration.
8. Send a test message.
9. Inspect the provider log.
10. Test real WooCommerce events.

The dedicated WordPress SMTP configuration guide provides a reusable application-level workflow.

You can also consider WP Mail SMTP for WordPress email routing when you need application-specific configuration, mail logs, or a provider integration.

[Insert image: WP Mail SMTP settings screen showing the mailer, From email, From name, and test-email controls | Alt text: “Configure Cloudways WordPress email with WP Mail SMTP”]

Step 6: Test the SMTP Configuration

Cloudways allows an Elastic Email test from:

Servers → Selected Server → SMTP → Send Test Email

Use:

• A sender address on a verified domain
• A destination address you control
• Gmail, Outlook, and Yahoo test recipients
• A real application event after the basic test

Cloudways currently documents ports 587 and 2525 for application SMTP connections in its Elastic Email setup guide. Verify the current credentials, encryption mode, and port inside your dashboard. eview Elastic Email Logs

Cloudways documents downloadable Elastic Email activity logs covering the previous seven days. Statuses can include queued, retrying, sent, opened, clicked, or other provider-defined events. sent* generally means the next receiving server accepted the message. It does not prove that the message appeared in the recipient’s inbox rather than spam, quarantine, or another folder.

[Insert image: Cloudways Elastic Email log export or provider activity screen showing message status, recipient, and response | Alt text: “Review Cloudways Elastic Email delivery logs”]

How Do You Set Up a Custom SMTP Provider on Cloudways?

A custom SMTP provider is configured by entering the provider’s SMTP host, port, encryption method, username, password or API credential, and verified sender address in the Cloudways server SMTP panel. Cloudways supports providers such as Gmail, SendGrid, Mailgun, Mandrill, and other external SMTP gateways. TP Information You Need

Collect these values from your provider:

Never publish SMTP passwords, API keys, screenshots containing credentials, or complete DNS private keys.

Cloudways Custom SMTP Setup Steps

1. Sign in to Cloudways.
2. Open Servers.
3. Select the target server.
4. Open SMTP.
5. Select Your Own SMTP.
6. Choose the provider or select Other.
7. Enter the SMTP host.
8. Enter the port.
9. Enter the username.
10. Enter the password or API credential.
11. Save the settings.
12. Select Send Test Email.
13. Test a real application event.

Cloudways states that outgoing messages from applications using that server route will be delivered through the selected SMTP gateway. : Cloudways custom SMTP form showing provider, host, port, username, and test-email button with credentials hidden | Alt text: “Configure custom SMTP on Cloudways server”]

Watch: Configure a Custom SMTP Provider on Cloudways

This official Cloudways tutorial shows where to enter your SMTP provider details, how to activate the server-level connection, and how to confirm the configuration with a test email.

Video: “How to Set Up Custom SMTP on Cloudways” by Cloudways.

When Gmail SMTP Is Appropriate

Gmail SMTP is most appropriate for low-volume, non-critical application email where the account’s sending limits and acceptable-use policies are sufficient. Google authentication policies and sending limits vary by account type and connection method, so current limits should be verified directly in Google documentation.

Cloudways’ own documentation contains differing Gmail volume descriptions across articles. Treat the Cloudways figures as implementation guidance rather than a universal Google sending-limit guarantee. -critical WooCommerce store, a dedicated transactional provider usually offers clearer event logs, bounce processing, complaint monitoring, and volume controls than a personal Gmail account.

When an API-Capable Provider Is Better

An SMTP provider with an email API may be better when you need:

• Template management
• Webhooks
• Bounce events
• Complaint events
• Suppression lists
• Per-message metadata
• Delivery analytics
• Regional endpoints
• Dedicated IP options
• Message streams
• Application-specific credentials

The Cloudways Laravel hosting guide can show how application frameworks manage environment variables, queues, mail drivers, and API credentials.

The Cloudways API guide is also useful for agencies or developers planning automated provisioning and operational workflows.

Which DNS Records Are Required for Cloudways Email?

Cloudways Email can require MX, SPF, DKIM, DMARC, CNAME, and provider-verification records depending on the selected mailbox and transactional providers. MX controls incoming routing, while SPF, DKIM, and DMARC help receiving systems evaluate whether outgoing messages are authorized and aligned with the visible sender domain.

What Does an MX Record Do?

An MX record identifies the mail servers responsible for receiving email addressed to a domain. Changing website hosting does not automatically require changing MX records.

For example, you can move a WordPress site to Cloudways while keeping Google Workspace mailboxes. The website A record changes, but the Google Workspace MX records remain intact.

What Does an SPF Record Do?

An SPF record publishes which systems are authorized to use a domain in the SMTP envelope identity. SPF does not authenticate the visible From address by itself, and forwarding can complicate SPF evaluation.

A domain should publish one SPF policy for each owner name.

“Multiple SPF records are not permitted for the same owner name.”

— Scott Kitterman, RFC 7208 author, Internet Engineering Task Force, 2014

RFC 7208 states that multiple SPF records can make the policy impossible to interpret correctly. Authorized providers should be combined into a single syntactically valid policy instead of being published as separate v=spf1 records. t SPF Configuration

TXT @ "v=spf1 include:emailsrvr.com ~all"
TXT @ "v=spf1 include:_spf.elasticemail.com ~all"

Consolidated SPF Example

TXT @ "v=spf1 include:emailsrvr.com include:_spf.elasticemail.com ~all"

The consolidated example authorizes both Rackspace and Elastic Email. The exact mechanisms and final qualifier should reflect your actual providers and policy, not a copied template.

What Does DKIM Do?

DKIM adds a cryptographic signature that allows a receiving system to verify that an authorized domain signed the message and that signed content was not altered in transit.

Each provider may use a different selector, such as:

selector1._domainkey.example.com
api._domainkey.example.com
google._domainkey.example.com

Multiple DKIM selectors can coexist because they use different DNS names. Copy the complete selector and public key from the provider dashboard.

What Does DMARC Do?

DMARC is an email authentication, policy, and reporting protocol that evaluates alignment between the visible From domain and authenticated SPF or DKIM identities. DMARC can request aggregate reports and tell receiving systems how the domain owner prefers failed messages to be handled. me the current IETF DMARC specification in 2026 and obsoleted RFC 7489 and RFC 9091. ployment sequence is:

1. Publish p=none.
2. Collect and analyze aggregate reports.
3. Identify every legitimate sender.
4. Fix SPF, DKIM, and alignment failures.
5. Move to a limited quarantine policy.
6. Increase enforcement gradually.
7. Use p=reject only after legitimate traffic is understood.

Authentication Does Not Guarantee Inbox Placement

SPF, DKIM, and DMARC improve authentication conditions, but they do not guarantee inbox placement. Recipient filtering can also evaluate content, sending history, complaint rates, bounce rates, engagement, URLs, attachments, message volume, and IP or domain reputation. ed Dual-Provider DNS Architecture

A domain using Rackspace for mailboxes and Elastic Email for website delivery may need:

MX:
mx1.emailsrvr.com
mx2.emailsrvr.com

SPF:
v=spf1 include:emailsrvr.com include:_spf.elasticemail.com ~all

DKIM:
Rackspace DKIM selector supplied by provider
Elastic Email DKIM selector supplied by provider

DMARC:
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

Tracking:
Provider-specific CNAME

This example is architectural, not a substitute for the current records generated by your providers.

[Insert image: Cloudflare DNS screen showing MX, one consolidated SPF record, separate DKIM selectors, DMARC, and DNS-only email records | Alt text: “Audit Cloudways Email DNS authentication records”]

How Do You Connect Cloudways Email to Gmail, Outlook, and Mobile Devices?

Cloudways Rackspace Email connects to email clients through secure IMAP for incoming synchronization and authenticated SMTP for outgoing messages. Cloudways currently documents secure.emailsrvr.com for both services, with IMAP over SSL on port 993 and SMTP over SSL on port 465. Email Client Settings

Configuration-sensitive values should be rechecked against current Cloudways and Rackspace documentation before deployment.

How Do You Use Cloudways Rackspace Email With Gmail?

Gmail can still be used to send as a Rackspace address through authenticated SMTP, but Gmail’s browser-based third-party POP fetching is being withdrawn. Google’s 2026 guidance states that Gmail will no longer fetch third-party email through the “Check mail from other accounts” POP feature. a freshness conflict with Cloudways’ August 2025 article, which still documents POP retrieval from Rackspace into Gmail. Follow Google’s newer policy rather than relying on the older POP workflow. ical options include:

• Use Gmail’s Send mail as feature for outgoing Rackspace SMTP, where still supported.
• Forward Rackspace mail to Gmail, after evaluating forwarding and authentication behavior.
• Add the Rackspace account to the Gmail mobile app using IMAP.
• Use Outlook, Apple Mail, Thunderbird, or another full IMAP client.
• Move the mailbox itself to Google Workspace when the Gmail web interface is a core requirement.

[Insert image: Gmail Accounts and Import screen showing the Send mail as configuration for a Rackspace address | Alt text: “Send Cloudways Rackspace Email through Gmail SMTP”]

How Do You Configure Microsoft Outlook?

1. Open Outlook’s account settings.
2. Add a new account.
3. Choose manual IMAP configuration when needed.
4. Enter the full Rackspace mailbox address.
5. Use secure.emailsrvr.com for incoming and outgoing servers.
6. Set IMAP port 993 with SSL/TLS.
7. Set SMTP port 465 with SSL/TLS.
8. Enable outgoing-server authentication.
9. Use the same credentials as the incoming server.
10. Run Outlook’s connection test.

Cloudways documents this IMAP and SMTP workflow for Outlook. : Microsoft Outlook advanced account settings showing Rackspace IMAP and SMTP ports | Alt text: “Configure Cloudways Rackspace Email in Outlook”]

How Do You Configure Apple Mail and iPhone?

Add a new Other Mail Account and enter:

• Name
• Full email address
• Mailbox password
• IMAP host
• SMTP host
• Full username for both services

Cloudways documents secure IMAP and SMTP configuration for iOS Mail using the Rackspace servers. : iPhone Add Mail Account screen showing Rackspace incoming and outgoing server fields | Alt text: “Add Cloudways Rackspace Email to iPhone”]

How Do You Configure Thunderbird?

Thunderbird can use:

• IMAP hostname: secure.emailsrvr.com
• IMAP port: 993
• IMAP security: SSL/TLS
• SMTP hostname: secure.emailsrvr.com
• SMTP port: 465
• SMTP security: SSL/TLS
• Username: Full mailbox address

Cloudways documents manual configuration and connection testing for Thunderbird. : Thunderbird manual configuration window showing Rackspace IMAP and SMTP values | Alt text: “Connect Cloudways Rackspace Email to Thunderbird”]

IMAP Versus POP Retrieval

IMAP synchronizes mailbox state across devices, while POP traditionally downloads messages into another client or account. IMAP is generally better for users who need folders, read status, sent messages, and deletions synchronized across several devices.

Periodic POP fetching is not real-time synchronization. Even before Google began withdrawing the Gmail web POP feature, Rackspace messages could arrive late because Gmail checked the external mailbox periodically rather than receiving an immediate synchronized update.

How Do You Test Cloudways Email Deliverability?

Cloudways Email deliverability should be tested across several recipient providers, real application events, authentication results, message headers, provider logs, bounces, replies, and inbox placement. One successful test message cannot prove that every template, recipient domain, traffic pattern, or application event will deliver reliably.

Repeatable Deliverability Test Checklist

1. Send to Gmail.
2. Send to Outlook or Hotmail.
3. Send to Yahoo.
4. Check inbox, promotions, junk, and quarantine.
5. Inspect the complete message headers.
6. Confirm SPF result.
7. Confirm DKIM result.
8. Confirm DMARC result and alignment.
9. Check the envelope-from domain.
10. Check the visible From address.
11. Check the Reply-To address.
12. Trigger a WordPress password reset.
13. Submit every contact form.
14. Place a WooCommerce test order.
15. Trigger an order-status change.
16. Test an invoice or account alert.
17. Review provider logs.
18. Investigate hard and soft bounces.
19. Reply to the message.
20. Confirm that replies reach a monitored mailbox.

Deliverability Verification Worksheet

Tools for Testing Cloudways Email

MXToolbox

MXToolbox can inspect MX records, SPF syntax, DKIM selectors, DMARC records, DNS propagation, and blocklist status.

[Insert image: MXToolbox lookup result showing MX, SPF, DKIM, and DMARC checks for a Cloudways-hosted domain | Alt text: “Check Cloudways Email DNS with MXToolbox”]

Google Admin Toolbox CheckMX

Google Admin Toolbox CheckMX can identify mail-routing and DNS configuration issues that may affect delivery to Google-managed recipients.

[Insert image: Google Admin Toolbox CheckMX results showing mail exchanger and authentication findings | Alt text: “Validate Cloudways Email routing with Google CheckMX”]

Mail-Tester

Mail-Tester sends a generated test address and evaluates authentication, content, headers, and several technical signals. Treat the score as a diagnostic aid, not an inbox-placement guarantee.

[Insert image: Mail-Tester report showing SPF, DKIM, DMARC, and message-content checks | Alt text: “Test Cloudways Email authentication with Mail-Tester”]

GlockApps

GlockApps can run seed-list tests across multiple mailbox providers and show where messages were placed.

Consider GlockApps email deliverability testing when you need broader placement testing than a few manually controlled inboxes.

[Insert image: GlockApps inbox-placement report comparing Gmail, Outlook, and Yahoo results | Alt text: “Compare Cloudways Email inbox placement with GlockApps”]

DMARC Analyzer

A DMARC reporting platform can aggregate XML reports and show which systems send using your domain.

Consider DMARC Analyzer for authentication monitoring when manual XML review is impractical.

[Insert image: DMARC Analyzer dashboard showing aligned, failed, and unknown sending sources | Alt text: “Monitor Cloudways Email DMARC alignment”]

WordPress Email Logging

An email-log plugin can confirm that WordPress generated a message and show headers or errors before the message reaches the external SMTP provider.

Application logs answer: Did WordPress create the email?

Provider logs answer: Did the delivery service accept and process the email?

Recipient headers answer: How did the receiving system authenticate and handle the email?

[Insert image: WordPress email-log screen showing a WooCommerce order email and delivery status | Alt text: “Trace Cloudways WordPress email delivery events”]

Why Are WordPress and WooCommerce Emails Not Sending From Cloudways?

WordPress and WooCommerce emails usually fail on Cloudways because the site lacks an authenticated SMTP route, uses incorrect credentials, sends from an unverified domain, has conflicting DNS records, or routes email through the wrong server-level provider. The correct diagnosis starts by identifying where the message journey stops.

Symptom-to-Cause Troubleshooting Table

Why Are WordPress Emails Not Sending?

Check the following sequence:

1. Confirm WordPress generated the email.
2. Run the SMTP plugin’s test.
3. Confirm the server-level Cloudways SMTP selection.
4. Verify host, port, and encryption.
5. Re-enter the SMTP username and credential.
6. Confirm the From domain is verified.
7. Inspect SPF and DKIM.
8. Review the provider log.
9. Check suppression and bounce lists.
10. Test another recipient provider.

Why Are WooCommerce Order Emails Missing?

WooCommerce email problems can exist inside WooCommerce even when SMTP is working.

Check:

• Whether the notification is enabled
• The configured recipient
• The order status that triggers the template
• Whether the order changed to the expected status
• Whether a plugin overrides the template
• Whether scheduled actions are delayed
• Whether the customer address is valid
• Whether the provider suppressed the recipient
• Whether the message entered spam

The Cloudways WooCommerce hosting guide explains the wider hosting and store environment around checkout, cron, caching, and transaction workflows.

Why Are Contact Form 7 Messages Missing?

A contact form may display a success confirmation after WordPress processes the form, even when the notification later fails.

Verify:

• The To address
• The From address
• The Reply-To header
• The sender domain
• SMTP routing
• Spam protection
• Plugin conflicts
• Provider logs
• Mailbox filters
• DMARC alignment

Use a From address on your own authenticated domain. Put the visitor’s email address in Reply-To rather than using the visitor’s unverified address as the visible From sender.

Why Does SMTP Authentication Fail?

SMTP authentication can fail because of:

• Incorrect username
• Normal password used instead of an app password
• Expired API credential
• Regenerated key
• Wrong port
• Wrong encryption mode
• Disabled SMTP access
• Provider account suspension
• Unverified sender
• Unauthorized server IP
• Copied whitespace
• Incorrect credential scope

Do not repeatedly retry a failing credential without reviewing the provider response. Repeated attempts can trigger security controls or temporary blocking.

Why Does Cloudflare Cause Verification Problems?

Cloudflare can cause email-related problems when provider verification or tracking CNAME records are proxied despite requiring direct DNS resolution. Cloudways explicitly instructs users to disable the orange proxy for the Elastic Email tracking record. nnot be proxied. Mail hostnames and verification records should follow the email provider’s exact DNS guidance.

How Much Does Cloudways Email Cost?

Cloudways Email cost is the combined price of mailbox licenses, transactional volume, migration, productivity-suite licenses, testing, retention, security, and management time. Comparing only the advertised mailbox rate can underestimate the real annual cost of operating and supporting business and application email.

Current Cloudways-Specific Pricing

Cloudways advertised the following on August 2, 2026:

• Rackspace Email: $1 per mailbox per month
• Rackspace storage: 25GB per mailbox
• Rackspace assisted migration: $10 per mailbox, according to Cloudways support documentation
• Elastic Email: Advertised from $0.10 per 1,000 emails

Pricing, billing increments, allowances, overages, content restrictions, taxes, and package availability can change. t Formula

Monthly email cost =
Mailbox licenses
+ Transactional email package
+ Overage charges
+ Productivity-suite licenses
+ Archiving or backup
+ Deliverability tools
+ Security or compliance services
+ Migration amortization
+ Agency management time
+ Applicable taxes

Example Cost Scenarios

The following examples use Cloudways’ published $1 Rackspace mailbox rate and represent planning estimates rather than provider quotations.

Annual mailbox-only examples:

• One mailbox: $12 per year
• Five mailboxes: $60 per year
• Two store mailboxes: $24 per year
• Twenty agency mailboxes: $240 per year

These totals exclude transactional delivery, migration, testing, taxes, archiving, and management.

For a fuller ownership model, compare the email layer with Cloudways pricing and additional costs.

→ Compare Cloudways Email Plans

What Are the Best Cloudways Email Alternatives?

The best Cloudways Email alternative depends on whether you need mailboxes, collaboration tools, privacy-focused communication, low-cost transactional delivery, developer APIs, or combined marketing and transactional workflows. Mailbox providers and transactional delivery services are different categories and should not be treated as interchangeable products.

When Should You Keep Rackspace Email?

Keep Rackspace when:

• You need straightforward domain mailboxes.
• Collaboration-suite features are unnecessary.
• The $1 Cloudways rate remains available.
• IMAP and webmail meet your needs.
• Existing aliases and forwarding are sufficient.
• You prefer billing through Cloudways.

When Should You Move to Google Workspace?

Move to Google Workspace when:

• Gmail web access is central to your workflow.
• You need shared calendars and Drive.
• You need stronger organization-level administration.
• You need Google Meet and collaborative documents.
• Gmail’s withdrawal of third-party POP fetching makes a connected external mailbox impractical.

When Should You Use Microsoft 365?

Use Microsoft 365 when:

• Outlook is the preferred client.
• Teams and Office applications are already standardized.
• Microsoft identity and device administration matter.
• Shared mailboxes and Microsoft collaboration workflows are required.

When Should You Use a Dedicated Transactional Provider?

Use Postmark, Amazon SES, Mailgun, SendGrid, Brevo, SMTP2GO, or another dedicated service when:

• Email is revenue-critical.
• You need message-level logs.
• You need bounce and complaint webhooks.
• You need API integration.
• You need suppression management.
• You need provider-specific templates.
• You need application-separated credentials.
• Your volume exceeds the practical limits of a mailbox account.

For hosting-platform options beyond Cloudways, compare the best Cloudways alternatives.

Does Migrating a Website to Cloudways Affect Existing Email?

Migrating a website to Cloudways does not require moving existing email when the current MX and authentication records remain correct. Website hosting and email hosting can stay with different providers, but careless DNS replacement during migration can remove MX, SPF, DKIM, DMARC, autodiscover, or verification records.

Safe Cloudways Email Migration Checklist

Before migration:

1. Export the complete DNS zone.
2. Record all MX records.
3. Record the complete SPF policy.
4. Record every DKIM selector.
5. Record the DMARC policy.
6. Record mail-related CNAME records.
7. Record current TTL values.
8. Confirm the existing mailbox provider.
9. Confirm where DNS is hosted.
10. Create a rollback document.

During migration:

1. Change only the records required for the website.
2. Preserve existing MX records.
3. Preserve email authentication records.
4. Verify nameserver changes do not replace the entire zone.
5. Test incoming mail before and after the change.
6. Test transactional messages.
7. Review propagation from several locations.

After migration:

1. Inspect website forms.
2. Test password resets.
3. Test WooCommerce or application events.
4. Review headers.
5. Review provider logs.
6. Monitor DMARC reports.
7. Keep the previous configuration available until the rollback window closes.

Email Migration Rollback Plan

A rollback plan should include:

• Previous MX records
• Previous SPF record
• Previous DKIM selectors
• Previous DMARC policy
• Previous mailbox credentials
• Old-provider access
• Responsible administrator
• Rollback decision threshold
• Expected recovery time
• Customer-communication plan

Do not cancel the old email provider immediately after changing MX records. Delayed senders and cached resolvers may continue delivering to the old system during the transition.

What Are the Best Cloudways Email Security Practices?

Cloudways Email security depends on protecting mailbox credentials, SMTP keys, DNS administration, recovery accounts, team permissions, and migration procedures. Email is often the recovery channel for hosting, domains, payments, and SaaS accounts, so one compromised or inaccessible mailbox can affect the wider business infrastructure.

Use Strong, Unique Credentials

Every mailbox, provider account, DNS account, and Cloudways account should have a unique password stored in a reputable password manager.

Do not reuse:

• Cloudways passwords
• Mailbox passwords
• WordPress administrator passwords
• SMTP credentials
• Domain registrar passwords
• Google or Microsoft administrator passwords

Enable Multi-Factor Authentication

Enable multi-factor authentication wherever the provider supports it.

Priority accounts include:

• Cloudways owner account
• Domain registrar
• DNS provider
• Google Workspace administrator
• Microsoft 365 administrator
• Transactional email provider
• Password manager
• Primary recovery mailbox

Protect API Keys and SMTP Credentials

Store credentials in:

• Environment variables
• Encrypted secrets
• Provider vaults
• Restricted configuration files
• WordPress configuration methods that avoid exposing secrets in screenshots

Never place credentials in:

• Public repositories
• Support screenshots
• Shared spreadsheets
• Blog tutorials
• Unencrypted email
• Client handover documents without access controls

Separate Administrative and Public Mailboxes

A public address such as support@example.com should not automatically be the sole recovery address for the domain registrar, Cloudways account, payment processor, and password manager.

This separation reduces the risk of a customer-facing mailbox outage locking administrators out of the systems needed to repair it.

Use Least-Privilege Team Access

Give each team member only the permissions required for their work.

For example:

• A content editor does not need DNS access.
• A support agent does not need the SMTP API key.
• A developer may need application configuration but not billing.
• A client may need mailbox access but not the agency’s central provider account.

Rotate Credentials

Rotate credentials when:

• An employee leaves
• A contractor finishes
• A key appears in a screenshot
• A repository was exposed
• A provider reports suspicious access
• A client relationship ends
• Ownership changes
• An administrator device is compromised

Monitor DMARC Before Enforcement

Begin with monitoring, identify legitimate senders, correct alignment problems, and then increase enforcement. Moving directly to p=reject without understanding the domain’s sending ecosystem can block legitimate systems.

Maintain Offboarding Procedures

An offboarding checklist should cover:

• Mailbox suspension
• Forwarding duration
• Data export
• Shared-account removal
• App-password revocation
• API-key rotation
• Team-permission removal
• Device sign-out
• Recovery-address changes
• Legal retention requirements

What Cloudways Email Screenshots and Practical Tools Should You Add?

A useful Cloudways Email tutorial should show the current dashboard paths, provider settings, DNS records, client configuration, test results, and logs that readers must reproduce. Screenshots should be date-stamped, redact credentials, and focus on actions rather than decorative interface images.

Recommended visual assets include:

1. [Insert image: Cloudways Integrations menu showing Rackspace Email and Elastic Email | Alt text: “Find Cloudways Email integrations in dashboard”]
2. [Insert image: Rackspace mailbox creation screen with password hidden | Alt text: “Create Cloudways Rackspace business mailbox”]
3. [Insert image: Rackspace MX, SPF, and autodiscover records in DNS | Alt text: “Add Cloudways Rackspace Email DNS records”]
4. [Insert image: Rackspace Webmail login screen | Alt text: “Open Cloudways Rackspace webmail account”]
5. [Insert image: Rackspace IMAP and SMTP configuration in Outlook | Alt text: “Connect Cloudways Email to Microsoft Outlook”]
6. [Insert image: Elastic Email package-selection screen | Alt text: “Choose Cloudways Elastic Email sending package”]
7. [Insert image: Elastic Email server-binding control | Alt text: “Bind Cloudways Elastic Email to server”]
8. [Insert image: Elastic Email domain-verification records | Alt text: “Verify Cloudways Elastic Email domain”]
9. [Insert image: Cloudways custom SMTP settings with credentials redacted | Alt text: “Configure Cloudways custom SMTP provider”]
10. [Insert image: WP Mail SMTP test-email result | Alt text: “Test Cloudways WordPress SMTP delivery”]
11. [Insert image: Cloudflare DNS authentication records with proxy status visible | Alt text: “Review Cloudways Email records in Cloudflare”]
12. [Insert image: MXToolbox authentication results | Alt text: “Diagnose Cloudways Email DNS with MXToolbox”]
13. [Insert image: Mail-Tester authentication report | Alt text: “Measure Cloudways Email authentication results”]
14. [Insert image: Provider delivery log showing accepted, deferred, and bounced events | Alt text: “Analyze Cloudways Email delivery events”]
15. [Insert image: Custom dual-provider architecture diagram | Alt text: “Separate Cloudways mailbox and transactional email”]

Avoid screenshots containing:

• SMTP passwords
• API keys
• DKIM private keys
• Full customer addresses
• Unredacted message content
• Billing details
• Recovery codes
• Domain registrar credentials

What Should You Do Next With Cloudways Email?

The next step is to identify whether your requirement is a mailbox, transactional sending, or both, and then build separate configuration and testing plans for each function. Documenting the current DNS state before making changes is the most important protection against accidental email outages.

Follow this sequence:

1. Classify the requirement. Decide whether you need receiving, automated sending, or both.
2. Choose the mailbox provider. Select Rackspace, Google Workspace, Microsoft 365, Zoho Mail, or another service.
3. Choose the transactional provider. Select Elastic Email or custom SMTP.
4. Document DNS. Export current MX, SPF, DKIM, DMARC, CNAME, and TTL values.
5. Create and secure accounts. Use unique passwords and multi-factor authentication.
6. Configure incoming mail. Add mailbox-provider MX and supporting records.
7. Configure outgoing mail. Bind Elastic Email or activate custom SMTP.
8. Verify domains. Add the provider-generated SPF, DKIM, tracking, and ownership records.
9. Consolidate SPF. Maintain one valid SPF policy per owner name.
10. Configure applications. Set the correct From and Reply-To addresses.
11. Run technical tests. Test SMTP, application events, and message headers.
12. Run real workflow tests. Test orders, forms, invoices, resets, and replies.
13. Review logs. Investigate bounces, suppressions, complaints, and rejected messages.
14. Document the final architecture. Record providers, owners, credentials, DNS, and renewal dates.
15. Schedule recurring audits. Review DNS, authentication, quotas, logs, and recovery access quarterly.

→ Start Cloudways Email Setup

Conclusion: Is Cloudways Email a Reliable Solution?

Cloudways Email can support a reliable business and transactional email architecture when each function is assigned to the correct provider and authenticated properly. Rackspace or another mailbox provider should handle human correspondence, while Elastic Email or custom SMTP should handle automated website and application messages.

The decisive principle is separation. Do not treat a mailbox, transactional delivery service, marketing platform, and WordPress mail function as interchangeable systems.

Before relying on Cloudways Email for customer communication or revenue-critical notifications:

• Document the DNS zone.
• Authenticate every sender.
• Test receiving and sending separately.
• Inspect message headers.
• Review provider logs.
• Protect credentials.
• Maintain a rollback plan.
• Recheck pricing and limits.

A deliberate setup gives you clearer diagnostics, safer migrations, and better operational control than relying on an unverified default mail route.

Frequently Asked Questions About Cloudways Email

Cloudways Email FAQs commonly concern mailbox inclusion, Rackspace and Elastic Email compatibility, transactional limits, Gmail integration, application-level SMTP, DNS authentication, and migration safety. The answers below address edge cases that often cause confusion during implementation.

Does Cloudways provide free email accounts?

No. Standard Cloudways hosting does not include conventional mailboxes. You must add Rackspace Email or connect an external mailbox provider. ic Email receive messages?

No. Elastic Email on Cloudways is an outgoing delivery service rather than a conventional inbox for receiving business correspondence. Use Rackspace or another mailbox provider for incoming mail. pace Email send WooCommerce order emails?

Rackspace can technically send ordinary outgoing messages, but Cloudways does not recommend it for automated, mass-volume transactional traffic. Use Elastic Email or a custom SMTP provider for WooCommerce notifications. pace Email and custom SMTP run together?

Yes. Rackspace handles mailbox communication, while custom SMTP handles server-level transactional delivery. The limitation applies between Elastic Email and custom SMTP because only one server-level transactional option can be active.

Can different WordPress sites on one server use different SMTP providers?

Yes, but not through two simultaneous server-level Cloudways transactional integrations. An application-level plugin can override the default route for an individual WordPress installation. still fetch Rackspace email through POP?

Google’s current guidance says Gmail will no longer fetch third-party messages through the browser-based “Check mail from other accounts” POP feature. Use forwarding, the Gmail mobile app with IMAP, or another IMAP client instead. ging the Cloudways website A record affect email?

Changing only the website A record should not change incoming email. Problems occur when MX or related authentication records are removed, replaced, or lost during a nameserver migration.

Should Cloudflare proxy email records?

Mail-related records should follow provider instructions. MX records are not proxied, and Cloudways specifically requires the Elastic Email tracking CNAME to have Cloudflare proxying disabled. a message pass SPF but fail DMARC?

DMARC requires alignment with the visible From domain. SPF can pass for an envelope domain that does not align with the visible From address, causing DMARC to fail unless aligned DKIM passes.

Does SPF, DKIM, and DMARC guarantee inbox delivery?

No. Authentication improves legitimacy and diagnostics but cannot guarantee inbox placement because recipient systems also evaluate content, reputation, volume, engagement, complaints, and other signals. rnal Link Report

References

Cloudways. (2026). Cloudways pricing and plans: Rackspace Email add-on pricing. 026). How to set up Rackspace Email Add-on on Cloudways. p Center. (2025). Which email add-on should I use? p Center. (2025). Does Cloudways provide servers for email hosting? p Center. (2025). How to activate the Custom SMTP Add-on. p Center. (2025). How to configure my email client with Rackspace Mailbox. p Center. (2025). Frequently asked questions about Rackspace Add-on. p Center. (2025). How to configure WP Mail SMTP Plugin to send emails. p Center. (2026). How to activate the Elastic Email Add-on. p Center. (2026). How to use Rackspace Email Add-on. p Center. (2025). How to merge multiple SPF records. ). Learn about upcoming changes to Gmailify and POP in Gmail. evine, J. (Eds.). (2026). Domain-Based Message Authentication, Reporting, and Conformance (DMARC), RFC 9989. Internet Engineering Task Force. (2014). Sender Policy Framework (SPF) for authorizing use of domains in email, version 1, RFC 7208. Internet Engineering Task Force. n Project. (n.d.). DMARC overview. n Project. (2016). Best authentication practices for email senders. n by:** ASRAF MASUM, Founder of ASRAF MASUM LTD
Asraf Masum works in SEO, affiliate marketing, SaaS, web hosting, WordPress, AI tools, digital marketing, and authority-site development.

Reviewed by: ASRAF MASUM LTD Editorial Team
Technical and time-sensitive claims were reviewed against current Cloudways, Rackspace, Google, IETF, and DMARC documentation available on August 2, 2026.

Disclaimer: This article was initially drafted using AI assistance. However, the content has undergone thorough revisions, editing, and fact-checking by human editors and subject matter experts to ensure accuracy.

Editorial planning note: The article structure, search-intent priorities, and required topic coverage follow the supplied Cloudways Email content brief.