|
› DALnet Services Help.
Introduction
dalnet services
This reference is based upon the DALnet services help page located here which is the original documentation. And as #mIRC is a DALnet channel, our users ask frequent questions about DALnet services. This is why a page containing DALnet services help is included.
DALnet's nick registration service allows users to register a nickname by providing
a password, preventing other users from using it. NickServ registration is required
for such things as registering channels and sending/receiving memos.
NickServ's help page
Chanserv, DALnet's channel registration service, supplies users with a way to
secure their channels from takeovers. Founding a channel gives a user the right
to add and remove ops and akicks, lock channel modes, etc.
ChanServ's help page
MemoServ allows users to send memos to other users with registered nicks even
when they are offline. Memos can be sent to individual users or to all ops in
a specific channel.
MemoServ's help page
Please use caution when sending your passwords to services. DALnet has developed
several methods of identification to prevent "impersonators" from getting your
passwords. These include:
- /msg nickserv@services.dal.net identify (password)
- /msg chanserv@services.dal.net identify (#channel)
(password)
- /nickserv identify (password)
- /chanserv identify (#channel) (password)
- /identify (nickname) (password)
- /identify (#channel) (password)
Depending on what IRC client you use (some common clients include mIRC, BitchX,
ircII, PIRCH, scrollZ), this is going to vary slightly. Some clients will allow
you to type /nickserv directly with no problems, others will require you to
type /quote nickserv, and finally others require /raw nickserv. Find out which
one works on your client.
Always use one of the methods above and make sure you are only replying to "NickServ"
or "ChanServ" when asked to supply your password. If you identify to a "fake"
service (someone using a nickname similar to the real services nicknames, such
as NickSenv or ChenServ), we will not be able to help you.
Nickserv HelpNickservDALnet's nick registration service allows users to register a nickname by providing a password, preventing other users from using it. NickServ registration is required for such things as registering channels and sending/receiving memos.
NICKSERV: acc
NickServ assigns every nickname an access level. You can use that to determine what kind of access that user has. The access level changes depending on level of proof the current user of that nickname has provided to NickServ.
Possible return values include:
0 - Nickname not registered or not currently online.
1 - User has not identified with a password and does not match an access mask entry.
2 - User has not identified with a password, but matches an access list entry.
3 - User has identified using the nickname password.
Command: /nickserv ACC (nickname)
Example: /nickserv acc zud |
|
| ACCESS |
/NickServ HELP ACCESS |
Details |
|
NICKSERV: access
NickServ maintains a database with addresses that are allowed to use the nickname without identifying with the password. This can come in handy, since by adding an access mask you can use your nickname without having to type the password every time you join, or you can give a friend access to your nickname without giving them the password.
You can add access masks to this database using the ACCESS ADD command.
To delete access masks, use ACCESS DEL.
To view access masks, use ACCESS LIST.
To clear access list, use ACCESS WIPE.
Command: /nickserv ACCESS (add/del/list/wipe) [user@mask]
Example: /nickserv access add calvin@hobbes.ncsu.edu
/nickserv access del *@alcatraz.com
/nickserv access wipe |
|
NICKSERV: drop
If you want to unregister a nickname, then you should use the DROP command. When issuing this command, NickServ will immediately halt all management of the specified nickname. After issuing the drop command, an email is sent to the currently set email for the nick. This email contains an authorization code that has to be copied and pasted while connected to DALnet or via the websystem to confirm the drop request process.
Before using this command you must use the IDENTIFY command with the nickname password. Please note that after dropping a nickname, it becomes available for immediate registration by someone else, so exercise caution when using this command.
If after dropping a nickname, someone else registers it, you cannot reclaim that nickname until the new owner lets it expire or drops it.
Command: /nickserv DROP (nickname)
Example: /nickserv drop cupid |
|
NICKSERV: ghost
Sometimes, especially if the network is unstable, or you get disconnected you may end up with a ghosted nickname. What that means is that although you have quit, the IRC server did not receive your quit, and has not released your nickname. It will still appear on any channels you were, and if you do a /whois you will see it has your internet address and your username.
You can retrieve this "ghosted" nickname by using the GHOST command.
Use of the password might or might not be required. If your current address is on the access list, then you do not need to use the password. If your current address is not in the access list, then you must supply the nickname password.
NickServ will then reply saying that the nickname was killed, at which time you can change your nick to your old nickname and continue chatting.
Command: /nickserv GHOST (nickname) [password]
Example: /nickserv ghost bear eXone.45 |
|
| IDENTIFY |
/NickServ HELP IDENTIFY |
Details |
|
NICKSERV: identify
If NickServ prompts you for a password you must reply using this command.
The nickname is optional. You should use it if you want to use the IDENTIFY for a nickname other than the one you are currently using.
If the password is correct, NickServ will notify you that you have successfully identified to your nickname, in which case you have full access to all commands. If not, then you have entered an incorrect password. Please note that passwords are case sensitive, thus a123 is NOT the same as A123 as far as NickServ is concerned.
If you have trouble remembering your password, you can go to #OperHelp and ask for a CSOP.
Command: /nickserv IDENTIFY [nickname] (password)
Example: /nickserv identify fr0g452
/nickserv identify stud 46.Turtle
or,
/identify fr0g452
/identify stud 46.Turtle |
|
NICKSERV: info
Using the INFO command will give you additional information about a nickname if that is registered, such as the last seen address and time, etc.
Command: /nickserv INFO (nickname)
Example: /nickserv info taz |
|
| RECOVER |
/NickServ HELP RECOVER |
Details |
|
NICKSERV: recover
Much similar to the GHOST command, the RECOVER command allows you to reclaim your nickname if someone is using it.
Command: /nickserv RECOVER (nickname) [password]
Example: /nickserv recover comet 8746GAp |
|
| REGISTER |
/NickServ HELP REGISTER |
Details |
|
NICKSERV: register
The REGISTER command allows you to register a nickname with NickServ, and have NickServ protect it.
Note the fact that the desired nickname does not appear anywhere on this command. NickServ will attempt to register the nickname you are currently using. Also note that the password is case sensitive. This means that A123 and a123 are different. After issuing the register command, an email is sent to the adress you set for the nick. This email contains an authorization code to complete the registration process. This code has to be copied and pasted while connected to DALnet or via the websystem to confirm the registration of your nick.
Please make sure you note your nickname password and do not give it away to anyone. The DALnet staff will not ask for your password. You can tell they are actually DALnet officials by using the /whois command, and see if they are an IRC Operator. If you forget your nickname password, please head to #OperHelp and ask for a CSOP. They can help you retrieve your password.
Nicknames will automatically expire after 30 days of absence.
Command: /nickserv REGISTER (password) (email address)
Example: /nickserv register HAwaii.662 alligator@gatorsrus.com |
|
| RELEASE |
/NickServ HELP RELEASE |
Details |
|
NICKSERV: release
If someone tries to use your nickname, an enforcer will take it within 60 seconds (provided that the ENFORCE option for that nick is turned on). The users nick will be changed to Guest***** and the nick will be held. Nicks being held in this manner cannot be used, and a person attempting to use a held nick will receive an error message. However, you can force NickServ to release the nickname immediately by using the RELEASE command.
Command: /nickserv RELEASE (nickname) (password)
Example: /nickserv release Peanybutter myfinepassword |
|
| SENDPASS |
/NickServ HELP SENDPASS |
Details |
|
NICKSERV: sendpass
The SENDPASS command will allow a user to request that his or her nickname password be sent to the email address on file for that nickname. This command should not be relied on as an alternative to managing your own passwords, but only as a "backup" in case of extreme situations. Please remember that you are still responsible for remembering your password(s) and keeping them private. Do not share your password(s) with anyone.
Command: /nickserv SENDPASS (nickname) (email address)
Example: /msg NickServ@services.dal.net SENDPASS Gamma someuser@someisp.com |
|
NICKSERV: SET
The nickserv SET command is used to apply/remove specific settings fro a nickname.
Command: /nickserv set OPTION SWITCH
Example: /nickserv set ENFORCE on
/nickserv set ENFORCE off |
|
| SET EMAIL |
/NickServ HELP SET EMAIL |
Details |
|
NICKSERV: SET email
By providing an email address for your nickname, IRC Operators can handle password requests much faster and easier. YOU MUST USE A REAL EMAIL ACCOUNT in order for us to provide you with a personalized authentification code. Changing an email adress is a two-stages process. After issuing it, an email is sent to the current set adress on the nick which will allow you to revoke and abort the change. If the change is not aborted within 48 hours a confirmation email is sent to the NEW set adress, allowing the user to confirm the change.
Command: /nickserv set EMAIL [PASSWORD] (email address)
Example: /nickserv set email mypass aly@gator.com |
|
| SET ENFORCE |
/NickServ HELP SET ENFORCE |
Details |
|
NICKSERV: SET enforce
This setting allows you to prevent unauthorized users from using your nickname. When a user connects using your nickname, NickServ will look through the access list looking for a matching address. If one is not found, NickServ will ask the user for a password. If the correct password is not supplied within 60 seconds, NickServ will change that person's nickname to a 'Guest' nickname. Literally, they will be called something such as Guest768543, Guest55998, and so on.
Command: /nickserv set ENFORCE (on/off)
Example: /nickserv set enforce on
/nickserv set enforce off |
|
| SET MAILBLOCK |
/NickServ HELP SET MAILBLOCK |
Details |
|
NICKSERV: SET mailblock
Turning this feature on will prevent anyone from using the SENDPASS command on your nickname. The SENDPASS command allows you to send your nickname password to your email address on file. Changing an email adress is a two-stages process. After issuing it, an email is sent to the current set adress on the nick which will allow you to revoke and abort the change. If the change is not aborted within 48 hours a confirmation email is sent to the NEW set adress, allowing the user to confirm the change. CAUTION: If you enable the MAILBLOCK feature, you will no longer be able to request your password be sent via email and you will be entirely responsible for keeping track of it on your own.
Command: /nickserv set MAILBLOCK (ON|OFF)
Example: /msg NickServ@services.dal.net SET MAILBLOCK ON |
|
| SET NOMEMO |
/NickServ HELP SET NOMEMO |
Details |
|
NICKSERV: SET nomemo
After registering a nickname with NickServ, you will gain access to MemoServ, which allows you to send and receive brief (255 character) messages.
Use this command to disallow memos being sent to you.
Command: /nickserv set NOMEMO (on/off)
Example: /nickserv set nomemo on
/nickserv set nomemo off |
|
| SET NOOP |
/NickServ HELP SET NOOP |
Details |
|
NICKSERV: SET noop
After registering a nickname with NickServ, you will gain access to ChanServ, which allows you to register channels, as well as receive AOP or SOP status on channels.
To disallow users from granting you AOP/SOP status, use this command.
Command: /nickserv set NOOP (on/off)
Example: /nickserv set noop on
/nickserv set noop off |
|
| SET PASSWD |
/NickServ HELP SET PASSWD |
Details |
|
NICKSERV: SET passwd
NickServ allows you to modify your nickname password using the PASSWD command. Prior to using this command, you are required identify with the current password. Upon a successful password change an email is sent to the email adress of the nick. No passwords will be included in that email. It is just a way to inform you that the password has been changed, and if you didnt issue that change, to take action and revoke it to prevent further damage.
Command: /nickserv set PASSWD (oldPassword) (newPassword)
Example: /nickserv set passwd 38hula alohA57 |
|
| SET SHOWEMAIL |
/NickServ HELP SET SHOWEMAIL |
Details |
|
This option allows the user to choose whether or not regular IRC users gets to see their email address set during registration or via /nickserv set email
Command: /nickserv set SHOWEMAIL (on/off)
Example: /nickserv set showemail off |
|
| SET URL |
/NickServ HELP SET URL |
Details |
|
You can use this command to append a URL to your nickname. This can be anything from homepage to your favorite website.
Command: /nickserv set URL (url)
Example: /nickserv set url http://www.dal.net |
|
| SIDENTIFY |
/NickServ HELP SIDENTIFY |
Details |
|
NICKSERV: sidentify
NickServ provides a non-verbose output for the command.
Example: /nickserv sidentify fr0g452
/nickserv sidentify stud 46.Turtle |
|
Chanserv HelpChanservChanserv, DALnet's channel registration service, supplies users with a way to secure their channels from takeovers. Founding a channel gives a user the right to add and remove ops and akicks, lock channel modes, etc.
| ACCESS |
/ChanServ HELP ACCESS |
Details |
|
CHANSERV: access
With this command, you can view your channel status. The nickname parameter is optional. If none is entered, this field defaults to yourself. Here are the possible results:
-1 - User is AKicked from channel
0 - User has no access to channel
1 - User has AOp status on channel
2 - User has SOp status on channel
3 - User is on the founder nickname access list, but has not identified to either the nickname nor channel.
4 - User has founder status on channel because they have identified to the founder nickname
5 - User has founder status on channel because they have identified to the channel
Command: /chanserv ACCESS (channel) [nickname]
Example: /chanserv access #dragonrealm
/chanserv access #dragonrealm MirclMax |
|
CHANSERV: akick
AKick stands for Automatic Kick. Once placed on the akick list, the problem user will be automatically kicked and banned upon entering the channel.
Only the channel founder and SOP's are able to modify the AKick list.
Command: /chanserv AKICK (channel) (add/del/list) [nickname/user@host]
Example: /chanserv akick #flash add *!*@*.blah.net
/chanserv akick #flash del 5
/chanserv akick #flash list |
|
CHANSERV: aop
An AutoOp is a user with special privileges on a channel; one being that they will automatically be granted operator status from ChanServ upon entering the channel. Others include any setting that the channel founder of may set to AOPs or higher.
ADD - Adds new AOp nickname or user mask to list.
DEL - Deletes AOp from channel list.
LIST - Lists AOps with index number.
WIPE - Clears AOp list.
Note that only the Founder can use WIPE.
Command: /chanserv AOP (channel) (add/del/list/wipe) [nickname/user@host/index #]
Example: /chanserv aop #HotSpot add janedoe
/chanserv aop #HotSpot add *!jane@doe.org
/chanserv aop #HotSpot del 4
/chanserv aop #HotSpot del janedoe
/chanserv aop #HotSpot wipe |
|
CHANSERV: count
This command will display the number of AOps, SOps, and AKICKs in a channel. Limited to AutoOp or higher.
Command: /chanserv COUNT (channel)
Example: /msg ChanServ@services.dal.net COUNT #Macintosh |
|
CHANSERV: deop
If you have op priveledge to a channel (AOp, SOp, or FOUNDER), you have access for ChanServ to deop user(s) on the channel using this command.
You can specify more than one nick by stacking: nick1 nick2 nick3
Command: /chanserv DEOP (channel) (nickname)
Example: /chanserv deop #arhause angel-
/chanserv deop #arhause tatertot entropi evenstar the_saviour |
|
CHANSERV: drop
Dropping a channel will forfeit ownership and ChanServ will no longer have control over it.
Before dropping a channel, the user must identify to ChanServ with the channel password. After issuing that command, chanserv will give you an authorization code that you must enter in order to confirm the drop request.
Command: /chanserv DROP (channel)
Example: /chanserv drop #HotShots |
|
| IDENTIFY |
/ChanServ HELP IDENTIFY |
Details |
|
CHANSERV: identify
In order to maintain a channel, certain channel settings are often required. To modify these settings, it is necessary to identify as the channel founder. This is a function for channel security and protection.
Command: /chanserv IDENTIFY (chan) (password)
Example: /chanserv identify #toxic el3phant85
or,
/identify #fruitloops peanuThEAD |
|
CHANSERV: info
Use this command to retrieve detailed information on the specified channel, such as channel founder, registration date, channel topic, etc.
Command: /chanserv INFO (channel)
Example: /chanserv info #ohio
/chanserv info #cleveland |
|
| INVITE |
/ChanServ HELP INVITE |
Details |
|
CHANSERV: invite
When a channel is set +i (invite) or +k (requires key), a user is able to join the channel when invited. However, a user with AOp or higher status is able to have ChanServ invite them.
Command: /chanserv INVITE (channel)
Example: /chanserv invite #alligators |
|
CHANSERV: mdeop
Mass Deopping is removing the operator status of a great deal of operators at once. In this case, ChanServ will deop anyone who has a lesser status on the channel than the person issuing the command.
AOps - AOps can only use this command on channels that have the opguard option shut off. Because this command will only deop anyone who has a lesser status than you, an AOp can only deop users who have been temporarily given operator status through mode +o.
SOps - When an SOp uses this command, they will deop anyone on the channel who is an AOp or below.
Founder - When the founder uses this command, they will deop everyone on the channel, excluding themselves, of course.
Command: /chanserv MDEOP (channel)
Example: /chanserv mdeop #Soda |
|
CHANSERV: mkick
Masskicking is removes of all persons on a channel. Everyone in the channel will be kicked and banned.
If you are outranked by any individuals on the channel, this command will NOT be accepted.
Command: /chanserv MKICK (channel)
Example: /chanserv mkick #Front9 |
|
CHANSERV: op
If you have op priveledge to a channel (AOp, SOp, or FOUNDER), you have access for ChanServ to op user(s) temporarily on the channel using this command.
You can specify more than one nick by stacking: nick1 nick2 nick3
Command: /chanserv OP (channel) (nickname)
Example: /chanserv op #fishbowl venus
/chanserv op #fishbowl venus entropi evenstar the_saviour |
|
| REGISTER |
/ChanServ HELP REGISTER |
Details |
|
CHANSERV: register
Channel registration is required in order for ChanServ to aid you with routine functions of managing a channel.
Command: /chanserv REGISTER (channel) (password) (description)
Example: /chanserv register #myDogSpot L4meR456 Channel about my dog Spot |
|
| SENDAUTH |
/ChanServ HELP SENDAUTH |
Details |
|
CHANSERV: sendauth
When a founders nick expires, the successor will be sent an AUTH code by MemoServ to gain access to the channel. If the first memo fails, the successor can re-request the AUTH code to be sent to them again through MemoServ using the following command.
Command: /chanserv SENDAUTH (channel) S
Example: /msg ChanServ@services.dal.net SENDAUTH #mynewchannel S |
|
| SENDPASS |
/ChanServ HELP SENDPASS |
Details |
|
CHANSERV: sendpass
The SENDPASS command will allow a user to request that his or her channel password be sent to the email address on file for the founders' nickname. This command should not be relied on as an alternative to managing your own passwords, but only as a "backup" in case of extreme situations. Please remember that you are still responsible for remembering your password(s) and keeping them private. Do not share your password(s) with anyone.
Command: /chanserv SENDPASS (#channel) (email address)
Example: /msg ChanServ@services.dal.net SENDPASS #dalnethelp someuser@someisp.com |
|
CHANSERV: SET
The chanserv SET command is used to apply/remove specific settings for a channel.
Command: /chanserv set (channel) OPTION SWITCH
Example: /chanserv set #DragonRealm desc The Realm!! |
|
| SET DESC |
/ChanServ HELP SET DESC |
Details |
|
CHANSERV: SET desc
The channel description is set upon channel registration. This is a brief description of your channel which shows up under an INFO command. Use this command to change the currently set channel description.
Command: /chanserv set (channel) DESC (newDescription)
Example: /chanserv set #Looneybin desc We're insane!! |
|
| SET FOUNDER |
/ChanServ HELP SET FOUNDER |
Details |
|
CHANSERV: SET founder
With this command you can change foundership or change founder nicknames. You must be identified to the channel.
Command: /chanserv set (channel) FOUNDER |
|
| SET IDENT |
/ChanServ HELP SET IDENT |
Details |
|
CHANSERV: SET ident
This function forces channel AOPs and SOPs to identify to their nicknames before ChanServ grants them ops in the channel.
*note* This mode is automatically set on if opguard is enabled.
Command: /chanserv set (channel) IDENT (on/off)
Example: /chanserv set #mouse ident on
/chanserv set #mouse ident off |
|
| SET KEEPTOPIC |
/ChanServ HELP SET KEEPTOPIC |
Details |
|
CHANSERV: SET keeptopic
The keeptopic command is useful if your channel becomes unmanned at any point. Once everyone leaves the channel, all lists clear, such as the ban list and topic. With this command, ChanServ resets the last set topic.
Command: /chanserv set (channel) KEEPTOPIC (on/off)
Example: /chanserv set #cheese keeptopic on
/chanserv set #cheese keeptopic off |
|
| SET LEAVEOPS |
/ChanServ HELP SET LEAVEOPS |
Details |
|
CHANSERV: SET leaveops
Joining a empty registered channel in which you do not have access to will trigger ChanServ to deop you. To counteract this, use this command to turn LEAVEOPS on.
Please note that if the OPGUARD option is set on, LEAVEOPS is cancelled.
Command: /chanserv set (channel) LEAVEOPS (on/off)
Example: /chanserv set #foo leaveops on
/chanserv set #foo leaveops off |
|
| SET MAILBLOCK |
/ChanServ HELP SET MAILBLOCK |
Details |
|
CHANSERV: SET mailblock
Turning this feature on will prevent anyone from using the SENDPASS command on your channel. The SENDPASS command allows you to send your channel password to the email address on file for the founders' nickname. CAUTION: If you enable the MAILBLOCK feature, you will no longer be able to request your password be sent via email and you will be entirely responsible for keeping track of it on your own.
Command: /chanserv set (channel) MAILBLOCK (ON|OFF)
Example: /msg ChanServ@services.dal.net SET #dalnethelp MAILBLOCK ON |
|
| SET MEMO |
/ChanServ HELP SET MEMO |
Details |
|
CHANSERV: SET memo
After channel registration, memos are able to be sent to the channel ops. To restrict who can send channel memos, use this command.
NONE - No one is able to send channel memos.
AOP - AOps and above are able to send channel memos.
SOP - SOps and Founder are able to send channel memos.
Founder - Only the channel founder is able to send channel memos.
Command: /chanserv set (channel) MEMO (none/aop/sop/founder)
Example: /chanserv set #weLoveMemos memo aop
/chanserv set #weHateMemos memo none |
|
| SET MLOCK |
/ChanServ HELP SET MLOCK |
Details |
|
CHANSERV: SET mlock
This command locks channel modes so that they stay even after the channel clears.
Command: /chanserv set (channel) MLOCK (+Modes-Modes)
Example: /chanserv set #mIRC4Dummies mlock +tn-i
/chanserv set #mIRC4dummies mlock * |
|
| SET OPGUARD |
/ChanServ HELP SET OPGUARD |
Details |
|
CHANSERV: SET opguard
If you are concerned about your ops opping someone who might take over the channel or if you simply wish to have total control over who recieves ops, use the opguard command. When you turn this command on, only the Founder, SuperOps, and AutoOps that are list are able to receive operator status. Even if someone were to manually op someone not in the list, ChanServ would immediately deop the user.
Command: /chanserv set (channel) OPGUARD (on/off)
Example: /chanserv set #zilla opguard on
/chanserv set #zilla opguard off |
|
| SET PASSWD |
/ChanServ HELP SET PASSWD |
Details |
|
CHANSERV: SET passwd
With this command you can change channel password. You must be identified to the channel with the current founder password.
Command: /chanserv set (channel) PASSWD (current Password) (newPassword)
Example: /chanserv set #TomatoPatch passwd asdf1234 jklu456 |
|
| SET PRIVATE |
/ChanServ HELP SET PRIVATE |
Details |
|
CHANSERV: SET private
Not to be confused with the channel mode +p, the private option will not list your channel if the /list command is used. In respect to privacy, this option also cancels out the ChanServ invite command.
Command: /chanserv set (channel) PRIVATE (on/off)
Example: /chanserv set #looneybin private on
/chanserv set #ninjas private off |
|
| SET RESTRICT |
/ChanServ HELP SET RESTRICT |
Details |
|
CHANSERV: SET restrict
This option will only allow ops into a channel. If someone who joins is not on the AOp/SOp list, they will be kickbanned when they enter the channel.
Command: /chanserv set (channel) RESTRICT (on/off)
Example: /chanserv set #operhelp restrict on
/chanserv set #operhelp restrict off |
|
| SET SUCCESSOR |
/ChanServ HELP SET SUCCESSOR |
Details |
|
CHANSERV: SET successor
This option allows a channel founder to set a successor to the channel. When the founder nick expires, the successor can then with help of an AUTH code claim foundership of the channel. The first below example shows how the Nick123 is set to successor of the channel #mystro while the second shows how to remove a successor.
Command: /chanserv set (channel) SUCCESSOR [nickname] [-]
Example: /chanserv set #mystro successor Nick123
/chanserv set #mystro successor - |
|
| SET TOPICLOCK |
/ChanServ HELP SET TOPICLOCK |
Details |
|
CHANSERV: SET topiclock
In order to moderate the channel topic, ChanServ allows the founder to select the groups that are able to modify it. When turned on, this command also performs KEEPTOPIC.
SOP - Only SOp's and founders are able to change topic.
FOUNDER - Topic is managed by the founder only.
OFF - Toggles topiclock off if already set.
Command: /chanserv set (channel) TOPICLOCK (SOP/FOUNDER/OFF)
Example: /chanserv set #sharks topiclock founder
/chanserv set #sharks topiclock sop |
|
| SET UNSECURE |
/ChanServ HELP SET UNSECURE |
Details |
|
CHANSERV: SET unsecure
This option is turned OFF by default. If you set a channel unsecure, you do not have to identify to ChanServ to change channel settings. It is only required for you to have an channel access of 3 (founder nick access match). This, in turn, lessens the security of your channel.
Command: /chanserv set (channel) UNSECURE (on/off)
Example: /chanserv set #poo unsecure on
/chanserv set #poo unsecure off |
|
| SET URL |
/ChanServ HELP SET URL |
Details |
|
CHANSERV: SET url
One way to let users know you have a site for the channel is to set your channel url with the address of your page. ChanServ will announce the url to users upon entering the INFO command.
Command: /chanserv set (channel) URL (url)
Example: /chanserv set #Daddymack url http://www.mackdaddy.net |
|
| SET VERBOSE |
/ChanServ HELP SET VERBOSE |
Details |
|
CHANSERV: SET verbose
This option allows the founder of a channel the option to view commands being issued by SOps and AOps of the channel. Only valid commands that are carried out by services are displayed. Commands issued with an invalid syntax, bad parameters, or without sufficient access are not displayed.
INFO, IDENTIFY, and SET PASSWD commands are never displayed.
Command: /chanserv set (channel) VERBOSE (ON/OFF)
Example: /chanserv set #aquarium verbose on
/chanserv set #aquarium verbose off |
|
| SET WEBPASSWD |
/ChanServ HELP SET WEBPASSWD |
Details |
|
CHANSERV: SET webpasswd
Will change the password for your web site at channels.dal.net so you can delegate web access without giving out the channel password.
Command: /chanserv set (channel) WEBPASSWD [new password]
Example: /chanserv SET #italia WEBPASSWD mynewpassword |
|
CHANSERV: sop
A SuperOp is a user with high privileges on a channel; the main one being that they can add AutoOps and Akicks to the channel list. Others include any setting the founder of the channel may set to SOps or higher.
ADD - Adds new SOp nickname or user mask to list.
DEL - Deletes SOp from channel list.
LIST - Lists SOps with index number.
WIPE - Clears SOp list.
Note that only the Founder can use WIPE.
Command: /chanserv SOP (channel) (add/del/list/wipe) [nickname/user@host/index #]
Example: /chanserv sop #myCatFluffy add bandit
/chanserv sop #myCatFluffy del entropi
/chanserv sop #myCatFluffy wipe |
|
| SUCCESSOR |
/ChanServ HELP SUCCESSOR |
Details |
|
CHANSERV: successor
This command will let you remove your successor status from a channel. If a founder added you as the successor of his channel without your approval, you can use this command to remove yourself. You must identify to your nick to use this command.
Command: /chanserv successor #channel del
Example: /msg ChanServ@services.dal.net SUCCESSOR #mystro DEL |
|
CHANSERV: unban
Use this command to have ChanServ unban addresses in the channel ban list.
Recent changes were been made to ChanServ's UNBAN command. The ME option has been removed and the ALL option replaced with "*"
Command: /chanserv UNBAN (channel) [nickname/user@host/*]
Example: /chanserv unban #goose
/chanserv unban #goose taz
/chanserv unban #goose * |
|
CHANSERV: why
This command is used to tell why the given nick is gaining operator status (ops) on the given registered channel (No access, AOp, SOp, Founder).
Command: /chanserv WHY (channel) [nickname]
Example: /chanserv why #italia icequeen |
|
Memoserv HelpMemoservMemoServ allows users to send memos to other users with registered nicks even when they are offline. Memos can be sent to individual users or to all ops in a specific channel.
MEMOSERV: del
Although this command will not remove them, they will be indicated as deleted (shows up with a 'D' on a LIST command).
If instead of a number you use the ALL keyword, MemoServ will delete and PURGE all memos from your inbox, making them unable to retrieve. Exercise this with caution.
Command: /memoserv DEL (memo index)
Example: /memoserv del 4
/memoserv del 1,2,3,4 |
|
| FORWARD |
/MemoServ HELP FORWARD |
Details |
|
MEMOSERV: forward
Use the FORWARD command to forward all messages sent a nickname to another nickname. When a user sends a memo, they will see the nickname the memo is being forwarded to. This allows you to receive all your memos on one nickname, thus minimizing hassle and confusion.
Command: /memoserv FORWARD (nickname) (password)
Example: /memoserv forward zudly miCr0246 |
|
MEMOSERV: list
This command will display the first twenty memos in your memo box. An asterix (*) represents all new memos. If you wish to display memos past your first twenty, specify a starting point.
Command: /memoserv LIST
Example: /memoserv list
/memoserv list 6 |
|
MEMOSERV: news
Display the latest breaking services news with this command.
Command: /memoserv NEWS |
|
MEMOSERV: purge
You use the PURGE command to remove all memos that are marked as deleted from your inbox. Please note that after using the command all memos will be permanently lost, and unrecoverable.
Command: /memoserv PURGE |
|
MEMOSERV: read
You use the READ command to display messages sent to you. To obtain the memo index, you must use the LIST command.
You can specify more than one memo by stacking: index1,index2,index3
Command: /memoserv READ (memo index)
Example: /memoserv read 1
/memoserv read 4,5,6 |
|
MEMOSERV: send
Using the SEND command, you can send a memo to another user, or to a registered channel.
The recipient can be a registered nickname or a registered channel. Note that in both cases, some settings available to the nickname or channel owner might be set to prevent sending a memo.
Command: /memoserv SEND (nickname/channel) (message)
Example: /memoserv send testUser I love sending memos!!
/memoserv send #testUsers I love sending memos to this channel!! |
|
| SENDSOP |
/MemoServ HELP SENDSOP |
Details |
|
MEMOSERV: sendsop
Use the SENDSOP command to send a message to all channel SOPs and the FOUNDER.
The format is the same as that of the standard SEND command, only that the recipient must be a channel. The message text must be less than 255 characters long, else MemoServ will return an error, and you will need to resend the message.
Command: /memoserv SENDSOP (channel) (message)
Example: /memoserv sendsop #weLoveMemos memo to the sops, memo to the sops |
|
MEMOSERV: undel
You use the UNDEL command to undelete memos from your inbox. You need to use the LIST command to find out the memo number.
Note that memos that have been purged (using either the DEL ALL or the PURGE command) cannot be undeleted.
You can specify more than one memo by stacking: index1,index2,index3
Command: /memoserv UNDEL (memo index)
Example: /memoserv undel 3
/memoserv undel 1,2,5,7,4 |
|
|
|
|
You have no new messages