• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Any tips on taming spam with Plesk?

J

JerkyChew

Guest
It seems like a lot of spam is making it through our Plesk server. I was wondering what kind of advice you guys have on how to tame this a bit... Can I customize Spam Assassin from a terminal without worrying about Plesk overwriting anything or breaking itself?

I'm always nervous about modifying stuff on the server from a terminal, as Plesk will sometimes go in and overwrite changes I've made (DNS and subdomains come to mind). Are there any caveats I should know about, or any 'best practices' I should follow when it comes to Spam on Plesk? Thanks in advance.
 
We use a combination of MAPS servers and IP blocking at the firewall which seems to work fairly well.
 
We use 4PSA Spam Guardian on our server, It blocks about 90% on our server.
 
4PSA Spam Guardian

We use Spamguardian from 4PSA . It's really great software to adjust spamassassin settings with multiple level permissions and settings .

http://www.onofis.com
Onofis Internet Servisleri
 
Back
Top