Adding mailbox and service users

Quick-start guide: home 1 2 3 4 5 6 7
 

You add mailbox and service user accounts when you want to provide someone with access to your site's services.

After you have added an account, the individual can log in to the User Administrator control panel to send and receive email, manage their contact information, and use services such as FTP, Telnet, and SSH.

To add a mailbox and service user account:

  1. Optional: If you are adding many users with similar settings, you can set the User Defaults template to preset the disk quota and services options on the Add User form.

  2. In the shortcuts area of the Home page, click Add User (Users section). The Add User form opens.

  3. In the Username field, enter the name you want the user to type when he logs on. User names can be up to 40 alphanumeric characters in length, and they cannot contain spaces.

  4. Note: This username also becomes the first part of the individual's email address (<username>@<yourdomain.com>), but you do not need to type the @ symbol or domain name in this field.

  5. In the Fullname field, enter the user’s first and last names. Names can be up to 40 alphanumeric characters in length, and they can contain spaces.

  6. In the Password field, enter the password the user will use to log on. Passwords are case sensitive, cannot contain spaces, and have to be at least one character in length. Allowed characters include: a-zA-Z 0-9 , . - _ / + $ ~ : % @ !

  7. In the Confirm Password field, enter the password again.

  8. In the Disk Quota field, enter the amount of disk space, in megabytes, you want to reserve for the user. To allow an unlimited amount of disk space, type 0 (zero). To determine how much disk space is available on your site, check the Configuration page.

  9. Note: Be aware that disk quotas are not supported on NFS-mounted servers. If you know your site is on an NFS-mounted server, or if you receive an error in this field when adding an account, type 0 (zero) in this field.

    To determine whether your site is on an NFS-mounted server, contact your service provider.

  1. Optional: enable the user's access to any of the following services:

  1. If Telnet is available to your site, you can select the Telnet check box to allow the user to connect remotely to your site's server using a Telnet connection. Through this connection, users who are comfortable using a UNIX shell environment can log on to your site and search, copy, run scripts, and perform other tasks. To prevent Telnet access, leave the check box blank.

  2. If SSH (Secure Shell) is available to your site, you can select the SSH Secure Shell check box to allow the user to connect remotely to the server using an SSH connection. SSH provides a secure connection through which users who are comfortable using a UNIX shell environment can log on to your site to search, copy, run scripts, and perform other tasks. To prevent SSH access, leave the check box blank.

  3. If FTP is available to your site, you can select the FTP check box to allow the user to use FTP, File Transfer Protocol, to transfer files between their computer and your site. This service is especially useful for individuals who need to upload content to your site and who are not using Microsoft FrontPage to publish content. To prevent FTP access, leave the check box blank.

  1. Optional: If subdomains are enabled for your site and you want to allow the user to upload Web site content to a subdomain A smaller component of a root domain name. For example, if you own the root domain name mysite.com, WEBppliance enables you to create subdomains such as sales.mysite.com. You do not need to register subdomains, since they are based on your registered root domain name, but users can access them by typing the subdomain URL in a browser just as they do mysite.com. If your service provider enables this feature, you can create and host new subdomains based on your registered domain name. instead of to your root domain, select the Create a user subdomain checkbox, otherwise leave it blank.

  2. Note: A user subdomain is a subdomain with the same name as the user being added.
    For example, if you are adding a user, Bob, to your site, mysite.com, and if you select the Create a User Subdomain checkbox, then a subdomain 'bob' will be added. The subdomain can be accessed as http://bob.mysite.com.

    For user subdomains, the web content directory defaults to the public_html directory of the user. Thus, the content for the subdomain, bob, will be placed in the directory /home/bob/public_html/.  

    If you do not want the subdomain content to default to the user's public_html directory, then you must first add the user Bob without selecting the Create a User Subdomain checkbox, then use the Subdomain Manager to add a new subdomain, and choose the owner as Bob.

   If you enable this option, you need to provide this additional information:

  1. In the CGI Support field, select an appropriate CGI script A small program written in a language such as Perl, TCL, C, or C++ that functions between HTML pages and other programs on Web servers. A CGI script might allow search data to be entered on a Web page and sent to a database management system for lookup, then formatted and returned to a user as results. option.

The options are as follows:

  1. None - Users cannot work with CGI scripts.

  2. Only in ScriptAlias - CGI scripts are, by default, placed in the /cgi-bin/ directory. Selecting the ScriptAlias option allows you to override this default and place them in a folder within the local file system of the site. This is called an alias folder.
    For example, if a cgi script is placed in the alias folder     /usr/Web/cgi-bin/ instead of the default /cgi-bin/, then a request for http://myscript/cgi-bin/search runs the script from the alias folder /usr/Web/cgi-bin/search instead of from the root folder /cgi-bin/search.

  3. In the CGI-BIN directory - Users can place CGI scripts in the default CGI-BIN directory outside the subdomain directory, /cgi-bin/ directory.

  4. In the CGI Script Extensions field, enter the extension of the application (pl, php) that can be used to write CGI scripts for the subdomain.   

  5. Note: The value in this field depends on the type of CGI support enabled for the subdomain in step 9(a).

    Default values are set for the following CGI Support options:

    None     - None.  No script support.
    Only in ScriptAlias -     ALL (any script placed in the ScriptAlias directory will be executed)

    If you choose In the CGI-BIN directory, you can specify the scripts that you want executed, for example, php, pl etc.  

  1. Click Add. The user account is added.

Be sure to notify the user that the account is ready and briefly explain how to access the account. You might want to provide instructions for accessing services you enabled in addition to providing the login information.

Login information includes:

On a Name-based site:

<user_name>@<domain_name.com>

or

<user_name>#<domain_name.com>
 

On an IP-based site:

<user_name>

On a name-based domain type:

<user_name>@<domain_name.com>
or
<user_name>#<domain_name.com
where <user_name> is the User Administrator user name and <domain_name.com> is the domain name of your site.
 

On an IP-based domain type:
<user_name>
where <user_name> is the User Administrator user name.

On a name-based site:

<user_name>@<domain_name.com>

or

<user_name>#<domain_name.com>
 

On an IP-based site:

<user_name>

On a name-based site

anonymous@<domain_name.com>

or

anonymous#<domain_name.com>

or

ftp@<domain_name.com>

or

ftp#<domain_name.com>

 

On an IP-based site

anonymous or ftp

where <user_name> is the user name you created for the user and <yourdomain.com> is the domain name of your site.

Next topic in quick-start guide: Set up your site's email services
 

Related Topics