You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Daniel Olmedilla <ol...@l3s.de> on 2004/09/29 01:46:24 UTC

Importing old auto-whitelist

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I have just upgraded to spamassassin 3.0 from the 2.64 and I have realized 
that there is a new format for the auto-whitelist. Before it was a GNU DBM 
file (files named auto-whitelist.pag and auto-whitelist.dir) and now it is a 
berkeley DB (file named auto-whitelist). I am running it now. However, the 
old entries of my auto-whitelist (in GNU DB) have not been upgraded to the 
new file (in Berkeley DB).

Does anyone know how to import my old auto-whitelist into the new file?

Thanks in advance,

	DOC
- -- 
     Daniel Olmedilla
     Learning Lab Lower Saxony (L3S)
     Deutscher Pavillon
     Expo plaza 1
     D - 30539 Hannover

     Phone: +49 (0)511 762.9741 / +49 (0)511 7621.9714
     Fax:     +49 (0)511 762.9779 / +49 (0)511-7621.9712

     http://www.l3s.de/~olmedilla/
     E-Mail: olmedilla@l3s.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBWffUHyADsW1P33oRAhbfAKCgpaPw6vTVclZgOBZLttM3gWQBQACghS5Q
ijp9PIhytH9MVyylnOUJMVE=
=a+LR
-----END PGP SIGNATURE-----

Re: Importing old auto-whitelist

Posted by Michael Parker <pa...@pobox.com>.
On Wed, Sep 29, 2004 at 01:46:24AM +0200, Daniel Olmedilla wrote:
> 
> I have just upgraded to spamassassin 3.0 from the 2.64 and I have realized 
> that there is a new format for the auto-whitelist. Before it was a GNU DBM 
> file (files named auto-whitelist.pag and auto-whitelist.dir) and now it is a 
> berkeley DB (file named auto-whitelist). I am running it now. However, the 
> old entries of my auto-whitelist (in GNU DB) have not been upgraded to the 
> new file (in Berkeley DB).
> 

This can happen sometimes when one database type gets favored over
another.  It won't recognize the old db and wil just start up a new
one.

> Does anyone know how to import my old auto-whitelist into the new file?
> 

While you can do it, more often than not it's not worth it.  Consider
it an expire and just remove the old db and continue using the new
one.

Michael