Spam Filtering no longer working after upgrade to cpanel 11

[jlkolpin]

Yah so I'm running stable, server was running great, spam was being blocked, virus email was being blocked, auto updates on (I thought great, one less thing to worry about WRONG)..

Now, this is the first time I've used cPanel but I'm an old web server admin using linux for a long time now so it's not like I'm completely lost here.

Wake up the other morning and wow I got a new version of WHM and email saying SA is not enabled but the email server IS STILL ACCEPTING EMAILS?!?! Does this even remotely sound SANE?

Okay not a problem, went and did what the email said to do, it worked.
checking things out and whoops mail is being dumped.. Checked out logs, they changed how clamav socket is connected to. Not a problem, moved the socket file in clamd.conf FIXED

On the upgrade, my SSL certificate I installed in WHM/cPanel got uninstalled (got some freaked out clients calling me on that one too (more money and time lost). FIXED

So before the "upgrade", Spamassassin was working like a champ. Which comes to my MAJOR sore point here..

I have gone through this forum from one end to another seeing all kinds of issues with the upgrade from perl versions to all kinds of other stuff. My problem is everything is working but spamassassin is allowing all kinds of spam through now.. UNACCEPTABLE

tried sa-learn to no avail, made sure it was doing the internet tests, bayesian was enabled, ect etc.. still getting spam.. What changed and why is there no notifications somewhere in the upgrade notes or whatever saying hey SA has been changed and it's gonna let spam through now (new feature! MORE WORK AND UPSET USERS FOR YOU).

Everything looks great but after seeing this happen I can't work on the server for a few days because I just don't trust it. I have to stop what I do and monitor it to make sure there isn't any other "surprises".

On another note.. this is probably the worst scenario I've ever seen when it comes to developement. STABLE should mean upgrading is STABLE not just that version ran stable for a while or something.. I think y'all need to go back and set up some more reliable quality control or something because people are paying for this software, paying for stable to be stable, and not getting it. I would expect for the cost of cPanel, it would be a tight product.. Right now I have my doubts, please show me otherwise...


aaaagh this makes me so angry

 

[cPanelNick]

Did you upgrade to perl 5.8.8 before updating to cpanel 11?

Did you read the release notes?

http://www.cpanel.net/products/cPanelandWHM/linux/cpanel11/releasenotes.pdf

You could also switch back to the old spam system in the exim config editor in WHM.

Are you messages not being scanned? Does /var/log/maillog or /var/log/exim_mainlog have an errors about spam assassin? Are the any X-Spam headers in the messages?

However, your best bet is to submit a support ticket @ https://tickets.cpanel.net/submit/ This should ensure the quickest resolution.

 

[jlkolpin]

Perl.. how am I supposed to prepare for this when the auto-updates just went and did all this on it's own? Couldn't tell you whether it had the newer perl before or not, never had a perl issue to deal with so..

reading the release notes AFTER the fact is kind of a silly idea.. If I had only known I was going from 10 -> 11 maybe I would have read them BEFORE the upgrade and been prepared instead of busting my ass under pressure from a bunch of users and my boss...

The point I am making here is that the entire update system is NOT SANE.. not for anyone to use because they are just going to wake up with a broke down server... The option shouldn't be there if it isn't presented in a sane manner which from what I am seeing is not the case here... When you call something stable and upgrade it to current stable.. the upgrade process should also be stable.. if you can't make it so, then force that upgrade to be done manually and notify the server admin via email... Make sense? I think so...

 

[rachweb]

Perl.. how am I supposed to prepare for this when the auto-updates just went and did all this on it's own? Couldn't tell you whether it had the newer perl before or not, never had a perl issue to deal with so..

reading the release notes AFTER the fact is kind of a silly idea.. If I had only known I was going from 10 -> 11 maybe I would have read them BEFORE the upgrade and been prepared instead of busting my ass under pressure from a bunch of users and my boss...

The point I am making here is that the entire update system is NOT SANE.. not for anyone to use because they are just going to wake up with a broke down server... The option shouldn't be there if it isn't presented in a sane manner which from what I am seeing is not the case here... When you call something stable and upgrade it to current stable.. the upgrade process should also be stable.. if you can't make it so, then force that upgrade to be done manually and notify the server admin via email... Make sense? I think so...

There is option in the Cpanel to choice manual update. Server Configuration --> update config.

 

[jlkolpin]

There is option in the Cpanel to choice manual update. Server Configuration --> update config.

not the point.. the point is auto-updates should skip updates that could break something and notify server admin that there are updates available that auto-updater could not do because it would break certain parts of the server.. what good is an auto-update function that lets your server become broken while you sleep?

Plus it would be nice for manual updaters to get an email saying there are updates ready to install (with descriptions so we can go check the change logs or whatever is necessary before we are broken) instead of having to go to the interface all the time to check...

The idea is that the auto-updater is worthless and dangerous at this point so why not tweak it a little and make it work like an auto-updater should?

*EDITED*
Don't get me wrong everyone i do think this is a pretty excellent product.. I like most of the changes in the upgraded WHM as well. So don't think I'm trying to cut these folks down I'm just pointing out that their utility has a bad flaw that should probably get fixed somehow...