AM
Subject: Re: Re: SA 3.0.2 MASSIVE memory cpu problems
| please help! still no solution for that!
| still massive CPU and Mem problems
|
| [EMAIL PROTECTED] schrieb am 16.03.2005 19:56:54:
|
| > -BEGIN PGP SIGNED MESSAGE-
| > Hash: SHA1
|
| >
| > I would suggest running with -D
please help! still no solution for that!
still massive CPU and Mem problems
[EMAIL PROTECTED] schrieb am 16.03.2005 19:56:54:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I would suggest running with -D and monitoring spamd memory size
> as it starts up. Something is causing it to bal
Justin!
[EMAIL PROTECTED] (Justin Mason) wrote on 16.03.05 21:46:>-BEGIN PGP SIGNED MESSAGE->Hash: SHA1>>>I would suggest running with -D and monitoring spamd memory size>as it starts up. Something is causing it to balloon to massive>sizes after startup.
nothing special during startup; it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would suggest running with -D and monitoring spamd memory size
as it starts up. Something is causing it to balloon to massive
sizes after startup.
Presumably you are limiting the size of the messages sent in for scanning,
as recommended in the do
Greg,
i have
use_auto_whitelist 0
in the local.cf
But thanks anyway
Wolfgang
"Greg Allen" <[EMAIL PROTECTED]> schrieb am 16.03.2005 13:54:24:
> Some users have had problems with corrupt AWL database after upgrade of
> Spamassassin. Try disabling AWL to see if that is your issue.
>
> -Orig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Greg,
> Some users have had problems with corrupt AWL database after upgrade of
> Spamassassin. Try disabling AWL to see if that is your issue.
I'm totally new to the list and I don't know 3.0.2 so I'm not sure how
helpful this is goin
Some users have had problems with corrupt AWL database after upgrade of
Spamassassin. Try disabling AWL to see if that is your issue.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 16, 2005 5:44 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Su
