Sure, you could do that too. But then as time passed, you'd get an increasingly out of date spamdb as you waited for your collections to get to a decent size. It's up to the user if they want to go through the hassle of transfering the collection, or using an out of date spamdb.
Fritz Borgstedt wrote: >> It wouldn't make anything void (as far as I know), it would just make >> a >> new spamdb based of your current collections folder, which will be >> near >> empty when you're just starting, generating a tiny spamdb of little >> to >> no significance. >> >> Instead of just transferring the spamdb, you might also want to >> transfer >> the collections folders (spam, notspam, errors) so you have a good >> base >> to start your new collections with, and then you can also >> rebuildspamdb >> without generating a tiny spamdb. >> > > Yep, but there may be the idea (just an idea) to stop running > rebuildspamdb on the server. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
