Michael Chapman wrote:
> Hi there:
>
> This should be a fairly simple question for the experts out there ...
> everything I'm receiving is being blacklisted, and the reports
> indicate that all these messages are flagged as "USER_IN_BLACKLIST."
> Where? I don't have a user_prefs, and my global is really simple:
First, I assume by your "global" you mean your local.cf
Have you tried the simple approach of commenting out all your
blacklist_from commands?
Do you have *ANY* other .cf files in the same directory as your
local.cf? SA will read ALL of them, and use ALL of them.
Are you sure you're even using the right directory? Try running
spamassassin --lint -D and the earlier parts of the debug output should
list all the directories and files SA is using.
In particular this line could be quite useful to you:
[22185] dbg: config: using "/etc/mail/spamassassin" for site rules dir
Along with the lines that follow indicating all the .cf files
Looking at the message headers, I'm assuming you're using SpamAssassin
3.2.2. You really should include that kind of info in your posts.
One part that makes me wonder what's missing is your own system seems to
have generated:
X-Old-Spam-Status: No, score=-0.9 required=8.0 tests=AWL,BAYES_00,
USER_IN_BLACKLIST,USER_IN_WHITELIST autolearn=ham version=3.2.2
I don't see anything in your posted config that would have blacklisted OR
whitelisted the message. But somehow, it got both.
Also, using your same configuration (as posted) I get:
X-Spam-Status: No, score=-2.8 required=8.0 tests=RCVD_IN_DNSWL_MED,
RCVD_IN_SORBS_WEB,RDNS_NONE autolearn=ham version=3.2.3
Admittedly a different version of SA, but that shouldn't affect the
white/blacklist decisions.
That's telling me there's more to your config than you think. Personally, I
think the --lint -D should take you pretty far into finding out what's going
on, or at least give you all the files you need to grep.
You could also try running a message through spamassassin -D on the command
line. This would tell you which exact address matched a blacklist, but you'd
have to wade deep into the debug output to find it.
