How to create a mailbox in cPanel
Creating an email mailbox in cPanel is one of the most common tasks when a business starts using its own domain for professional communication. The workflow is usually straightforward: create an email account (user@domain), set a strong password and a quota, then log in via Webmail or configure an email client (Outlook, Thunderbird, mobile). In real life, most issues come from details: DNS and MX records, quota planning, correct server settings, deliverability (SPF/DKIM/DMARC), and migration from an older mail provider.
Before you begin, confirm three things: (1) your domain is connected to the hosting account, (2) DNS is correct (MX records point to the right mail server), and (3) you can log in to cPanel. If you still need a domain, use Domain Registration. If you need a cPanel-based environment for website + email, see Hosting. For secure connections and trust, ensure SSL is available via SSL Certificates (this also improves Webmail security).
1) Open “Email Accounts” and create a new mailbox
Log in to cPanel and go to “Email” → “Email Accounts” (sometimes simply “Email Accounts”). Click “Create”. Choose the domain (if your account hosts multiple domains) and enter the mailbox username (for example, info, sales, billing). cPanel will show the full address such as info@yourdomain.com.
Next, set a strong password. Use the password generator when available and store it in a password manager. Email accounts are frequent attack targets, so weak passwords are the #1 avoidable risk. If multiple people need access, avoid sharing one mailbox password widely—create personal mailboxes and use forwarders or shared workflows for addresses like info@.
2) Choose a quota and understand why it matters
cPanel asks you to set a mailbox quota (how much storage the mailbox can use). This is not just a number. When the mailbox reaches the limit, it may stop accepting new mail or bounce messages back to senders. Choose quotas based on real usage. Accounting or legal mailboxes often need more space because attachments are large. If you frequently exchange big files, consider storing documents in a separate storage solution instead of relying on email attachments.
Also consider the overall disk space of your hosting plan. One unlimited mailbox can fill the entire account storage and impact both email and the website. A good habit is to review the largest mailboxes periodically and clean up “Sent” and “Trash”, or implement archiving rules. Storage planning is part of keeping email reliable.
3) Access your email: Webmail or an email client (IMAP/POP3/SMTP)
After creation, cPanel typically offers “Check Email” or “Access Webmail”. Webmail is convenient for quick access without configuration. For daily work, many users prefer an email client. IMAP is recommended in most cases: mail stays on the server and syncs across devices. POP3 is older and downloads mail to one device; if configured poorly it can cause confusion when messages disappear from other devices.
SMTP is for sending. Typical secure settings are: outgoing server on port 465 (SSL) or 587 (STARTTLS), authentication enabled, username as the full email address. Incoming IMAP is usually 993 (SSL) or 143 (STARTTLS), POP3 is 995 (SSL) or 110. In some hosting setups, using the server hostname recommended by cPanel avoids certificate mismatch warnings while DNS changes are still propagating.
Use the “Configure Mail Client” page in cPanel to view the exact settings for your account. Some providers also offer auto-configuration files for common clients. Always prefer TLS/SSL ports. If your client warns about certificates, confirm you are using the correct mail server name and that SSL is properly installed.
4) DNS and MX records: the most common reason email “doesn’t work”
Creating a mailbox in cPanel does not automatically route mail to it unless DNS points to the same mail server. If your domain’s MX records still point to a previous provider (or a service like Google Workspace), mail will go there instead. If you are migrating, plan the change: create mailboxes first, prepare client settings, then switch MX at a low-traffic time. Keep access to the old mailbox for a while, because some messages may still arrive there during DNS propagation.
MX changes take time to propagate. If certain senders still deliver to the old server, it is usually caching, not an unexplained error. Also consider deliverability records: without SPF/DKIM/DMARC, outgoing mail may end up in spam or be rejected by strict receivers. Even if you cannot implement everything immediately, at least SPF is often a fast improvement.
5) Security and deliverability: SPF, DKIM, DMARC, password hygiene
To improve trust and delivery rates, configure email authentication. SPF declares which servers are allowed to send mail for your domain. DKIM adds a cryptographic signature so receivers can verify the message was not altered. DMARC defines policy and provides reporting when SPF/DKIM fail. These are essential if you send emails to customers and want messages to land in inboxes, not spam. cPanel often enables DKIM automatically when it manages the DNS zone.
On the account side, use strong unique passwords and enable two-factor authentication (2FA) for cPanel if available. Avoid sharing mailbox credentials widely. When employees leave, rotate passwords and revoke access. Many incidents happen not through sophisticated exploits but through credential guessing or stolen passwords from compromised devices.
6) Forwarders, autoresponders, and filters
cPanel provides useful tools such as forwarders, autoresponders, and filters. Forwarders can distribute mail from shared addresses like info@ to multiple people. Autoresponders help during vacations or for “we received your message” confirmations. Filters can sort mail into folders or apply labels. Start conservative: overly aggressive filters can hide important messages, so review and adjust once you see how they behave in real use.
7) Quick troubleshooting checklist
If you are not receiving mail, check: MX records point correctly, the mailbox is not over quota, the password is correct, and the client uses the right ports. If outgoing mail lands in spam, verify SPF/DKIM/DMARC and check content patterns (too many links, suspicious attachments). If a client cannot connect, ensure you are using IMAP 993 and SMTP 465/587 with TLS and full email address as the username.
After creation: a short verification routine
After you create the mailbox, test it: (1) log in to Webmail and send a message to an external address, (2) reply back and confirm inbound delivery, (3) configure your email client with IMAP + SMTP and verify sending with authentication, (4) confirm TLS is enabled and there are no certificate warnings, (5) review quota usage and clean Trash, (6) if you changed DNS, monitor whether the old provider still receives mail. This takes minutes and prevents long troubleshooting later.
If email is business-critical, define long-term retention and backup expectations. Mailboxes often become part of the company archive, so quota planning, archiving routines, and security should be considered early. A clean process today prevents surprises later when storage fills up or deliverability becomes unreliable.