Mail routing · Beginner · 30 minutes
How to create an email account in cPanel — Creating the Mailbox Is Easy. Making the Domain Deliver to It Is the Job
The panel will happily create a mailbox for a name whose mail has been going to somebody else for two years, and it will not mention it.
The short answer
Look up the MX record for the domain before you create anything, and make cPanel's mail routing for that domain agree with it. A mailbox is storage; the MX record is the instruction that decides whether any message ever reaches that storage. Get them out of step and the account exists, looks perfect, and receives nothing.
Half an hour is the right budget, and most of it is checking rather than typing. Creating the account takes a minute: pick the domain, type the local part, and accept the password the panel generates instead of composing one. The rest is confirming the routing, sizing the quota, round-tripping a test message, and making sure SPF names the server that will be sending.
By the Hosting & Domains team · Reviewed 24 August 2026
Beginner
Assumed knowledge
5
Steps, first to last
Free
Cost of asking
Proven
Checked where you will do it
Written for whoever holds the domain. If mail for this name has ever lived anywhere else — a previous host, a free provider, a business suite somebody set up years ago — the routing check below is the whole page and everything else is a formality.
The checks are read-only lookups and the account creation is reversible. Nothing here can lose a message that is already delivered.
The mailbox and the routing are two different things
Creating an email account in cPanel allocates storage on this server and a password to reach it. That is all it does. Where the world sends mail for your domain is decided by the MX record in your zone, and the two have no automatic relationship whatsoever.
cPanel adds a third setting between them: the mail routing for each domain, which can be local, remote or automatic. Local means this server keeps everything for that name and delivers it internally. Remote means it hands mail on to whatever the MX record says. Automatic means it follows the MX record. A local setting on a name whose MX points elsewhere is the quiet failure: the server keeps the message, delivers it to its own empty mailbox, and nothing bounces.
Find out where the name's mail actually goes
Look up the MX record for the domain. There are three answers you might get. It points at this server, in which case create the mailbox and carry on. It points at a third-party provider, in which case a mailbox created here will never receive anything until you change the record. Or there is no MX record at all, in which case mail falls back to the A record, which works until the day the A record changes for a reason that had nothing to do with mail.
Publish an MX record explicitly, even when it names the same host the A record points at. Implicit behaviour is behaviour that changes without warning when somebody moves the website.
Creating it, and giving it room
In cPanel, open Email Accounts and press Create. Pick the domain, type the local part, accept the generated password. On the quota, be generous, or leave it uncapped within whatever storage the plan permits.
A mailbox at its ceiling begins rejecting what arrives, which is the least helpful way for a message to fail: the sender receives a refusal that reads as though your domain is broken, and by the time somebody mentions it, it has been going on for a week.
Prove it in both directions before you print it
Sign into Webmail, send a message to an outside address, and reply to it from there. Receiving proves the MX record and the routing; sending proves SMTP and authentication. The pair together is the only evidence that the address works.
Then take the settings from the panel's Connect Devices page and configure the account as IMAP, so the phone, the laptop and the browser all look at one server-side mailbox instead of each hoarding its own dwindling copy.
The records that decide whether it arrives in the inbox. Delivery is not the same as arrival. Your SPF record has to name the server that sends for you, or large providers will treat perfectly genuine mail from your domain as forgery. Add DKIM signing so each message carries a signature they can check against a key in your zone.
Then decide the shape of the address list. People who answer get mailboxes; roles such as info@ and sales@ get forwarders. The test is whether the address has to keep anything: if it does, a mailbox, and if it only needs somewhere to go, an alias, which costs nothing.
The panel these instructions were written against
The registrar record, the zone editor and cPanel all sit behind one login here, so nothing in these instructions asks you to work out which supplier holds which setting — the commonest reason a five-minute change costs an afternoon.
NVMe storage and LiteSpeed caching sit beneath every tier, the smallest one included. That is the floor here rather than an upgrade path.
- Every step run against a live zone
- The registry rule named before it bites
- Registrar, DNS host and web host kept apart
- Someone to ask at any hour you stall
Why Hosting & Domains
Standard on every plan
The routing checked first
The one step that decides whether the mailbox will ever receive anything, and the one every other guide leaves until the troubleshooting section.
The silent failure named
Local delivery on a name whose MX points elsewhere loses mail without a bounce. Invisible unless somebody tells you where to look.
Delivery and arrival separated
SPF and DKIM decide whether genuine mail from your domain reaches an inbox or a spam folder. That is a zone job, not a mailbox job.
Honest about the size of it
Beginner level, about 30 minutes, most of it checking rather than typing.
An address roster that scales
Mailboxes for people, forwarders for roles. Decided once, it stops the account collecting passwords nobody looks after.
A desk that keeps your hours
Someone answers at any hour, and can see from their side whether a message ever reached the server.
Quick Start
Order placed to site online
- 1
Look up the MX record before you create anything
One lookup tells you whether mail for this name comes here at all. If it points at a third-party provider, a mailbox created in cPanel will never receive a thing, and nothing will bounce to tell you.
- 2
Set the domain's mail routing to match
In cPanel, set routing to automatic or remote so the server follows the MX record you published. A local setting on a name whose mail lives elsewhere swallows messages silently, which is the commonest mail fault there is.
- 3
Create the account
Email Accounts, then Create. Pick the domain, type the local part, and accept the generated password instead of composing one. Thirty seconds, once the routing is settled.
- 4
Give the mailbox room it will not outgrow
Be generous, or leave it uncapped within the plan's storage. A full mailbox refuses incoming mail and the sender sees a rejection that looks like your whole domain is broken.
- 5
Round-trip a message, then check SPF and DKIM
Send out from webmail and reply back in. Then confirm SPF names the sending server and DKIM is signing, or genuine mail from your name gets filed as forgery.
Built In
Fitted to every plan
- Spam and virus screening on every mailbox from the moment it exists
- Mailboxes that answer at the name on your registration
- A free certificate on every plan, reissued before the old one expires
- cPanel, the panel most of the industry already runs
- A PHP version chosen per site from the control panel
- WordPress Toolkit, with the updating seen to for you
- SSH, Git and Composer on the developer tiers
- Engineers who bring your current site across for nothing
- LiteSpeed caching built into the server rather than bolted on by plugin
- WebP image conversion built in at no extra charge
Frequently Asked
Questions we field again and again
I created the mailbox and nothing arrives at all.
Two causes account for almost all of it. Either the MX record points at another provider, so the world never sends anything here, or cPanel is set to deliver that domain locally while the MX points elsewhere, so the server keeps messages and files them into an empty local mailbox. Check the record, then check the routing setting, in that order.
Can a name have its mailboxes here and its website somewhere else?
Yes, and it is a perfectly ordinary arrangement. MX and A are independent records: point A wherever the site is and MX here, and each service works without knowing about the other. Just remember that SPF must then name the correct sending host, because the website is not it.
Does a mailbox come with the name or with the hosting?
With the hosting. Every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP and spam filtering on from the start. A name on its own resolves wherever you point it and holds no mail of its own — and there is standalone email hosting for a name whose website lives somewhere else.
How many names can one account hold?
The domain list itself is not capped. Whether they can all serve separate websites depends on the plan: from the Turbo tier upward an account runs several sites, each with its own name, mailboxes and certificate. If the extra names belong to clients rather than to you, reseller hosting keeps each one properly walled off.
Keep reading
Joomla Hosting
Joomla hosting with the name, the mailboxes and the certificate in one account.
Domain Names
Register, transfer and hold names in one list — year one included with annual hosting.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
Mail that arrives at the name you hold.
Mailboxes on every plan, and a zone editor where the MX record is one screen from the account.
View Domain Names plans