Email stuck at (Pending Setup: validating MX record )

thargy said 1 year, 1 month ago:

And when I click Server Addresses for unclecraig.com it says the following under the ‘MX Records’ section -

Actual Settings:
No MX records were found for unlcecraig.com

I am hosting my DNS on CloudFlare.com – and have an identical setup with thargy.com and unclecraig.org and can confirm that in those 2 cases everything is working fine. However the unclecraig.com domain transferred to you yesterday and cloudflare gained control of the DNS ~16 hours ago – since then you have been throwing away my mail on my main account.

Despite the help taking you to an article about “Pending Setup: MX Error” (which mine doesn’t say), there is no retry link (as suggested in the article) and no way to be able to force the system to check the MX records again – which I know are correct.

Please respond quickly as you are bouncing emails!!!

sherrod said 1 year, 1 month ago:

@thargy,

After reviewing a DNS Look up on the Domain I am not showing that the Domain has any MX Records associated with it. You will want to use the steps found in the following like to locate the proper MX Records for your Email Account. Once located contact your Hosting Provider and have them update the MX Records for the Domain:

Checking Your MX Record Settings in the Email Control Center.

Sherrod

thargy said 1 year, 1 month ago:

[Re-edited reply as original got rejected as it had email addresses in it (because it was debugging emails!)]

Thanks but you it’s apparent you didn’t even read my message before replying and sending a generic link.

I said in my message that I checked the Server Addresses and the GoDaddy was incorrectly showing that there were no MX records, I even sent an example email to support which shows the following -

“n1pismtp01-001.prod.ams1.secureserver.net rejected your message to the following e-mail addresses:

<OBFUSCATED>unclecraig.com (<OBFUSCATED>unclecraig.com)

n1pismtp01-001.prod.ams1.secureserver.net gave this error:
#5.1.0 Address rejected. “

This email shows that the MX records are correctly routing emails to the GoDaddy servers where they are getting bounced due the account setup not being finalised as GoDaddy is incorrectly asserting the MX records are missing.

Cloudflare was set up with the correct MX records about a week ago, I’ve been waiting for GoDaddy to set the nameserver registration to point at CloudFlares nameservers. That completed ~17 hours ago. Since then GoDaddy has been stuck reporting the ‘validating MX records’ message and asserting there are no MX records.

I have 2 identical working configuration for thargy.com and unclecraig.org set up in exactly the same way which are working.

sherrod said 1 year, 1 month ago:

@thargy,

The initial inquiry was read, and the response was based on the a DNS lookup for the Domain you provided in the error: No MX records were found for unlcecraig.com.

However, after reviewing this once again I apologize for missing the other version of the Domain you provided: unclecraig.com.

A DNS look up of the unclecraig.com domain is showing that you are pointing to the European Region email servers:
smtp.europe.secureserver.net. [Preference = 0]
mailstore1.europe.secureserver.net. [Preference = 10]

As this is the case, I would suggest first to review the Email that was created in the Email Control Center to ensure that the Domain was set correctly as the error you copied from there is showing the Domain spelled: unlcecraig.com.

If it is correctly spelled there and you are still seeing this message I would suggest to simply edit the Email Account and then click ok. This action will force the email system to once again verify the MX Records.

Once again I apologize for missing the difference in the Domain spellings the first time.

Sherrod

thargy said 1 year, 1 month ago:

@Sherrod

Thank you so much! Sometimes it’s impossible to see the wood for the tress. I set up the email address prior to the domain transfer to avoid any downtime (ironically). I set it up with 3 other domains and a lot of DNS records. In doing so I must have accidentally typed unclecraig as unlcecraig and despite spending hours scouring settings I never spotted the typo!

I should now be able to proceed to setup thank you!

Craig

timb said 1 year, 1 month ago:

@thargy

Glad to hear you were able to resolve this issue. Thanks for posting on our support forum!

Tim B