Anyone having luck with fixing the clapf cron errors?
unknown key: "avg_addr"
unknown key: "avg_port"
relate to settings in /etc/clapf.conf for AVG's avgscan - not sure about this one yet:
unknown key: "spaminess_of_too_much_spam_in_top15"
Running yum --enablerepo=atomic install clapf leaves quite a few things out (e.g. /var/lib/clapf/stat/clapf.stat, mysql/db setup and cron errors), reading up on the various aspects (postfix+clampf+clamav+spamasaassin) of documentation doesn't quite cover everything.
Currently using Plesk's Mail->Preferences->DNSBL service to replace most of spamdyke did (although Spamdyke DID disable BL checks on port 587 if the user authenticated - may pose a spam loophole later). Postfix sends messages out to clamav successfully, but spamassassin never seems to come into the mix, this lets a lot of spam through that was previously caught by the Qmail system - Switched over to postfix yesterday after problems with Qmail on Plesk 9.3 (as noted by others: viewtopic.php?f=4&t=3771
), bounced messages kept getting stuck in a loop eventually maxing out CPU/memory. The combination of spamdyke (without greylisting), qmail-scanner, clamav, spamassassin+bayes_db was catching 99.9% of bad mail, but the loop/overload problem was untennable.
I feel committed to sticking with Postfix as I can see that fine-tuning has the potential to yield great results, but at the moment set-up is catching 90% of spam and there are a lot of errors with cron and missing mysql database.
I will post on any successs as and when I get there, if anyone else has any tips I'd be grateful to share and produce docs/guide from the combined findings.