• 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 per-user configuration

tkalfaoglu

Silver Pleskian
Server operating system version
Rocky Linux 8.9
Plesk version and microupdate number
Obsidian latest
Hello everyone!
Some (strange) user wanted to get all his junk mail delivered. I checked and he already disabled his Spam Filter setting in his mail settings.
I checked the disk and this is what I found at /var/qmail/mailnames/domain/user/.spamassassin/user_prefs file:

#ATTENTION!
#
#DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY,
#SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED.
required_score 7.0
rewrite_header subject
Shouldn't this file reflect that SA is disabled for this user? I changed the required_score to something very high so his mail wouldn't get filtered. but perhaps this should be done automatically when the user disables his/her spam protection settings?
 
If SpamAssassin is disabled for an account, the configuration file has no effect. You can check your /var/log/maillog for incoming mails for that address. SpamAssassin should not show up in that sequence.
 
many thanks. I thought the config file would "automagically" be used by spamassassin as long as "per user" parameter was specified when launching spamd.
 
If SpamAssassin is disabled for an account, the configuration file has no effect. You can check your /var/log/maillog for incoming mails for that address. SpamAssassin should not show up in that sequence.

Hi, wouldn't the SpamAssassin server-wide rules (if active) apply to that user also? Even if the individual user_prefs do not?
 
Back
Top