SQLBlackWhitelist using wildcards

[Scott Silva]

on 2/21/2008 12:37 PM Julian Field spake the following:
> Unfortunately you can't do that without slowing it down a lot. The 
> SQLBlackWhiteList stuff, instead of allowing wildcards and hence having 
> to check every entry in the list for every message, reduces the whole 
> problem to a couple of hash table lookups which are very fast, as it 
> knows that there aren't any wildcards.
> 
> If you allow the use of wildcards, every entry has to be matched against 
> every address of every message. This is slow and is why MailScanner 
> rulesets shouldn't ideally have more than several hundred (or maybe a 
> thousand) entries. The SQL stuff does not allow wildcards much, with the 
> result that it can just do table lookups to find if the address is 
> listed or not. This is enormously faster than searching every entry of a 
> ruleset.
> 
> The reason the SQL black+whitelist support is fast, not because of it 
> being SQL (which actually makes it run slower) but because it doesn't 
> support wildcards.
> 
> I hope that explains my design philosophy a bit for this feature.
> 
> Jules.
> 
> William A. Knob wrote:
>>       Hi all!
>>
>>    People, I want to use "wildcards" on my black/whitelist SQL tables 
>> to use with Mailscanner... Anybody knows how can I do that? Or anyone 
>> has made a modification on the "SQLBlackWhiteList.pm" script to do 
>> that stuff?
>>
>>    Regards;
>>
>>
> 
> Jules
> 
Does matching only a domain slow it down?
IE... using 'domain.com' to match '*@domain.com' instead of the default of 
'user at domain.com'.

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080221/7fcd6a91/signature.bin