Changes between Version 2 and Version 3 of ExpireBayes
 Timestamp:
 Apr 25, 2006, 8:17:45 PM (17 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

ExpireBayes
v2 v3 15 15 }}} 16 16 17 Note that while this forces an expiry run to take place, it doesn't guarantee that any tokens will actually be deleted. The expiry logic still gets used (quoted from the salearnman page):17 Note that while this forces an expiry run to take place, it doesn't guarantee that any tokens will actually be deleted. The expiry logic still gets used (quoted from the [http://spamassassin.apache.org/full/3.0.x/dist/doc/salearn.html salearn] man page): 18 18 19 * figure out how many tokens to keep. take the larger of either bayes_expiry_max_db_size* 75% or 100,000 tokens. therefore, the goal reduction is number of tokens  number of tokens to keep.19 * figure out how many tokens to keep. take the larger of either {{{bayes_expiry_max_db_size}}} * 75% or 100,000 tokens. therefore, the goal reduction is number of tokens  number of tokens to keep. 20 20 21 21 * if the reduction number is < 1000 tokens, abort (not worth the effort). … … 38 38 }}} 39 39 40 You can reduce bayes_expiry_max_db_size, of course, but first try forcing a manual expiry run (salearn forceexpire) to see whether that turns out to be enough to do the job. For example, here's what I just generated on one of my test machines:40 You can reduce {{{bayes_expiry_max_db_size}}}, of course, but first try forcing a manual expiry run (salearn forceexpire) to see whether that turns out to be enough to do the job. For example, here's what I just generated on one of my test machines: 41 41 42 42 {{{