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

Question Spamd, per-user configuration

tkalfaoglu

Silver Pleskian
Server operating system version
Rocky Linux
Plesk version and microupdate number
Plesk Obsidian 18.0.64 Update #1
Hi. I'm trying to enable per-user settings of spamassassin. Here is what I have:

Code:
# more /etc/sysconfig/spamassassin 
# Options to spamd
SPAMDOPTIONS="--create-prefs --daemonize --helper-home-dir=/var/qmail --max-children=5  --razor-home-dir='/var/lib/razor/' --razor-log-file='sys-syslog' --username=popuser --user-config --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin"

However I often see:
spamd: handle_user (userdir) unable to find user: '[email protected]'

I check the disk, and the
-rw------- 1 popuser popuser 193 May 26 2023 user_prefs
file exists at the /var/qmail/mailnames/somedomain.com/info/.spamassassin directory.. and the file is older than today, i.e. it was not just created after this warning message.

I even check the file as popuser, and popuser HAS access to that file no problems.

What am I doing wrong :)
Thanks, -t
 
Back
Top