Hell Ryan,
All blacklisted addresses in SpamAsassin should be immediately rejected. You should see in
/home/$user/.spamassassin/user_prefs
-
Code:
blacklist_from domain.tld
If you're modifying Exim's Reject Spam score threshold the following should be referenced:
Apache SpamAssassin™ reject spam score threshold | This option sets the spam score that Apache SpamAssassin™ uses to reject incoming messages.
- Enter a positive or negative number, which may contain a single decimal point.
Important:
If you enter a value that contains an integer greater than or less than 0 and a decimal point, Apache SpamAssassin multiplies the value that you enter by a measure of ten. For example, if you enter a spam score threshold of 1.6, Apache SpamAssassin sets the threshold to 16.
For example, if you enter a spam score threshold of 1.0, Apache SpamAssassin sets the threshold to 10.
- Select No reject rule by spam score to disable this option.
For more information, visit Apache SpamAssassin's documentation. |
So, with what you have set right now, it's most likely not going to actually reject anything. What you should set if you're trying to reject mail with score X or higher is a number ike 5.0 if you're conservative or 10.0 if you're wanting to be a bit more lenient.
If you set this to 5 this would mean that if SpamAssassin scan's the mail and it receives a score of 5 or higher (the higher the score the more likely it's spam) it will automatically be rejected.
In my local.cf I have blacklisted domains, senders, and a few subject lines
Can you show me what you're putting in local.cf?
All I would like to do is reject those. Now they just come in marked SPAM.
What are you adding specifically? I used *@gmail.com and found that the mail was automatically attributed a score of 104.8:
Code:
Warning: "SpamAssassin as myuser detected message as spam (104.8)"
(the 4.8 is a result of some other test's I have added on this server for spam assassin testing purposes, normal gmail email shouldn't come through with this high of a score)
I also see that the filter that is setup to reject mail when it's got a high score (like this does) is being flagged:
Which means that it just sent the email to /dev/null (essentially deleted it)