NickServ ACCESS

The NickServ ACCESS list is used for making NickServ able to recognise you as the owner of a nickname based on your user@host. The NickServ ACCESS list is only to be used for yourself to be able to access your nickname and avoid hitting the NickServ enforcer changing your nick to a guest-12345 nickname.

The nick enforcer will only enforce nicks that are set with nickserv setting ENFORCE.

To view your access list simply type:

 /nickserv ACCESS LIST

You will be able to see your current access list for your nickname, it will look something like this:

 Access list:
     1) Fredde@12.23.34.*
 End of Access List.

This would mean that everyone on the network matching the user@host of 'Fredde@12.23.34.*' would be recognised to have access to my nickname and also have access to the channels that my nick has access to. If you notice that your access list is not matching you then please remove your user@host to it like this:

 /nickserv ACCESS DEL 1

We want to point out that the user@mask is not nickname@ip, its the userid@host that needs to be added. The userid is shown in your /whois like this: nick!userid@host so you just take away the nick! part and voila you have your userid@host.

You then need to add your user@host that you found in your whois like this:

 /nickserv ACCESS ADD fredde@1.2.3.*

And if we again try do a /nickserv ACCESS LIST we will see this:

 Access list:
     1) fredde@1.2.3.*
 End of Access List.

Security

We would like to point out that if a too wide user@mask is set on your nick perhaps something like: *@1.* there would be a great chance of users that are not you gaining access to your nick and therefor also to your channels, so we would like you to refrain from setting an access entry too wide. A very wide access list is also considered as services abuse and could get your nickname frozen by an AvadeNET IRC Operator.

A user that is matching an entry on the access list will be able to use the nickserv RECOVER and nickserv RELEASE commands without providing any password like this:

 /nickserv RECOVER nick
 /nickserv RELEASE nick

So you can see how important it is that you place the correct user@mask for your nickname as other users might get access to your nick.

If the nickserv setting SECURE is activated, services will not recognize you as the owner of that nickname until you actually identify to the nickname rendering the nickname more secure. The use of SECURE on your nickname will disable the access list of your nick.

If a channel is set with the setting IDENT, only users identified to a nickname on the channels avoice+ lists will be able to gain any access to the channel. If you need further help feel free to join #Help.