What is the name of the domain?
example.com
What is the issue you’re encountering
Email works through webmail, but not any email client
What steps have you taken to resolve the issue?
Hi all,
Having some confusing issues with email after setting up cloudflare.
After enabling, website works fine, I can send and receive emails fine from my online portal webmail.mydomain.com so clearly it is working, but all of my email clients stop working.
Not just one. My samsung phone, tablet, PC running outlook and laptop running Thunderbird all stop receiving emails. No error, they all just check and stop, as if no new email was there.
When I revert the name servers back to godaddy defaults, everything works fine immediately.
There must be something off in my MX setup with CF, I assume, as this has all worked fine for years when directly on my registrar host.
Attached is a screenshot of my original DNS with GODaddy, which I imported to CF. Second screenshot attached is with additional A name record for mail, and updated MX record. to try and resolve the problem. With no luck.
What am I missing?
Cheers all.
Screenshot of the error
Set the Proxy status to Unproxied (
) / DNS-only, for the third record in your screenshot, the one named “mail”.
1 Like
Hi @DarkDeviL ,
No change, unfortunately. Server still unreachable from the mail clients.
99% sure this is not the case, but just to ask the question, could it be anything with my SPF record? I have:
“v=spf1 a:mydomain.com ip4:(server-ip) include:secureserver.net ?all”
Should I be adding IPs for the cloudflare servers?
Further suggestions?
Thanks in advance.
While your SPF record does indeed need work, it is not something that will have any affect on client connections.
Make sure your clients are using mail.example.com and not example.com as their server name.
As for the SPF record, you should lose the a: mechanism. Your A record is proxied which means that it will resolve to Cloudflare IPs. Those will never be sending email for your domain. You also never want to end an SPF policy with ?all since it results in the same outcome as having no SPF policy.
No.
Thanks for spotting the SPF error, @epic.network >
Now that you mention it, I actually don’t know how that record got there. It’s a newly registered domain that I registered and I guess that is the default.
I’ve updated that as required.
Regarding your comment:
Make sure your clients are using mail.example.com and not example.com as their server name.
I was previously using just example.com.
I did try updating to mail.example.com on my mobile, still with no luck. Perhaps I didn’t wait long enough and missed the DNS propagation or something.
I will save the records fresh and try again later from my other PCs. Fingers crossed.
1 Like
