Ok, I searched the forums, and found no other topics that looked like my issue. Just signed up here, have lots of experience with Cpanel from the past. I setup spamassassin to rewrite subject (1) and it is hitting the email's and modifying the headers, but not tagging the subject (rewriting them with ****SPAM****) I've turned it off, reset the user_prefs and re-enabled it, but still no dice.

Its doing MOST of its work, and I guess I could live with it just re-writing the headers and sort with those, but why is it not rewriting the subject lines...

Jason

I've got the server doing sorting via the headers and sending all if to spam@myaddress, but its kind of annoying having to connect and download yet another email address into my mail program.

Any suggestions on why spamassassin is not rewriting subjects? I really dont think this warrants opening a trouble ticket, its not a dire support issue.

Jason

Please send me your control panel link, username and password for it to support@hostony.com

Will check.

Email Sent.

If you figure it out, can you post or email what was broken, so I can fix it in the future if it happens again?

Thanks!!
Jason

Same problem (bucheron.net).

The same thing happend on my old hosting provider with a twist. Spamassassin was hitting the email, but wasnt injecting headers into it or changing the subject. I think it has something to do with the way the email system is setup on systems running cpanel. I've run my own box here for development for years, and I run spamassassin on it w/o problems via qmail, so its just a configuration issue is all. I think its not invoking spamassassin with the correct args... Its like its passing all the args BUT the subject args... The old provider was able to correct the issue, but alas they never told me any of the ways why things on their end were corrected. It will be nice to know why it does that, so if it does it again, we can fix it on our end without having to bother support...

How we comming along with this Stanly?

Jason

Speaking of all the SMTP issues...

Hows that spamassassin problem coming along?

I got an email saying to check it now, but its still not working. I replied to that email a day or so ago as well, still not working, no replies yet..

Jason

We're working with this issue and will keep you updated.

Well, figured out the problem for you guys...

But you'll need to fix it on your end... I cant.

The server is running spamassassin 3.0.0 and the config files are for 2.55. A Re-install of spamassassin will fix that, or just unpack the config files below from the 3.0.0 source...

configuration file "/usr/share/spamassassin/20_body_tests.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_compensate.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_head_tests.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_html_tests.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_meta_tests.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_phrases.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_porn.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_uri_tests.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/23_bayes.cf" requires version 2.55 of SpamAssassin, but this is code version 3.000000. Maybe you need to use the -C switch, or remove the old config files? Skipping this file at /usr/lib/perl5/site_perl/5.8.4/Mail/SpamAssassin/Conf/Parser.pm line 329.

Can this be fixed asap?

Thanks!
Jason

Thank you for adviсe.

We'll take it to consideration.

Not to sit here and beat a dead horse:



But the problem is still not resolved. I submitted a trouble ticket this morning, hopefully we can get it resolved soon..

Thanks
Jason

EDIT:
Quick response on the ticket, they will try and upgrade cpanel tonight (cpanel must be upgraded to upgrade spamassassin, integration) so we'll see if that helps

Thanks for the fast response Gleb

Welp, the problem has been fixed...

A Quick Summary of what happened for those keeping track...

Cpanel in its nightly update, upgraded Spamassassin to the latest build 3.0.0. In doing this, some boner a Cpanel decided not to put this upgrade to a test, and broke spamassassin for all the cpanel users on linux. Good Job!! So in a scramble they released a patch, still didnt work. The end users (hostony) had to rebuild spamassassin etc... Lets hope the nightly update doesnt break it again, Bad Cpanel, Bad...

So the hostony guys have been hitting it hard and after finding some links to an official cpanel bug, and some resolution its been fixed. For the past couple of hours Alec and I have been working hard on this... and he fixed it...

One side note that I've read in the bug reports, don't use the cpanel spamassassin configuration to change your prefs, it supposedly still breaks spamassassin from marking your email.. the most notable change is that you need to delete:

rewrite_subject 1
subject_tag *****SPAM*****

and put in:

rewrite_header Subject *****SPAM*****

This should make it work if yours is still not working.

Again, thanks Hostony Support staff!

Alec, I'd buy you a pint, but I'm sure I wont be in the Ukraine anytime soon, so have one for me!

Jason

If you don't

2 JasonJones:

No problem and welcome to Ukraine

One more thing. It is more reasonable to add

rewrite_header Subject ****SPAM(_SCORE_)****

instead of

rewrite_header Subject *****SPAM*****

Yes, that would be better, to allow you to see how things are scoring and adjust your hits accordingly...

Also for those who need to test it to make sure its formating and reporting properly, its easy. You dont have to type in a long email with all kinds of terms like Viagra, Lolita, Sex etc... just put in this string of characters EXACTLY like it is, on one line, no spaces, all CAPS in the email and it should trigger it.. it scores 1000.0

XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X


Its the GTUBE string, kind of like the ecar string for testing virus programs.

Jason

it just seems that lots of things are going through Spam assassin even though they are obviously Spam. If only we could train the baysean filter

Well, you need to use custom rulesets or lower your score considerably. In its default state, spamassassin will find lots of "problems" with an email and tag it and score it but the score will still be under 10 and it will not be flagged. I go through and create the ruleset where things like the nigerian scam are tagged high, remove links are tagged high etc... things that are common to spam, all tag high, the result is that most of the spam I get is tagged on average in the 30-50pt range and 99.9% of my spam is filtered. Every so often I catch a legitimate email in there, mostly emails from companies that have either sold me something (receipt) or thanking me for signing up. The autoresponders that the companies are using create the email and it LOOKS like spam to the filters, missing headers, html only, guaranteed keywords etc...

I find that scoring known spam rules high is better than just lowering your score to catch more spam. If you just lower your score, you'd need to lower it to about 2-3 to make it semi-effective, you will catch a LOT of innocent email. By leaving the score to 10, and modifying the rulesets to score things like html only as 7 instead of the .02 or whatever it normally does, makes it more effective.

Jason

I too have been having this problem for a while now but I thought it would fix itself (most things do within a few hours/days). I have it rewrite the subject and it does not rewrite them. Also, when I check the message headers it most definetly registers as spam, I have my rules set to very low levels so it doesnt take much to be considered spam. The headers mark it as spam, (i.e. 32/8.00 required) but it does not mark it.

thejokes.net
Server 22

If you read above, there was a change in ver3 of spamassassin that uses a different subject tag. Cpanel will break that so you must edit the file by hand and upload it via ftp or using shell access... the new tag is:

rewrite_header Subject ****SPAM(_SCORE_)****

Give that a whirl...

Jason

Thank you much. I will give 'er a try.