Email ending in SPAM after moving to Cloudflare

[meghan2]

What is the name of the domain?

Ray J. Green | Proven Business Growth Strategies & Leadership Coaching

What is the error number?

na

What is the error message?

na

What is the issue you’re encountering

I have a newsletter that sends from Beehiiv, but since moving to Cloudflare, my domain no longer passes and ends up in SPAM

What steps have you taken to resolve the issue?

Sending the emails from the Beehiiv platform.
The emails headers now do not pass and the emails are marked as SPAM.

A week ago they worked fine, and the headers passed.

I will upload screenshots of the headers and the issues.

What are the steps to reproduce the issue?

Send an email from Beehiiv.
Check email headers.

Screenshot of the error

[meghan2]

[meghan2]

DNS Records

[fritex]

@meghan2

https://rayjgreen.com

At least the TXT record which contains your Google Verification is not correct, please fix this and remove \009 which is in front:

;; ANSWER SECTION:
rayjgreen.com.          0       IN      TXT     "\009google-site-verification=exXxQ-7AFYyResvfFcaCjxfxQqephyAREMT71dEAoHA"
rayjgreen.com.          0       IN      TXT     "v=spf1 include:_spf.google.com include:sendgrid.net include:mail.beehiiv.com include:em6017.rayjgreen.com ~all"

@meghan2

Send an email from Beehiiv.

May I ask how did you setup your Beehiiv custom domain at Cloudflare DNS tab?

How to use a custom domain for your publication - Knowledge Base - beehiiv

Here are some FAQ and ideas:

Sending & Best Practices - Knowledge Base - beehiiv

Did you changed your web domain, instead of email domain?

[epic.network]

Your SPF record has an include mechanism that references a nonexistent SPF at em6017.rayjgreen.com.

SPF Surveyor - dmarcian

[meghan2]

No I didn’t change my web domain instead of my email domain.
And it was working before I moved to cloudflare ad now it’s not.

Here’s how it’s setup.

[meghan2]

[fritex]

Thank you for feedback.

Kindly, make sure those CNAME records are unproxied (DNS-only).

From your 1st screenshot showing DNS records, I can see the:

1. CNAME 1b42._domainkey,
2. CNAME 1b4._domainkey and
3. CNAME em6017 all are proxied

On the DNS tab of Cloudflare dashboard, click on the “Edit” link nearby of the each one-by-one, therefrom click on the to switch it to and Save those changes.
Wait some minutes for those changes to apply. Re-test email sending after 10-15mins.