• 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 and Plesk

tkalfaoglu

Silver Pleskian
Dear All,

Having installed and running Spamassassin successfully with Plesk integration, I was wondering if anyone has done some work towards deleting incoming email if the score exceeds some number.

I know Amavis can do that, but I was hoping for a quick hack to the shell that scans each incoming email..

Thanks!
-turgut
 
If you use ART's qmail-scanner package with SA, you can modify the file:

/var/qmail/bin/qmail-scanner-queue.pl

find the line my $sa_delete_site='0'
and modify it.
# st: Spam messages with a score higher than
# (required_hits + sa_delete) should be deleted (or rejected).
# Only relevant if SpamAssassin is used. Score of 0
# means deliver all messages. Defaults to 0.
# If sa-quarantine is set, sa-delete must be greater.
my $sa_delete_site='0';
(down around line 211)
 
Back
Top