• 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

K

kw1162

Guest
I recently moved from IMail and RAQ, to Plesk as a single server hosting solution. The Plesk has generally worked ok, but the Spamassassin is not helping much. Training for some of my customers has started to hang the server. Does anybody know of a good configuration for this, or just a better product to use?
Thanks
kw
 
Note that another way to train Spamassassin is to upload spam filter rules manually.


You may download spamassassin rules for example from:
http://www.rulesemporium.com/rules.htm


You need to put them to %plesk_dir%Additional\Perl\site\share\spamassassin
in Plesk for Windows.

Then restart Plesk Management Service


In the Plesk for Linux these configuration files should go in the site-specific area - typically /etc/mail/spamassassin or /etc/spamassassin. All files in this directory matching *.cf will be processed in lexical order.

If you put the *.cf files in /etc/mail/spamassassin then they are applied to all users on the system.

If you want to make the rules specific to one user, its different. Putting the *.cf files in the user's $HOME/.spamassassin/ directory won't work, they actually have to be in the $HOME/.spamassassin/user_prefs file.


You may learn more from the following article:
http://wiki.apache.org/spamassassin/WhereDoLocalSettingsGo
 
Back
Top