problem with cpanel installing Mail SpamAssassin

[Mani]

got 2 servers online today and after installing cpanel found spamd is failed

then i did run

/scripts/fixspamassassinfailedupdate

ended up with

Spamassassin Update Failed, reinstalling!
Method: Perl Expect
Fetching CPAN timestamp...Done
Testing connection speed...(this could take a while)...Done
Ping:8.249 Testing connection speed to www.mednor.net using pureperl...(159250.00 bytes/s)...Done
Ping:15.654 Testing connection speed to mirrors.kernel.org using pureperl...(105466.67 bytes/s)...Done
Ping:18.812 Testing connection speed to cpan-sj.viaverio.com using pureperl...(20953.33 bytes/s)...Done
Three usable mirrors located
Three usable mirrors located
Mirror Check passed for www.mednor.net (/index.html)
commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm'
CPAN: File::HomeDir loaded ok (v0.65)
CPAN: Storable loaded ok (v2.16)
Going to read /home/.cpan/Metadata
  Database was generated on Sat, 28 Jul 2007 20:51:00 GMT
cPCPAN: Module holdback ( held back to 3.2.1)
Running get for module 'Mail::SpamAssassin'

  The module Mail::SpamAssassin isn't available on CPAN.

  Either the module has not yet been uploaded to CPAN, or it is
  temporary unavailable. Please contact the author to find out
  more about the status. Try 'i Mail::SpamAssassin'.
Running get for module 'Mail::SpamAssassin'
CPAN: Digest::SHA loaded ok (v5.45)
CPAN: LWP::UserAgent loaded ok (v2.036)
CPAN: Time::HiRes loaded ok (v1.9707)
CPAN: YAML loaded ok (v0.65)
Fetching with LWP:
  http://69.72.164.155/pub/CPAN/authors/id/CHECKSUMS

Warning: No checksum for cPCPAN in /home/.cpan/sources/authors/id/CHECKSUMS.

The cause for this may be that the file is very new and the checksum
has not yet been calculated, but it may also be that something is
going awry right now.
Proceed? [yes]
CPAN: File::Temp loaded ok (v0.18)
Package seems to come without Makefile.PL.
  (The test -f "/home/.cpan/build/anon-5pWQhE/Makefile.PL" returned false.)
  Writing one on our own (setting NAME to MailSpamAssassin)
Unable to install module Mail::SpamAssassin, because it cannot be fetched from CPAN at /scripts/cPScript/cPCPAN.pm line 258.

upcp --force did not help

I installed SpamAssassin 3.1.9 manually and worked but wanted to find out how to solve this exact problem

currently on cp v 10 perl 5.8.8 but did try all of them untill the current verison all the same

the servers resolve domains and ping other domains every thing else seems to be ok just cant think where this issue pops from maybe too sleepy to think more.

[jerrybell]

I'm having the same problem with an existing set of cpanel servers. It seems that the cpanel supported version (3.2.1) was taken off of cpan due to some vulnerabilities, and now cpanel is no longer able to install spamassassin.

[Mani]

The problem is that the author removed SpamAssassin 3.2.1 from all servers, and it caused problems

you have to install 3.2.2 your self untill cpanel solve this thru update

[deddy]

I checked CPAN regarding version 3.2.2
It isn't available there.
What's up with Mail::SpamAssassin on CPAN ?

[Mani]

hey deddy

it seems related to this but not sure

http://www.securityfocus.com/bid/24481

[Igor The Troll]

Okay guys I know it is a bug but what can we do?

I am on a shared server hosting account and they are not telling me anything but wait for an update from Cpanel.

Can you tell me when will the update be out?

If it is going to take a long time is there a third party script that I can install in my account that will stop Spam?

Thank you

[Mani]

Igor

ask your host to install it manually

they can install 3.1.9 or even 3.2.2 untill cpnael do some thing about this

[deddy]

version 3.2.1 is back on CPAN. You should be able to install it.

Please run

/scripts/checkperlmodules

This should fix your problem

If you are not able to run this command as "root"
ask your provider to do this for you.

[Mani]

I think you mean

/usr/local/cpanel/bin/checkperlmodules

[deddy]

I think you mean

/usr/local/cpanel/bin/checkperlmodules

That's the same

[chirpy]

cPanel moved checkperlmodules to /scripts while back in v11.

As Mani has said, spamassassin developers screwed up their CPAN repository entry, so you either have to wait their fix to propagate the CPAN network or install from source.

[Mani]

nice to see ya here chripy

well they seems fixed it, it works fine now unless if they change again

for my self since I depend on stables only am still V 10

[opt2bout]

We're running 3.22 as installed by one of the latest cPanel 11 (C15845) updates, but even with SpamAssassin turned on by the client's control panel, we're not getting any checks at all.

SpamD is running, and if we run a few of the messages through spamassassin in test mode, we get high scores and the correct proposed subject rewrites.

Currently we get nothing if it goes through Exim, no header rewrites with spamassassin version information, no score, nothing.

Does anyone else have this problem? Any suggestions?

EDIT: turning SA on globally doesn't make any difference

[sparek-3]

I believe this may be a problem with SpamAssassin 3.2.2 and DCC. I saw a lot of problems regarding this overnight, apparently most of our servers were upgraded to SpamAssassin 3.2.2 last night and we have been having a lot of spam problems since.

I created a patch that should resolve this. I got the information for the patch at:

http://www.gossamer-threads.com/list...commits/105775

I just applied the patch this morning, and so far everything looks better, but as always proceed at your own risk.

You probably want to back up the affected file first. This will only work if you are running Perl 5.8.8. It might work if you change the paths accordingly, but I don't know, all of our servers are running Perl 5.8.8.

cp /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Util.pm /root

Now apply the patch:

chmod 644 /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Util.pm
patch -p0 < spam322util.patch.txt
chmod 444 /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Util.pm
/scripts/restartsrv_spamd

(Is the chmod to 644 and then back to 444 necessary? I'm not sure, at 444 the file is not suppose to be writeable, but you are doing this as root, so I don't know. At any rate the above steps will work, it just may include a few unnecessary steps).

The patch file is included.

Again, proceed with caution in regards to this. If you experience any problems, remember you backed up the Util.pm file in your /root directory on the server so you can always restore it.

[opt2bout]

I believe this may be a problem with SpamAssassin 3.2.2 and DCC. I saw a lot of problems regarding this overnight, apparently most of our servers were upgraded to SpamAssassin 3.2.2 last night and we have been having a lot of spam problems since.

Thanks for the patch.

We initiated a call to the server's hosting provider before doing anything. Their first instinct was that it is a perl issue. However we are running Perl 5.8.7.

After they got through (they didn't document to us what they did), I ended up with SpamAssassin working, in a new and strange way...

The X-Spam-Report header is being populated even if the message is not spam. The header is the typical "This message is spam, ..." message. And, if the message IS flagged as spam, the header stays the same...but the attachment of the original mail message is not created. You basically get the entire message delivered with the Subject header re-written with "***SPAM***"

Not liking this...and not sure if going back to 3.2.1 would resolve the issue...I think we were on 3.1.8 before the cPanel update.

I went ahead an applied your patch just in case...nothing seemed to change before or after.

Thanks