Actually a mail in doubt is mission-critical for a normal functioning of my app, and a SPF dysfunction has worse consequences – we beheld that some hosts have combined my domain to their spam blacklist. So, this not a pardonable issue.
Thankfully, I’ve solved a problem and it wasn’t formidable to do.
I’m using this site on a VPS, that hosts several domains. The base IP for a VPS is A.B.C.X (for example)
this one site in doubt has a dedicated IP, A.B.C.Y (for example)
So, a “A” record for a domain is A.B.C.Y, though a mail use is all hosted on a VPS, that is A.B.C.X. Atlanta Stove Repair . They don’t match, and that’s because a SPF Test failed.
My SPF record states “v=spf1 a mx -all” , definition a IP of a sender-host contingency compare a IP in a “A” record. It didn’t.
Rather than bitch with a IPs, a resolution was distant simpler. we altered a SPF record to:
“v=spf1 a mx ip4:A.B.C.X -all”
Thus permitting a base VPS mail use to send mail imagining from my domain.
Wait an hour for a DNS to propagate… afterwards we sent another exam summary to spf-test@openspf.org
the response:
Now a SPF exam passes. jdbyrider .
SPF is an keen art; we can conclude how easy it is to ignore, or configure badly. But now we know a significance of doing it, and doing it right. The initial time around we was merely pasting in an ignorant suggestion, and but meaningful it my SPF exam has been unwell for a prolonged time. It took me a integrate of hours to review a small deeper, know how SPF works, how to exam if it is working, and figure out a solution. chevrolet dealerships .
I wish this thread helps someone overcome a same problems.