Fritz Borgstedt wrote: >"Eric B." <[EMAIL PROTECTED]> schreibt: >>One of those tests would be delaying. However, if you aren't >>deleting the tuplet associated with the address, you are skipping over one >>of >>the tests that you are counting on helping you block spam. > > >Delaying is only one instrument, we are playing big band here. >After deleting in the whitelist and reporting to spam, the next >message from same source will come through delaying and will be >blocked by a spamfilter and the tuplett will be deleted.
Hmmm - I hadn't thought of the entire sequence that way. That makes a lot of sense. I guess this highlights my lack of knowledge as to what happens when something is reported as spam. I had assumed that the report was saved to the bayesian db, and at the next rebuildspamdb, would be incorporated into the spamdb. But until then, it was just simply stored as a report to deal with. Does ASSP actively do anything with reported spam prior to the time the db is rebuilt? Thanks, Eric ------------------------------------------------------------------------- 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
