• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question SPF Spam Protection: is it working ?

OverWolf

Regular Pleskian
Server operating system version
Almalinux 9.7
Plesk version and microupdate number
18.0.76u2
Hi,
I've configured Plesk to reject email when SPF fail, but I'm receiving email even though the rule is matched.
Is this correct, or I'm doing something wrong ?

Thank you
 

Attachments

  • SPF_fail.jpg
    SPF_fail.jpg
    13.7 KB · Views: 9
  • SPF_fail2.jpg
    SPF_fail2.jpg
    12.8 KB · Views: 9
  • SPF_setting.jpg
    SPF_setting.jpg
    42.4 KB · Views: 10
Hi,

The SPF Checking mode indicated in your screenshot will result in an SPF reject only when the sending domain has an SPF record and checks against that record result in fail.

You might want "Reject mail when SPF does not resolve to pass", but that will also reject any emails from domains that didn't publish an SPF record or your server can't resolve the SPF record of the sending domain.

1773049005898.png

Having multiple SPF records for the same domain/subdomain will result in SPF check failures.

I recommend keeping "Reject mail when SPF resolves to fail".
 
Back
Top