Further to: > That's a goal of a fully running, fully populated Bayesian database. > But > of course you cant just pull email out of thin air. You need email > going in and out to "build" your Bayesian database with. If you get > more > spam than ham and it is taking you a long time to fill the ham, then > there isn't much you can do about that. Something that I would > recommend > to help off-set the amount of spam needless collected, is to use > various > logging options to discard spam instead of collecting it. Options 6 > and > 7 are listed as recommended choices for certain "Collecting/File Paths" > for this reason. If you aren't, you should use these recommendations. > But other than that, there really isn't much you can except send more > mail to bolster the ham side of the equation.
Could he set the option (in the Logging section): Spam Log Frequency: Store every n'th spam message. The same as for non spam but helps prevent spam corpuses being skewed by flooding. It is recommended that this be set depending on spam volume. Default value = 1, log every message. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
