cPanel Email Not Receiving or Sending? How to Find and Fix the Cause

Overview

For cPanel email not receiving or not sending, open Email > Track Delivery in cPanel first. It shows whether the message reached the server and what happened to it. Almost every case then comes down to one of seven causes: a full mailbox, MX records or Email Routing pointing the wrong way, a filter or forwarder, missing SMTP authentication, the hourly sending limit, or authentication failures at the receiving end.

This guide is for anyone with a cPanel hosting account, including Host & Tech cPanel shared hosting customers, whose mail has stopped arriving, bounces, or never leaves the Outbox. The fixes are ordered from most to least likely, and each one names the exact bounce or error text so you can match it to what you’re seeing. You don’t need server access for any of them.

If the problem is that your mail app won’t connect at all (certificate warnings, password prompts), start with cPanel email settings for Outlook, iPhone and Android instead.

What causes cPanel email to stop receiving or sending

How to fix cPanel email not receiving or sending

Fix 1: Check Track Delivery before changing anything

Track Delivery is the fastest way to tell a server problem from a client problem, and most people skip it.

1. In cPanel, go to Email > Track Delivery.
2. Enter the address in Recipient Email (optional) and click Run Report.
3. Use Show Failures and Show Deferred to narrow it down, then click the information icon on a row to read the full SMTP response.

Read the result like this. If the message isn’t listed at all, it never reached this server, so check Fix 3. If it shows as delivered, the server did its job and the message went to a folder, a forwarder or the spam filter (Fix 4). If it failed, the response text tells you which fix below applies. Ask the sender for the exact time they sent it; on a busy account that saves a lot of scrolling.

Fix 2: The mailbox is full

When a mailbox reaches its quota the server refuses new mail and the sender gets a bounce mentioning the quota. Your mail app usually shows no error, so this looks like mail silently stopping.

1. Open Email Accounts and look at the usage bar next to the address.
2. If it’s full or close, click Manage and raise Allocated Storage Space, or set it to unlimited if your plan’s disk allows.
3. Empty Trash and Junk in webmail. Large Sent folders from phones that save a copy of every attachment are a common culprit.

The default quota on new accounts can be small. Raising it the day you create the mailbox avoids this entirely.

Fix 3: MX records or Email Routing point the wrong way

MX records tell the world where your mail lives. Check them from your own computer:

dig MX yourdomain.com +short

On Windows:

Resolve-DnsName yourdomain.com -Type MX

If the result names your hosting server (often mail.yourdomain.com or yourdomain.com), mail is meant to arrive in cPanel. If it names Google (smtp.google.com or aspmx.l.google.com) or Microsoft (*.mail.protection.outlook.com), your mailboxes live there and cPanel mailboxes won’t receive anything. Fix the MX record in Zone Editor, or at your registrar if your DNS is hosted elsewhere, and allow for DNS propagation time.

Then check Email > Email Routing. This one catches a lot of businesses after they move to Google Workspace or Microsoft 365. If the routing is still set to Local Mail Exchanger, the server believes it’s in charge of your mail. Anything sent from the same server, such as your website’s contact form or WooCommerce order emails, gets dropped into a cPanel mailbox nobody reads instead of going to Google or Microsoft. Set it to:

• Remote Mail Exchanger if your mail is hosted with Google, Microsoft 365 or another provider.
• Local Mail Exchanger if your mailboxes are in cPanel.

Automatically Detect Configuration decides from the IP address of your lowest-numbered MX record, so it can land on the wrong option while DNS is changing. Pick the option explicitly.

Fix 4: A filter, forwarder or spam setting is moving the mail

If Track Delivery says a message was delivered but it’s not in the Inbox, something on the account moved it.

• Email Filters and Global Email Filters: look for rules that discard mail or move it to a folder. A rule matching a common word in the subject catches more than people expect.
• Forwarders: a forwarder set to redirect rather than copy sends mail elsewhere and leaves nothing in the mailbox. See how to set up email forwarding in cPanel for the difference.
• Spam Filters: if Automatically Delete New Spam (Auto-Delete) is on with a low score, legitimate mail can be deleted before you ever see it. Turn auto-delete off, or raise its threshold, and check the spam folder in webmail.
• Your mail app: Outlook’s Focused Inbox and phone rules can hide mail too. If it’s in webmail but not on your phone, the server is fine.

Fix 5: Please turn on SMTP Authentication in your mail client

This bounce (full text starts with 550-Please turn on SMTP Authentication in your mail client) means your mail app tried to send without logging in. The server refuses to relay unauthenticated mail so it can’t be used for spam.

1. In your mail app, open the account’s outgoing (SMTP) settings.
2. Turn on authentication and use the same username (your full email address) and password as incoming mail.
3. Use port 465 with SSL/TLS, or 587 with STARTTLS. Port 25 is often blocked by home and mobile ISPs.

In classic Outlook the setting is under More Settings > Outgoing Server > My outgoing server (SMTP) requires authentication.

Fix 6: Domain has exceeded the max emails per hour

The full message reads like Domain yourdomain.com has exceeded the max emails per hour (x/y (z%)) allowed. Message discarded. Shared servers cap how many messages each domain can send per hour to protect everyone’s IP reputation. Messages over the limit are not queued; they have to be resent.

• If you didn’t send a lot of mail: treat it as a compromise until proven otherwise. Change the mailbox passwords, check the website for a spammed contact form, and look at Track Delivery for recipients you don’t recognise. Then open a ticket so we can confirm the queue is clean.
• If it was a newsletter or bulk send: send newsletters through a dedicated service rather than your hosting mailbox, or spread the send over several hours.
• If you routinely need more: a VPS with WHM lets you set the limit yourself under Tweak Settings > Max hourly emails per domain.

Fix 7: Mail sends but goes to spam or gets rejected

If Track Delivery shows your message was accepted by the recipient’s server but it landed in spam, or Gmail bounced it with a 5.7.26 code saying the sender is unauthenticated, the receiving side doesn’t trust your domain yet.

1. Open Email > Email Deliverability and fix any SPF or DKIM record marked as a problem. Install the suggested record does it for you when your DNS is hosted with us.
2. If you also send through Google, Microsoft 365 or a newsletter service, your SPF record has to include them. How to create an SPF record has examples for the common combinations.
3. Add a DMARC record once SPF and DKIM pass. On a VPS, configuring SPF, DKIM and DMARC in WHM covers the server side.
4. If authentication passes and mail is still rejected, check whether the server IP is on a blocklist. Preventing email spam and blacklisting explains how to check and get delisted.

How to prevent it

• Set a realistic mailbox quota when you create an account, and have webmail or your phone archive old mail yearly.
• Whenever you move mail to or from Google or Microsoft 365, update the MX records and Email Routing on the same day.
• Keep SPF and DKIM green in Email Deliverability, and re-check it after adding any new service that sends as your domain.
• Use SMTP authentication for website forms (a plugin such as WP Mail SMTP logged in to a real mailbox) instead of PHP mail, so form mail is traceable and passes SPF.
• Send newsletters through a mailing service, not your hosting mailbox.