JSON-RPC:Server ban exception

The server_ban_exception.* JSON RPC calls can add, remove and list server ban exceptions (ELINEs).

= Structure of a server ban exception = The following object is used in responses.

NOTE: Only server ban exceptions are handled through server_ban_exception.*. See the other API calls for handling spamfilter, server bans and name bans.

= API Calls =

server_ban_exception.list
List server ban exceptions (ELINEs).

Request arguments
No mandatory arguments

Example
{"jsonrpc": "2.0", "method": "server_ban_exception.list", "params": {}, "id": 123}

server_ban_exception.get
Retrieve all details of a single server ban exception (ELINE).

Request arguments
Mandatory arguments (see structure of a server ban for an explanation of the fields):
 * name

Example
{"jsonrpc": "2.0", "method": "server_ban_exception.get", "params": {"name":"*@127.0.0.0/8"}, "id": 123}

server_ban_exception.add
Add a server ban exception (ELINE).

Request arguments
Mandatory arguments (see structure of a server ban for an explanation of the fields): Optional arguments:
 * name: user@host mask or extended server ban
 * exception_types: eg  for a kline exception
 * reason: reason for the ban
 * set_by: who set the entry
 * the duration (this is rarely used, as usually exceptions are permanent!), either:
 * expire_at, OR
 * duration_string

Example request
{"jsonrpc": "2.0", "method": "server_ban_exception.add", "params": {"name":"*@192.168.0.0/16", "exception_types":"kGzZ","reason":"this is a test"}, "id": 123}

server_ban_exception.del
Delete a server ban exception (ELINE).

Request arguments
Mandatory arguments (see structure of a server ban for an explanation of the fields): Optional arguments:
 * name
 * set_by: who unset the entry

Example
{"jsonrpc": "2.0", "method": "server_ban_exception.del", "params": {"name":"*@192.168.0.0/16"}, "id": 123}