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

SpamAssassin Bypassing Spam with SPF

F

FFCus

Guest
I've been seeing some spam messages come through that have no indication in the headers that SpamAssassin has checked the message.

The common theme here seems to be that the messages all contain an SPF header such as:

Received-SPF: pass (hotmail.com: domain of [email protected] designates 218.79.139.159 as permitted sender)

Does SpamAssassin give a green light to any message that has this record in the header? Any idea how to stop it if so?

Thanks in adavance -- I haven't been able to find anything on the SpamAssassin site yet.
 
I am having a hard time understanding how Spamassassin works. We have it installed but have no idea if its even working. I get porn spam all the time and it's getting annoying. What have you guys done to prevent this?
 
Back
Top