NICKSERV

Many of the OperServ commands are listed in the OperServ help files however they are issued with different services agents such as NickServ or ChanServ, the reason why they are listed under OperServ is because you need OperServ access to issue these commands. OperServ access levels are Services Administrator also referred to as SA, ChanServ Super Op aka CSop, and root administrator.

DROP - Drop a registered nick.

INFO - Show info on a registered nick.

GETPASS - Show the password for a registered nick.

LIST - List nicknames that match a selected value.

MARK - Set a nickname so that it can't be getpassed or setpassed.

SETPASS - Set the password for a registered nick.

UNIDENTIFY - Make nickserv forget your identification to a nickname.

WIPE - Delete all access list entries for a registered nick.

Example:

/msg nickserv getpass Mark

Usage: NICKSERV DROP <nick>

This command will allow you to remove the registration for a nickname. You do not need the password in order to drop it. 

Example:

/msg nickserv drop Lashell

You can drop nicknames that you feel are inappropriate or that need to be re-registered.

COMMAND REMOVED

Please see SETPASS.

Example:

/os help nickserv setpass

Usage: NICKSERV INFO <nick>

This will show the information on a nick including fields that can only be seen by opers, such as marks.

Example:

/msg nickserv info Lashell

Whenever you do an info command while opered, you will see the additional information available to opers. Whenever you're working with a nick, it is generally a good idea to check its info just in case it shows you something useful.

Usage: NICKSERV LIST <param> [<hits>]

You can list nicknames matching a value you have selected. You can list from 2 to 250 nicks.

Examples:
 
/msg nickserv list *jen*

/msg nickserv list *bot* 50

List is useful if you either need to find a particular nick or are looking for nicks that match a general pattern. For example, you can use list to search for nicks that might be attempting to impersonate administrative positions, but with searches broader than you would want to outright prohibit. 
However, whenever you start doing searches based on strings, you run the risk of people finding less obvious ways to use nicks that you would rather they not. Generally, actually monitoring the network is the best way to enforce rules, but this can be a tool to assist you.

Usage: NICKSERV MARK <nick> [on|off] [<reason>]

The mark command allows you to prevent other CSops from doing a GETPASS or a SETPASS to a nickname. It can be used to indicate that you are dealing or dealt with a nickname. Note: Root users can override the mark command.

Example:

/msg nickserv mark ConferenceRooms nick owner is a CSop

Sometimes users ask for passwords to nicks that they do not own, if such happens and it is fully investigated, marking the nick can prevent other CSops from wasting time investigating again. 
It also can be used to mark nicks of CSops, since they will not require other CSops to getpass their nicks for them. Mark, however, is a versatile command, and can be used to attach any necessary information to a nickname.

Usage: NICKSERV SETPASS <nick> <password>

This command allows you to set the password for a nickname, without using the nick in question and without being identified to it.

Example:

/msg nickserv setpass boca-mike Foxvalley

This is useful if you forget your own password, you can simply set it to something you can remember. You can also use setpass for other people if you have a reason to. However, you may wish to make sure that they own the nick first.

Usage: NICKSERV UNIDENTIFY <nickname>

NickServ maintains a list of nicknames that you have identified to. The unidentify command allows you to remove an entry from that list, effectively making NickServ unaware of the fact that you have identified to that nick.

Example:

/msg nickserv unidentify NikB

This is useful if you wish to not have access to the abilities that go with that nickname. For example, if you identified to a nick that is an AOP in a room, but you wish to enter without being opped, you can unidentify. It is also useful if you want to unidentify from your network operator nick, so that you no longer have CSop access. 
You can, of course, get your access back simply by identifying. If you wanted to let someone else use your computer, you would probably want to unidentify to all of your nicks and rooms, de-oper, and switch nicks.

Usage: NICKSERV ACCESS WIPE <nick>

This command will wipe the entire access list of a user. To view an access list you would type /msg nickserv access list <nick>. 

Example:

/msg nickserv access wipe ConferenceRooms

Sometimes an access list is so badly set that it is simpler to wipe all of the entries and add in some properly set entries than to individually delete the poorly set entries. This is true when the person has entries that are far too wide, such as *@* or several entries that are too specific, showing a lack of understanding of how to use wildcards. 
Another problem that sometimes occurs is that users add entries that include a !, because they think that access lists work like bans. Access lists are very similar, but you do not need to specify the nickname, so you should not have an exclamation mark in an access list entry. Access lists that are too wide will give too many people access to the nick, and ops in rooms where that nick has ops. 
Access lists that are poorly set will require the nick owner to identify more often, and they may get affected by protect if it is set on.