>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.
Nope. The rebuildspamdb is running on one server and the spamdb is copied to a second. That is the situation we are discussing here. This can be done without restarting assp on the second server and should be done without running rebuildspamdb on the second ( which is so obvious, that i forgot to mention it in my first reply). I run this for years - copying the spamdb from my primary mx to my secondary. fritz ------------------------------------------------------------------------- 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
