General Topics

How I Fixed My cPanel Email Not Receiving Emails After Reconnecting My Domain to Cloudflare (Complete Guide)

If your domain expired, you reconnected it to Cloudflare, your website works, but your company email (admin@yourdomain.com, info@yourdomain.com, etc.) suddenly stopped receiving emails, this guide will help you fix it.

After spending hours troubleshooting a real-world case involving Cloudflare, cPanel, TrueHost, MX records, and DNS propagation, I discovered that the issue wasn't the mailboxes themselves—it was the DNS records that changed after the domain was re-added to Cloudflare.

In this guide, I'll show you exactly how to diagnose and fix the problem.

The Problem

Here's what happened.

  • The domain expired.

  • After renewing it, the domain had to be re-added to Cloudflare.

  • The website started working again.

  • Existing cPanel email accounts still existed:

    • admin@macrohustle.com

    • hr@macrohustle.com

    • healthcare-unit@macrohustle.com

  • But no incoming emails arrived.

Outgoing email wasn't the issue. The real problem was that incoming mail wasn't reaching the server.

Why This Happens

When a Cloudflare zone is deleted and recreated, Cloudflare may not restore all your previous DNS records automatically.

Your website can work perfectly while your email silently fails because email depends on different DNS records.

The most important records are:

  • MX records

  • Mail host records

  • SPF

  • DKIM

  • DMARC

Even if your mailboxes still exist inside cPanel, the internet won't know where to deliver messages if those DNS records are wrong.

Step 1: Confirm Your Email Accounts Still Exist

First, log into cPanel.

Go to:

Email → Email Accounts

You should see your existing mailboxes.

If they're still there, don't recreate them.

The problem is almost certainly DNS.

Step 2: Verify Email Routing in cPanel

Go to:

cPanel → Email Routing

Make sure:

  • Local Mail Exchanger is selected.

This tells your server that your email accounts live on that server.

If it's set to Remote Mail Exchanger, incoming mail will fail.

Step 3: Compare Cloudflare DNS with cPanel Zone Editor

This turned out to be the biggest clue.

Inside cPanel → Zone Editor, the correct records looked like this.

Record

Value

A

145.239.19.134

MX

macrohustle.com

mail

macrohustle.com

webmail

145.239.19.134

cpanel

145.239.19.134

whm

145.239.19.134

But Cloudflare initially had different MX records pointing somewhere else.

That prevented incoming mail from reaching the server.

Step 4: Fix Cloudflare DNS

Open:

Cloudflare → DNS → Records

The final working configuration became:

Type

Name

Content

Proxy

A

@

145.239.19.134

Proxied

CNAME

www

macrohustle.com

Proxied

MX

@

mail.macrohustle.com

DNS Only

CNAME

mail

macrohustle.com

DNS Only

A

webmail

145.239.19.134

DNS Only

A

cpanel

145.239.19.134

DNS Only

A

whm

145.239.19.134

DNS Only

Important

The following records must never be proxied.

They should remain gray (DNS Only):

  • mail

  • webmail

  • cpanel

  • whm

  • MX

Using the orange Cloudflare proxy on mail-related records often breaks mail services.

GENUINE BRAIN TEST

Based on the article, which word best completes this sentence: "After approval, _____ can download your app just like any other Android application"?

Step 5: Test Your MX Records

After updating DNS, don't guess.

Use MXToolbox.

Enter your domain.

You should see something similar.

The successful result showed:

  • MX published

  • mail.macrohustle.com

  • IP 145.239.19.134

That confirmed the internet was now routing email to the correct server.

Step 6: Check Webmail

One confusing moment happened during troubleshooting.

Opening:

mail.macrohustle.com

loaded the main website.

At first this looked like an error.

It wasn't.

The correct login is:

webmail.macrohustle.com

If Roundcube opens, that means:

  • your mail server is running,

  • your mailbox exists,

  • authentication works.

That's actually a good sign.

Step 7: Track Incoming Mail

If mail still doesn't arrive, don't keep changing DNS.

Instead, open:

cPanel → Track Delivery

Send yourself a Gmail message.

Then refresh the page.

Possible results include:

Status

Meaning

Accepted

Server received the mail

Deferred

Temporary delivery problem

Rejected

Server refused the message

No entry

Mail never reached the server

This page gives the exact SMTP response from Exim, making it much easier to diagnose server-side problems.

Step 8: Check Outgoing Mail

Inside Roundcube:

  1. Log into your mailbox.

  2. Send an email to Gmail.

If Gmail receives it:

  • SMTP works.

If it fails:

  • Roundcube usually displays the exact error.

This separates incoming mail issues from outgoing mail issues.

Common Mistakes That Break cPanel Email After Cloudflare

Here are the biggest mistakes we discovered.

Wrong MX Records

Using:

  • route1.mx.cloudflare.net

  • route2.mx.cloudflare.net

  • route3.mx.cloudflare.net

when you're actually using cPanel mailboxes.

Missing Mail Host Records

Without:

  • mail

  • webmail

  • cpanel

  • whm

your mail services become inconsistent.

Proxy Enabled

Never proxy mail-related records.

Use DNS Only.

Wrong Email Routing

Always use:

Local Mail Exchanger

when your mailboxes live inside cPanel.

Final Working Configuration

After fixing everything, the setup looked like this.

Service

Status

Website

Working

Cloudflare DNS

Correct

MX Records

Correct

SPF

Present

DKIM

Present

Webmail

Working

Local Mail Exchanger

Enabled

The only remaining recommendation was adding a DMARC record to improve email security.

Example:

Host: _dmarc
Type: TXT
Value: v=DMARC1; p=none;

You can later change p=none to quarantine or reject after confirming everything works.

Key Takeaways

If your cPanel company email stops receiving messages after reconnecting your domain to Cloudflare, don't immediately recreate your mailboxes.

Instead:

  • Verify your email accounts still exist.

  • Set Local Mail Exchanger.

  • Match Cloudflare DNS with your cPanel Zone Editor.

  • Keep mail records as DNS Only.

  • Verify MX records using MXToolbox.

  • Use Track Delivery to see exactly what happens when someone emails your domain.

Following these steps can save hours of frustration and restore your business email without rebuilding your entire email setup.