http://bugzilla.spamassassin.org/show_bug.cgi?id=3609
------- Additional Comments From [EMAIL PROTECTED] 2004-07-14 23:47 ------- man. in thinking about this some more, 2 is the right thing to do based on us currently allowing the other bayes_* options like bayes_journal_max_size, bayes_expiry_max_db_size, bayes_auto_expire, etc. imo, it pretty much comes down to: if bayes_path is set for a global db, then most of those options should be disabled. if bayes_path points at a per-user db, then the options should be enabled. slightly complicate this with "if any of the options are set to something not the default in the global configuration, don't let the user override". the goal of all this is to not let the user screw over the system by changing the options to be the most resource intensive per message. so for 3.0.0, I think we need to make bayes_learn_to_journal work in the spamd case, and then examine the other issues for a later release. thoughts? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
