• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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