On Sat, 15 Feb 2003, David D. Hagood wrote: >Date: Sat, 15 Feb 2003 09:23:08 -0600 >From: David D. Hagood <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Content-Type: text/plain; charset=us-ascii; format=flowed >List-Id: <dri-devel.lists.sourceforge.net> >Subject: Re: DRI Mailing list maintanence / maintaner > >Could the list be set up to: >1) maintain a list of email addresses that have been verified GOOD. >2) maintain a list of email addresses that have been verified BAD (e.g. >[EMAIL PROTECTED]). >3) Check all inbound messages, such that: > 3a) If the message is from an email subscribed to the list, ACCEPT. > 3b) If the message is from a verified GOOD email, ACCEPT. > 3c) If the message is from a verified BAD email, REJECT. > 3d) Otherwise, hold message for 1 week, and send message to sender >asking for confirmation. > 3e) If no confirmation received after 1 week, purge message. > 3f) If confirmation received, add sender to GOOD list and post message. > >That way, everything is automated, 99.9% of the spams will be dropped, >and any spammers that DO confirm can be moved from the good list to the >bad list.
spamassassin does probably better spam filtering than any homebrew mechanism someone could come up with in a short amount of time. That handles getting rid of the BAD posts, and with very low false positives. I get about 0.5% false positives. With minor tweaking it would be 0 though. As for #1 above, the list of addresses verfied "GOOD" would be those who subscribed to the list in the first place. -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
