The old one was only 12k, I did not use it much and it was disabled before the upgrade to latest SA. I have never cared much for the concept of AW. This latest version of SA turns AW on by default however.
I think when SA turned it on, it started failing because it was created with a very old db_file. It just could not talk to it. So I renamed it to get rid of the old one. I could have deleted it, but I just wanted to be safe since I don't know everything going on behind the scenes with the code. :-) So maybe I will try AW for a little while again and see if I change my opinion of auto-whitelist. I can always disable it again. -----Original Message----- From: qqqq [mailto:[EMAIL PROTECTED] Sent: Monday, March 07, 2005 2:58 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; users@spamassassin.apache.org Subject: Re: More problems was Re: DB_FILE error causes serious deep recursion/system overloading problem Greg, How large was auto-whitelist? I just renamed mine and it was about 85Megs. Ironically, I have a VERY old one in the same directory that was about the same size. QQQQ ----- Original Message ----- From: "Greg Allen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <users@spamassassin.apache.org> 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 | | /var/spool/filter/.spamassassin | | and renamed the auto-whitelist file to auto-whitelist.old | | The system created a new auto-whitelist and so far so good. | | I think this may have to do with DB_file upgrade, but the developers would | know more than me. | | | | | | -----Original Message----- | From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] | Sent: Monday, March 07, 2005 1:36 AM | To: users@spamassassin.apache.org | Subject: More problems was Re: DB_FILE error causes 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 from home | directories/.spamassassin and from /var/lib/nobody/.spamassassin -- that | had no effect, either. | | Two more quick notes: | | The SuSE version is 8.2 (not 9.2) on the server. Perl version is 5.8.0 . | | Besides using up almost all the CPU cycles when auto-whitelist was | enabled, spamd was also eating up almost all the memory. | | Alayne | | On Mon, 7 Mar 2005 [EMAIL PROTECTED] wrote: | | > I had a serious spamd problem this evening after we rebooted our server | > (running SuSE Linux 9.2). We had been running SpamAssassin 3.0.1 since | > last October and it had been working very well for several months. | > | > Suddenly, shortly after the upgrade, the load averages for the server shot | > through the roof (from 0.09 to 30-40) for no reason we could see. We | > narrowed it down to spamd. Once we killed that, everything was fine. | | [...] | -- | Alayne McGregor | alayne at twobikes.ottawa.on.ca | | "I am not amused by this 21st century. I want to take it back for a full | refund, | and can we have a real one, please?" -- Charles Stross (Locus, January, | 2005) | |
