Spamassassin not using blacklist to mark emails

My spamassassin installation is not using any of my blacklist items to score messages. Currently I have three custom blacklist files in my /etc/mail/spamassassin folder. contains manually entered blacklist entries. contains specific entries that I wanted to keep separate from other manual entries. contains about 50 items specifically designed to blacklist messages from certain domains in the form of: blacklist_from *@*.vu

None of these blacklist items are being used to flag messages in SA. Running 'spamassassin -D --lint' reveals no errors and shows all files being loaded.

I'm at a loss.
Who is Participating?
Tekz08Connect With a Mentor Author Commented:
Alright I just figured this out. Turns out that MailCleaner uses the spamd daemon and had the siteconfigpath set in spamd.conf to /usr/mailcleaner/share/spamassassin and did not mention /etc/mail/spamassasssin at all.

I moved my custom config files over to that directory and the rules started working after restarting services.

Thanks for participating.
John HurstBusiness Consultant (Owner)Commented:
It has been a while since I have used Spamassissin. In the version I used, blacklist entries were in user_prefs, but a newer version might be different.

More importantly, I had difficulty with *@*.vu.  I use *.vu or *.ar or *.whatever. That worked very well.  Use the following to unblacklist from *.de

blacklist_from   *.de
unblacklist_from *
whitelist_from   *

What I suggest you do is create a rule you want working and see if you can make one file work.

As I noted, it has been a long while since I have used Spamassissin since my mail now gets filtered by

.... Thinkpads_User
John HurstBusiness Consultant (Owner)Commented:
@Tekz08 - Any follow up?

Check the message headers of one of your emails. Do you see this?

Return-Path: <>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on my mailserver
X-Spam-Level: **
X-Spam-Status: No, score=2.6 required=5.0 tests=HK_RANDOM_FROM,
      autolearn=no version=3.3.2
X-Original-To: Me
Delivered-To: Me

... Thinkpads_User
We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

Tekz08Author Commented:
I switched my top-level domain blacklists over to the *.de format but it's still not working properly.

All my blacklists and custom rules are not being applied, even though spamassassin -D --lint shows that they are being read.
John HurstBusiness Consultant (Owner)Commented:
Thanks for the update. I am an end user so I have limited operating knowledge, so some questions:

1. Per an earlier post, what do your mail headers say (Outlook headers for example). Is Spamassissin working at the user level?

2. Are you setting up user rules? I could not tell from the long output list. But each user needs a separate rules file so my rules can be different than yours.

3. Have you tried removing and then re-installing Spamassissin?

Thanks, ... Thinkpads_User
Tekz08Author Commented:
Figured out solution.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.