[Feature Request] Add support for reply types to DNSBL checking about charybdis

[Elizafox]

I am surprised that in 2013, at least 5 years after it appears the original authors seem to have abandoned BOPM, people are still using it.

For tor nodes I recommend tor.ahbl.org. However, I see what you are getting at. A reply-matching config option may be in order.

[ineffyble]

@ElizaCat Unfortunately, the world of IRC is full of abandoned software. The original X-Chat still has many users, which hasn't been updated since 2010. irssi is a very popular client, again, 2010.

But yeah, we wouldn't need BOPM if the replies were supported in the IRCd.

[Elizafox]

Two years actually for irssi. Its last SVN update was in 2011. Also, xchat svn has changes from last week. This is pretty much irrelevant to the discussion.

I will add reporting types. By default, all will be considered a match.

[Elizafox]

I have a patch if you don't mind helping me test.

[ineffyble]

Sure, problem is that there's not any easy way to test DNSBLs (unless I was able to setup my own I guess). I guess if I use an open proxy that I know is listed on one...

[Elizafox]

@neoinr please try this patch and tell me how it works: https://gist.github.com/Elizacat/5427473

[Elizafox]

Syntax to add to your blacklist block, is before the reason, add something like

matches = "6", "8", "127.0.0.1";

The first two will match the last octet, the last one will match the entire IP. The only lookups for the moment supported are 127.x.y.z style responses.

[ineffyble]

@ElizaCat Patch worked perfectly.
Connected via open proxy without config changes, got a blacklisted error.
Added a replies line set to "2" (the sample reply for the blacklist), connected fine.
Added "127.0.0.9" (the reply for HTTP proxy) to the replies line, got a blacklisted error.

[Elizafox]

Awesome. I'll land it then.