iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
No. Cloudways does not run mailbox hosting on its own servers. Cloudways hosts your applications and servers, while email is supplied through a separate add-on or an outside provider. For people who need normal send-and-receive addresses, the documented Cloudways option is Rackspace Email. For password resets, receipts, alerts, and other application-generated messages, use Elastic Email, the Cloudways SMTP add-on, or another SMTP service.
This separation explains why you cannot create a mailbox in a standard Cloudways application panel. A complete setup also requires DNS work: MX records route incoming mail, while SPF, DKIM, and DMARC help authenticate outgoing mail. The right choice depends on whether you need human inboxes, transactional sending, or both.
Why can’t I create a mailbox in Cloudways?
You cannot create a regular mailbox because ordinary Cloudways hosting is an application and server service, not an email-hosting service. The platform supplies infrastructure for websites and applications; mailbox storage, spam filtering, user administration, authentication, deliverability controls, and abuse handling are provided separately.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesCloudways states in its official FAQ: “We provide different email solutions through Cloudways Email add-ons, so you can set up email hosting or SMTP sending for your domain even though we don’t host email on our own servers.” In practice, this means a server can run your website while another service stores and delivers messages for you@example.com.
The product boundary is intentional rather than an unfinished mailbox screen. Installing an application on a Cloudways server does not create IMAP or webmail accounts, and adding a mail-related DNS record does not create storage. You must activate an email service and then connect your domain to it.
What kind of email do you need?
Choose a mailbox service when a person needs an address that can send and receive messages. Choose transactional email when software needs to send high-volume or event-triggered messages. If you need both, configure them as separate services and keep their credentials and sender identities distinct.
Human mailboxes
A mailbox is appropriate for addresses such as sales@example.com or alex@example.com. Users expect a webmail interface or a mail client, folders, search, spam controls, contacts, and persistent storage. Incoming mail is delivered by the domain’s MX records to the mailbox provider.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Application or transactional sending
Transactional messages include password resets, invoices, receipts, account verification, shipping notices, and monitoring alerts. An SMTP or API provider accepts messages from your application and sends them to recipients. These services are not a replacement for an employee inbox: they generally do not provide the normal mailbox experience your staff expects.
Both functions
A common arrangement is Rackspace Email for people and Elastic Email or another SMTP service for application traffic. Your application should use its own SMTP credentials and a verified sender, while users sign in to the mailbox service. This separation reduces the risk that a compromised website password exposes employee mail and prevents bulk application traffic from damaging the reputation of a human-mail domain.
What is the Cloudways Rackspace Email option?
Rackspace Email is the documented Cloudways add-on for custom-domain inboxes. Cloudways’ 2026 guide states a price of $1.50 per mailbox per month and 25 GB of mailbox storage per user. Treat those figures as the guide’s stated terms, not a permanent promise: account pricing, packaging, taxes, regional availability, and renewal terms can change, so confirm the amount shown in your Cloudways account before ordering.
What you get
- A send-and-receive mailbox for a custom domain.
- Individual storage allocated per user; the cited allowance is 25 GB.
- DNS instructions for routing mail and enabling authentication.
- A suitable service for normal business correspondence rather than mass-volume application delivery.
What it is not for
Cloudways warns that Rackspace Email is not intended for mass-volume transactional email. Do not use a staff mailbox as the SMTP engine for thousands of password resets or marketing-style sends. Use Elastic Email or another transactional SMTP provider for that workload.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11DNS records used by Rackspace
The Cloudways setup guide gives MX examples including mx1.emailsrvr.com and mx2.emailsrvr.com, along with SPF and autodiscover records. Enter the exact values shown for your account; do not substitute a value copied from a different provider. Cloudways says DNS changes can take 24 to 48 hours to propagate, although individual resolvers may update sooner or later.
Also popular on Amazon
When should you use Elastic Email?
Use Elastic Email when your application needs reliable transactional delivery rather than personal inboxes. Cloudways requires domain verification and DNS records for SPF, DKIM, MX, and DMARC before sending is fully configured.
Typical messages
- Password-reset and email-verification links.
- Order confirmations, receipts, and invoices.
- System alerts, contact-form notifications, and scheduled reports.
- Other messages generated by an application event.
Verification and DKIM requirement
Verification proves that your application is authorized to send for the domain. You publish the provider’s SPF and DKIM records at the DNS host, add the required MX record when instructed, and publish a DMARC policy. Cloudways’ 2026 documentation says new domains must use a 2048-bit DKIM key from October 2026. Existing domains verified with an older key are described separately in that guide, so follow the live instructions for the domain you are configuring rather than reusing an old key.
Why Elastic Email does not replace a mailbox
Elastic Email handles programmatic sending. It does not turn a Cloudways application into an employee inbox, and the presence of an SMTP credential does not provide IMAP storage, folders, or a webmail account. Keep application sending and human correspondence on the services designed for each job.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →What does the Cloudways SMTP add-on do?
Cloudways documents a free SMTP add-on for connecting an application to an SMTP service. The documentation names SendGrid, Mailgun, Mandrill, Gmail, and custom SMTP services as possible providers. Any charges from a third-party provider remain your responsibility.
The add-on supplies a route for application messages; it does not create mailboxes. You still need a provider account, verified sender identity, and correct DNS authentication. Store SMTP credentials in the application’s secret configuration, not in source code or a public repository, and keep them separate from employee mailbox passwords.
SMTP add-on versus an external provider
The Cloudways add-on can simplify application configuration, while an external provider may offer its own API, event logs, suppression management, analytics, support plans, or volume limits. Compare the provider’s current terms before selecting it. The names listed in Cloudways documentation are examples of integrations, not a guarantee that every service has identical features or availability.
How do I point my domain’s MX records to another provider?
Pointing MX records changes where new incoming mail is delivered. Perform the change at the DNS host that is authoritative for your domain, not necessarily inside Cloudways. Follow the provider’s exact record values and keep a rollback copy of the previous DNS zone.
- Identify the requirement. Decide whether you are configuring a human mailbox, application sending, or both. Choose the service before changing DNS.
- Activate the service. Add Rackspace Email for normal inboxes, Elastic Email for transactional sending, the Cloudways SMTP add-on, or an external SMTP provider. Record the account identifiers and sender domains.
- Open the authoritative DNS zone. Check the domain’s nameservers to determine which registrar or DNS provider actually publishes records. Editing a non-authoritative zone has no effect.
- Add the provider’s MX records. Remove obsolete or conflicting MX records when moving all incoming mail. For the documented Rackspace configuration, the guide includes
mx1.emailsrvr.comandmx2.emailsrvr.com; use the priorities and any additional records exactly as supplied for your account. - Publish SPF. Add or update the domain’s SPF TXT record so it authorizes the service that sends mail. Keep one SPF record for the domain; merge mechanisms when necessary instead of publishing multiple independent SPF records.
- Publish DKIM. Add the provider’s selector and public key. For a new Elastic Email domain in the Cloudways 2026 instructions, use a 2048-bit DKIM key.
- Publish DMARC. Add a DMARC TXT record at the provider-recommended host and begin with a policy appropriate to your migration stage. The provider’s instructions determine the exact value and reporting addresses.
- Complete domain verification. Return to the provider dashboard and run its verification check. Correct spelling, host-name formatting, quoting, and duplicate records if verification fails.
- Wait for propagation. Cloudways says Rackspace DNS changes may take 24 to 48 hours. During that period, different networks can see old and new records.
- Test both directions. Send a message from an outside account to the new mailbox, reply from the mailbox, and trigger a representative application message. Inspect headers for SPF, DKIM, and DMARC results and check the provider’s delivery log.
What each DNS record does
| Record | Purpose | What to verify |
|---|---|---|
| MX | Routes incoming mail to the mailbox provider. | Old and new records are not conflicting; priorities match the provider’s instructions. |
| SPF | Lists servers authorized to send for the domain. | There is one valid SPF record and it includes every legitimate sender. |
| DKIM | Uses a cryptographic signature to authenticate outgoing messages. | The selector and public key match the provider; new Elastic Email domains use a 2048-bit key under the October 2026 requirement. |
| DMARC | Lets receiving systems apply a policy when SPF or DKIM alignment fails and optionally send reports. | The host name and policy are exactly what your provider specifies. |
| Autodiscover | Helps compatible mail clients find account settings. | Use the value supplied in the Rackspace setup instructions if your clients require it. |
Which email alternative fits your Cloudways setup?
The deciding question is not which service has the most features; it is whether the service stores mailboxes, sends application mail, or does both. Use this comparison before changing DNS.
Also popular on Amazon
| Option | Best for | Mailbox included? | Key setup work | Cost information available here |
|---|---|---|---|---|
| Rackspace Email add-on | Custom-domain human inboxes | Yes | MX, SPF, autodiscover, propagation, and mailbox creation | $1.50 per mailbox/month and 25 GB per user stated in Cloudways’ 2026 guide; verify current terms |
| Elastic Email add-on | Transactional application sending | No | Domain verification, SPF, DKIM, MX, and DMARC | Not stated in the supplied Cloudways material |
| Cloudways SMTP add-on | Connecting an application to an SMTP service | No | Provider account, SMTP credentials, sender verification, and DNS authentication | The add-on is documented as free; third-party charges are separate |
| External SMTP provider | Application sending when you need another provider’s limits or tooling | Usually no | Provider-specific credentials, DNS records, and delivery monitoring | Varies by provider; not stated |
What should you compare before choosing an email provider?
Compare the service against your actual mail flow, not just its advertised sending limit. A cheap mailbox can be unsuitable for application bursts, and a powerful SMTP service can be frustrating for employees who need calendars and folders.
- Mailbox versus sending-only capability: Confirm whether users receive mail, whether IMAP or webmail is included, and whether application delivery is permitted.
- Custom-domain features: Check aliases, distribution groups, forwarding, catch-all behavior, subdomains, and the number of domains or users allowed.
- Migration and retention: Look for IMAP import, export, mailbox preservation, retention controls, and a documented path to leave the service.
- Security: Check multi-factor authentication, admin roles, password policies, account recovery, encryption, audit logs, and abuse-response procedures.
- Authentication and deliverability: Confirm SPF, DKIM, DMARC alignment, bounce and suppression handling, dedicated or shared sending reputation, and diagnostic logs.
- Storage and administration: Compare per-user storage, archiving, attachment limits, user provisioning, and the effort required to suspend or remove an account.
- Support and limits: Read current support hours, escalation routes, rate limits, daily quotas, acceptable-use rules, and regional availability.
- Total cost: Include per-user mailbox fees, sending volume, add-on fees, taxes, migration work, storage upgrades, and renewal terms.
- DNS effort: Count the records, verification steps, subdomains, and future changes your team can maintain safely.
How do you migrate mail without losing delivery?
Plan the mailbox migration separately from the Cloudways application move. Email can remain with one provider while the website runs elsewhere as long as the authoritative DNS records continue pointing to the mail service.
Before the cutover
- Inventory every mailbox, alias, forwarding rule, shared address, and application sender.
- Check whether the destination supports importing existing messages and contacts.
- Lower DNS TTL ahead of the change if your DNS provider allows it, while recognizing that cached records can still persist.
- Export or otherwise preserve the old mailbox data according to the old provider’s terms.
- Prepare new accounts and test sending before changing MX records.
During and after the cutover
- Publish the destination MX, SPF, DKIM, and DMARC records.
- Keep the old service available during the propagation window where possible.
- Test inbound delivery from multiple unrelated domains and test outbound replies.
- Watch both providers for delayed messages, bounces, and forwarding failures.
- Update mail clients, mobile profiles, website contact forms, and integrations with the new credentials.
- Remove the old MX records only after you have confirmed that no legitimate traffic still depends on them.
What are the most common Cloudways email problems?
Most failures come from using the wrong service type, editing the wrong DNS zone, or leaving contradictory records behind. Diagnose the symptom before changing settings again.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →There is no “create mailbox” button
This is expected on standard Cloudways hosting. Activate the Rackspace Email add-on or choose another mailbox provider; installing an SMTP add-on will not create an inbox.
Incoming mail still goes to the old provider
Check the domain’s authoritative nameservers, remove obsolete MX records, confirm priorities, and allow time for caches to expire. Query the domain from more than one network rather than trusting a single local DNS result.
Domain verification fails
Compare the provider’s required host name, record type, value, and quotation marks with the published DNS zone. Common causes include adding the record at the wrong DNS host, duplicating an SPF record, or copying a DKIM selector incorrectly.
Messages send but land in spam
Inspect the message headers for SPF, DKIM, and DMARC results, then check the provider’s bounce and reputation information. Correct authentication alignment and use a consistent, recognizable sender; do not respond to deliverability problems by sending more volume from a human mailbox.
The website cannot send after a mailbox change
Mailbox credentials and application SMTP credentials are independent. Recheck the application’s SMTP host, port, encryption mode, username, password, sender address, and any provider-specific restrictions, then test with a single controlled message.
Also popular on Amazon
Some recipients receive mail while others do not
Check propagation and recipient-side rejection messages, then compare the provider’s delivery log with the recipient’s headers. A successful SMTP handoff only proves that the receiving server accepted the message for processing; it does not guarantee inbox placement.
Can Cloudways host a website and email with different providers?
Yes. Your website’s A or CNAME records can point to Cloudways while your domain’s MX records point to a mailbox provider. These record types serve different functions, so moving the application does not require moving email and moving email does not require moving the application.
Keep a written DNS map showing which records belong to the website, mailbox service, and transactional sender. That map prevents a future web migration from accidentally deleting MX, SPF, DKIM, or DMARC records.
Recommended Free Tools
Frequently Asked Questions
Can I keep my existing mailbox if I move my website to Cloudways?
Yes. Leave the domain’s MX records pointed at the existing mailbox provider and change only the website records needed for Cloudways. Test the site and mail independently after the DNS change.
Can one domain use different addresses for staff and application alerts?
Yes. Staff addresses can use the mailbox service while the application sends from a dedicated address or subdomain. Separate sender identities make it easier to apply different authentication and reputation policies.
Do I need to change nameservers to use Cloudways email add-ons?
Not necessarily. You can keep your current DNS host and publish the required records there, provided you know which service is authoritative and can edit its zone.
Is an SMTP password the same as an employee email password?
No. An SMTP credential authorizes an application to submit messages and should be stored as a secret. Employee mailbox credentials control a user account and should not be embedded in website configuration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
