• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

SPF problems

B

bcrooker

Guest
I am running Plesk 9.0.0.2 and am having issues with SPF.

I have our server set up to create the records only. We are using Qmail. When I send email directly through our server using authenticated SMTP (with SSL enabled or disabled, sending using port 25 or 587) the email always gets tagged as "Received-SPF: neutral".

I am pretty sure that this setup worked fine with previous versions of Plesk, and am wondering if the difference is how they are doping SPF and SA now (with the before-local hooks).

Is this correct behavior? Shouldn't I be able to send email using authenticated SMTP through our server without it getting a neutral SPF tag?
 
Back
Top