SpamAssassin runs amok after Update

[Coteaux]

I was running ISPConfig 2.1.1 on Suse 10.0 64 bit. Everything was fine: Emails were scanned, Spam was discarded...
Then I did an update to ISPConfig 2.1.2 and now, everytime a mail arrives the system, the spamassassin-process eats all the memory (2GB) and the swap until the kernel kills the process. The server is so laggy in these times that I cannot interfere.
Where can I search for an error? How is this spamassassin-script started?

I did the perfect install for suse with the changes for 64 bit in the compile-file and the changes for the suse-courier-start-scripts from this forum.

[till]

You can try this (from the ISPConfig installation manual):

SpamAssassin

The ISPConfig comes with SpamAssassin, but without the Perl modules needed by
SpamAssassin. Run the following command after the installation of the ISPConfig:

/home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin

If errors appear you have to install some Perl modules.

perl -MCPAN -e shell
install HTML::Parser
install DB_File
install Net::DNS (when prompted to enable tests, choose "no")
install Digest::SHA1

To leave the Perl shell type

q

If

/home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin

does not return any error everything is fine. You can then leave SpamAssassin by typing
" CTRL + c".

[Coteaux]

Thanks for the quick reply!

/home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin
didn't show any message at all.
The perl-modules are all up to date.

There was a patch from SuSE for Courier (autoinstalled by you). Could it have to do with that?

[till]

Originally Posted by Coteaux

Thanks for the quick reply!

/home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin
didn't show any message at all.

Thats ok. And the process does not aet up your memory?

The perl-modules are all up to date.

Ok.

There was a patch from SuSE for Courier (autoinstalled by you). Could it have to do with that?

No, courier is not involved with mailscanning.

Spamassassin is invoked by a procmail recipe.

[Coteaux]

Thats ok. And the process does not aet up your memory?

No, that process is ok.
The process which has to be killed is for example (from ps aux):

10002 9784 77.8 65.9 1385860 1347520 ? R 16:31 0:08 /usr/bin/perl -T -w /home/admispconfig/ispconfig/tools/spamassassin/usr/bin/spamassassin --prefs-file=/srv/www/web1/user/web1_sysadmin/.user_prefs

If other users receive mail it is similar.

[falko]

What's in /srv/www/web1/user/web1_sysadmin/.user_prefs? Also post the output of

ls -la /srv/www/web1/user/web1_sysadmin/