Feature Requests item #2799180, was opened at 2009-05-31 20:59 Message generated for change (Comment added) made by paulcockings You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126468&aid=2799180&group_id=250683
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Paul Cockings (paulcockings) Assigned to: Nobody/Anonymous (nobody) Summary: % spam limits Initial Comment: Imported from dspam-community tracker # 2475630 Paul Cockings ( paulcockings ) - 2008-12-29 20:56 It would be great if you could filter junk email into categories based on spam probability %. for example:- Good (0% to 49%) Junk suspects (50% to 69%) Junk (Range 70% to 100%) Obviously good emails would be forwarded Junk suspects could be forwarded with JUNK SUSPECT added to the Subject field, or automatically deleted, or wait for manual checking/deletion Definite Junk could be set to be automatically deleted, or wait for manual checking/deletion via the web interface The user profile would have defaults just like other parameters, but for 'advanced' users their web interface could include options for setting the % ranges, or the number of categories split. An end user option for what to do with virus could also be integrated ie whitelist certain types of file (in case clamav has false positive on regular occurrence) ---------------------------------------------------------------------- >Comment By: Paul Cockings (paulcockings) Date: 2009-05-31 21:00 Message: Imported comment: Date: 2009-01-15 07:06 Sender: dovzamir The web GUI already categorizes the spam by colour. It would be easy enough to parametrize the percentage that each colour represents. Are you suggesting then, that we have separate quarantines for each category? Wouldn't that make dspam more complicated to administer? I would personally like to see us simplifying it so that "regular" users can make use of it. One motif that kept coming up, and my own experience with users confirms this, is that dspam is too complicated for the general user, so group classification was born. I'd prefer to make something much simpler and intuitive and make a tool useful for as large a user base as possible. Paul, I wouldn't want to see us going toward virus integration, or any other mail filtering, over and above what dspam does now. We need to concentrate on doing our mission, anti spam, as best we can. Any deviation will take resources from our main stream and bring down the overall quality of the product we supply. I don't see us doing a better job than clamav, when clamav fails. Also, that would mean running mail through dspam before clamav. Shouldn't clamav be run before dspam? My setup does: 1) RDBMS --> Reject/Accept 2) Domain Lookup --> Reject/Accept 3) No known user --> dev:null (stops them trying to find a real user, and no backlash) 4) clamav --> dev:null/Accept 5) spamass --> dspam 5) dspam --> quarantine/mailbox Now I only use the spamassassin step to see how much more accurate dspam is. This setup works great. Virtually no spam gets through and very little false positives (I'm at 99.981% after over 300,000 emails in my personal account). Let's just try to be the best damn anti-spam product on the net! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1126468&aid=2799180&group_id=250683 ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Dspam-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-devel
