DKIM & SPF are not transferring over (or not recognize) when email is sent

General Email Routing
1

What is the name of the domain?

worldwidepressnetworkcom

What is the error number?

550-5.7.26

What is the error message?

SMTP error code that indicates your email has been blocked because the sender is unauthenticated

What is the issue you’re encountering

Typically occurs when Gmail detects that the email is missing proper authentication through SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail).

What steps have you taken to resolve the issue?

None

What are the steps to reproduce the issue?

We are currently using Cloudflare for our nameservers associated with our VPS platform via Namecheap WHM/cPanel.
I am encountering issues with email deliverability on my VPS platform through Namecheap WHM/cPanel. When sending test emails to my Gmail account. My messages are being blocked due to ongoing DKIM and SPF issues. Additionally, test emails sent to other providers such as Outlook and GMX are consistently being delivered to the junk email folders, also attributed to DKIM and SPF issues.

I have thoroughly reviewed and verified the DKIM and SPF settings within Namecheap WHM/cPanel, ensuring they match the configurations in Cloudflare’s settings area. Both settings are identical and show as valid.

Anyone assistance in resolving this matter would be greatly appreciated.

2

The domain worldwidepressnetwork.com has no SPF (or even any TXT) record at all.

Are you sure you’re in the correct Cloudflare account in which this domain is active?

Can you share a screenshot of the Cloudflare DNS page?

3

I am trying to send you five screenshots …but new members here are only allowed to send one per post. I will send later today. In, addition I am currently at work now. So, please excuse my response back.

I added a SPF txt in Cloudflare, unless it’s in the incorrect place.:thinking:

For starters here is one screen shot within Cloudflare showing SPF.

Screenshot_20240901-123623
Screenshot_20240901-123623720×1600 79.1 KB

4

Screenshot_20240901-123439
Screenshot_20240901-123439720×1600 72.7 KB

5

Screenshot_20240901-123521
Screenshot_20240901-123521720×1600 96.1 KB

6

Screenshot_20240901-123601
Screenshot_20240901-123601720×1600 123 KB

Last image. Please excuse my delayed response back to you due to my job.:slightly_smiling_face:

7

The SPF and DKIM records in a screenshot are for server2.worldwidepressnetwork.com.

If you’re sending emails as [email protected], then that should pass.

But I guess you’re sending mails as [email protected], which will fail. You need the records at the root domain.

2 Likes
8

:slightly_smiling_face:Again, here is SPF (txt) screenshot on Cloudflare - unless it’s in the incorrect place.

Screenshot_20240901-123623
Screenshot_20240901-123623720×1600 79.1 KB

9

You have no published SPF record for worldwidepressnetwork.com.

You can add one in your Cloudflare DNS.

10

I am sending emails (or wish to send emails as) worldwidepressnetwork.com and not as server2.worldwidepressnetwork.com

I very new to this (a “rookie” so to speak).

How do you place records in the root domain - how do I find? Does these updated configurations go into Cloudflare and Namecheap WHM/cPanel or both?

NOTE: Namecheap WHM/cPanel within it’s dashboard does give me the opportunity of renaming server2.worldwidepressnetwork(dot)com to worldwidepressnetwork(dot)com - will this also help resolve my SPF/DKIM (so to speak)?:thinking:

11

For the second DNS record in the above screenshot:

  1. Click “[Edit]” next to your DNS record(s) containing “server2” in their name.

  2. Remove “server2” from their name.
    “default._domainkey.server2” should become “default._domainkey”.

  3. Click “[Save]”.

For the fourth DNS record in the above screenshot, -

And any other DNS record(s), that you need to change to the root domain, naked domain, apex domain, […]:

  1. Click “[Edit]” next to your DNS record(s) containing “server2” in their name.

  2. Enter your domain, e.g. “worldwidepressnetwork.com”, or “@”, in the name field.

  3. Click “[Save]”.

To prevent further issues with your SPF going forward, also remove the redundant “a” and “mx” mechanisms from it.

Final result: “v=spf1 ip4:162.0.231.113 -all”

12

A post was split to a new topic: Added site and now ERR_SSL_VERSION_OR_CIPHER_MISMATCH

15

Is the Root Domain area located in Namecheap WHM/cPanel or Cloudflare? Please be specific. And if it is under Namecheap WHM/cPanel …they have several SPF/DKIM editing sections (Editing Area Name Needed). Thanks George.:slightly_smiling_face:

16

There is no “area” for the root domain.

Root domain, naked domain, apex domain are all synonyms, that are referring to your domain name, without any sub-domain labels.

E.g. for a host name like “admin.intranet.example.com”, phrases like the root domain, the naked domain and the apex domain will all be referring to the domain name “example.com”.

When you’re using Cloudflare name servers for your domain name, the changes must be made through Cloudflare.

1 Like
18

Thanks everyone. Everything is working perfectly now. See image for settings. And I received a perfect score of 10/10 at mail-tester.com

X2
X21920×858 86.5 KB

2 Likes
19

Thanks …everything is working fine now and I scored a 10/10 at mail-tester.com.

2 Likes
20

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.