1 ##################################################################################
2 # Blitzed Open Proxy Monitor #
6 ##################################################################################
10 # NICK <nickname> : Defines what nickname BOPM will be using.
17 # USER <username> : Defines what username BOPM will be using in place of
24 # REALNAME <realname> : What realname (the bit in /whois after
25 # nick/ident/host) should bopm use?
28 REALNAME Blitzed Open Proxy Monitor
31 # NICKSERV_IDENT <line> : Line to send to nickserv to identify
32 # Leave commented to not use.
34 #NICKSERV_IDENT PRIVMSG NICKSERV :IDENTIFY password1234
35 NICKSERV_IDENT NICKSERV :IDENTIFY password1234
39 # CHANSERV_INVITE <line> : Line to send to chanserv to request invite to a
40 # channel. %s must exist in the line and is the
41 # channel. Leave commented to not use.
43 #CHANSERV_INVITE PRIVMSG CHANSERV :INVITE %s
44 CHANSERV_INVITE CHANSERV :INVITE %s
48 # BINDIRC <ip> : IP to bind to for IRC connection
56 # BINDSCAN <ip> : IP to bind to for scan connections
64 # SERVER <servername> : IRC host BOPM will be monitoring connections on.
65 # This is what bopm will connect to, so please make
69 SERVER myserver.blitzed.org
72 # PASSWORD <password> : If you need a password to connect to your server,
73 # define it here. Leave commented if not.
80 # PORT <port> : Port of IRC host BOPM will be monitoring connections on
81 # This is the port that BOPM will connect to in order to get on
82 # IRC itself, it is nothing to do with what ports it checks on
83 # clients, nor do you need to list every port your ircd
84 # accepts clients on. You need only 1 PORT definition.
92 # CHANNELS <list> : Comma seperated list of channels bot will join/privmsg
94 # There cannot be spaces between channels, only commas.
99 # KEYS <list> : Comma separated list of keys for channels above. Again
100 # there should not be spaces between these keys, only
101 # commas. Also if a channel above does not need a key, you
102 # need to put some text anyway, it will be ignored (this is
103 # the same syntax that IRC clients use to join multiple
105 # Keep this commented if you don't need any keys.
111 # OPER <user> <pass> : Username and Password of O line BOPM will be using
117 # OPER_MODES <modes> : Mode string to set on itself as soon as it opers up.
118 # This should include whatever mode enables connect
119 # notices (usually +c), and often a good idea to disable
120 # helper modes so that users don't try to talk to the
128 # SCANIP <ip> : IP to command possible open proxy to connect to. This is
129 # usually the same IP as the IRC host we're monitoring. Don't
130 # leave this 127.0.0.1
137 # SCANPORT <port> : Port to command possible open proxy to connect to.
138 # This is usually an IRC related port (such as 6667). THIS
139 # HAS NOTHING TO DO WITH WHAT PORTS ARE SCANNED! When BOPM
140 # connects to the client, this is the port ON YOUR SERVER
141 # that BOPM tries to make it connect to. This should
142 # normally be a port that your ircd is listening on. You
143 # therefore only need one SCANPORT directive.
150 # TIMEOUT <seconds> : Number of seconds before a particular scan on a client
151 # will timeout. The higher this is set, the more chance of
152 # slower proxies being caught. However a higher value also means
153 # more demand for file descriptors at any one time.
154 # A default value of 30 is recommended.
161 # TARGET_STRING <string> : Target string we test for in the data read by the scanner,
162 # this should be a string within the data that your ircd usually
163 # sends on connect. The default should work on most bahamut
164 # based ircds once you edit it for your server name.
166 # Suggestion is to place the FULL notice string with the server
167 # source name as your target string (this won't work for hybrid
168 # servers as they don't send the server source.
170 # This would prevent the odd clients running IRC servers on port
171 # 8080/8000 from being confused with a proxy.
173 TARGET_STRING *** Looking up your hostname...
177 # KLINE_COMMAND <command> : Line used in issuing KLINES. Two %s are required
178 # within the line which will specify the klined
179 # host and the IP address which you may find
182 # Do not add anymore ':' characters after the initial
183 # : character in the kline (even for a website) as
184 # the IRCD will reject it.
186 # You should probably make sure this is a
187 # TEMPORARY KLINE, otherwise people who fix their
188 # proxies will not be able to get back onto your
189 # net. The example below is correct for DALNet's
190 # Bahamut and by default places a 30 minute
193 # !!!! IMPORTANT !!!! If you change the description on the line below
194 # WE WILL NOT SUPPORT YOU. It is very important that
195 # users banned are able to visit the DNSBL and remove
196 # themselves; if not, they will be permanantly banned
197 # from your network (as they will not have the
198 # knowledge to remove themselves from the DNSBL).
200 # If you don't like the rather Blitzed-like pages
201 # then you can use this command instead:
203 # KLINE_COMMAND KLINE *@%s :Open Proxy found on your host. Please visit www.blitzed.org/opm/index2.phtml?ip=%s for more information
205 # Here's a GLINE example for ircU:
206 # KLINE_COMMAND GLINE +*@%s 1800 :Open proxy found on your host. Please visit www.blitzed.org/proxy?ip=%s for more information.
208 KLINE_COMMAND KLINE *@%s :Open Proxy found on your host. Please visit www.blitzed.org/proxy?ip=%s for more information.
213 # DNSBL_ZONE <name> : Name of the DNS zone that every user will be checked
214 # against. For example, Blitzed uses opm.blitzed.org (and
215 # you can too, if you like). If you don't understand what
216 # a DNSBL is, you can try looking at
217 # http://www.blitzed.org/opm. This zone should NOT have a
218 # dot at the end. If you leave this variable commented, no
219 # check will be done.
221 DNSBL_ZONE opm.blitzed.org
226 # DNSBL_TO <email> : Email address that reports of open proxies should be
227 # sent to. If this is not set, proxies will not be reported
228 # by email. You can report to multiple addresses by
229 # separating them with commas.
231 #DNSBL_TO postmaster@[127.0.0.1]
236 # DNSBL_FROM <email> : Email address that your bopm will use to communicate
237 # with DNSBL_TO, above. The Blitzed DNSBL requires
238 # that this email address be received by a real person,
239 # i.e. you. If this is not set, proxies will not be
242 #DNSBL_FROM email@example.com
247 # SENDMAIL <path> : Absolute path to your sendmail binary. If this is not
248 # set, proxies will not be reported by email.
250 #SENDMAIL /usr/sbin/sendmail
255 # HELP_EMAIL <email> : When someone messages bopm with "INFO" it will tell
256 # them to email a certain address for help. If you are a
257 # Blitzed admin you should be setting this to
258 # "help@lists.blitzed.org"
260 HELP_EMAIL help@lists.blitzed.org
265 # AWAY <away message> : If this is set then bopm will use it as an away
266 # message as soon as it connects.
268 AWAY I'm a bot. Your messages will be ignored.
270 # FDLIMIT <limit> : Limit number of open file descriptors for SCAN ONLY (this does
271 # not include file descriptors used for the IRC socket or log files.
272 # Once limit has been reached, any further scans are queued until
273 # there are file descriptors free
275 # Keep this limit equal or less than MAXPOLL as defined in options.h
280 # EXCLUDE <hostmask> : Exclude hosts matching this pattern from DNSBL
281 # checks and proxy scans. The hostmask uses familiar
282 # IRC wildcards * and ? and matches against both IP
283 # and hostname. Use EXCLUDE multiple times to build a
284 # list. You should not be using EXCLUDE unless you
285 # have very good reason; if BOPM is finding false
286 # positives then we regard that a serious problem and
287 # would like to be told.
290 #EXCLUDE some-isp-??.example.com
292 # PIDFILE <filepath> : Full path specifying where bopm should record its
295 PIDFILE /path/to/bopm.pid