----- Original Message ----- From: "Jason R. Mastaler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 12, 2003 2:15 AM Subject: Re: cdb whitelist
> "Jesse Guardiani" <[EMAIL PROTECTED]> writes: > > > Thanks! That will help in the short run. I'll try to implement this > > tommorrow so that I can get this server up and running. > > The `build_dbm()' function in Util.py contains an example of this > technique FWIW. > > > I'm a little worried that even just with 50 domains TMDA may put a > > rather high load on my server if I require each TMDA customer's > > tmda-filter program to look through a 50 domain wildcarded flat file > > for every incoming and outgoing email. > > Yup, I wouldn't even try this. > > > Now, as I understand it, CDBs are hash tables, correct? And you can > > get extremely good retrieval speed as long as you know exactly what > > you're looking for, correct? It's like a hit or miss thing. > > Exactly correct. > > > But my case is rather specialized. I JUST want to see if the > > incoming or outgoing email's DOMAIN is listed in the CDB. This can > > be accomplished without wildcarding, but I don't think it can be > > accomplished with current TMDA filter functionality. I think it may > > require a special filter type, an option to a current filter, or > > some more overhead to the current wildcarding code. (I vote for a > > new filter type, personally, and I'd like to see the -autocdb and > > -autodbm functionality added for good measure.) > > [...] > > > So, Jason, would you be opposed to the creation of a new CDB filter > > type (or similar functionality) that simply looks up the domain part > > of an email in a CDB? > > Something is tickling the back of mind telling me that there is a good > reason why we haven't already implemented this. Hmmm. Perhaps not. > > No, I don't have a problem with adding this. > > So, perhaps it would work like this: > > The portion after the first `@' in the e-mail address is considered > the "domain". e.g, > > [EMAIL PROTECTED] -> mastaler.com > [EMAIL PROTECTED] -> cs.yale.edu > > Your flat file or CDB/DBM contains nothing but domain names. e.g, > > wingnet.net > mastaler.com > tmda.net > cs.yale.edu > > Now, this isn't wildcarding, so with the above file, mail to > [EMAIL PROTECTED]' would not match. You'd have to add > wopr.wingnet.net to the list first. > > Next, I think this feature only makes sense in conjunction with the > from-(file|cdb|dbm) or to-(file|cdb|dbm) sources. How about we add a > `-domains' option to each which tells the parser that the file or DB > might also contain domain names. Then an attempt will be made to > straight match the domain name in addition to the e-mail address. > > For example, > > from-file -domains -autocdb ~/.tmda/lists/domains_allow ok > > to-file -domains -autocdb ~/.tmda/lists/domains_allow bare > > Where `domains_allow' would contain a list of e-mail addresses and/or > domain names. Wilcards would be treated the same as they are now; > ignored if using a DBM/CDB source or option. > > Does this sound right? Yup. Sounds perfect. > _________________________________________________ > tmda-workers mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-workers > _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
