EMAIL PROTECTED]>;
Sent: Monday, March 07, 2005 12:41 AM
Subject: RE: More problems was Re: DB_FILE error causes serious deep
recursion/system overloading problem
| I had a problem with auto-whitelist. I had errors writing to it when I
| tested with spamassassin -D --lint
|
| I went to t
Sent: Monday, March 07, 2005 12:41 AM
Subject: RE: More problems was Re: DB_FILE error causes serious deep
recursion/system overloading problem
| I had a problem with auto-whitelist. I had errors writing to it when I
| tested with spamassassin -D --lint
|
| I went to the auto-whitelist directory
[EMAIL PROTECTED] wrote:
Well, turning off auto-whitelist does solve the system load problem.
Unfortunately, it's also become clear that it turns off all spam tagging,
meaning SpamAssassin is useless.
Any ideas, please?
Wow!
I turned off AWL and sure enough, I see all the system resources free
This is not good. You should make sure that you upgraded all of the
supporting files including db_file to latest from cpan.org
run spamassassin -D --lint to see what files it uses and upgrade those.
You need to get your db working again it looks like to me.
-->debug: bayes: no dbs present, canno
serious deep
recursion/system overloading problem
Well, turning off auto-whitelist does solve the system load problem.
Unfortunately, it's also become clear that it turns off all spam tagging,
meaning SpamAssassin is useless.
Any ideas, please?
I tried moving out all auto-whitelist files
Well, turning off auto-whitelist does solve the system load problem.
Unfortunately, it's also become clear that it turns off all spam tagging,
meaning SpamAssassin is useless.
Any ideas, please?
I tried moving out all auto-whitelist files from home
directories/.spamassassin and from /var/lib/nob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It would be worthwhile moving the AWL db files out of the way to see
if that helps; run with -D to see what file might be being loaded.
There certainly seem to be major (but infrequent) bugs in DB_File
somewhere. :(
- --j.
writes:
> This is int
This is interesting as I am dealing with a load issue that started at 3.0.1
as well.
All of a sudden, all of my RAM is being used. I added a second CPU to the
box to no avail.
I am using AWL as well and will try to run it without to see what happens.
Unlike you, when I run it in debug mode, I do
