When you create an email account in cPanel and it refuses to send, receive, or authenticate, the error message rarely tells you the real problem. I've walked through hundreds of these tickets. Most failures fall into seven patterns, and each has a specific fix.
This guide covers the actual errors you'll see in webmail, Outlook, Thunderbird, or your phone's mail app, then shows you how to diagnose and resolve each one.
Error 1: Authentication Failed (Invalid Username or Password)
Symptoms
Your mail client refuses to connect. The error says "Authentication failed," "Invalid credentials," or "Username and password not accepted." You're certain the password is correct because you just set it.
Root cause
The username format is wrong. cPanel requires the full email address as the username, but many clients auto-fill just the part before the @ symbol. Another common issue: the account exists in cPanel but hasn't fully propagated to the mail server's authentication database, usually due to a stale cache.
The fix
Open your mail client settings and verify the username field shows the complete email address:
Username: [email protected]
NOT: user
If that's already correct, reset the password in cPanel to force a cache refresh:
- Log into cPanel
- Go to Email Accounts
- Find the account and click Manage
- Enter a new password and click Update Email Settings
- Wait 60 seconds, then test again
If you're using Outlook, delete the account profile entirely and re-add it. Outlook caches credentials aggressively and sometimes won't pick up the corrected username even after you change it.
Error 2: SMTP Port 25 or 587 Connection Refused
Symptoms
You can receive mail but not send. The client shows "Cannot connect to SMTP server" or times out when you hit Send. Webmail works fine.
Root cause
Your ISP or hosting provider blocks outbound port 25 to prevent spam. Port 587 might also be filtered. Some residential ISPs block both. The server itself is fine; the network won't let the packets through.
The fix
Switch to port 465 with SSL, which ISPs rarely block:
SMTP Server: mail.yourdomain.com
Port: 465
Encryption: SSL/TLS
Authentication: Required
If port 465 also fails, your provider is blocking all common mail ports. Two workarounds:
- Use webmail when you're on that network
- Connect through a VPN to bypass the ISP's filters
To verify which ports are open from your location, run this from a terminal:
telnet mail.yourdomain.com 25
telnet mail.yourdomain.com 587
telnet mail.yourdomain.com 465
A successful connection shows a banner from the mail server. "Connection refused" or a timeout means the port is blocked.
Error 3: Mailbox Quota Exceeded
Symptoms
New mail bounces back to senders with "Mailbox full" or "Quota exceeded." You can send but not receive. The account worked yesterday.
Root cause
The mailbox hit its storage limit. cPanel assigns a default quota when you create an account, often 250 MB or unlimited. If it's limited and you never clean old mail, the box fills up. Attachments count against the quota, and a few large PDFs or images will eat it fast.
The fix
Check the current usage in cPanel under Email Accounts. The quota and used space appear next to each account. If it's at or near 100%, you have three options.
Option 1: Increase the quota
- Click Manage next to the account
- Change the quota field to a higher number (in megabytes) or select Unlimited
- Click Update Email Settings
Option 2: Delete old mail
Log into webmail, go to the Trash and Sent folders, and delete everything you don't need. Then empty Trash. Quota updates within a few minutes.
Option 3: Archive to local storage
If you use Outlook or Thunderbird, move old messages to a local folder on your computer. They'll no longer count against the server quota.
After freeing space, ask senders to retry. Bounced messages don't automatically re-deliver.
Error 4: DNS Records Missing or Incorrect
Symptoms
Mail delivery is intermittent. Some messages arrive instantly, others bounce or vanish. Senders receive "Could not find mail server" or "DNS lookup failed." Outbound mail works fine.
Root cause
Your domain's MX record is missing, points to the wrong server, or hasn't propagated yet. MX records tell other mail servers where to deliver mail for your domain. If the record is absent or wrong, inbound mail fails.
The fix
First, check your current MX record from a terminal:
dig yourdomain.com MX +short
You should see something like:
0 mail.yourdomain.com.
The number is priority (lower wins). The hostname should match your mail server. If the command returns nothing or points to an old server, update your DNS.
In cPanel, go to Zone Editor or Email Routing and ensure Local Mail Exchanger is enabled. This automatically creates the correct MX record.
If you manage DNS elsewhere (Cloudflare, your registrar), add an MX record manually:
Type: MX
Name: @ (or blank, depending on the interface)
Priority: 0
Value: mail.yourdomain.com
DNS changes take time. Propagation averages 15 minutes but can stretch to a few hours. Test again after waiting.
Error 5: SSL Certificate Name Mismatch
Symptoms
Your mail client displays a certificate warning: "The certificate name does not match the server name" or "Cannot verify server identity." Mail still works if you click through the warning, but the error reappears every time you connect.
Root cause
You configured the client to use your domain name (mail.yourdomain.com) but the server's SSL certificate is issued for a different hostname, often the server's main hostname. The client sees the mismatch and assumes a security problem.
The fix
Find out what hostname the certificate is actually for. In cPanel, check SSL/TLS Status or ask your host. Then update your mail client to use that hostname instead:
Incoming Server: server123.yourhost.com
Outgoing Server: server123.yourhost.com
Mail routing still works because the server accepts connections for all domains hosted on it. You're just matching the certificate name to stop the warning.
Alternatively, if you control DNS and want to keep using mail.yourdomain.com, install a certificate that covers that name. Many hosts support AutoSSL or Let's Encrypt for mail subdomains.
Error 6: Graylisting or SPF/DKIM Failures Causing Delays
Symptoms
Messages you send arrive hours late or not at all. Recipients never receive them, or they land in spam. Replies from Gmail or Outlook take 10-30 minutes to show up in your inbox. No error appears in your sent folder.
Root cause
The receiving server uses greylisting (temporarily rejecting mail from unknown senders) or checks SPF and DKIM records to verify you're not spoofing the sender address. If those records are missing or misconfigured, mail gets delayed or rejected.
The fix
Check SPF and DKIM in cPanel
- Go to Email Deliverability
- Look for warnings or red X marks next to your domain
- If SPF or DKIM is invalid, click Manage and then Install the suggested record
The correct SPF record for a typical cPanel server looks like:
v=spf1 +a +mx +ip4:YOUR.SERVER.IP.HERE ~all
DKIM requires a public key in DNS and a private key on the server. cPanel generates both automatically if you enable DKIM in Email Deliverability.
After fixing the records, test delivery to a Gmail address. Check the message headers ("Show original" in Gmail) for SPF and DKIM pass results:
Received-SPF: pass
Authentication-Results: dkim=pass
Greylisting delays clear up on their own after the sending server retries. You can't disable greylisting on the recipient's side, but valid SPF/DKIM makes it less likely they'll use aggressive filtering.
Error 7: Webmail Login Loop or "Session Expired"
Symptoms
You enter your email and password in Roundcube, Horde, or SquirrelMail. The page reloads and shows the login screen again. No error message, just an endless loop. Sometimes you see "Session expired" even though you just logged in.
Root cause
Browser cookies are blocked or corrupted, often due to privacy extensions, Incognito mode, or third-party cookie settings. Webmail relies on session cookies to keep you logged in. Another cause: the server's session directory is full or has permission errors, preventing new sessions from being created.
The fix
Client-side fix
Clear your browser's cookies and cache for the cPanel domain, then try again. If you're in Incognito or Private mode, switch to a normal window. Disable extensions like Privacy Badger or uBlock Origin temporarily to rule them out.
In Chrome, check chrome://settings/content/cookies and make sure "Block third-party cookies" is off or the cPanel domain is in the allowed list.
Server-side fix (if you have SSH access)
Log into the server via SSH and check the session directory:
ls -lh /var/cpanel/userhomes/cpaneluser/sessions/
If it's full of old session files, clear them:
find /var/cpanel/userhomes/*/sessions/ -type f -mtime +7 -delete
That removes sessions older than seven days. Restart cPanel services to be safe:
/scripts/restartsrv_cpanel
If you don't have SSH access, contact your host and describe the loop. They can clear sessions or check permissions.
What to check first
When email breaks, work through this sequence:
- Verify the username is the full email address
- Confirm the password by resetting it in cPanel
- Check mail client port settings (465 for SMTP, 993 for IMAP, 995 for POP3)
- Look at the account's quota and disk usage
- Run
dig yourdomain.com MXto confirm DNS - Review Email Deliverability in cPanel for SPF/DKIM warnings
- Test webmail in a clean browser or Incognito window
Most issues resolve at step 1, 3, or 4. The rest are edge cases but common enough that you'll hit them eventually.
How do I know if the mail server itself is down?
Try logging into webmail directly at https://yourdomain.com:2096 or through cPanel's webmail link. If webmail loads, the mail server is running. If it times out or shows a connection error, the service is stopped or the server is offline. Check your hosting provider's status page or open a ticket.
Can I use Gmail to send mail through my cPanel account?
Yes. In Gmail's settings, add your cPanel email as a "Send mail as" address. Use your cPanel server's SMTP settings (port 465, SSL, full email as username). Gmail will route outbound mail through your server, so SPF and DKIM need to be configured or recipients might flag it as spam.
Why do some messages go to spam even though SPF and DKIM pass?
SPF and DKIM prove the message is authentic but don't guarantee inbox placement. Spam filters also check content (words, links, formatting), sender reputation (IP address history), and recipient engagement (do people mark your mail as spam?). If your server's IP has been used for spam in the past, mail gets filtered even with valid records. Check your IP against blacklists and consider a dedicated IP if you're on shared hosting.
What's the difference between POP3 and IMAP?
POP3 downloads mail to your device and usually deletes it from the server. IMAP syncs mail across devices and leaves it on the server. Use IMAP if you check mail from multiple devices (phone, laptop, webmail). Use POP3 if you only use one device and want local storage. IMAP uses port 993; POP3 uses port 995.
Fixing it properly
Email in cPanel breaks in predictable ways. Authentication errors almost always mean the username isn't the full address. Connection failures point to blocked ports or wrong encryption settings. Quota, DNS, and SSL problems show specific symptoms that map to specific fixes.
When you see an error, match it to one of the seven patterns above and follow the steps. If the first fix doesn't work, check the next most likely cause. Avoid guessing or changing multiple settings at once; you'll lose track of what actually solved it. Test after each change. Most email problems resolve in under five minutes once you know where to look.