Atomicorp

kudos scott. It all seems to be working without a hitch now. For those following along, the major issue for me seemed to be a conflict in how spamassassin and psa-spamassassin worked (or didn't work) together. So in the end I Uninstalled psa-spamassassin, installed the latest version of SpamAssassin...

I think you hit on it Scott. There was some sort of conflict with Spamassassin and psa-spamassassin. I performed all of the above, adding in a step to upgrade spamassassin from 3.06 to 3.23 from your rpm packages while I was at it. The only issue that raised was Pyzor checks failed, citing an intern...

No difference Scott. Something is definitely screwy somewhere. The only way I can apparently get SA to automatically delete messages is to set it to do that in the Plesk cp for that email address. And then it goes off of the hit setting there, not the SA_DELETE in the qmail-scanner.ini file. Which i...

/etc/sysconfig/spamassassin SPAMDOPTIONS="-d -c -m5 -H" FTR, I did some further checking and the other addresses (or at least the handful I spot checked) are letting through the high hit spam too, so my prior hunch regarding the mailgroup forwarding wasn't necessarily correct. It would app...

Were you ever able to sort out what was happening jrf? Just yesterday I installed Scott's rpm's (clamd razor-agents dcc and pyzor, along with qmail-scanner) that I found in another thread. I'm getting exactly the same thing if I try to set SA_DELETE in the qmail-scanner.ini file, at least with some ...