> repo after crash 1: > > file1 > file2 > file3 [...]
Thomas... maybe I'm missing something here but... won't it be possible to let the "rebuildspamdb" act on those files too and (e.g. - just thinking loud) using the bayes DB to analyze them and check if they're good or bad, so automagically removing bad files while keeping good ones ? As a note, I found that "bad behaviour" from the CA (crash analyzer) while looking at the "live maillog"; I saw the CA rejecting a couple of legit emails and checking them I also found that the senders were whitelisted... is the CA kicking in even before some "formal checks" (e.g. whitelisting for IP or sender and all the other stuff ?) If so, may it be possible to move the CA checks at a later point so that some of the checks (e.g.) black/white IP lists, SPF, senderbase.... and in general the checks performed on the envelope data may work and possibly help in classifying the mail as good or bad ? ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
