• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Make SPF check ignore SPF type DNS records

TobiasP

Regular Pleskian
Server operating system version
Debian 9.13
Plesk version and microupdate number
18.0.43 Update #1
I currently face the issue that an external sender is sending mails to me and has an SPF record configured as a TXT (as it should be) but also an SPF Type DNS Record which does not designate the same servers as the TXT recrord.
It seems that the SPF check mechanism plesk uses gives higher priority to an SPF type record and therefore the SPF checks for mails from this domain fails.

is there a way to disable/ignore the SPF Type DNS record lookup for a sender domain?
 
hello @TobiasP,

there's no ability in Plesk to ignore SPF record type in case TXT exists.
moreover, at RFC4408 you can find that
If any records of type SPF are in the set, then all records of type TXT are discarded.

so, this is correct behavior.

IMHO, such sender should update all their DNS records accordingly.
 
yes I know - but what if the admins of this domain don't understand what the issue is and won't remove the SPF record... I'm the one getting the blame since they say "everybody else is receiving our emails" (probably because other recipients don't check the SPF so strict or the SPF type record not at all)
so maybe there is a way to allowlist the domain so no spf checks are performed on my side?
 
Back
Top