Julian Underwood wrote:
Here's another example message:
http://168.100.199.67/message2.txt
This message contains both SURBL hits, a correct score total, and
appropriate mark up.
I think the problem is SURBL points aren't being tallied or even
calculated when a spam first comes in, therefore these messages don't
get tagged. I tested it by sending a URL to my organization which
grossly triggers SURBL, yet it goes through not being tagged as spam.
Any thoughts on how I could troubleshoot this? And perhaps rectify it?
Maybe some log I could view? The annoying thing is if I check a message
manually with spamassassin at the command-line, it calculates the points
correctly.
Sample messages that show it working, quite obviously, won't help to
resolve your problem of it not working.
If you want to provide a sample, provide a copy of a mail that "didn't
work", that is, one that shows the problem.
In any case, I'll just guess. Remove the "-L" from the SPAMDOPTIONS in
/etc/sysconfig/spamassassin. Restart spamd, and send me some food. :)
Daryl