Except ban block

The except ban block allows you to exempt users from things like GLINEs, blacklists, spamfilter restrictions, etc. This is useful when you want an ISP banned, but still want specific users to be able to connect. IRCOps also often exempt their own IP to make sure they are never accidentally banned.

You can also use the  command on IRC to add/remove exemptions dynamically (which are stored in a permanent database, tkldb).

Syntax
except ban { mask ; type { .... }; /* this is optional */ };

The mask specifies the mask to be exempt from banning. It is recommended to use IP addresses in the mask if possible (eg: *@192.168.*) rather than hostnames (eg: *@*.someisp.xx). In the mask you can use a hostname, or even Extended server bans, but then the except ban { } will be ineffective against exempting from ZLINE and GZLINE for technical reasons (when bans and except ban { } blocks are processed no DNS lookup and no ident lookup has been done yet).

Valid types are:

If you do not specify any type, then the exception defaults to: kline + gline + zline + gzline + shun.

Exempt by IP
except ban { mask *@192.168.*; mask *@192.0.2.5; }

except ban { mask { *@192.168.*; *@10.*; *@127.*; } }

Exempt by certificate fingerprint
This would allow the user with the certficate fingerprint , to bypass KLINE and GLINE server bans and spamfilter restrictions. except ban { mask ~certfp:1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef; type { kline; gline; spamfilter; } }

Exempt by services account name
This would allow the user with a services account of  to bypass spamfilter restrictions: except ban { mask ~account:ExampleAccount; type { spamfilter; } }