Assuming that this whitelist would be used to LOWER the score of an email, and not just exclude them from SURBL. Then we would go thru even moreresearch before we whitelist a domain. There is a LOT of work that goes into adding a domain to our whitelist, and that is JUST for exclusion!
Nah, just exclude. I don't know why anyone would want to use it for a nice score since it'd be *so easy* to end up with FNs. I only used the term "white list" as that's what Jeff has called the exclusion list on the mailing list, and what you said ("whitelisting local domains") in your original message.
My whole idea was skipping the lookup entirley. Why would you want to do a
lookup for google even if it is cached?
I'd rather trade 2ms for a cached lookup than consuming even more memory for the extra local white list array.
Additionally, assuming there isn't an extreme query frequency drop off after the top 100 or 200 excluded domains, it would be nice to have access to the rest of the exclusion list which wouldn't be realistic to be storing (and currently copying around) in memory.
There's got to be a reason why SpamAssassin currently only includes the top 100 or whatever excluded domains... either the rest of the data wasn't useful or it wasn't worth the performance hit having them in memory.
New additions to the exclusion list would immediately be available too, not that that is really a huge concern.
Daryl
