spamdyke looks for the IP address in many different formats. If the IP
address is 11.22.33.44, it looks for:
11.22.33.44
011.022.033.044
11.022.033.044 (new in version 4.0.0)
11.22.033.044 (new in version 4.0.0)
11.22.33.044 (new in version 4.0.0)
44.33.22.11
44.11.22.33
33.22.11.44
44.33.1122
3344.11.22
11.22.8492 (last two octets converted to long integer)
11223344
011022033044
11022033044
1122033044
112233044
44332211
044033022011
185999660 (entire IP converted to long integer)
0b16212c (entire IP converted to hex digits)
Basically, these are all the different formats I've seen in real life.
As people report new ones, I add them too.
As for putting filter entries in the main configuration file instead of
separate files, I'm a step ahead of you. :) Version 4.0.0 already
contains this feature.
-- Sam Clippinger
Marcin Orlowski wrote:
> Sam Clippinger wrote:
>
>
>> Other connections are not being blocked because their rDNS names don't
>> end in country codes. Instead, they use three-character TLDs like
>> ".com" and ".net". If you want to block those connections as well, use
>> the "ip-in-rdns-keyword-file" option and put ".com" and ".net" in the
>> keyword file.
>>
>
> Thanks! That seem to work fine. Would it be possible to also match
> IPs in "glued" form? i.e: 11.22.33.44 => 11223344.domain not
> just 11.22.33.44.domain?
>
> PS: I'd love to have just one config file for spamdyke for siplicity
> and instead of ip-in-rdns-keyword-file put just a bunch of
> ip-in-rdns-keyword=.com
> ip-in-rdns-keyword=.net
> type of entires in main config file. Doable?
>
> Thanks for nice tool.
>
> Regards,
>
_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
