• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

SpamAssassin Server wide does not work in 8.0.1

A

AbraCadaver

Guest
I have a 1&1 root server (FC4 2.6.16.33-061227b / Plesk 8.0.1-fc4.build80060613.20).

For spamassassin I have server wide enabled, hits=7, tag the subject with *****SPAM*****

No mails are tagged even blatant spam that is tagged on other spamassassin enabled servers. Also, I thought all emails whether suspected spam or not had some X-Spam headers added to the email? None of my received emails do, spam or otherwise.

In addidtion I have the following MAPS zones: zen.spamhaus.org;bl.spamcop.net;problems.dnsbl.sorbs.net;multihop.dsbl.org;l2.spews.dnsbl.sorbs.net

With the exception of 3 domains with web content and 1 with email accounts all other settings are Plesk default settings (other than stated above).

This worked in 7.5. I just enabled server wide and magically I started receiving spam with the *****SPAM***** subject. I did not upgrade from 7.5, that bombed out horribly so this is a fresh install.

I tried updating to 8.1, however that bombed horribly as well and I reimaged the server. I can't with any confidence ever update Plesk again.

Thanks!
-Shawn

ps -ef|grep spamd
popuser 13372 1 0 10:07 ? 00:00:00 /usr/bin/spamd --username=popuser --daemonize --helper-home-dir=/var/qmail --max-children 5 --pidfile=/var/run/spamd/spamd_full.pid --socketpath=/tmp/spamd_full.sock
popuser 13374 1 0 10:07 ? 00:00:00 /usr/bin/spamd --username=popuser --daemonize --helper-home-dir=/var/qmail --max-children 5 --pidfile=/var/run/spamd/spamd_light.pid --socketpath=/tmp/spamd_light.sock
popuser 13376 13372 0 10:07 ? 00:00:00 spamd child
popuser 13377 13372 0 10:07 ? 00:00:00 spamd child
popuser 13378 13372 0 10:07 ? 00:00:00 spamd child
popuser 13379 13372 0 10:07 ? 00:00:00 spamd child
popuser 13380 13372 0 10:07 ? 00:00:00 spamd child
popuser 13382 13374 0 10:07 ? 00:00:00 spamd child
popuser 13383 13374 0 10:07 ? 00:00:00 spamd child
popuser 13384 13374 0 10:07 ? 00:00:00 spamd child
popuser 13385 13374 0 10:07 ? 00:00:00 spamd child
popuser 13386 13374 0 10:07 ? 00:00:00 spamd child
root 29430 29327 0 13:57 pts/1 00:00:00 grep spamd

service spamassassin status
spamd (pid 13386 13385 13384 13383 13382 13380 13379 13378 13377 13376 13374 13372) is running...

cat /etc/mail/spamassassin/local.cf
required_hits 5
report_safe 0
rewrite_header subject *****SPAM*****
required_score 7

cat /etc/mail/spamassassin/spamassassin-default.rc
# send mail through spamassassin
:0fw
| /usr/bin/spamassassin

cat /etc/mail/spamassassin/spamassassin-spamc.rc
# send mail through spamassassin
:0fw
| /usr/bin/spamc

cat /etc/mail/spamassassin/init.pre
# comments ...

# RelayCountry - add metadata for Bayes learning, marking the countries
# a message was relayed through
#
# loadplugin Mail::SpamAssassin::plugin::RelayCountry

# URIDNSBL - look up URLs found in the message against several DNS
# blocklists.
#
loadplugin Mail::SpamAssassin::plugin::URIDNSBL

# Hashcash - perform hashcash verification.
#
loadplugin Mail::SpamAssassin::plugin::Hashcash

# SPF - perform SPF verification.
#
loadplugin Mail::SpamAssassin::plugin::SPF
 
Additionally, I just noticed that if I go to a current email address in the control panel, that spamassassin is off, but if I click Mailbox I can enable it. Also, if I create a new mailbox in this domain or another, spam filtering is available and checked by default.

This, even though SpamAssassin is set to Server Wide settings and Personal Settings is not checked.

This is only info, I'm not concerned if users can have their own personal spamassassin settings or not, this is just weird. Is there any difference between how the server wide settings work and how the personal settings work?

-Shawn

Edit: O.K. I see why this is the case, it just allows users to get the Spam icon enabled to set preferences.

SpamAssassin is still not working though.

This seems to be a common issue here that has not been resolved. Maybe someone from SWsoft should look at it!?!?
 
Back
Top