• 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.

Input Plesk Email Security - treatment of SPF softfail

TomBoB

Silver Pleskian
Server operating system version
almalinux 8.8
Plesk version and microupdate number
18.0.53
Hi all, asking for input / opinions about the behaviour of SPF softfail in Plesk Email Security, and a possible slight change/adjustment in its behaviour.

Scenario: all our servers use PES. DMARC, DKIM, SPF enabled. SPF is set to "reject mails when SPF resolves to fail (deny)". Didn't choose softfail as that can cause issues when emails are being forwarded.

Just received a mail with SPF status "softfail". Is an obvious spam/phishing mail. Which is what got me thinking again.

Here is the question / suggestion for discussion:
When "reject mails when SPF resolves to fail (deny)" is chosen, currently mail with softfail are just being processed normally and put into the inbox. Which is the standard procedure.
But wouldn't it be a more fitting option under that setup that softfail mails are being put into spam. (Or have a choice between standard procedure and "put into spam")?

As per commonly thought definition that softfail means that an email is probably not authorized to being sent [in contrast to a hardfail where it definitely isn't authorised, and a neutral/pass one].

I'm aware is a fine line to pick in a server setup - to not create/label too many mails falsely as spam, while still catching most spam.
I'm also aware that above behaviour/option is likely outside any RFC, but (at least in my opinion) would be a good enhancement of PES its spam treatment.

[Background; we operate in a corner of the planet where money is extremely tight. So choosing one of the big antispam offerings isn't an option. PES is affordable under the circumstances and works pretty well after we tweaked most spamassassin rules to what fits us and our clients best. But of course always looking to improve where-ever possible]

Cheers,
Tom
 
As a workaround you can change the default score for the SPF softfail rule in Spamassassin to a value that's higher than your spam threshold so that messages with soft failed SPF always are moved to the spam folder.

Code:
score SPF_SOFTFAIL 10
 
Back
Top