On Mon, Apr 04, 2011 at 11:46:51PM +0200, Stevan Baji?? wrote: > On Sun, 03 Apr 2011 17:31:44 +0200 > Elias Oltmanns <e...@nebensachen.de> wrote: > > > Hi there, > > > Hallo Elias, > > > > switching from CHAIN to OSB tokenizer, I understand, makes the old > > tokens mostly useless or even harmful since OSB might achieve better > > accuracy when starting from scratch. I wouldn't mind losing most of the > > tokens if it wasn't for the automatic whitelisting information. So, My > > question is whether there might be any practical way to keep the > > whitelist information during a transition from CHAIN to OSB (or any > > other combination of tokenizers for that matter). > > > > Thanks in advance for any advice you can give me, > > > just switch to OSB and leave the old CHAIN tokens in the database. They will > make your DSPAM just slower but will not do any other harm. And then run the > usual DSPAM maintenance tasks. After 14 days the maintenance SQL script or > the shell script included in the 3.9.x series should purge your old CHAIN > tokens since they will not have any hit if you use OSB. > > Ahh. Yes. There is no way to just delete all tokens and leave the whitelist > tokens in the database. It's all or nothing. > > > > > Elias > > > Stevan
Also, I think you need to leave your training mode set to TEFT (Train on everything.) so that the expiration will work. Otherwise tokens will be kept forever. As far as keeping the old whitelisting tokens, if you have archives of good mail, it should be possible to calculate the whitelist token hash manually and make a list of the tokens to save in the DB. Cheers, Ken ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
