RE: AWL growing too large

2006-03-21 Thread Gary W. Smith
age- > From: derringer [mailto:[EMAIL PROTECTED] > Sent: Monday, March 20, 2006 7:01 PM > To: users@spamassassin.apache.org > Subject: RE: AWL growing too large > > > I'll post my reply here, since my question on manipulating the AWL hasn't > been responded t

RE: AWL growing too large

2006-03-20 Thread derringer
WL has adjusted badly, and I want to fix that specific email address:IP pair, and I simply can't do that with the current tools. Any suggestions other than switching to MySQL and directly manipulating the database? -- View this message in context: http://www.nabble.com/AWL-growing-too-large-t

Re: AWL growing too large

2006-03-19 Thread Nix
On Sun, 19 Mar 2006, Matt Kettler stipulated: > I'm just pointing out the only time I've had the dual-install problem was due > to > a CPAN install, not a source install.. And that was a LONG time ago. I've had it on boxes with vendor trees of perl in strange places and multiple simultaneously li

Re: AWL growing too large

2006-03-19 Thread Matt Kettler
Nix wrote: > On Wed, 15 Mar 2006, Matt Kettler said: >> On the other hand back in 2.31 era I was using cpan, and I *did* get a dual >> install once. However that was CPAN deciding to install a whole new copy of >> perl >> to put SA into because the required perl version was screwed up. > > Well,

Re: AWL growing too large

2006-03-19 Thread Nix
On Wed, 15 Mar 2006, Matt Kettler said: > On the other hand back in 2.31 era I was using cpan, and I *did* get a dual > install once. However that was CPAN deciding to install a whole new copy of > perl > to put SA into because the required perl version was screwed up. Well, you'll be glad to kno

Re: AWL growing too large

2006-03-16 Thread mouss
Michael W Cocke a écrit : > > You could never convince me to do that - the CPAN install facility is > just too useful for me to do anything that would impede my using it! > (Was that a sentence? it's too early here.) > > I install anything perl from either CPAN or source tarball, in that > order

Re: AWL growing too large

2006-03-16 Thread Michael W Cocke
On Wed, 15 Mar 2006 18:24:41 -0500, you wrote: >jdow wrote: > >> >> OK, when the storage structure of the tarball based package you want >> changes how do you extirpate the old and insert the new without the >> rather depressingly familiar dual SpamAssassin install? (Not that the >> package syste

Re: AWL growing too large

2006-03-15 Thread Mark Martinec
Michael, > This line right here tells me that you are NOT using MySQL for you AWL db. Oops, my bad. Bayes is on SQL, AWL is obviously not. Still, is the complaint warranted or am I expecting too much from a bdb-based awl? Mark

Re: AWL growing too large

2006-03-15 Thread Michael Parker
Mark Martinec wrote: > Matt Kettler wrote: >> in the /tools directory of the tarball is a script called >> "check_whitelist". If you run check-whitelist --clean, it will run >> through the current user's AWL and purge any AWL entries which have only >> been seen once. > > $ check_whitelist --clean

Re: AWL growing too large

2006-03-15 Thread Mark Martinec
Matt Kettler wrote: > in the /tools directory of the tarball is a script called > "check_whitelist". If you run check-whitelist --clean, it will run > through the current user's AWL and purge any AWL entries which have only > been seen once. $ check_whitelist --clean Out of memory during request

Re: AWL growing too large

2006-03-15 Thread Matt Kettler
jdow wrote: > > OK, when the storage structure of the tarball based package you want > changes how do you extirpate the old and insert the new without the > rather depressingly familiar dual SpamAssassin install? (Not that the > package systems like RPM always get it right. They do better than mo

Re: AWL growing too large

2006-03-15 Thread jdow
From: "Matt Kettler" <[EMAIL PROTECTED]> mouss wrote: Matt Kettler a écrit : AFAIK, *VERY* few distro packages contain anything from tools. That said, I personally wonder why anyone would use a distro package for something that updates are often time-sensitive. (ie: SpamAssassin, clamav, et

Re: AWL growing too large

2006-03-15 Thread Matt Kettler
mouss wrote: > Matt Kettler a écrit : >> >> AFAIK, *VERY* few distro packages contain anything from tools. >> >> That said, I personally wonder why anyone would use a distro package for >> something that updates are often time-sensitive. (ie: SpamAssassin, clamav, >> etc). >> > > While I try to a

RE: AWL growing too large

2006-03-15 Thread Gary W. Smith
ilto:[EMAIL PROTECTED] > Sent: Wednesday, March 15, 2006 1:51 PM > To: Matt Kettler > Cc: jdow; users@spamassassin.apache.org > Subject: Re: AWL growing too large > > Matt Kettler a écrit : > > > > > > AFAIK, *VERY* few distro packages contain anything from tools. &g

Re: AWL growing too large

2006-03-15 Thread mouss
Matt Kettler a écrit : > > > AFAIK, *VERY* few distro packages contain anything from tools. > > That said, I personally wonder why anyone would use a distro package for > something that updates are often time-sensitive. (ie: SpamAssassin, clamav, > etc). > While I try to avoid pre-packaged bi

Re: AWL growing too large

2006-03-15 Thread Matt Kettler
jdow wrote: > From: "Matt Kettler" <[EMAIL PROTECTED]> > >> Jim Smith wrote: >>> I've got some clients with auto-whitelist files in their >>> /home/USER/.spamassassin directory that are over 20 megs. Is there a >>> ceiling >>> to these AWL files and a way to adjust that ceiling? I think 20 megs is

RE: AWL growing too large

2006-03-15 Thread Gary W. Smith
nal Message- > From: Kris Deugau [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 15, 2006 1:24 PM > To: users@spamassassin.apache.org > Subject: Re: AWL growing too large > > mouss wrote: > > you mean the size of the berkeley db? yes, this may be larger than > >

Re: AWL growing too large

2006-03-15 Thread jdow
From: "Matt Kettler" <[EMAIL PROTECTED]> Jim Smith wrote: I've got some clients with auto-whitelist files in their /home/USER/.spamassassin directory that are over 20 megs. Is there a ceiling to these AWL files and a way to adjust that ceiling? I think 20 megs is rather large for clients with 2

Re: AWL growing too large

2006-03-15 Thread Kris Deugau
mouss wrote: you mean the size of the berkeley db? yes, this may be larger than needed. but this shouldn't be a problem. ... unless it means that your users are coming far too close to their $HOME disk quota for it to be useful. (20M quota + 10M AWL file + lots of incoming spam = lots of ann

Re: AWL growing too large

2006-03-15 Thread mouss
Jim Smith a écrit : > I got the same results. I ran check_whitelist --clean and after lots of > scrolling names and the appearance of cleaning, the file size is the same as > it was to start. Other suggestions to try? Thx. > you mean the size of the berkeley db? yes, this may be larger than neede

RE: AWL growing too large

2006-03-15 Thread Jim Smith
> Sent: Wednesday, March 15, 2006 12:17 PM > To: users@spamassassin.apache.org > Subject: RE: AWL growing too large > > Matt Kettler wrote: > > Jim Smith wrote: > > > I've got some clients with auto-whitelist files in their > > > /home/USER/.spamassassin

RE: AWL growing too large

2006-03-15 Thread Bowie Bailey
Matt Kettler wrote: > Jim Smith wrote: > > I've got some clients with auto-whitelist files in their > > /home/USER/.spamassassin directory that are over 20 megs. Is there > > a ceiling to these AWL files and a way to adjust that ceiling? I > > think 20 megs is rather large for clients with 25 meg l

Re: AWL growing too large

2006-03-15 Thread Matt Kettler
Jim Smith wrote: > I've got some clients with auto-whitelist files in their > /home/USER/.spamassassin directory that are over 20 megs. Is there a ceiling > to these AWL files and a way to adjust that ceiling? I think 20 megs is > rather large for clients with 25 meg limits. If it needs to be 20+ m

AWL growing too large

2006-03-15 Thread Jim Smith
I've got some clients with auto-whitelist files in their /home/USER/.spamassassin directory that are over 20 megs. Is there a ceiling to these AWL files and a way to adjust that ceiling? I think 20 megs is rather large for clients with 25 meg limits. If it needs to be 20+ megs to work well, I'll ne