AW: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1

[Nißl Reinhard]

Hi Benny,

attached is the output of the below mentioned command.

As far as I read it, the AWL plugin gets loaded.

Bye.
--
Reinhard Nißl, TB3, -198

-Ursprüngliche Nachricht-
Von: Benny Pedersen [mailto:m...@junc.org] 
Gesendet: Freitag, 27. Juli 2012 02:57
An: users@spamassassin.apache.org
Betreff: Re: How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1

Den 2012-07-26 17:26, Nißl Reinhard skrev:

 reading the manuals, I've discovered that the AWL plugin isn't loaded 
 anymore in spamassassin 3.3. Therefore I put the following lines into
 local.cf:

oh no, do not put loadlugin into *.cf files its wrong pr design, but so much 
wiki and bad behavior still continues

for a start:

spamassassin 21 -D --lint | less

see this list, it also answers why loadplugin does not go into *.cf files 
hopefully

recheck your *.pre files

 loadplugin Mail::SpamAssassin::Plugin::AWL use_auto_whitelist 1

 but the file auto-whitelist hasn't been touched since the upgrade from 
 3.1 to 3.3 (to be precisely: spamassassin-3.3.2).

 What am I still doing wrong?

nothing just reading the wroung homepage



lint.txt.xz
Description: lint.txt.xz

How do I reenable AWL on spamassassin 3.3 after upgrade from 3.1

[Nißl Reinhard]

Hi,

reading the manuals, I've discovered that the AWL plugin isn't loaded anymore 
in spamassassin 3.3. Therefore I put the following lines into local.cf:

loadplugin Mail::SpamAssassin::Plugin::AWL
use_auto_whitelist 1

but the file auto-whitelist hasn't been touched since the upgrade from 3.1 to 
3.3 (to be precisely: spamassassin-3.3.2).

What am I still doing wrong?

Bye.
--
Reinhard Nißl, TB3, -198

How do I shrink a 2.6 GB large auto-whitelist file in spamassassin 3.3?

[Nißl Reinhard]

Hi,

before the upgrade to 3.3 (to be precise: spamassassin-3.3.2), AWL was enabled 
and working for years with spamassassin 3.1. Over time auto-whitelist has grown 
to 2.6 GB.

I tried sa-awl as mentioned in the manuals to have a look at the contents, but 
it was eating up all memory and swap space (with no output yet) so I killed it 
before kernel would kill any other vital processes.

So how can I shrink that huge Berkley-DB file?

Bye.
--
Reinhard Nißl, TB3, -198