{"id":78106,"date":"2026-11-02T16:56:53","date_gmt":"2026-11-02T14:56:53","guid":{"rendered":"https:\/\/tremhost.com\/blog\/?p=78106"},"modified":"2026-11-05T18:52:48","modified_gmt":"2026-11-05T16:52:48","slug":"how-to-troubleshoot-email-not-sending-in-cpanel-a-complete-guide","status":"publish","type":"post","link":"https:\/\/tremhost.com\/blog\/how-to-troubleshoot-email-not-sending-in-cpanel-a-complete-guide\/","title":{"rendered":"Email Not Sending in cPanel: How to Troubleshoot and Fix It"},"content":{"rendered":"<p>When email will not send from a cPanel account, the cause is usually one of five things: wrong SMTP settings in your mail app, a blocked outgoing port, missing or broken SPF and DKIM records, a sending limit on the hosting account, or a sending IP on a blacklist. Start by sending a test from webmail. If webmail works, the problem is your mail app; if webmail also fails, use cPanel&#8217;s Track Delivery and Email Deliverability tools to find the cause.<\/p>\n<h2>Is the problem sending, receiving or both?<\/h2>\n<p>Before you change anything, find out exactly what is failing. Run two tests:<\/p>\n<ol>\n<li>Send a message from your business mailbox to an outside address you can check, such as a personal Gmail account.<\/li>\n<li>Reply from that outside address back to your business mailbox.<\/li>\n<\/ol>\n<p>Write down any error message or bounce you get. A bounce tells you a lot: codes starting with <strong>4<\/strong> (such as 421) are temporary deferrals that the server will retry, while codes starting with <strong>5<\/strong> (such as 550) are permanent rejections that need fixing. The text after the code usually names the reason, such as authentication failure, a full mailbox or a blocked IP.<\/p>\n<h2>Quick diagnosis table<\/h2>\n<table>\n<thead>\n<tr>\n<th>Symptom<\/th>\n<th>Likely cause<\/th>\n<th>Where to check<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Webmail sends, Outlook or phone does not<\/td>\n<td>Wrong SMTP server, port, encryption or password in the app<\/td>\n<td>Email Accounts, then Connect Devices<\/td>\n<\/tr>\n<tr>\n<td>Messages stuck in the Outbox<\/td>\n<td>Blocked port or failed SMTP authentication<\/td>\n<td>Mail app settings; try port 465 or 587<\/td>\n<\/tr>\n<tr>\n<td>Mail sends but lands in spam or bounces at Gmail<\/td>\n<td>Missing or invalid SPF, DKIM or DMARC<\/td>\n<td>Email Deliverability<\/td>\n<\/tr>\n<tr>\n<td>Bounces mention a blacklist or &#8220;blocked&#8221;<\/td>\n<td>Sending IP listed on a blocklist<\/td>\n<td>Track Delivery, then a blacklist checker<\/td>\n<\/tr>\n<tr>\n<td>Sending stops after many messages<\/td>\n<td>Hourly sending limit reached<\/td>\n<td>Ask your host<\/td>\n<\/tr>\n<tr>\n<td>Nobody can email you<\/td>\n<td>Wrong MX records, wrong routing or full mailbox<\/td>\n<td>Zone Editor, Email Routing, Email Accounts<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Step 1: Check the account and password<\/h2>\n<p>In cPanel, open <strong>Email, then Email Accounts<\/strong>. Confirm the address exists and is not suspended. If the user cannot log in, reset the password, then update it everywhere the mailbox is connected: Outlook, phones, tablets and any website contact form that sends through it. A device still using the old password can trigger repeated login failures.<\/p>\n<p>If you have not set up the mailbox yet, follow the Help Centre guide to <a href=\"https:\/\/tremhost.com\/help\/create-email-account\">create an email account<\/a>.<\/p>\n<h2>Step 2: Check the SMTP settings in your mail app<\/h2>\n<p>If webmail sends but your app does not, the app is misconfigured. In Email Accounts, choose <strong>Connect Devices<\/strong> next to the mailbox to see the exact settings cPanel recommends. Then check:<\/p>\n<ul>\n<li><strong>Outgoing server:<\/strong> the hostname shown in Connect Devices.<\/li>\n<li><strong>Port and encryption:<\/strong> 465 with SSL\/TLS, or 587 with STARTTLS. Avoid port 25 for sending from a mail app; many internet providers block it.<\/li>\n<li><strong>Authentication:<\/strong> &#8220;My outgoing server requires authentication&#8221; must be on, using the full email address as the username and the same password as incoming mail.<\/li>\n<\/ul>\n<p>For phones, the <a href=\"https:\/\/tremhost.com\/help\/set-up-email-on-phone\">set up email on your phone<\/a> guide walks through Android and iPhone.<\/p>\n<h2>Step 3: Use Track Delivery to read the server&#8217;s answer<\/h2>\n<p>Open <strong>Email, then Track Delivery<\/strong>. Search for the recipient address and look at the result for your failed message. It shows whether the message left the server, was deferred or was rejected, and the reason the receiving server gave. This is the fastest way to tell a local configuration problem from a rejection by the other side.<\/p>\n<h2>Step 4: Fix SPF, DKIM and DMARC<\/h2>\n<p>Large mail services such as Gmail and Outlook.com check whether a message really comes from a server allowed to send for your domain. If the checks fail, mail is rejected or filed as spam.<\/p>\n<ul>\n<li><strong>SPF<\/strong> lists the servers allowed to send for your domain.<\/li>\n<li><strong>DKIM<\/strong> adds a cryptographic signature to each message.<\/li>\n<li><strong>DMARC<\/strong> tells receivers what to do when SPF or DKIM fails, and where to send reports.<\/li>\n<\/ul>\n<p>Open <strong>Email, then Email Deliverability<\/strong>, select the domain and look for problems. If your DNS is hosted on the same server, cPanel can often repair SPF and DKIM for you. If your DNS is hosted elsewhere, copy the suggested records into that provider&#8217;s DNS panel. A domain must have only one SPF record; if you also send through another service, merge both into a single SPF record rather than adding a second. More on this in the <a href=\"https:\/\/tremhost.com\/help\/emails-going-to-spam\">emails going to spam<\/a> guide.<\/p>\n<h2>Step 5: Check sending limits<\/h2>\n<p>Shared hosting accounts commonly limit how many messages each domain can send per hour, to protect the server&#8217;s reputation. A newsletter or a compromised contact form can hit that limit quickly, after which further mail is deferred or rejected. If sending stops after a burst of messages, ask your host for the limit on your plan, and send bulk mail through a dedicated newsletter service instead.<\/p>\n<h2>Step 6: Check blacklists and compromised accounts<\/h2>\n<p>If bounces mention a blocklist, check the sending IP shown in Track Delivery with a public blacklist checker. On shared hosting, contact your host, who can investigate and request removal. Also check whether one of your mailboxes or a website form has been sending spam: change mailbox passwords, update WordPress plugins and look for messages you did not send in the Sent folder or Track Delivery.<\/p>\n<h2>Step 7: If incoming mail fails too, check MX and routing<\/h2>\n<p><strong>MX records<\/strong> tell other servers where to deliver mail for your domain. In <strong>Domains, then Zone Editor<\/strong>, check the MX records match your email provider&#8217;s values. If your website is hosted in cPanel but your email is on Microsoft 365 or Google Workspace, the MX records must point to that service, not to the web server. The <a href=\"https:\/\/tremhost.com\/help\/edit-dns-records\">edit DNS records<\/a> guide shows where to change them.<\/p>\n<p>Then open <strong>Email, then Email Routing<\/strong>. Use <strong>Local Mail Exchanger<\/strong> if the mailboxes live on this cPanel server, <strong>Remote Mail Exchanger<\/strong> if another service handles email, or <strong>Automatically Detect Configuration<\/strong> to let cPanel decide from the MX records. A wrong setting here makes the server keep mail meant for another provider, or reject mail it should accept.<\/p>\n<p>Finally, check quotas in Email Accounts. A full mailbox, or a hosting account at its disk limit, stops new mail arriving.<\/p>\n<h2>Step 8: On a VPS, check the mail service and logs<\/h2>\n<p>If you run your own cPanel VPS with root access, you can check the mail queue in WHM, restart the Exim mail service from WHM&#8217;s Restart Services, and read the Exim log at \/var\/log\/exim_mainlog for the exact error. On shared hosting you do not have this access; your host does.<\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Why does webmail send but Outlook does not?<\/h3>\n<p>Because the mailbox and server are working, but Outlook has the wrong outgoing server, port, encryption or password. Copy the settings from Connect Devices in cPanel.<\/p>\n<h3>Which SMTP port should I use?<\/h3>\n<p>Use 465 with SSL\/TLS or 587 with STARTTLS, with authentication on. Port 25 is often blocked by internet providers for mail apps.<\/p>\n<h3>Why do my emails reach Gmail&#8217;s spam folder?<\/h3>\n<p>Usually because SPF, DKIM or DMARC is missing or wrong, or the content looks like bulk mail. Fix the records in Email Deliverability first.<\/p>\n<h3>How long do DNS changes take to work?<\/h3>\n<p>Changes to MX, SPF or DKIM records can take a few hours to be seen everywhere, depending on the records&#8217; TTL.<\/p>\n<h2>Next step<\/h2>\n<p>If you have worked through these steps and mail still fails, Tremhost customers can open a ticket or message support on WhatsApp (+263 73 563 9917), Monday to Friday, 08:00 to 17:00 CAT, with the bounce message and the time you sent the test. If you would rather not manage mail on your web hosting at all, <a href=\"https:\/\/tremhost.com\/emailhosting\">Tremhost business email<\/a> starts at $5 a month for up to 50 mailboxes, with spam and virus filtering and SPF, DKIM and DMARC set up for you.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When email will not send from a cPanel account, the cause is usually the mail app&#8217;s SMTP settings, a blocked port, missing SPF or DKIM records, a sending limit or a blacklisted IP. This guide walks through each check in order, using cPanel&#8217;s own tools.<\/p>\n","protected":false},"author":226,"featured_media":78107,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[49],"tags":[],"class_list":["post-78106","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tips"],"_links":{"self":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/78106","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/users\/226"}],"replies":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/comments?post=78106"}],"version-history":[{"count":2,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/78106\/revisions"}],"predecessor-version":[{"id":81252,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/posts\/78106\/revisions\/81252"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/media\/78107"}],"wp:attachment":[{"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/media?parent=78106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/categories?post=78106"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tremhost.com\/blog\/wp-json\/wp\/v2\/tags?post=78106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}