• 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 Just Stopped Working

L

lloy0076

Guest
I'm using Debian still on 7.5.4.

Specifically:

psa v7.5.4_build75051014.16 os_Debian 3.1

beijing:/opt/psa/bin# cat /etc/apt/sources.list
#deb file:///cdrom/ sarge main

deb https://autoinstall.plesk.com/debian PSA_7.5.4/
deb http://ftp.filearena.net/pub/debian/ stable main
deb http://ftp.au.debian.org/debian/ stable main
deb-src http://ftp.au.debian.org/debian/ stable main

deb http://security.debian.org/ stable/updates main

I have the following spamassassin(s) installed:

beijing:/opt/psa/bin# dpkg -l | grep spam
ii psa-qmail-rbls 0.70-debian3.1 Antispam DNS-based block lists
ii psa-spamassass 7.5.4-debian3. SpamAssassin support for Plesk.
ii spamassassin 3.0.3-2 Perl-based spam filter using text analysis
ii spamc 3.0.3-2 Client for SpamAssassin spam filtering daemo

Spamassassin has suddenly stopped checking messages. Here's what I did:

1. Purchase spamassassin upgrade
2. Installed spamassassin
3. Turned it on for all users using the group operation
4. Checked to see if it worked

It did 4 days ago.

5. Get back to work
6. Check to see if it worked

It's stopped working.

It is running:

popuser 6204 0.0 2.3 22952 20896 ? Ss Jun11 0:00 /usr/sbin/spamd --username=popuser --daemonize --helper-home-dir=/var/qmail --max-children 5 --create-prefs --nouser-config --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --pidfile=/var/run/spamd/spamd_light.pid --socketpath=/tmp/spamd_light.sock --siteconfigpath=/dev/null
popuser 6205 0.0 2.3 23336 21348 ? Ss Jun11 0:00 /usr/sbin/spamd --username=popuser --daemonize --helper-home-dir=/var/qmail --max-children 5 --create-prefs --nouser-config --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --pidfile=/var/run/spamd/spamd_full.pid --socketpath=/tmp/spamd_full.sock

There's no qmail-scanner anywhere or anything and I can't see any logging by spamassassin at all.

DSL
 
Bletch!

I enabled it in:

/etc/default/spamassassin

...and restarted it via the Plesk interface and now it seems to be working.

(until it stops working again)

DSL
 
Back
Top