SpamAssasin is not working

[NetX]

All the domains on my server are receiving tons of spam because SpamAssasin is not working.

In the panel or whm it looks normal but when the spam messages are received the spam flags are nor marked:

X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Status: No, score=
X-Spam-Score:
X-Spam-Bar:
X-Spam-Flag: NO


Any ideas to fix this problem?

Thanks.

[cpanelnick]

Try this

/scripts/autorepair spamd_dbm_fix
/scripts/restartsrv_exim

[sabarishks]

just add the enries in following

/etc/mail/spamassassin/local.cf
allow_user_rules 1

/home/user/.spamassassin/user_prefs
rewrite_header subject Spam


/scripts/perlinstaller --force Mail::SpamAssassin
/etc/init.d/exim restart

[linux.newbie]

The above tweaks will make it run for a couple of hours, then spamassassin stops again. No permanent fix yet.

[cpanelnick]

The above tweaks will make it run for a couple of hours, then spamassassin stops again. No permanent fix yet.

Does spamd just die, or is it still running? What is in /var/log/maillog ?

[linux.newbie]

spamd is active but emails are not getting tagged, same result as given in the first post. A restart of exim found to kick it alive again.

[cpanelnick]

spamd is active but emails are not getting tagged, same result as given in the first post. A restart of exim found to kick it alive again.

Be sure to check /var/log/maillog for more information the next time it dies out.

[khalid-swish]

Thats the issue - Service Status is saying that spamd is up...?

[linux.newbie]

Nothing out of the ordinary other than the regular logging entries

[DBJoshua]

SA also stopped working on all of my servers yesterday.. all set to autoupdate to Release builds.

[cpanelnick]

This may be due to the new 'NOT QUIT' spammer attacks. You should open a ticket so one of our staff and look @ it.

https://tickets.cpanel.net/submit/

[dahatecatalyst]

since the update to CP11 all of our servers have basically a useless spamassassin. We have been forced to have all accounts use boxtrapper to keep from the accounts being completely inundated with flooding spam. We are looking for some sort of formal patch or direction into how to get back to the protection we had before the cp11 upgrade.

[cpanelnick]

since the update to CP11 all of our servers have basically a useless spamassassin. We have been forced to have all accounts use boxtrapper to keep from the accounts being completely inundated with flooding spam. We are looking for some sort of formal patch or direction into how to get back to the protection we had before the cp11 upgrade.

If you have custom ACL rules in your exim configure, spamassassin will not work until you manually resolve the conflicts in the exim configuration editor. Also why have you waited so long to submit a ticket?

[dahatecatalyst]

If you have custom ACL rules in your exim configure, spamassassin will not work until you manually resolve the conflicts in the exim configuration editor. Also why have you waited so long to submit a ticket?

I'm actually working on a network with about 2000 cpanel servers. How can I trace any issues with ACL errors? are these logged in /var/log/exim_paniclog? I have sorted this out in most cases but I still have a problem of runaway spamd processes consuming 80-90% CPU. I will trove the forum for further answers