Since someone brought it up... ;-) A compromise that I would like is to have the whitelist in a seperate file like the blacklist. I currently have an ASP web page where my staff can update the white and black lists. The blacklist is super-easy to write code to update, but whitelist is more difficult and dangerous because a script is playing with global.cfg. That makes me uncomfortable. I wound up putting special comments in the whitelist file like "##!-- WHITELIST STARTS HERE --##" so my script could cut out the whitelist section, rebuild it, then rewrite the entire file. Having the whitelist free and clear of the rest of global.cfg would make me sleep better at night.
In this case, others could easily script an export of their customer database if they wish and automatically dump it into the whitelist file periodically. --Todd. ----- Original Message ----- From: "R. Scott Perry" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, July 13, 2002 9:29 AM Subject: Re: [Declude.JunkMail] Whitelist/blacklist question... > > >Could it be possible to have an option to use an ODBC datasource for the > >whitelist and blacklist tests? > > It's unlikely, but something that we will consider. > > >My thought is that email is MUCH more critical for this situation where > >if a home user looses a piece of mail because of a false positive it's > >not as bad... Ok we could debate that later but hear me out... > > Just one quick note here. Whitelisting is meant as a last resort, for > E-mail that you absolutely, positively must have, and where the sender > won't fix their problems. > > It has the same drawback that filtering does -- it can catch a lot of stuff > it shouldn't. Just as you don't want a filter to catch all mail from Dr. > Dick Hitchcock, people have seen a sudden increase in spam when > whitelisting "mail.com" (which ends up whitelisting @hotmail.com, a popular > return address for spammers). > > >Using an ODBC datasource might speed up Junkmail's processing because it > >could issue SQL select queries to a persistently open database. > > Actually, Declude JunkMail's current whitelisting would likely be faster. > > >Additionally, I could write an ASP front end to modify the white/black > >list easier. > > If the 200 item limit were removed (something we will have to do > eventually), would that make a difference? Going to ODBC is going to > involve a lot of extra work, that might be only minimally useful. > -Scott > > --- > [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". You can E-mail > [EMAIL PROTECTED] for assistance. You can visit our web > site at http://www.declude.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". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
