Incidently, we are now receiving hundreds of spam emails per day per account after they stopped updating the rules for 3.3.2, where we used to only receive a few when the rules were being updated daily. I believe the default setup we do in the product is to perform a nightly rules update. That doesn't sound like a lot (especially compared to some of my personal accounts), until compared with the fact ~four months ago I got zero.Then multiply that count across all our employees (some of whom get a lot more spam than I do) and the problem is very real.Spam Assassin is no longer updating rules for the version of SA that c Panel is currently on,and I am seeing an increase in spam as a result.
SA-Update needs to identify which version it is updating so it can provide an update stream that matches the features supported with the version that is actually running on the target machine.
Or if that is to difficult, just provide separate update sites for c Panel to access for each version of Spam Assassin.
This should be a special case, rule updates are no longer provided.
Expect more and more customers opening cases due to high amounts of spam because you guys choose not to provide the current supported version to you clients.
First, the situation with Spam Assassin not updating its rules since April illustrates a problem that c Panel and the maintainer of Spam Assassin need to resolve.
If nothing else, if it takes c Panel six months to incorporate a "current" version of Spam Assassin into c Panel, we should ask that Spam Assassin provide support for that older version during that window of time.We are among others here that have noticed a considerable increase in the amount of spam received in the last few months. We have Spam Assassin 3.4.0 running on our mail server and it has not made an impact on the recent surge of spam.If our experience is any indication, the newer version as-is doesn't help.I asked if there was any way to do that and was instructed to wait for 11.46 In the last two hours I received over 80 new spam messages. As has been mentioned on the forums, one of the first things you should do is remove the bayes data and the autowhitelist data and restart spamd.If you never bother to do that, they eventually become fairly polluted. Those along with sensible management of the Bayesian database and AWL (if you use it, and you probably shouldn't) keep things running best on 3.3.2.We are currently forming a project team to tackle the recent spam problem.