Hi Charles, Yours was the one I couldn't remember the name of...my apologies...<grin>. I've been meaning to take a look at it for some time...but haven't gotten to it yet. I'll have to bump it up on the priority list.
Your math is correct, but we are small enough that we don't spend anywhere near that time....only a tenth of what you mentioned. However, that's why I recommended to them to spend the time initially, and then move to a semi-automated, user-controlled solution once they were comfortable with the detection levels and adjustment processes. You're entirely correct on the user control of protection level. We're looking at implementing a typical pairwise comparison type method so the user picks their tolerance for false positives balanced against their tolerance for spam, and the system then chooses the appropriate weightings to use. Darin. ----- Original Message ----- From: "Charles Frolick" <[EMAIL PROTECTED]> To: "Darin Cox" <[EMAIL PROTECTED]> Sent: Monday, October 25, 2004 12:12 PM Subject: Re[2]: [Declude.JunkMail] Best Practices for handing legit email flagged as spam? Hello Darin, Monday, October 25, 2004, 10:22:11 AM, you wrote: DC> We're working on an independent version of SpamReview that has more DC> information and adjustments capabilities built in, but there are two DC> existing freeware products on the Declude Utilities page: SpamReview being a DC> desktop app, and another one (sorry forgot the name) being web based. I made one of the web based solutions, they all have a slightly different approach, but the end result is the end user is, for the most part, in control. Mine is called Spam Review Web App (I am very bad at comming up with names for these things). I have not actively made changes in over a year, but I use it in production myself with 8.05, and it works well even though it was designed around 6.06. I may, if I can get free the time, rework it into ASP.Net with some newer tricks I have been thinking about, but I have not really had the time. If you want to look at, even for ideas for your own app, it can be found at: http://spamreview.argolink.net/software/ DC> We review the hold queue several times a day, adjusting for false positives, DC> and have a spam reporting address to adjust for false negatives. We figure DC> it takes us about an hour/10k messages/day for the review and tweaking DC> process. We are considering moving to a bulk folder mentality, with DC> automated processes for users to report messages as spam or not spam. If I follow the math, for my 300K messages/day, you would spend 30 hours per day reviewing and tweaking, OUCH! BTW, I work for an ISP, so in many ways it is better to let the end user decide the protection level and report "false positives" for review. In a corporate environment, company policy can dictate a joke mailing list as not a false positive, but as unwanted mail, I don't have the same liberties. -- Best regards, Charles mailto:[EMAIL PROTECTED] --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
