VBCoder wrote: > 2). The uninstall of Spambayes I did should have removed the > experimental settings. This would have fixed the problem I had. I > understand that there may be a case where some settings would want to > be preserved and that that could be a problem.
We never remove any settings or training data when the user uninstalls. There have been times in the past where a new version of SpamBayes required uninstalling the old version before installing the new one, and we don't want users to lose their settings in that case. We also sometimes recommend that a user uninstall SpamBayes to see if a particular problem goes away without it. If it doesn't, we can assure them that they can simply reinstall and all their settings will be intact. > 3). The re-install should have detected the bad settings and raised a > flag at that time. That's not a bad idea. The install runs in an installer application called InnoSetup and not in the SpamBayes code, but we might be able to write a "settings checker" applet that we could kick off during setup. We would still need to check the settings whenever SpamBayes loads them, though, because the user could modify the file at any time. A better solution might be to do a better job of catching these errors and providing more informative messages to the user when SpamBayes is initialized. > 4). The instructions for the experimental settings could include the > expected type and range alone with an example. More information about these settings is available in the source code and exposed by the Web UI for the POP3 Proxy, but that doesn't help Outlook users who are running from the binary. Improved documentation would certainly help if we expect to get useful results about these options. -- Kenny Pitt _______________________________________________ [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
