• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue SPF validation Failed, but why?

Thera

Regular Pleskian
Server operating system version
Debian 9.13
Plesk version and microupdate number
Version 18.0.44 Update #3
Hey there, i got a new customer in my Server and they got a lot of Problems with incoming Mails. I cant find the Reason. new SPF record set This Morning from -all to ~all

Can you help me?

Thank you!

said: 550
5.7.23 SPF validation failed. : Reason: default (in reply to end of DATA
command)
 
Hey there, i got a new customer in my Server and they got a lot of Problems with incoming Mails. I cant find the Reason. new SPF record set This Morning from -all to ~all

Can you help me?

Thank you!

said: 550
5.7.23 SPF validation failed. : Reason: default (in reply to end of DATA
command)
Domain is bestminutetravel.com
 
Hey there, i got a new customer in my Server and they got a lot of Problems with incoming Mails. I cant find the Reason. new SPF record set This Morning from -all to ~all
An SPF check is always performed against the server of the sender. If your customer has issues with incoming email, changing the SPF record of the domain of your customer does not have any effect. As the issue is (most likely) at the senders domain, which you have no control over (unless it's a domain you own/manage as well of course).

None the less, the link posted by @GwenDragon contains some useful options you could consider.
 
Back
Top