The kind of wildcards you're asking for (especially "*.*") would not be easy to implement. However, the code that requires a keyword to be surrounded by non-alphanumeric characters could be easily removed if you want to test the results. In filter.c, just remove the if() block from lines 697 to 706 (in version 4.0.5). Rerun "make" and install the new binary. My instinct says you won't like the new behavior but I could easily be wrong.
In the long run, the best solution is probably to add support for regular expressions. They're much more flexible and powerful and the documentation would be much simpler as well, since many tutorials already exist for regexps. Several people have asked for regular expression support and it's on my list (though it's not high priority at the moment). -- Sam Clippinger Youri V. Kravatsky wrote: > Hello Sam, > > >> BTW, spamdyke won't find a keyword like "dyn" in the middle of other >> text like "dynamic". In order to match, a keyword must (1) be at the >> beginning of the name, (2) be surrounded with non-alphanumeric >> characters (i.e. dots or dashes) AND include the rDNS name's TLD (e.g. >> "example" would not be found in "11.22.33.44.example.com") or (3) the >> keyword must begin with a dot AND match the entire end of the rDNS name >> (e.g. ".example.com" would match "11.22.33.44.example.com"). This logic >> exists to prevent a keyword like "dynamic" from matching >> "11.22.33.44.notdynamic.example.com". >> > Well, it is not good really, I know that correctly work on wildcards is not > easy work in C, unlike, perl, but it would be very good to use file like > .*dynamic.* > .dynamic*.* > > .broadband*.* > > .*broadband.* > > .*cable.* > > .cable*.* > > .*pppoe.* > > .pppoe*.* > Or else we will read log for a full days to find out all possible > home-dynamic-cable-broadband providers all over the world... > > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
