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

Issue Spamassassin changes not being written to user_prefs

Jllynch

Regular Pleskian
It appears that Plesk isn't writing all settings to the spamassasin user_prefs file when I change them
eg
/var/qmail/mailnames/domain.com/fred/.spamassassin/user_prefs

I turn it off spamassassin for fred in the panel the file still contains;

rewrite_header subject ***SPAM***
required_score 7.0

We have Spamassassin and this set to on in global settings;
Apply individual settings to spam filtering

If I change the score that gets changed in the user prefs file.

Could it be that spamassasin wont turn off if there is email in the /spam ipam folder?

What is the solution?

My product version: Plesk Onyx 17.0.17 Update #32
Update date: 2017/08/26 03:16
Build date: 2017/03/22 17:00
OS version: CentOS 7.3.1611
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2
 
This issue still exists..
anyone?
I tried turning off the spam protection for a user, but the user_prefs file is unchanged.
 
I have a suspicion that spamd is NOT called at all if the user disables the spam checking for his/her email.
So, the user_prefs is not read in that case.. But it needs to be tested.
 
Back
Top