I'm running the latest ASSP 2.2.2 build 12248 (Win2k8, ActivePerl, MSSQL), but I observed the same behavior with previous versions as well; in short, if I manually "trim" the spam/notspam folders down to 14000 files (or less, but same count for both) and start a rebuild, the rebuild report tells me that the corpus is ok (balanced) but then, if I leave ASSP running for (say) a week or so (the box gets quite a bunch of traffic), the spam folder keeps growing and growing and the corpus quickly moves to "slight spam heavy" and then "too spam heavy" and the ASSP "automatic cleanup" doesn't seem to help; the rebuild deletes some "excess files" but the file count seem to be small if compared to the amount of files stored; the relevant (or they should) parameters in my config are:
MaxFiles: 14000 FilesDistribution: 1 MaxAllowedDups: 5 MaxBayesFileAge: 30 10 MaxKeepDeleted: 10 MaxCorrectedDays: 1000 MaxNoBayesFileAge: 15 autoCorrectCorpus: 0.6-1.4-4000-10 now... is this a bug or an expected behaviour ? And if it's expected, what can I do (e.g. config change) to avoid this issue ? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
