ChanServ
SET UNSECURE

Are you sick of typing /ChanServ identify #yourchannel yourpasswordhere ? Do you have to type it before EVERY command you attempt to use with ChanServ? Well today's your lucky day. With this command, you can tell ChanServ to stop asking you for your password every time you want to do something. Access is given to any address that is listed in the Founder's NickServ access list without having to identify first. The reason why this command is called "unsecure" is that in certain cases, someone may be able to spoof your address (take on your exact address to gain control of your channel.) Just be careful using it! The information provided below will tell you how to use this command and give you pointers for some problems you may come across.

Set Unsecure

Usage:
/chanserv set (channel) unsecure (On|Off)
NOTE: you do not need to use parentheses.
Breakdown:
- Channel
  Substitute the name of the channel you want to secure/unsecure here. For example, #hotsoup.
- On|Off
  The default setting for this command is Off. It will stay off unless you turn it On.
Examples:
/chanserv set #hotsoup unsecure on
ChanServ would respond:
-ChanServ- Unsecure option on channel #hotsoup is now ON -ChanServ- Change will become permanent at next database sync in 22 minute(s)
Obviously, the name of the channel, the on/off, and the number of minutes left to database sync will change depending on what you input.
Extra Notes
- If after typing the example command, ChanServ tells you:
  -ChanServ- Password authentication required for that command: -ChanServ- Retry after typing /msg ChanServ identify #hotsoup <password><[>
  It means that you need to identify yourself, letting ChanServ know that you have access to that command. Only the founder of the channel can change these settings. But after turning this command on, you shouldn't have this problem anymore, unless your access list changes.
- If after typing the example command, ChanServ tells you:
  -ChanServ- Access denied to that function for channel #hotsoup
  Several things are possible:
  - You may have typed the name of the channel wrong. Especially if your channel is very similar to another; perhaps yours is #hotsoup! and someone else's is #hotsoup, perhaps you left off the !. Check to make sure you have the channel name inputted correctly.
  - You may not own that channel. Registrations DO expire, sometimes passwords are guessed, perhaps you thought you registered the channel correctly when you actually didn't, and then someone else registered it; there are a multitude of reasons why this might be so. You can use the info command to see who DOES own the channel. If for some reason you feel that you should own a channel and you don't, you can /join #dragonrealm and ask for assistance.
  - If you really do own the channel and know the password for it, using the identify command will allow you to gain access to the channel. If the mask you are using for your nick is not in your NickServ access list, then ChanServ will also not recognize you. (Perhaps you are IRCing from an account that you have never used before, or perhaps your address hasn't resolved and your address is numberfied, both of these things could happen, and if you don't add them to your access list, Services won't recognize you without your password.) That doesn't mean that the channel doesn't belong to you, or the nick either, for that matter, it just means that you would have to use your password to tell the Services that yes, it's really you. That's why it's always very important to write your passwords down. If for any reason you don't remember your password, you can find a listing of services ops by typing
    /motd services.*
    and then finding one of those people listed on-line. You can also go to #dragonrealm if you are unable to find a services op; perhaps they will be able to find one for you.
· · ChanServ homepage · Services · Home · ·