SERVICES

Usage: SERVICES <command> <values>

There are some aspects of ConferenceRooms Services that you can customize to your needs. Some examples are that nickname and room registration can be individually enabled and disabled. 

CLONESCAN - Enable or disable scanning for clones.

DISABLE - Disable the profile.

ENABLE - Enable the profile.

FIELD - Configure nickserv information fields.

LIST - List the services settings.

MEMOSERV - Enable or disable MemoServ.

SET - Set additional options.

Example:

/as help services <command>

The defaults should be fine for most networks, but customizing your settings allows your setup to better suit your network.

Usage: SERVICES CLONESCAN [<enable|disable>]

This command enables or disables scanning for clones. Clones are multiple users from the same host. Not all clones are harmful, some are legitimate users from the same connection. 

Example:

/as services clonescan enable

Clone scanning is generally recommended. You can customize the scanning with triggers and with the AdminServ SECURITY options.

Usage: SERVICES DISABLE

This disables services on the server. Your settings all remain intact for when you want to enable them.

Example:

/as services disable

If you are part of a network where another server is providing services, then you should disable services for your server.

Usage: SERVICES ENABLE

This will enable services on your server.

Example:

/as services enable

Services must be enabled before they can be started.

Usage: SERVICES FIELD [LIST|SET] [1-12] [<name>] [<description>]

LIST - List all services fields.

SET - Set the properties on a specific field.

This command will allow you to set extended information fields in NickServ. For example, you can add fields for age, location, business or fax number. For any changes made to the services field settings, Services must be restarted before the changes are enabled.

Example:

/as help services field <topic>

NickServ fields show up when people do a /nickserv info <nick>.

Usage: SERVICES FIELD LIST

This command will allow you to list all services fields and their settings.

Example:

/as services field list

Usage: SERVICES FIELD SET [1-12] [<name>] [<description>]

Fields are numbered from 1-12. If you do not specify a description, it will use the name. The name cannot contain any spaces.

Example:

/as services field set 1 Age

By adding additional fields people can make information available to those who want to look at their profile. Additional fields let people customize how they appear on the chat network.

Usage: SERVICES LIST

This command will list your current settings for services.

Example:

/as services list

This will show you all of your settings and help you check for which options may be missed or not yet set.

Usage: SERVICES MEMOSERV [<enable|disable>]

This command enables or disables MemoServ for the server. 

Example:

/as services memoserv enable

You may wish to only offer certain services to your users. Several services can be separately enabled and disabled.

Usage: SERVICES SET <command> [<parameter>]

These commands allow you to customize several aspects of services. 

BUDDYLISTS - Enables or Disables the buddy list feature set.

CHANEXPIRE - Set the expiry time for rooms.

CHANREG - This command limits who can register a channel.

CLONE-KILL-MULTIPLIER - Sets the multiplier for killing clones.

DEFTRIGGER - Set the default clone trigger.

FOLDER - Set MemoServ features.

NICKEXPIRE - Set the expiry time for nicknames.

NICKREG - This command limits who can register a nickname.

PASSWDFILTER - Sets the complexity required of users passwords.

REGCHAN - Enable or disable registration for rooms.

REGISTER - Sets user registration options.

REGNICK - Enable or disable registration for nicknames.

Example:

/as help services set <topic>

It is useful to go over these commands so that you will understand what options are available. In most cases the default settings are sufficient, but changing them may make things work better for your particular network.

Usage: SERVICES SET ACCLIST-DEFAULT <on|off>

Controls whether services will add the default access mask when you register a nickname. "OFF" means no access list is added. "ON" means that the default access list will be added.

Example:

/as services set acclists on

This will still give users the control of being able to add access masks but does not do it for them.

Usage: SERVICES SET AUTOPROTECT <nomral|high|off>

Normal: Newly registered nicknames will require positive identification before access to the nickname is granted. 

High: Enables the 'aggressive protection' mode for nicknames. When enabled, if you attempt to use a nickname that you do not have access to, services with immediately change your nickname to Guest.

Example:

/as services set autoprotect high

/as services set autoprotect off

The reason that we don't enable this by default is that new users that are not familiar with chat will register a nickname, disconnect and then when they reconnect they don't know the NICKSERV IDENTIFY command. So you might want to give some thought to how your user base will deal with this being enabled.

Usage: SERVICES SET AUTOSECURE <normal|high|off>

Enables the 'enhanced security' mode for nicknames. When enabled, NickServ does not check access lists at all, and positive authentication via password is required before you can use your nickname.

When this is set to high services will aggressively protect a nickname and when it detects that a nickname is being used the user will be switched to guest nickname.

Example:

/as services set autosecure high

/as services set autosecure on

When high mode is used users must identify to their nicknames prior to using them.

Usage: SERVICES SET BUDDYLISTS <on|off>

Enables or Disables the buddy list feature set.

Example:

/as services set buddylists on

Usage: SERVICES SET CHANEXPIRE <days>

This command sets how many days a room must go without services opping anyone before it expires.

Example:

/as services set chanexpire 30

Expiration is important because it frees up rooms that are no longer being used or properly managed for others to take over and run. This is especially important if room registration is open to all users. Many users will register rooms and then forget about or abandon them. Short expiry times make it easier for new users to find good room names. 
However, too low an expiry time will cause people's rooms to expire too easily. Even well managed rooms may have quiet times, especially if most of the users are students and have vacations at the same time.

Usage: SERVICES SET CHANREG [disable|open|oper]

This command changes the registration behavior of channels, limiting who can register. 

The restrictions for each of the settings are as follows:

disable Channel registration is disabled. Existing registered channels remain registered and usable. 

open Channel registration is available to everyone. 

oper Channel registration is only available to users with server operator privileges.

Example:

/as services set chanreg diable

/as services set chanreg open

/as services set chanreg oper

The default for this is "open" which allows anyone with a registered nickname to register a channel.

Usage: SERVICES SET DEFTRIGGER <number>

This command sets the default trigger level for clone warnings. Clone warnings go off when there are multiple users from the same address.

Example:
 /as services set deftrigger 7

Low trigger values will pick up several legitimate sources for multiple users from the same address, primarily cybercafes. Although you can set custom triggers for specific addresses, see SECURITY TRIGGER. A large default trigger will fail to pick up many examples of harmful clones. A setting between 5 to 12 is probably best and then each warning can be investigated and dealt with appropriately.

Usage: SERVICES SET FOLDER <command> <number>

The folder commands set the limits for how many folders each user can have, how many memos each folder can hold, and how many memos from the same nick each folder can hold. The FOLDER commands work with MemoServ.

CAPACITY - Set how many memos each folder can hold or how many memos from the same nick each folder can hold.

LIMIT - Sets how many folders each user may have.

Examples:
/as help services set folder <topic>

When setting your folder limits, decide how you want to your users to use MemoServ and set limits that encourage that use. Larger limits will make memos more useful and encourage their use. Smaller limits may encourage users to only send memos for quick notes and to use other options, such as email, for more important messages.

Usage: SERVICES SET FOLDER CAPACITY <command> <number>

SOURCE - Limit memos per folder from a single source.

TOTAL - Limit the total number of memos in each folder.

This command set limits the number of memos from a single source and folders that can be created inside the memo system. 

Example:

/as help services set folder capacity <topic>

Larger memo capacities are easier on the user, while smaller values conserve space and encourage people to clean out their memo boxes. Large source values are convenient, but make it easier for users to flood each other with memos. Memo flooding is not common, since it is easy to trace and deal with users who do so, but it does happen on occasion. 
If users are allowed to create their own memo folders, then you can have a smaller source capacity, since they can move memos from users who frequently memo out of their inbox. If they cannot create new folders, you might want to allow a larger source capacity. In general a source capacity between 5 to 10 is good.

Usage: SERVICES SET FOLDER CAPACITY SOURCE <number>

Specify how many memos should each folder hold from a specific user. 

Example:

/as services set folder capacity source 10

This is a security setting that can be used to prevent memo floods from one user to another.

Usage: SERVICES SET FOLDER CAPACITY TOTAL <number>

Specify how many memos should each folder hold. 

Example:

/as services set folder capacity total 50

This can prevent Denial of Service attacks against the server itself by sending memos to users online and filling up the database with 'junk'.

Usage: SERVICES SET FOLDER LIMIT <number>

This command sets how many folders each user may have. The value must be at least three, to accommodate the three default folders. If it is three, then users cannot make their own folders.

Example:

/as services set folder limit 5

How many folders users should be allowed would depend on how you want your users to use MemoServ. If you intend them to just use memos for temporary communications, you probably want a low memo folder limit. If you want users to use memos for communications they will store and reference later, then you probably want a larger memo folder limit.

Usage: SERVICES SET NICKEXPIRE <days>

This command lets you set how many days without use it takes before a registered nickname will be dropped. 

Example:
 
/as services set nickexpire 25

As with CHANEXPIRE, the larger the expiry time the harder it will be for new users to find available nicks. But the lower the expiry time the more difficult it is to keep them. The nickexpire should probably allow for moderate vacations or temporary loss of internet access without causing the user to lose a nick, but still be small enough to clean out unused nicks. 
Especially since some people will register nicks and either forget they had them or become bored with chat and stop altogether. A limit between 20 and 35 is probably good.

Usage: SERVICES SET NICKREG [disable|open|verify|oper]

This command changes the registration behavior of nicknames, limiting who can register, or what kind of verification should be required before finalizing the registration. 

The restrictions for each of the settings are as follows:

disable: Nickname registration is disabled. Existing registered nicknames remain registered and usable. 

open: Nickname registration is available to everyone. No verification is performed. 

verify: Nickname registration is available to everyone. Verification of the e-mail address specified is performed, and a registration code which must be supplied to services within 24 hours in order to complete the registration is sent back via e-mail. Existing registered but unverified nicknames remain registered, but cannot be added to channel access lists unless verified. 

oper: Nickname registration is only available to users with server operator privileges. No verification is performed.

Example:

/as services set nickreg diable

/as services set nickreg open

/as services set nickreg verify

/as services set nickreg oper

The default for this is "open" which allows everyone to register nicknames without additional verification. 
When using "VERIFY" mode, the SMTP feature must be properly configured. If it is not, mails may not reach their intended destination, and registrations may expire. 

Notice: Services maintains an extensive database of valid top-level domains that it uses to verify if a nickname is valid or bogus. The database is processed once during startup and kept in memory after that. In the event that a new top-level domain is created, it may be necessary to receive an updated version of the database (or edit the file) to ensure proper validation of e-mail addresses.

Usage: SERVICES SET PASSIVE <enable|disable>

Makes services act in PASSIVE mode -- nobody will get opped/voiced by ChanServ unless they explicitly ask services to do so using the OP command. 

Example:

/as services set passive enable

Usage: SERVICES SET PASSWDFILTER <none|basic|extended>

This command configured the built-in services password filtering engine. This can be used to enforce limitations on what is a valid password. It can be very useful because it can prevent users from using their nickname, channel name or the word "password" as their password.

Example:

/as services set passwdfilter none

/as services set passwdfilter basic

/as services set passwdfilter extended

Passwords must always be at least 4 characters long, but not longer than 32 characters, and cannot contain non-printable characters, such as the "bold attribute" (Ctrl-B in mIRC) or the "color attribute" (Ctrl-K in mIRC). Each setting implies all restrictions imposed by lower settings
 
The following restrictions apply only when the filter level is set to "basic":

The minimum password length is increased to 6 characters

The password cannot contain the word "password" or"drowssap" 

The password of a nickname cannot contain the nickname being registered 

The password of a channel cannot contain the name of the channel being registered

The following restrictions apply only when the filter level is set to "extended":

The password must contain at least one character from at least two of the following character groups: uppercase letters (A-Z), lowercase letters (a-z), digits (0-9) and symbols (punctuation marks, currency symbols, arithmetic operators, etc) 

The password of a nickname cannot contain the e-mail address or "real name" field of the nickname being registered 

The password of a channel cannot contain the description of the channel being registerered 

The password of a channel cannot be the same as the password of the channel founder's nickname.

Usage: SERVICES SET REGCHAN <disable|open|opers>

This command will configure how services will allow users to register channels. You can disallow all users, let all users or only allow server operators:

Disable: Channel registration is not enabled.

Open: All users can register channels.

Opers: Only Server Operators can register channels.

Example:

/as services set regchan open

/as services set regchan opers

/as services set regchan disable

You could, in theory, only allow the registration of rooms. But since having a registered room requires a registered nickname, this is not a generally useful configuration. You can disallow both, allow both, or allow only registration of nicknames. The advantage of only allowing nick registration is that you can set up all the rooms you want in advance and then close registration.

Usage: SERVICES SET REGISTER <command> <enable|disable>

CHANS - Allows you to disable channel registration.

NICKS - Allows you to disable nickname registration.

These commands allow you to allow or disallow registration of nicknames and rooms. You can allow registration of just nicknames while not allowing people to register rooms.

Example:

/as help services set register <topic>

You could, in theory, only allow the registration of rooms. But since having a registered room requires a registered nickname, this is not a generally useful configuration. You can disallow both, allow both, or allow only registration of nicknames. The advantage of only allowing nick registration is that you can set up all the rooms you want in advance and then close registration. 
But nickname registration is much more important for an enjoyable chat experience. Nicknames give users a persistent identity on the chat network.

Usage: SERVICES SET REGISTER CHANS <enable|disable>

Enable or disable room registration.

Example:

/as services set register chans disable

When set off no one can register rooms.

Usage: SERVICES SET REGISTER NICKS <enable|disable>

Enable or disable nickname registration.

Examples:

/as services set register nicks enable
		
When set off no one can register nicknames. Most of the services command set will not be useful to users without a nickname.

Usage: SERVICES SET REGNICK <disable|open|verified|opers>

This command will configure how services will allow users to register nicknames. You can disallow all users, require email verification, let all users without verification or only allow server operators:

Disable: Channel registration is not enabled.

Open: All users can register channels.

Opers: Only Server Operators can register channels.

Verified: Used when you want to have email verification for nicknames.

Example:

/as services set regnick disable

/as services set regnick open

/as services set regnick verified

/as services set regnick opers

If verified is set then you must have an SMTP server configured otherwise this will default to open.

Usage: SERVICES SET REMOTE-OPER <enable|disable>

This command is only applicable when OperServ is enabled. It controls whether services will be able to grant operator privileges to configured users, using the command "/OS OPER <nickname> <password>". This can be especially useful in multi-server networks, where duplicating the list of operators on each server would be cumbersome.

Example:

/as services set remote-oper enable

The list of operators is maintained by OperServ, and is configurable by the command "/OS OPERCFG". Only operators entries that are enabled and have a password configured can take advantage of the remote-oper feature.