SpamAssassin not enabled

[tiggerific]

Hi. Having some trouble getting SpamAssassin enabled on my cPanel. I'm running the following:

WHM 10.8.0 cPanel 10.8.2-R83
RedHat Enterprise 3 i686 - WHM X v3.1.0

I have SA installed and the process shows up in ps:

/usr/bin/spamd -d --allowed-ips=127.0.0.1 --pidfile=/var/run/spamd.pid --max-children=5

I also have it enabled in both Tweak Settings and in the Service Manager.

But... I can't for the life of me get it to appear in the user's cPanel accounts, regardless of which theme I use. I thought it might be a theme issue, so I went directly to the cpanel "spam.html" URL and got the SpamAssassin setup, but when I clicked the ENABLE SPAMASSASSIN button there, I get the following error message:

Attempting to enable SpamAssassin...

Warning! the spamassassin feature has been disabled!


SpamAssassin is now: disabled

So - how on earth do I ENABLE SpamAssassin so that cPanel/WHM knows it's enabled?

Any help would be greatly appreciated as I have searched the forums and Google for hours and not found any answer to this issue.

Thanks.

[avijit]

You may have disabled spamd whm > service manager .

As you disable it there it creates a file /etc/spamdisable which makes it disable. Make sure that the file /etc/spamdisable is deleted.

Delete /etc/spamdisable and restart exim , spamd should function again.

[tiggerific]

Well, you were right. I did have that file. Have deleted it and restarted exim, but still no luck. Restarting exim responded with:

Shutting down clamd: [ OK ]
Shutting down exim: [ OK ]
Shutting down antirelayd: [ OK ]
Shutting down spamd: [ OK ]
Starting clamd: [ OK ]
Starting exim: [ OK ]
Starting exim-smtps: [ OK ]
Starting antirelayd: [ OK ]
Starting spamd: [ OK ]


But I still have the issue of cPanel accounts not showing the SpamAssassin link and the same error about it being disabled when I go directly to the spam.html page.

[avijit]

Which cPanel build are you using ?

Make sure that the SpamAssasin is enabled in the Main >> Server Configuration >> Tweak Settings >> Mail.

Both the following must be enabled :

SpamAssassin
SpamAssassin Spam Box delivery for messages marked as spam (user configurable)

[tiggerific]

WHM 10.8.0 cPanel 10.8.2-R83
RedHat Enterprise 3 i686 - WHM X v3.1.0

I also have it enabled in both Tweak Settings and in the Service Manager.

and "SpamAssassin Spam Box delivery for messages marked as spam (user configurable)" is enabled too.

[avijit]

Try installing the perl module:

/scripts/perlinstaller --force Mail::SpamAssassin
and then
/etc/rc.d/init.d/exim restart
/scripts/restartsrv spamd
/scripts/fixspamassassinfailedupdate

If the problem continues, give the output of the
tail -n30 /usr/local/cpanel/logs/error_log

[tiggerific]

Thanks for taking the time with this...

I had already attempted a forced install with the realperlinstaller and the only thing I hadn't already tried was the fixspamassassinfailedupdate. Anyway, I did run them all again and still no joy.

For the /usr/local/cpanel/logs/error_log:

Child [30224]: exited with signal 13
Child [8028]: exited with signal 13
Child [11758]: exited with signal 13
Child [15627]: exited with signal 13
Child [19543]: exited with signal 13
Child [21871]: exited with signal 13
Child [27778]: exited with signal 13
Child [31952]: exited with signal 13
Child [3670]: exited with signal 13
Child [9629]: exited with signal 13
Child [23854]: exited with signal 13
Content-type: text/html

Internal Error: "" Normal Connection Timeout (Probably closed browser on a HTTP/1.1 session) at cpsrvd.pl line 1572.
Child [31911]: exited with signal 13
Child [5616]: exited with signal 13
Child [10018]: exited with signal 13
Child [17727]: exited with signal 13
Child [24049]: exited with signal 13
Child [28436]: exited with signal 13
Child [30170]: exited with signal 13
Child [3106]: exited with signal 13
Child [8142]: exited with signal 13
Child [15584]: exited with signal 13
(internal death) Mon May 15 21:04:58 2006 [17674] error: Died at /usr/local/cpanel/Whostmgr/LibShare.pm line 873.
        main::__ANON__('ALRM') called at /usr/local/cpanel/Whostmgr/LibShare.pm line 881
        eval {...} called at /usr/local/cpanel/Whostmgr/LibShare.pm line 870
        main::objget('http://web.cpanel.net/whmnews/nph-secindex.cgi?version=10.8.2-R8...', 0, 1) called at whostmgr/bin/whostmgr.pl line 6573
        main::themecommand() called at whostmgr/bin/whostmgr.pl line 207
Child [24443]: exited with signal 13 

I don't *think* anything in that lot relates to spamd or spamassassin, but i could very easily be wrong about that.

My guess is that you were probably closest the first time with regard to whatever cPanel happens to do to it when you disable it. It's been disabled on this server ever since SA started being shipped with cPanel and maybe there's another "disabling" script in there somewhere

Just FYI, I have also done /scripts/upcp --force which obviously amounted to nothing. I even tried to track back through the cPanel code to find out where (in "addspam.html") it actually looks to find out that SA is disabled in the first place.

In the "Email" page, it uses the following:
<cpanelif !$CONF{'skipspamassassin'} $CPDATA{'FEATURE-SPAMASSASSIN'}>

and on the addspam.html page, this:

<cpanel Email="addspam()">

but I couldn't find out where the addspam() function was hidden.

Maybe finding that would narrow down what cPanel is at least looking for??

[avijit]

Have a look into this and try it.

http://forums.cpanel.net/showthread....t=SpamAssassin

[tiggerific]

Sounded like a good idea!

But no, my files in /usr/bin all have today's date on them, and I don't even have the /usr/share/scripts directory (lucky I checked before removing them all).

However, I don't have the startup script in init.d, but the /scripts/restartsrv does work.

So, still looking for the problem/solution.

[beekeeper]

Warning! the spamassassin feature has been disabled!

It sounds like your default feature set has SA disabled.

In WHM use the feature manager to check the features lists for the default and disabled feature sets. You may also need to check the specific feature set associated your test account plan.