";
}
?>
Note that the only difference than the example from PHP manual is
how we send status headers.
* On some PHP providers, you are not allowed to configure PHP
yourselves. Any reconfiguration or module additions will require
pestering their system administrator. On our system, it is not
necessary to get in touch with our system administrator to change
PHP configuration (however we will be gladfully help you if you
ask us). Please see the previous sections on how to configure PHP
on our system.
Using CGI Scripts in General
CGI scripts are basically regular scripts that called by web browser.
You can create CGI scripts by using Perl, Python, Ruby or even shell
scripts and C/C++.
To use CGI scripts you need to name your scripts with any of these
extensions: .cgi, .pl, .py. You will also need to chmod +x or chmod
0755 your CGI scripts. AutoCorrect can do that automatically to all of
your CGI scripts, please see the section called "Using AutoCorrect
Feature" for more information.
When developing CGI scripts, you might need information about the
exact location of interpreters or utilities such as Perl interpreter
or UNIX sendmail. These information can be obtained from Language
Settings menu.
Caution
CGI scripts must be in UNIX text format. If you create the scripts
within Microsoft® Windows® environment you will need to use ASCII mode
when uploading using FTP, or fix the uploaded file afterwards by using
AutoCorrect. Please see the section called "Using AutoCorrect Feature"
for more information about AutoCorrect.
Installing Perl CPAN Modules
CPAN is a repository of Perl modules. Perl is shipped with command
line tools to automatically install Perl modules. indoglobal.com goes
a step further by offering an interface for customers to install CPAN
modules from SiteManager.
To install CPAN modules, go to Perl Settings under Language Settings
from SiteManager. There you will see the currently installed Perl
modules under your account.
Click Perl Module Installation start installing Perl module. On the
next screen you will see detailed instruction on how to install Perl
module. First, you should try automatic install first. If it fails
then you can try the other methods in order. Automatic installation
sometimes won't work if the module in question requires user
interaction when installing.
To perform the other methods of installation, you need to log on to
your shell account. Please refer to the section called "Logging in to
UNIX Shell Account" for more information.
Using Active Server Pages (ASP)
Active Server Pages (ASP) is a web development environment commonly
used in legacy Microsoft® Windows® based server environment. While
indoglobal.com uses Linux servers exclusively, we also offer Sun ONE
Active Server Pages for our customers who need to run their legacy ASP
based scripts on our servers.
Note
If you starting a new development and not starting from existing
legacy ASP based code, consider using programming language other than
ASP. While our servers supports ASP, it is not the native environment
for running legacy ASP based scripts, especially when the ASP code in
question is developed under Microsoft® Windows® environment. Other
languages like PHP or Perl are better supported on our servers.
In order to use ASP, as usual you need to name your files with
extension .asp. Make sure the extension is in lower case, especially
when you are uploading from a Microsoft® Windows® environment. Please
also note that filenames on our servers are case sensitive. This is
different from Microsoft® Windows® environment where filenames are
case insensitive.
For more information about developing ASP applications using Sun ONE
Active Server Pages, please see the official documentation.
Tip
If you find ASP is too limiting for developing your application, you
can try converting your ASP scripts to PHP scripts. Please refer to
the section called "Converting ASP Scripts to PHP" for more
information.
Difference From Microsoft® Windows® Version
ASP's native environment is Microsoft® Windows® and therefore most ASP
scripts also developed under Microsoft® Windows®. Since indoglobal.com
uses Linux based servers exclusively, care must be taken when
developing ASP based application. The following listed several
differences between original Microsoft® Windows® version of ASP and
Sun ONE ASP installed on our servers.
* Case sensitivity. Filenames are case insensitive in Microsoft®
Windows® environment, while under Linux they are case sensitive.
It is advisable that you use lowercase to name files and also when
referencing a filename inside your ASP code.
* Database support. Most ASP application developed under Microsoft®
Windows® system uses Microsoft® SQL Server(TM) or Microsoft®
Access® for its database backend. However, under our servers there
are no option to use either product, you will need to use MySQL or
PostgreSQL as your application's database backend. If you already
have database under Microsoft® SQL Server(TM) or Microsoft®
Access® you will need to migrate your data to one of our supported
database products. There are several utilities for converting your
data to MySQL at
http://www.mysql.com/doc/en/Contrib_converters.html. For
PostgreSQL, there are also several useful conversion utilites at
http://techdocs.postgresql.org/.
* Connecting to database. ASP applications developed under
Microsoft® Windows® typically use ODBC system DSN to make
connection to database. However, for security reason we don't use
system DSNs. Instead you will need to use DSN-less connection
string. For more information about connecting to databases, please
refer to the section called "Using MySQL Database in Your
Application" or the section called "Using PostgreSQL Database in
Your Application".
ASP Components
Other than the standard ASP components, there are also other popular
ASP components:
* SMTP sending component. We use the CDONTS.NewMail similar to
NewMail component included with Microsoft IIS. However it does not
include these properties and methods: AttachURL, ContentBase,
ContentLocation, MailFormat, SetLocaleIDs, Version.
* POP component. This component is used to retrieve email messages
from a POP3 server.
* File upload component. This component enables users to save files
uploaded by site visitors to the server.
For more information on how to use these components, please refer to
ASP Online Help at http://aspdoc.indoglobal.com.
Using AutoCorrect Feature
AutoCorrect is a feature of SiteManager that will attempt to
automatically fix common errors. At the moment, it will attempt to do
the following.
* Fix the attributes of home directory. Improper permission of your
home directory could result in security hole or problem serving
your web files.
* Fix the attributes of web files. AutoCorrect will automatically
fix attributes of web files such as HTML, or CGI.
* Convert legacy Microsoft® Windows® text files to standard UNIX
text format. Text files include most CGI scripts, HTML and PHP
files. Using Microsoft® Windows® format will result in problems
serving most CGI scripts.
* Lowercase the extension of web files. File extensions such as
.html, .cgi or .php must be in lowercase, AutoCorrect will try to
automatically fix those.
* Create support files, directories and symlinks if they are not
already exist. Some directories and files under your home
directory is required for some applications. Deleting these could
result in problems. For example, PHP session support needs to
store session files under var/state/php under your home directory,
if this directory is missing, PHP session will not work correctly.
Note
Please try AutoCorrect first if you encountered errors on your web
site.
To use AutoCorrect, please do the following:
1. Log on to SiteManager if you haven't already done so.
2. Click on AutoCorrect on the navigation bar.
3. On the next screen you will be prompted by a confirmation screen.
Click Yes and then click AutoCorrect.
Access Control Configuration
indoglobal.com provides an easy way to restrict access to part of your
web site. You can manage your web users and groups information. You
can also modify access control information for part of your web site.
All can be done conveniently without leaving SiteManager.
Managing Your Web Users and Groups
Our SiteManager has a database for storing username and password
information. You can use this database for authenticating access to
part of your web site. You can manage this database by using Web User
& Group from inside SiteManager
There are several operation that can be done from this menu.
* Creating new user. Click on Create new user menu and fill the
information of the new user on the next screen. The most important
part is User ID and password, they are used by your users to
authenticate themselves. You can also fill the group membership if
you want this user to be a member of a group. A user can be a
member of more than one group.
* Creating new group. Click on Create new group and fill the group
information on the next screen. The important field here is Group
ID.
* Deleting a user or group. You can delete a user or group by using
delete link on the right side of user or group ID you want to
delete.
* Editing a user or group. You can edit a user or group by using
edit link on the right side of user or group ID you want to edit.
Please note that you will not be able to change the user or group
ID.
Restricting Access to Part of Your Web Site
There are several place where the above user & group database can be
useful inside SiteManager.
* Restricting access to part of your web site.. You can restrict
access to part of your web site by using Access Control menu under
file manager. Please see the section called "Using SiteManager's
File Manager" for more information.
* Restricting access for WebDAV users. You can restrict access for
your WebDAV users by using DAV Access Control menu under
filemanager. Please see the section called "Using WebDAV to Manage
Files" for more information about WebDAV.
* Restricting access to your log files analysis result. You can do
that by using Site analysis access control under Log Files &
Analysis menu. Please see the section called "Access Control
Configuration" for information.
Under each of those menus, you can configure who has access to a
particular resource. On the configuration page you will see several
fields.
* Authentication String. This is the string sent to web browser as
an identifier. You can leave this to default if you wish.
* User Allowed to Access. Specify which class of users you want to
allow access to this resource. You can allow any visitors, allow
any authenticated user, allow users belong to specific group(s),
or only allow specific user(s). To allow specific users or groups,
you also need to specify in the selection box which users or
groups will be allowed.
* Host Allowed to Access. You can specify which host to allow or
deny access here. You can allow all hosts except the listed hosts,
or you can deny all hosts except the listed hosts.
* Access Allowance. This field configures how user and host based
authentication above interacts. You can choose if access granted
whenever both user authentication and host authentication are
successful. You can also choose to grant access if any of user
authentication and host authentication is successful. Leave it to
default if you don't understand.
Creating a Graphical Counter
You can easily create a graphical counter using file manager.
1. Log on to SiteManager if you haven't already logged on.
2. Go to File Manager menu and then click browse on the subdomain in
which you want to create the counter. You also might want to
browse for directory where you want to put the counter into.
3. Click on Create Counter when browsing your subdomain contents.
4. On the next screen you need to specify the name of the counter
file. The counter will be created under the current directory. You
also need to specify the digit style and starting value of the
counter. You can choose from our extensive collection of digits
consisting more than 500 digit styles!
5. Click on Create Counter to create the counter
On the confirmation screen you can see the code you need to paste to
your HTML files. For example if you created a counter named
'mainpage.count' then you will need to use the HTML fragment similar
to this to call the counter:
Log Files and Analysis
Every hit to your web site will be logged to a log file on our server.
That log file will then be rotated, archived to your account, and
analyzed once every 24 hours.
Active Log Files
Before getting rotated, every log files are not owned by your account.
If your account username is u777, your active log files are stored
under directory /home/userdata/u777/logs/. Every log files under this
directory are still active, data is still being written into it.
Inside this directory, there are several log files:
* active_http_access_log, logs access to HTTP web server.
* active_https_access_log, logs access to HTTPS web server.
* active_httpdav_access_log, logs access to WebDAV over HTTP server.
* active_httpsdav_access_log, logs access to WebDAV over HTTPS
server.
* active_http_error_log, logs errors for HTTP web server.
* active_https_error_log, logs errors for HTTPS web server.
* active_httpdav_error_log, logs errors for WebDAV over HTTP server.
* active_httpsdav_error_log, logs errors for WebDAV over HTTPS
server.
* active_pop3_log, logs access to POP3 server.
* active_smtpauth_log, logs email deliveries done using our SMTP
server.
* active_smtp_in_log, logs incoming email deliveries to your
account.
* active_smtp_out_log, logs outgoing email deliveries from your
account.
Note
Every active log files are not owned by your account. And therefore
they won't use your account's disk space allocation.
Archived Log Files
Active log files are archived every 24 hours. Every 24 hours, all the
active log files above are compressed and moved to your home
directory. If your account's username is u777 then your log archive
directory is /home/u777/logs.
Important
We don't guarantee the log rotation will always run everyday. If you
find one or several days are missing, you will find the data for the
particular day(s) in the next archived log file.
Unlike the active logs, the archived log files do take up your
account's disk space. You can set the maximum size of archived log
files you want to keep in your account. If the amount of archived log
files exceeds the specified maximum size, our system will start
deleting old log files until they are below the specified maximum
size. This maximum size defaults to 5000 KB. To change the maximum
archived log files please do the following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Log Files & Analysis menu.
3. Inside you will see the current maximum size of archived log files
to keep. To change it, go to Change log files configuration menu.
4. On the form, change the value of field 'Size of old log files to
keep' and click Update.
You can also download the archived log files. You can download them
using standard means such as FTP, scp or sftp.
Log Files Analysis
Your log files will also get analyzed by our system while rotated. The
result of analysis will be stored under stats directory under your
home directory. For example if your username is u777 then they are
stored under /home/u777/stats. By default you can access them from a
web browser by visiting http://stats.example.com, assuming your domain
name is example.com.
Our system uses third party analysis engines when analyzing. Currently
we use Webalizer and AWStats. By default only Webalizer engine is
used. You can change which engine to use from Log Files & Analysis
menu.
Access from web site to the analysis results (i.e.
http://stats.example.com) by default is restricted only to group
administrator. By default nobody is member of this group, you still
need to define user that will be allowed to access them from Web Users
& Groups.
Tip
You can change the time zone used in your log files and analysis
results by changing the time zone setting at the Preferences menu.
To change which user or group that will be granted access to your
analysis results, you can use Site analysis access control menu under
Log Files & Analysis menu. For more information about access control
in general please refer to the section called "Access Control
Configuration".
Running Scheduled Tasks
Task scheduler is used if you want to run a task periodically. To add
a new task to be scheduled, please do the following steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Task Scheduler menu where you can see the list of your
scheduled tasks.
3. Click on Add New Scheduled Task to add a task.
4. On the next screen you will see three fields. 'Task Name' is the
name of the task, you can put anything to describe the task you
want to create, it will be shown on your list of scheduled task.
The second field 'Command to Run' is the most important, please
specify the complete command line of task you want to execute. The
third field 'Comments' is simply a comment box, you can specify
any information here. Click on Add New Task to proceed.
5. Go back to the main Task Scheduler menu. You will see the task in
question, but it is not scheduled to run yet. To create a schedule
for this task, click edit on the right of the task in question.
6. Click Add New Schedule to create a schedule for this task.
7. Follow the instruction on the next screen. You can add yearly,
monthly, weekly, daily or hourly schedule. You can also set this
task to run everytime our server boots.
Tip
You can add more than one schedule to a single task.
On the edit task menu, you can also edit the task information if you
need to change something. For example if you want to change the
command line to perform.
Tip
To schedule a PHP script, you can use wget as the command line. For
example, you want http://example.com/daily.php to be scheduled, you
can use a command line like 'wget http://example.com/daily.php -O- -o
/dev/null'.
Creating HTML to Email Forms
Sending email to the owner of the site is fairly common.
indoglobal.com provides an easy way to do this. You don't have to
install your own HTML form to email CGI scripts. Of course you may
still install your own CGI scripts if you wish.
Our preinstalled form to email handler resides on
/global/nms-fmail.cgi. To make use of it, you need to write an HTML
form that refers to that script. Here's an example HTML snippet code
which will send mail to address feedback@example.com when someone
submits the form.

Please enter your comments

Form Configuration
The hidden 'recipient' input field in the example above told the HTML
form to email script who to send the email to. This is how the script
configuration works. Here is the full list of field names that you can
set using hidden form inputs.
* recipient: the email address to which the form submission should
be sent. If you would like it copied to more than one recipient
then you can separate multiple email addresses with commas. Please
note that you are not allowed to send emails to outside of your
domain, for example you cannot set recipient field to email
addresses not ending with example.com, assuming your domain
account is example.com.
* subject: the subject line for the email.
* redirect: if this value is present, it should be a URL and the
user will be redirected there after successful form submission. If
you don't specify a redirect URL, then instead of redirecting, it
will generate a success page telling the user that their
submission was successful.
* bgcolor: the background color of the success page.
* background: the URL of the background image for the success page.
* text_color: the text color for the success page.
* link_color: the link color for the success page.
* vlink_color: the vlink color for the success page.
* alink_color: the alink color for the success page.
* title: the title for the success page.
* return_link_url: the target URL for a link at the end of the
success page. This is normally used to provide a link from the
success page back to your main page.
* return_link_title: the label for the return link.
* sort: This sets the order in which the submitted form inputs will
appear in the email and on the success page. It can be the string
'alphabetic' for alphabetic order, or the string 'order:' followed
by comma separated list of the input names. For example the sort
field of 'order:name,email,age,comments' will have the fields
ordered as such.
* required: this is the list of fields that the user must fill in
before they submit the form. If they leave any of these fields
blank then they will be sent back to the form to try again.
* missing_fields_redirect: if this is is set, it must be a URL, and
the user will be redirected there if any of the fields listed in
'required' are left blank. Use this if you want finer control over
the error that the user sees if they miss out a field.
* env_report: This is a list of the CGI environment variables that
should be included in the email. This is useful for recording
things like the IP address of the user in the email. For example
you could specify env_report value of
'HTTP_USER_AGENT,REMOTE_ADDR,REMOTE_HOST' if you want the form to
report back to you the web browser, IP address, and hostname of
the submitter.
* print_blank_fields: if this is set then fields that the user left
blank will be included in the email. Normally, blank fields are
supressed to save space.
As well as the above hidden inputs, there are a couple of non hidden
inputs which get special treatment.
* email: this will be used as the address part of the sender's email
address in the email.
* realname: this will be used as the name part of the sender email
address in the email.
Using SSL/TLS
SSL (Secure Sockets Layer) or TLS (Transport Layer Security) is used
to secure traffic between two hosts on the Internet. For example it
can be used for securing traffic from and to an e-commerce site.
By default SSL/TLS is enabled on your account but using a self signed
certificate. That means users will be asked to trust the certificate
before using the service. A self signed certificate is like a fully
signed certificate, traffic will be fully encrypted. The only
difference is it is not trusted by web browsers, users will need to
trust the certificate before using the service.
Getting and Installing a Fully Signed Certificate
You also have the option to use a fully signed certificate with the
following condition.
* A fully signed certificate signed for your domain will require a
dedicated IP address. By default your account will not have a
dedicated IP address. Please refer to our homepage or contact our
sales department to get a dedicated IP address.
* You will need to get your certificate signed by a certificate
authority by yourself. They will probably ask you to give them
some information about your domain and an administrative fee.
Important
Please note that any dedicated IP address request must be justified.
We will only grant a dedicated IP address to accounts that absolutely
require fully signed SSL/TLS certificate such as e-commerce sites or
similar sites.
To install a fully signed certificate to your account please follow
the following steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to SSL/SSH/OpenPGP menu and then SSL/TLS Settings menu.
3. In this page you will see the current information about your
current SSL/TLS certificate. If you haven't installed an SSL/TLS
certificate it should tell you that SSL/TLS certificate is not
installed. Click on 'Install or Renew SSL/TLS Certificate'.
4. In this page there are a step by step instructions you need to
take. The first step is to generate or import web server private
key. Choose accordingly from the action field and follow the
instructions. Only choose import if you already have a private key
with another server.
5. Next, create a certificate signing request (CSR). Click on Create
on the action field. On the next screen you will be asked
information about your organization. A special field is Common
Name, you will need to enter your domain name to be used in the
certificate here, you can also enter your subdomain name here.
Please note that only one domain or subdomain may be specified
here, you can't specify all of your subdomains. Please double
check the name of your domain before continuing. When done, click
on Create CSR
6. On the next screen you will be presented with a text box
containing a CSR block. You will need to copy this text fully
(including the BEGIN CERTIFICATE and END CERTIFICATE line.
7. Make the necessary arrangement with your choice of certificate
authority to get your certificate signed. You probably will need
to pay them an administrative fee. You will also need to confirm
your identity, probably by phone. Usually you will need to send
them the necessary paperwork, either by fax or by mail. You will
also need to send them your certificate signing request (CSR) at
some point, usually by copying and pasting it to a web form or
sending it by email. Every certificate authorities differs in the
way they verify your information, please contact them if you need
more information.
8. If the certificate authority authorizes you, you will receive an
SSL/TLS certificate from them. Please save this certificate to a
file and don't lose it!
9. Go back to the Install SSL/TLS Certificate menu and upload the
certificate to our web server. Click on 'upload' on the right of
'Upload the SSL certificate from certificate authority' step. On
the next screen you will be presented with a text box. Paste the
SSL/TLS certificate content to this box. Make sure you also
include the lines BEGIN CERTIFICATE and END CERTIFICATE.
10. (this step is optional) If the certificate authority requires an
intermediate CA certificate or server certificate chain, you will
need to upload it here. Your certificate authority will provide
you with the intermediate certificate you can upload here if
required.
11. Activate the SSL/TLS key pair to install them to our web server.
Please wait at most one hour before the certificate gets
installed.
Warning
Do not delete your web server private key after you receive your
certificate from certificate authority. Doing so will make it
completely unusable and you will need to regenerate it again..
Note
An SSL/TLS certificate file has an expiration date. You will need to
renew your SSL/TLS certificate when it expires.
Migrating From Another Server
We provide a feature for you to easily migrate your web contents from
another server. This is useful if you are migrating from another web
hosting company.
To migrate your web contents please do the following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Migration Tools menu and then Migrate web contents from
another server menu.
3. On the first screen you will be asked about the target subdomain
where you will download the files. Please note that any web files
inside this subdomain will possibly be overwritten.
4. Click on Next. On the next screen choose the type of remote host,
please choose accordingly.
5. Follow the instructions on the next screens. The amount of
information you need to provide depends on the type of host you
choose on the previous screen.
Checking Your Web Site from Link Errors
Sometimes when developing a web site you will sooner or later make a
mistake when creating a link. Also, an external URL could no longer be
available and thus a link to it will become a dead link. We provide a
tool to check your web site for such errors.
To check your web site for linking errors, please do the following.
1. Log on to SiteManager if you haven't already done so.
2. Go to Miscellaneous menu and then go to Check your web sites for
link errors.
3. On the next screen, choose your current subdomains you want to
check for linking errors. And then click Check for Errors.
The analysis might take some time to finish. When it finishes, it will
send you an email notification. The result will appear under your web
statistic subdomain in the directory linbot/. By default the result
will be under http://stats.example.com/linbot/ assuming your account's
domain is example.com.
Converting ASP Scripts to PHP
Sometimes programming in Active Server Pages (ASP) could be very
limiting. PHP on the other hand is a similar language but have a lot
more features and flexibility. You have the option to convert your ASP
scripts without doing everything from scratch again.
To attempt to convert your ASP scripts to PHP, you need to do the
following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Miscellaneous menu and then go to ASP to PHP converter sub
menu.
3. Inside, you will be presented with several fields. Choose your
subdomain on the 'subdomain to convert' field to convert every ASP
files inside that subdomain. You also have the option to choose
more than one subdomain.
4. On the database field, please specify the database used by the ASP
script you want to convert. Or you can choose Automatic detection
to let it detect the database automatically. If the ASP scripts in
question does not use database, please use Automatic detection.
5. If the ASP scripts you want to convert come from a non Y2K
compliant Microsoft® Windows® NT Server, please set Y2K Problem
Handling to 'yes'.
6. On the variable name case mangling field, you can choose if you
want to converter to change the case of variables. Variable names
in ASP is case insensitive, unlike PHP where variable names is
case sensitive. You can use this option to force the case of
variable names.
7. On the last field, you can choose if you want every created PHP
files includes global.php.
8. Click on Convert ASP to PHP in order to start the conversion.
Important
ASP to PHP conversion is not guaranteed to be 100% perfect. However it
is still better than rewriting the scripts from scratch.
File Permission
Important
Don't worry if you don't understand anything in this section, just use
AutoCorrect to fix almost all your permission problems automatically.
Any file in your account needs to be in correct permission before it
can function correctly. You can change file permission by using
SiteManager's file manager or FTP. AutoCorrect will also fix your
files' permission automatically. If you find your scripts do not
function correctly, please try AutoCorrect first. For more information
about AutoCorrect please refer to the section called "Using
AutoCorrect Feature".
Directories on your account need to be in mode 0755. This is the
default when creating directories, so you won't need to do chmod after
creating them. More permissive mode (like 0755) is not allowed, CGI
scripts will refuse to function if placed within too permissive
directories.
Dynamic CGI scripts (such as Perl, Python, or Ruby) should be in mode
0755. Static files (such as HTML documents or images) should be at
least in mode 0644 (but it won't hurt to have them in 0755). Under no
circumstances should files be in mode 0666 or 0777.
Important
Some scripts come with installation manual that tell the user to chmod
files or directories to mode 0777 or 0666. This is not required in our
system where CGI scripts are running as their own owner privileges. In
fact, in some cases, our system will refuse to run scripts when they
are in those modes.
Database Server Administration
Table of Contents
Types of Database
Creating and Managing Databases
Managing MySQL Database
Dumping and Restoring MySQL Database
Using MySQL Database in Your Application
Managing PostgreSQL Database
Dumping and Restoring PostgreSQL Database
Using PostgreSQL Database in Your Application
Types of Database
indoglobal.com offers two types of database servers: MySQL and
PostgreSQL. Both are popular databases dan sometimes required by third
party software.
MySQL Database
MySQL is the most popular relational database management system
(RDBMS) in the Internet today. A lot of web applications, free or
commercial depends on MySQL for their database backend. The speed,
compactness and simplicity of MySQL makes it suitable for most web
sites.
PostgreSQL Database
PostgreSQL is another popular database product. It has a complete set
of features found in higher end database systems. While not as popular
as MySQL, PostgreSQL still have its place in web sites. Quite some
third party applications utilizes PostgreSQL as backend database
server.
Support for More Than One Database
indoglobal.com offers these two databases to its clients. You can
create more than one database on an account. This has the advantage
that it will simplify your development process since you can easily
separate database for various functions, and will not clobber a single
database with various unrelated tables.
Aside from that, you will also find a lot of third party software that
uses the same table name, especially with common table names such as
'user' or 'group'. If you need to install two or more programs that
uses a table named 'user' and only allowed to use only a single
database, then you are in trouble. The only solution would be to edit
those programs so that it would use another table name. In
indoglobal.com system you are able to create two databases for two
different programs and they won't conflict or require heavy
modifications.
You are allowed to create as many databases as you need. The maximum
limit of databases you can create is only limited by your disk space
quota.
Creating and Managing Databases
To create a database, please follow the following steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database server menu.
3. Inside database server menu, there are two options for creating
database, one for MySQL and one for PostgreSQL. Click on
appropriate menu to create a database.
4. Specify the name of database and its password. You can use the
Generate to generate a random password. For PostgreSQL, please
also specify the encoding to be used in the new database.
5. Click on Create Database button to create the database.
Note
Database name is always prepended with your account username in order
to avoid name conflict with other users.
From the database server menu, you can see the currenly created
databases. There are also several actions you can do to your existing
databases.
* manage, this will manage your database from inside SiteManager you
can add tables, modify tables, make a dump, execute queries, and
others. This is currenly only available for MySQL database.
* password, this is used to change your database password.
* delete, this is used to delete your database. Please be careful
when using this function, since it will delete the database and
its contents without means to reverse the action.
* example, shows you how to connect to the database, execute a
simple query and disconnect in various popular languages.
Managing MySQL Database
Our SiteManager includes a complete administration interface for
managing your MySQL database. To access it, go to Database server menu
and click on manage for the database you want to manage.
Alternatively you can also manage your MySQL databases using the more
familiar command line tools.
Managing MySQL Database Using Command Line
To manually manage your MySQL databases, you need to log on to your
shell account. Please see the section called "Logging in to UNIX Shell
Account" for more information about logging on to your shell account.
Inside shell account, you can use the standard MySQL command line
client to manage your database. If your database name is u777_database
and the password is PASSWORD, you can connect to the database by
issuing the following command.
mysql -uu777_database -pPASSWORD u777_database
Inside MySQL shell, you can issue any SQL command to the database
server. Please consult MySQL documentation for more information.
Note
Due to security concerns, our database servers do not allow LOAD DATA
or any SQL commands that accesses filesystem directly.
Managing MySQL Database Using Alternative Software
While we provide a way to easily manage your MySQL Database, you may
opt to use third party tools. There are basically two class of MySQL
management software: web based application that might need to be
installed on the server, and client based application that must be
installed on user's computer.
The first class of MySQL management software need to be installed on
your account, just like other regular web based application. One
popular software of this class is phpMyAdmin. To configure these kinds
of management software, follow the instruction in the section called
"Using MySQL Database in Your Application".
Important
There are several administration task that can't be done from third
party management software. For example, you can't use them to create
database.
The second class of management software are basically regular client
application that must be installed on your computer. These software do
their work by remotely connecting to MySQL database on our server. You
need to supply several information to the software before it will be
able to work correctly:
* Hostname: primary-ip.example.com, assuming your domain name is
example.com
* Database name: specify the name of database you want to connect
to. For example: u777_database
* Username: the name of database, the same as your database name
above.
* Password: the password of this database that set from SiteManager
Creating new Table
Tables can be created by using Create New Table menu. To create a
table, please follow these steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to create. From there click on Create New Table.
3. On the first screen you need to enter the table name, the table
type and an optional comment. Table type can be MyISAM, ISAM or
BerkeleyDB. The difference of each table types is described at
MySQL manual. Click Next to continue.
4. On the next screen you need to specify the name and type of the
first field of the table. You can add more fields later in the
following menu. Click Next to continue.
5. On the next screen you will see your current information about the
table you want to create. At this point the table is not created
yet. You can add or remove more fields and indexes. The interface
should be self explanatory.
6. When done designing table, choose Finished, create the table.
Modifying Table Structures
You can also modify table structures after it has been created. You
can add and remove fields and indexes. To modify table structure,
please do the following steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to create. From there click on edit structures
for the table you want to modify.
3. Follow the instruction on the next screen. You can change table
type, create new field, modify or drop existing fields, create new
index or drop existing index.
Caution
Changing table type might result in lost of certain table attributes.
Please see MySQL documentation for more information.
Deleting/Dropping MySQL Table
To delete a MySQL table, please do the following:
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to create. From there click on drop for the
table you want do delete.
3. Confirm your action on the next screen.
Note
Tables that have been dropped cannot be recovered. Please be careful
when dropping tables.
Modifying Records inside a MySQL Table
You can also add new records and modify existing records inside a
MySQL table from SiteManager.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to create. From there click on browse records
for the table you want do edit its records.
3. Inside the menu, you will be able to add new records or modify the
existing ones. The interface should be self explanatory. You can
change how the records are sorted by modifying the appropriate
drop down boxes.
Note
You can't delete or edit records on a table without primary key.
Manually Entering SQL Query
You can also manually enter SQL queries from SiteManager. This allows
you to perform more complex tasks by entering SQL queries directly
into MySQL database. To manually enter SQL queries, you need to do the
following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to enter queries into. From there click on SQL
shell.
3. Inside the menu, you will be able to perform SQL queries by typing
SQL commands into the text area and clicking on Send Query. If you
enter an SQL command that returns a result, the result in question
will be displayed at the bottom of the page.
Tip
In this page there are tables and fields drop down boxes containing
the currently created tables and fields in the current database.
Clicking on the drop down box will input the value into the text area.
There are also a history field containing previous SQL commands you
performed before.
Note
Due to security concerns, our database servers do not allow LOAD DATA
or any SQL commands that accesses filesystem directly.
Repairing and Optimizing MySQL Database
Sometimes database can get corrupted due to various reasons. You can
attempt to fix your database by doing the following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to repair. From there click on Check, repair,
analyze and optimize all tables.
Dumping and Restoring MySQL Database
Dumping and restoring are fairly common task of managing database.
Dumping is a process of making a file containing SQL queries that can
be used to construct the whole database. Dumping is commonly used to
download your database for backup or other purposes. Restoring is the
reverse process of dumping.
Dumping MySQL Database Using SiteManager
To dump MySQL database please do the following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to dump. From there click on Dump database.
3. Inside the menu, there are several options you can choose to
determine how you want the database to be dumped. Choose
accordingly and click Dump Database.
The available options are described below.
* What to dump. You can choose to dump both structure and data,
structure only or data only.
* Add DROP TABLE. If this option is selected, a DROP TABLE command
will be created before creating tables. Useful if you want to
replace existing database on the target database.
* Add LOCKs. If this option is selected, a LOCK TABLE command will
be added before creating tables.
* Complete INSERTs. Use complete INSERT command.
* Include all MySQL specific create options. This will include MySQL
specific create options such as specifying the type of table.
* Compress result. You can choose whether to compress the result or
not. You can choose gzip or bzip2 compression.
Note
Sometimes the dump result is not compatible with different MySQL
version. Please consult MySQL documentation for more information.
Restoring Database Using SiteManager
The dump file created above can be used for restoring database. You
can also use dump file created elsewhere, and optionally compressed
with gzip or bzip2. To restore database please do the following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Database Server menu and then click on manage for the
database you want to restore into. From there click on Batch
Query.
3. Inside the menu, you need to choose an MySQL dump file on your
system and then click on Send Query to continue. Optionally you
can choose if you want MySQL to ignore when it encounter an error
when restoring database.
Manually Dumping Database
You can also manually dump database using your shell account. You can
also make SQL dump files on other system using this method. To make an
SQL dump you need to log on to your shell account. Refer to the
section called "Logging in to UNIX Shell Account" for more
information. Issue the following command to dump your database. The
following assumes your database name is u777_database with the
password PASSWORD.
mysqldump -uu777_database -pPASSWORD \
u777_database > u777_database.sql
That command should create a file named u777_database.sql containing
the SQL dump. You can make a gzip compressed SQL dump by issuing the
following command instead of the above, useful when your database is
large in size.
mysqldump -uu777_database -pPASSWORD \
u777_database | gzip > u777_database.sql.gz
Manually Restoring Database
Similarly, to restore a database from a dump file, please do the
following command.
mysql -uu777_database -pPASSWORD \
u777_database < u777_database.sql
To do the same but with a gzip compressed dump file, do the following
instead of the above.
gunzip < u777_database.sql.gz | \
mysql -uu777_database -pPASSWORD \
u777_database
Tip
On the above commands, you can substitute gzip with bzip2 to use bzip2
instead of gzip compression.
Using MySQL Database in Your Application
To connect to MySQL database, you need to specify the following in
your application.
* Hostname: localhost or 127.0.0.1. Or if it is possible, use UNIX
socket /var/lib/mysql/mysql.sock
* Database name: specify the name of database you want to connect
to. For example: u777_database.
* Username: the name of database. In other words, this is the same
as your database name above.
* Password: the password of this database where can be set inside
SiteManager.
The following examples illustrates how to use MySQL database inside
your application, assuming the database to be used is u777_database
with password 'PASSWORD'.
Tip
You can also see examples inside SiteManager. Go to Database Server
and then click examples for the database in question.
Using MySQL Database With PHP
Using MySQL Database With Perl
# code taken from Perl DBI documentation
use DBI;
# connecting to database
my $username = 'u777_database';
my $password = 'PASSWORD';
my $dbh = DBI->connect("DBI:mysql:$username",
"$username", "$password");
# executing a single query without result
my $rv = $dbh->do($sql);
# retrieving result from a query
my $arrayref = $dbh->selectall_arrayref($sql);
# disconnect from database
my $rc = $dbh->disconnect();
Using MySQL Database With Python
import MySQLdb
# connecting to database
username = "u777_database"
password = "PASSWORD"
hostname = "localhost"
conn = MySQLdb.Connect(host=hostname,
user=username, passwd=password, db=username)
# create result/cursor object
cursor = conn.cursor()
# perform a query
cursor.execute(sql)
# get result set
result = cursor.fetchall()
# close the connection
conn.close()
Using MySQL Database With ASP
connect_string = "Driver={Mysql}; " & _
"Server=localhost; Database=u777_database; " & _
"UID=u777_database; PWD=PASSWORD"
' opening connection to database
set dbConn = server.createObject("ADODB.connection")
dbConn.open connect_string
' perform a query
Set recordset = dbConn.Execute(SQL)
' closing connection
dbConn.Close
Managing PostgreSQL Database
At the moment you need to log on to your shell account in order to
manage your PostgreSQL database. Please see the section called
"Logging in to UNIX Shell Account" for more information about logging
on your shell account.
When inside your shell account, you can use the standard psql command
line utility to administer your PostgreSQL database. Assuming your
PostgreSQL database name is u777_database, you can connect to your
PostgreSQL database by issuing the following command.
psql u777_database u777_database
When asked for password, enter your database password.
Inside psql shell, you can issue SQL commands. Please see PostgreSQL
documentation for more information.
Dumping and Restoring PostgreSQL Database
Dumping is a process of making a file containing SQL queries that can
be used to contruct the whole database. Dumping is commonly used to
download your database for backup or other purposes. Restoring is the
reverse process of dumping.
Dumping PostgreSQL Database
To dump your PostgreSQL database you need to be logged on to your
shell account. Please see the section called "Logging in to UNIX Shell
Account" for more information about logging on shell account. Assuming
your database name is u777_database, you need to use the following
command to dump your PostgreSQL database.
pg_dump -U u777_database u777_database \
> u777_database.sql
That command should create a file named u777_database.sql in the
current directory. You can use FTP or other means to download the
file.
To make a gzip compressed dump file, you can use a few modification to
the above command.
pg_dump -U u777_database u777_database \
| gzip > u777_database.sql.gz
Restoring PostgreSQL Database
To restore previously dumped database you need to use psql.
psql -U u777_database u777_database -f - \
< u777_database.sql
Similarly, you can use the following command to restore PostgreSQL
database when the dumped file is gzip compressed.
gunzip < u777_database.sql | \
psql -U u777_database u777_database -f -
Tip
In order to use bzip2 instead of gzip compression, you need to
substitute gzip with bzip2 and gunzip with bunzip2 respectively.
Using PostgreSQL Database in Your Application
To connect to PostgreSQL database, you need to specify the following
in your application.
* Hostname: localhost or 127.0.0.1.
* Database name: specify the name of database you want to connect
to. For example: u777_database.
* Username: the name of database. In other words, this is the same
as your database name above.
* Password: the password of this database where can be set inside
SiteManager.
The following examples illustrates how to use PostgreSQL database
inside your application, assuming the database to be used is
u777_database with password 'PASSWORD'.
Tip
You can also see examples inside SiteManager. Go to Database Server
and then click examples for the database in question.
Using PostgreSQL Database With PHP
Using PostgreSQL Database With Perl
# code taken from Perl DBI documentation
use DBI;
# connecting to database
my $username = 'u777_database';
my $password = 'PASSWORD';
my $dbh = DBI->connect("DBI:Pg:$username",
"$username", "$password");
# executing a single query without result
my $rv = $dbh->do($sql);
# retrieving result from a query
my $arrayref = $dbh->selectall_arrayref($sql);
# disconnect from database
my $rc = $dbh->disconnect();
Using PostgreSQL Database With Python
import pgdb
# connecting to database
username = "u777_database"
password = "PASSWORD"
hostname = "localhost"
conn = pgdb.Connect(host=hostname, user=username,
passwd=password, db=username)
# create result/cursor object
cursor = conn.cursor()
# perform a query
cursor.execute(sql)
# get result set
result = cursor.fetchall()
# close the connection
conn.close()
Using PostgreSQL Database With ASP
connect_string = "Driver={Postgres}; Server=localhost; " & _
"UID=u777_database; PWD=PASSWORD"
' opening connection to database
set dbConn = server.createObject("ADODB.connection")
dbConn.open connect_string
' perform a query
Set recordset = dbConn.Execute(SQL)
' closing connection
dbConn.Close
Improving Security
Table of Contents
Classes of Security
Keeping Third Party Software Up to Date
Writing Secure Scripts
Use Secure Protocols When Managing Your Account
What To Do When a Security Incident Happens
By its nature, it is harder to secure a web hosting environment. It is
very easy to secure a server whose job is solely serving web pages,
just close all ports besides HTTP port and make sure the web server is
up to date. However, in shared web hosting environment, it is not
possible to do that. What's good a web server, if you, our customers,
can not update your web site.
While indoglobal.com tries very hard to improve server security, our
clients are also responsible for securing their own accounts. In this
chapter, we will discuss many ways to improve your account's security.
Classes of Security
There are several classes of security in web hosting environment, each
with its own owner of responsibility. Each responsible party will need
to secure their own 'perimeter' before total security can be achieved.
Network Security
Basically, the server hosting your account is connected to a network,
which in turn connected to a much larger network called the Internet.
Successful attack to the network will make servers inside the network
unreachable or at least not easy to reach from the Internet. These are
some examples of attacks that target the network:
* Denial of service (DoS) attack. This attack sends a lot of data to
a target server or network so that the server or network will not
have enough bandwidth in order to serve legitimate requests. The
data sent are usually junk random data, but sometimes they are
specially crafted packets in order to confuse certain services.
* Distributed Denial of Service (DDoS). This kind of attack are
similar to DoS above, however DDoS attacks are launched from
several hosts on the Internet simultaneously, usually from
trojaned, zombie or cracked hosts. DDoS are several magnitude more
catastrophic than a simple DoS. Even big networks such as Yahoo!,
Amazon, CNN, and EBay had been taken down by DDoS attacks.
* Attack to network router. A network is connected to the Internet
through one or several routers. A successful attack to a strategic
router can bring down the whole network.
These classes of attacks are the responsibility of indoglobal.com's
upstream providers.
Server Security
These classes of security involves the server itself. Illegitimate
gain to a server usually achieved by exploiting a known vulnerability
of a service running on the server. Sometimes it is also possible for
an attacker to bring down the server instead of gaining an illegal
access.
These classes of security are the responsibility of indoglobal.com. We
try to make sure any software running on the server contain no known
vulnerabilities. If a vulnerability on a service were found, we always
try to update the software in question as soon as possible. We also
implement server firewall in order to make it harder for irresponsible
parties to gain illegal access to our server.
Since every user on our system doesn't trust each other, we also try
very hard to implement a clear separation between our users while
still allowing them to do administration tasks without hassle. A user
on our system should not be able to access other user's files or data.
User Account Security
The rest of this chapter will mostly discuss this class of attacks.
These attacks involves illegitimate gain to your account, for example:
* Shell vulnerability. Crackers can exploit these vulnerability to
get them shell access to your account.
* Cross site scripting (XSS). XSS occurs when a web application
gathers malicious data from a user, and then present the data to
another user verbatim without escaping. This could allow a
malicious user to hijack another user's account.
* SQL injection attacks. In this class of attacks, an attacker
inserts a carefully crafted query string to a vulnerable script in
order to confuse the script in question into executing any
arbitrary SQL commands.
User account security are the responsibility of our user. It is
impossible to expect us to be able to audit every code in every user's
account line by line and make sure all of them do not contain any
vulnerability. So it is important for our clients to update third
party software when a vulnerability is found. It is also important to
reduce mistakes when developing your web application. This chapter
will discuss these topics in greater detail.
Keeping Third Party Software Up to Date
We can't stress enough that security is a process, not a one time job.
No software is perfect, you shouldn't assume the software you
installed is without security problem. There might be security problem
that hasn't been discovered yet.
Once you installed a third party software, you will need to monitor
its development progress. If a security related problem is found, you
will need to update the installed software. If you continue to let the
software running without updating it, malicious party will be able to
take advantage of the security problem. The longer it runs unpatched,
the greater the risk.
To monitor the software's development, usually you just need to visit
the software' web site regularly. If a security problem is found,
often they will put an announcement on their web site.
Some software suffers from security problem more often than the
others. Below we list several software that traditionally has serious
security problem.
* PHP-Nuke. PHP-Nuke is a very popular portal system. However it
suffers from several security problem in the past. You should
visit their web site at http://www.phpnuke.org from time to time
just to know if an update is released to fix a security hole.
PHP-Nuke has a modular plugin architecture, if you use a module
from outside PHP-Nuke distribution, you will also need to monitor
the module's web site.
* PostNuke. Postnuke is a similar system to PHPNuke. While it is
considerably more secure than PHP-Nuke, it did have several
security problem in the past. It is a good idea to monitor their
web site at http://www.postnuke.org.
Writing Secure Scripts
This users' guide doesn't aim to be a complete guide on how to write
secure scripts. Instead, we will point you to several web site that
specialized on the topic.
Securing PHP Scripts
* http://www.onlamp.com/pub/a/php/2003/07/31/php_foundations.html
* http://www.developer.com/lang/article.php/918141
* http://www.devshed.com/c/a/PHP/PHP-Security-Mistakes/
* http://www.sklar.com/page/article/owasp-top-ten
* http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO/php.
html
* http://www.linuxjournal.com/article.php?thold=0&mode=nested&order=
2&sid=7237
Securing CGI Scripts in General
Securing against cross site scripting (XSS) attacks:
* http://www.cgisecurity.com/articles/xss-faq.shtml
* http://www.cert.org/advisories/CA-2000-02.html
* http://httpd.apache.org/info/css-security/
* http://www.perl.com/pub/a/2002/02/20/css.html
Securing against SQL or command injection attack.
* http://www.securiteam.com/securityreviews/5DP0N1P76E.html
* http://www.4guysfromrolla.com/webtech/061902-1.shtml
* http://www.aspectsecurity.com/topten/injection.html
Use Secure Protocols When Managing Your Account
Some communication protocols send data in clear text. This is not
desirable because a malicious third party could inspect your data on
the way to our server. Fortunately, there are safer alternatives that
doesn't expose your data so easily.
To provide access to your shell account, we provide two means: telnet
and SSH. To improve security, you should consider avoiding telnet.
Telnet sends your username and password in clear text. On the other
hand, SSH encrypts communication between you and our server. An
eavesdropper will have hard time if you are using SSH instead of
telnet.
We provide several ways for you to upload your web site contents. Each
way has different security implications.
* FTP. FTP doesn't encrypt your data, an eavesdropper could see your
username and password in plain text.
* WebDAV. WebDAV over HTTP (port 81) will not encrypt your data.
WebDAV over HTTPS (port 444) will encrypt your data.
* SiteManager file manager. Uploading your data using SiteManager
should be safe as long as you enable secure mode when logging in.
* Microsoft® FrontPage®. You can use Microsoft® FrontPage® over HTTP
or HTTPS. Use Microsoft® FrontPage® HTTPS mode to increase
security.
* scp, sftp, rsync. These protocols use SSH transport, and therefore
should be secure.
What To Do When a Security Incident Happens
Even if we did our best, sometimes we get unlucky. Maybe the attacker
found the vulnerability by himself before the software author get
noticed. Or maybe the attacker was simply lucky to find your web site
before you had a chance to make an update. Once an incident happens,
you need to do the following things.
1. Firstly, don't panic. Contact us if you require assistance.
2. You will need to erase all of your contents and then reupload from
your local backup. There is a chance that the malicious party
inserted a backdoor in your scripts.
3. Update any program or scripts to the latest version. Contact the
software maker of simply visit their web site for more
information.
4. If you happen to know the identity of the irresponsible party, do
not under any circumstances get in touch with them. A lot of these
people are people with serious mental problems. Talking with them
will not make you better, and certainly will not restore your web
site. Any contact to these people should be in the form of legal
action.
Email Management
Table of Contents
Types of Email Accounts
Creating a New Email Account
Default Mail Handler
Mandatory Email Accounts
Checking Emails
Configuring Spam Filter
Using Global Email Password to Access Your User's Account
Protecting Your Email With SPF
indoglobal.com offers a complete email system. You will be able to add
accounts and configure them to tailor to your own requirement.
Types of Email Accounts
There are several types of email accounts you can create.
* POP/IMAP account. Email sent to this type of account will be
stored on the server. Users then will be able to download their
email by using an email client software or check their mails by
using webmail. A POP/IMAP account also functions as a Jabber®
account, please see Jabber Instant Messaging for more information
about Jabber®
* Email forwarder. This type of email accounts will forward any
incoming mail to another email address. For example, you can
forward your emails to your account with a local ISP, but you can
use the address associated with your domain, not your ISP.
* Mailing list. Mailing list consists of its members' email
addresses. Any email sent to a mailing list account will be
distributed to its members. Our mailing list system is fully
automatic, for example a user can become a member by themselves,
email bounces are handled automatically, etc.
* Auto responder. Autoresponder will immediate reply any incoming
email with a given message. Beside that, the incoming message can
be forwarded to another email address as well.
* Email bouncer. This type of email account will simply reject any
incoming email, just like when this account has not been made. For
a reason why this email type is sometimes necessary, please refer
to the section called "Default Mail Handler" for more information.
* Email blackhole. This type of email account will simple discards
any incoming emails.
* Custom mail handler. An advanced user can use dynamic email
processing by using custom mail handler. To use this feature, you
need a working knowledge on how our email server (qmail-1.03)
works.
Tip
POP/IMAP email accounts are also user configurable to forward email to
another address and also as an autoresponder (vacation).
Creating a New Email Account
To create an email account please do the following steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Email menu.
3. Inside the email menu, there are links where you can add the types
of email accounts described above. Click on the link and follow
the instructions on the next screen.
Depending on which type of account you want to create, you will be
presented with different options:
* POP/IMAP account. You can limit the maximum size of the mail
account. If a new email arrives when the mailbox is full, then it
will be bounced back. You can specify 0 (zero) if you don't want
to limit the size.
* Email forwarder. On the add new mail forwarder menu, you need to
specify the forwarding destination. You can also specify more than
one email address by separating them with space.
* Mailing list. On the add new mailing list menu, you will need to
specify the owner of the mailing list. You also need to specify
the type and membership restriction of mailing list. You can alter
mailing list configuration later after the mailing list has been
created.
* Auto responder. On the add new autoresponder menu, you need to
specify forwarding destination where you want any incoming email
be forwarded to and the contents of autoresponder email, including
from, subject and the body of autoresponder mail.
* Email bouncer. You need to specify the message that will be
returned to the sender when an email sent to this address.
* Email blackhole. You don't have to specify anything when adding a
blackhole email address.
* Custom mail handler. You need to specify the custom action to take
whenever an email message arrives. Specify the action in dot-qmail
format.
Caution
Custom mail handler feature is for advanced users only, you need to
know about qmail server in order to use this feature.
Default Mail Handler
If your email users are located in one single location, for instance
in the office or school, you can use the default mail handler feature
of our email system. Using default mail handler together with a local
mail server will make your email system more efficient.
Note
Default mail handler is also known as DomainPOP or catchall email
address.
The default mail handler is given to each created subdomain that can
receive email. With default mail handler, any email that get sent to
an undefined address in the respective domain (or subdomain) will be
saved in the default mailbox that is located on our server. Then your
own email server in turn can download the whole mailbox and distribute
the email to a local mailbox on your email server* This way, your
users don't need to connect directly to our mail server, thus saving
your time and bandwidth.
This will explained better in example.
1. You create a mail server using MDaemon on your facility.
2. You add three users to your mail server: joe@uk.example.com,
john@uk.example.com and jane@uk.example.com. You configure your
mail server to deliver email to these users locally and assign
them password for your users to access their mailbox on your mail
server.
3. You create subdomain uk.example.com on our server and configure it
to use default mail handler. You don't create the individual
mailbox on our server, otherwise their email won't get sent to the
default mail handler.
4. You configure your own mail server to download email from the
default mail account default@uk.example.com periodically. Your
mail server then will sort the incoming emails and distribute them
to your users, while bouncing any emails with unknown
destinations.
5. Your users in turn will be able to download their own email from
your mail server inside your facility.
The default mail handler will handle all emails that the address has
not been defined by you. In example above, if your add
john@uk.example.com on our mail server, the email will get sent to a
mailbox on our server, not the default mail handler. Additionally,
this is where the email bouncer accounts come in handy. For example,
whenever john@uk.example.com resigns from your company, you can assign
a mail bouncer on our server, so any email that get sent to john will
bounced at our mail server, and you don't need to download john's
email again, saving you some bandwidth.
Warning
Lots of spammers employ spamming technique known as 'dictionary
attack'. They don't harvest email addresses, but they simply guess
email addresses of a known domain. If you are using default mail
handler and a spammer tries to 'dictionary' your domain, then you will
get a lot of mails to nonexistant users.
Editing Default Mail Handler
To edit the default mail handler, please do the following.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Email menu. On the default mail handler section, click edit
on the right of subdomain you want to edit its default mail
handler.
3. On the next screen you can change the default action. You can
change it to return to sender as undeliverable (default), deliver
to POP/IMAP account, or forward to another email address.
4. If you choose to forward to another email address, you need to
specify mail forwarding destination.
5. If you choose to deliver to POP/IMAP account, you need to specify
the password that can be used to download incoming email using POP
or IMAP.
6. Click Update Default Mail Handler to finalize your changes.
To download email messages and distribute them to your local user, you
will need to use an email client software that understand how to
manage multiple email accounts in a single POP/IMAP mailbox. This
software probably must also act as a POP/IMAP server itself to be able
to distribute mail to your local users. Examples of such clients are
MDaemon or Fetchmail.
Important
You must tell your default mail handler client to filter incoming
email messages using 'X-Rcpt-To' or 'X-POP3-Rcpt' headers. Please
refer to the client software's manual for more information on how to
do this.
Mandatory Email Accounts
There are some email addresses that are required by Internet standards
or common practice.
* postmaster@example.com, required by Internet standards to contact
the email administrator of the domain example.com.
* hostmaster@example.com, this address is used to contact the DNS
adminstrator of example.com.
* abuse@example.com, this address is a common practice within
Internet community to report abuses involving the domain
example.com.
By default emails to those addresses are forwarded to your contact
email address. You can change where they are forwarded by following
these steps.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Email menu and then click on Mandatory Mail Accounts
Configuration menu.
3. Specify where you want to forward email coming to mandatory email
accounts and click Update Mandatory Accounts to save the changes.
In addition of the mandatory email accounts, you can also set the
bounce email address. This is the default address that will receive
any bouncing email from your scripts.
Checking Emails
Every POP/IMAP accounts can be downloaded to users' computers by using
an email client software.
Note
This section only applicable to POP/IMAP email accounts. Other type of
email account cannot be downloaded to user's computer.
Receiving Emails
To receive emails, you need to set your email clients with the
following configuration.
* Protocol: POP3 or IMAP4. POP3 is more suitable for offline
operation where you download all emails at once, empty the server
mailbox, and read them offline. IMAP4 is more suitable for online
operation, it supports more features but some implementation of
client software will require emails to be stored on the server.
* Port: use standard port number, 110 for POP3, and 143 for IMAP4
* Hostname: pop.example.com or imap.example.com assuming your
account's domain is example.com. Both will work by default for
both protocols (POP3 or IMAP) assuming you haven't altered the
corresponding aliases from subdomain menu. It is recommended to
use imap.example.com for accessing using IMAP and pop.example.com
for POP3.
* Username: the complete email address, for example:
'john@example.com' without quotes. Or if your client software
doesn't support @ sign, you can use % (percent) instead, for
example: 'john%example.com' without quotes.
* Password: the password you set for the POP/IMAP email account in
question.
For more information about configuring popular email client software,
please refer to Appendix C, Email Clients Configuration.
Sending Emails
To send emails, it is recommended to use indoglobal.com's SMTP server
where possible. Alternatively, you may also use your ISP's SMTP server
if possible. However, if you choose to use your ISP's SMTP server,
please see the section called "Protecting Your Email With SPF".
However, some ISPs doesn't provide an SMTP server you can use to send
emails using email address hosted by our server. If this is the case,
you can use our SMTP server as follows.
* Protocol: SMTP
* Port: 8025 or 587, please note this is not the standard SMTP port
number
* Hostname: smtp.example.com assuming your account's domain is
example.com. This will work assuming you haven't altered the
corresponding aliases from subdomain menu.
* Username: the complete email address, for example:
'john@example.com' without quotes. Or if your client software
doesn't support @ sign, you can use % (percent) instead, for
example: 'john%example.com' without quotes.
* Password: the password you set for the POP/IMAP email account in
question.
Important
Due to the fact that our SMTP server is always farther than your ISP's
SMTP server, sending email using our server will always be slower than
using your ISP's SMTP server. To avoid abuses we are also forced to
make the necessary changes to our SMTP server that could make it
slower.
Note
Any email sent through our SMTP server will have its From address
rewritten.
For more information about configuring popular email client software,
please refer to Appendix C, Email Clients Configuration.
Checking Email Using Webmail
Webmail is a convenient way to check your email. With webmail you can
check your email anywhere with Internet access and a standard web
browser. You don't even need to configure an email client software
when using webmail.
Note
Webmail can be used only for your POP/IMAP email accounts.
When first creating your account, your webmail is configured at
http://webmail.example.com by default, assuming your domain is
example.com. Please see Subdomain and DNS for more information about
subdomain and DNS in general.
To log on to webmail, you need to visit your webmail address using a
web browser such as Mozilla or Microsoft® Internet Explorer®. On the
login screen, specify your POP/IMAP account email address and password
to log in. Inside the webmail, everything should be self explanatory.
Caution
On a shared or public computer, please make sure to log out from
webmail when leaving your computer.
Checking Email From WAP Devices
You can also check your email using a WAP device such as cell phone or
PDA. The address of WAPmail is the same as webmail, by default it is
http://webmail.example.com assuming your domain is example.com.
Our webmail system will automatically detect your device. If you are
using a standard web browser you will be redirected to standard web
mail. If you are connecting using a cell phone, you will be redirected
to a simplified WAP version.
Tip
Some mobile devices are also capable as a standard web browser. To
force it to use WAP (i.e. to conserve bandwidth), you can use URL like
http://webmail.example.com/wap instead.
Configuring Spam Filter
According to some studies, spam or junk email messages are the worst
thing happening in the Internet. We provide several ways to reduce the
volume of spam you need to deal with every day.
To configure spam filter, you need to log on to your webmail. Please
see the section called "Checking Email Using Webmail" for more
information about webmail. Inside webmail, then go to Options and then
Spam Filter.
Inside you can choose how would you like to combat spam. There are
several level of spam protection you can use, each with its own
weakness and strength. The levels of spam protection are described
below.
* Level 0: Spam protection disabled. When using this level, spam
protection is disabled. You will receive spam along with your
legitimate email messages.
* Level 1: Common keyword analysis. Our system will analyze incoming
email for certain keywords. If the number of keywords found
reaches a certain threshold, our system will treat the email as
spam and deliver it to Junk Mail folder.
* Level 2: Spam learning system. You tell our system which email
messages are spam and which ones are not. Our system will then
attempt to identify spam based on your input.
* Level 3: Challenge and response system.. Our system will keep
record of all legitimate senders. Any unknown senders will need to
confirm themselves in order to send you email messages.
More information about each level is described on the following
sections.
Spam Protection Level 1
With this level active, you don't need to anything else. Any
identified junk email messages will be delivered to your Junk Mail
folder. This method however is not as effective as the other levels of
spam protection. When using this level, it is better if you check your
Junk Mail folder for legitimate email messages that get misclassified.
Spam Protection Level 2
When using this level, you will need to get a bit involved with spam
filter. This level of protection requires your feedback, you need to
tell our spam filter which messages are junk email messages and which
ones are not. There are several ways to accomplish this.
Note
Flagging messages as spam or not spam will still work if this level of
spam filter is not active. However our system will not use this
information to classify incoming email messages.
* From mailbox view (the view that comes up when you click INBOX or
other folders) where you can select using the checkboxes on the
left of each of message. Check all email messages that are
spam/not spam and then click Spam or Not Spam, respectively.
* From email view (the view that comes up when you click on an email
message). Click spam or not spam depending on the legitimacy of
the message.
Note
Any email messages that marked as spam will be automatically moved to
your Junk Mail folder
You will need a sizable amount (1000+) of learned email messages
before the filter becomes effective. But when it becomes effective, it
is very effective when filtering spam.
Important
You need to identify both spam and non spam email messages you
receive. Identifying only spam messages is not enough.
Spam Protection Level 3
This level of spam protection requires active participation from both
you and the other party of email communication. This level of spam
filter combines several countermeasures such as whitelists, blacklists
and challenge and response. Spam protection level 3 should be very
effective, however it requires your active participation and a bit
knowledge on how the system works. On some cases it will also require
your peers to answer challenge sent to them.
Important
You need to understand how the system works before using spam filter
level 3. Failing to understand could result in loss of email messages.
When this level is active, every email destined for you will subject
to whitelists and blacklists. If the sender's email address is in your
whitelist, the message will be delivered to you. On the other hand, if
the sender's email address is in your blacklist, the message will be
bounced back. If the sender's email address is not listed on either
your whitelist or blacklist, then our email system will send a
challenge to the sender, if he/she replies the challenge then the
message in question will be delivered to you and he/she will be added
to your whitelist, so that he/she won't have to get challenged again
when sending you another email in the future.
Important
When subscribing to a Yahoogroups! or an ezmlm based mailing list, you
need to whitelist its extension address. For example, if you want to
subscribe an ezmlm mailing list list@example.com, you will need to
whitelist list-*@example.com.
You can also edit your whitelist and blacklist manually. From inside
webmail, go to Options and then Whitelist and Blacklist Management.
Inside, you will be able to add email address to or remove existing
ones from your whitelists and blacklists. You can also use wildcards
to specify multiple address, here are some common examples.
* *@example.com will match anyone@example.com but not
anyone@sub.example.com
* *@*.example.com will match anyone@sub.example.com but not
anyone@example.com
* *@=example.com will match both anyone@example.com and
anyone@sub.example.com
By using spam filter level 3, in addition of the main email address
(i.e. user@example.com) you can also use extension addresses. There
are several types of extension addresses.
* Dated Addresses. Our system can automatically tag your message
with a temporary email address which only works for a defined time
internal (e.g. one week). During this period, even those not on
your whitelist will be able to contact you using the dated
address. An example of a dated address is
user-dated-1063892913.a4d8d3@example.com, this particular address
can only be used to send you email unchallenged before 18
September 2003.
* Sender Addresses. Sender address is an email address that only a
certain sender can use to send you email. An example of a sender
address is user-sender-a29ecf@example.com. This address will only
accept messages from test@example.com unchallenged. Other messages
must go through the confirmation process.
* Keyword Addresses. Keyword address is a special address which will
work for any sender and indefinitely unless specifically revoked.
Any string can be used as the keyword. An example of a keyword
address is user-keyword-amazon.8w06e8@example.com, the keyword of
this address is 'amazon'. Keyword address are useful when you need
to give your address to another party but can't predict beforehand
the sendier address that will be used to send you email. For
example, you can use keyword address for signing up to Amazon or
eBay. If you later find out that Amazon misuse your address, you
can revoke this address by blacklisting the keyword address.
When composing email and spam filter level 3 is enabled, you have the
option to use extension address. This way, the 'from' field of your
email message is replaced by your extension address.
Note
By default, if you send an email to an address that hasn't whitelisted
yet, that address will be whitelisted automatically to prevent
deadlock when communicating with users that using similar system.
You can also generate extension address manually, useful if you need
to hand out an email address without sending an email message (e.g.
when dealing with a HTML form that asks for your email address). To
generate extension address manually, go to Options, then Spam Filter,
and then generate extension address.
Using Global Email Password to Access Your User's Account
Sometimes it is necessary to be able to access your user's email
account. Global email password can be used to access your user's email
account without changing their regular password. You only need to use
global email password in place of your user's regular password. For
example, you can log on to your user's webmail account by using their
username and the global email password. This will also work with your
users' POP and IMAP accounts.
Important
Although email accounts and Jabber® instant messaging accounts share
the same username and password, you cannot use global email password
to log on to your user's Jabber® account.
To change your global email password, please do the following:
1. Log on to SiteManager if you haven't already logged on.
2. Go to Email menu and then proceed to Edit Global Email Password.
3. On the next screen, specify a password in both fields. Choose
Update Global Password
4. Now you will be able to use the password you specified in place of
your user's password.
Protecting Your Email With SPF
Email has a weakness: it allows anyone to forge anyone else's email
address. This means any person could send a message claiming to be
from you, and only an email expert would be able to tell the
differences. Spammers, viruses and worms exploit this weakness all the
time. Viruses and worms often send emails with forged from address to
trick the recipients into opening it. Spammers almost always
impersonate innocent email address when sending their spam.
SPF protects you from this. It specifies which hosts on the Internet
can send mail as a specific user. SPF aware mail servers will then
reject emails that don't come from the specified hosts.
indoglobal.com supports SPF. By default any host on the Internet may
send email from your domain. This is the most expected setting today,
however you should change it to something more restricting in order to
be able to protect your domain from impersonation.
To configure your domain's SPF records, please follow these
instructions.
1. Log on to SiteManager if you haven't already logged on.
2. Go to Subdomain & DNS.
3. Choose edit mail handler for the domain you wish to configure its
SPF records.
4. You can review the current SPF configuration for the domain in
question in this page. To configure SPF, choose Configure approved
outgoing mail servers.
5. Follow the instructions and then choose Configure SPF Record to
save your settings. Please note that the server hosting your
account is automatically added to SPF record, you don't need to
add our server's hostname or IP address.
Note
Please allow 24 hours before the new SPF record can take effect.
Important
We recommend that you use our SMTP server when sending emails. If you
choose to send using your own or the ISP's SMTP server, please make
sure it is whitelisted in SPF.
Jabber® Instant Messaging
Table of Contents
About Jabber
Creating Jabber Account
Using Jabber Client Psi
Tips for Using Jabber
About Jabber®
Jabber® is an open instant messaging platform that uses an open,
XML-based protocols to create the standard functionality people expect
of an IM system: one-to-one chat, multi-user chat, the ability to
subscribe to someone else's presence, and so on. Jabber has been
approved as proposed Internet standard by Internet Engineering Task
Force.
The way Jabber® works is similar to legacy instant messaging platform
such as ICQ®, MSN® Messenger, Yahoo!® Messenger or AIM®. A user will
be able to contact his/her 'buddies' using a client program.
Why use Jabber® instead of other instant messaging services?
* Jabber® is an Internet standard just like HTTP or SMTP. There are
several implementations of servers and clients from a lot
companies. Just like web and email.
* Jabber® protocol is decentralized unlike proprietary instant
messaging system. Every domain owner could have their own Jabber®
server, just like email.
* There are fewer privacy concern with Jabber®, because
communications between Jabber® users don't involve a centralized
server controlled by a third party.
* As such, Jabber® is more suitable for business users. Also, client
software offered by proprietary instant messaging system are often
targeted to casual users rather than business users.
* Jabber® provides a way for its user to communicate with users from
legacy instant messaging platforms like Yahoo!® Instant Messenger,
AIM®, MSN® Messenger or ICQ®
* Jabber® is more personalized. Unlike with some of proprietary
instant messaging services, it identifies its users with a
notation similar to email addresses (user@domain).
* Jabber® supports multiple login. It means you can remain connected
at the office, while you connect with the same username from your
home.
* Jabber® client software is available on almost all operating
system.
* There are several free Jabber® account providers to register from
if the ISP doesn't provide it already.
Creating Jabber® Account
In indoglobal.com, your email account doubles as your Jabber® account
with an exception: your subdomain email account cannot be used as a
Jabber® account. For example: if you create an email account
joe@example.com, then the respective Jabber® account is also
joe@example.com. However, an email account nick@london.example.com
doesn't have a Jabber® account because london.example.com is a
subdomain.
Note
We made the Jabber® account the same as email account in order to
simplify administration and to reduce confusion. However, there are
Jabber® servers that don't follow this rule. You shouldn't assume a
Jabber® account is also a working email address, or vice versa.
Tip
The same password is used for both email service and Jabber® service.
You can change password from a Jabber® client and the email password
will be changed too, and vice versa.
To create an email account (and thus a Jabber® account), please refer
to the section called "Creating a New Email Account".
Using Jabber® Client Psi
Unlike proprietary instant messaging platform, there are several
client implementations of Jabber®. We provide official support for Psi
on Microsoft® Windows® or Linux platform. However there are several
other clients if you wish to use them.
In this section we will discuss Psi exclusively. They might of might
not apply to other clients. However the basic concept is the same.
Starting With Psi
To download Psi, you need to visit their homepage. Psi is available
for Linux, Microsoft® Windows® and MacOSX. Make sure you download Psi
for the right platform. To install Psi please follow the instruction
that goes with the download.
After running Psi for the first time, you will be greeted by the
profile menu. To run Psi for the first time, please follow the next
steps:
1. You need to create a profile if you want to use Psi. Click on
Profiles and then click New. On the Profile Name field, please add
a descriptive name and then click OK.
2. You will be taken back to the previous menu and your just created
profile should be pre-selected. Click Open to start Psi with the
profile.
3. Now you will be greeted by Add Account menu. Please add a
descriptive name for your Jabber® account and then click Add. Make
sure you don't have the Register new account checkbox unchecked.
4. The Account Properties menu will appear. On the Account tab,
please specify your Jabber® ID, for example: 'joe@example.com'.
There is also the Resource field. Resource is an additional string
that identifies your session. Jabber® supports multiple open
session, i.e. you can open a new session without shutting down the
previous connection. To identify multiple session, you need to
change the Resource field to something more descriptive. For
example, use 'Work' for the session you left at work, and 'Home'
for the session you use from home. Priority is the priority of the
session. The client with highest priority will receive be the one
who receive all incoming events.
5. On the Connection tab, please check the Allow Plaintext Login
checkbox.
6. Click Save to continue.
If everything is fine, Psi should now be connected to the server,
congratulations!
Using Gateways to Legacy Networks
Ideally, everybody should be using the same instant messaging
protocol, just like email. However, we don't live in a perfect world.
There are no less than four different popular instant messaging
protocol in use today, and that's not counting Jabber®. This makes it
hard for average users to communicate with all their friends. They
usually end up with several instant messaging accounts and several
clients running simultanously.
Jabber® tries to alleviate this problem by introducing a feature
called gateway. Gateway is a program on the server that translates
events coming from and into other instant messaging networks
transparently, so that a Jabber® user can see the events as if it is a
normal Jabber® events.
In order to use this feature. A Jabber® user will need to register
first. For Psi, please follow the next steps.
1. Click the menu button (the lower left one), and then choose
Service Discovery. The Service Discovery dialog will appear.
Please give the program a little time to download the list of
available services from the server.
2. There should be at least four services that can be used as a
gateway: AIM Gateway, ICQ Gateway, MSN Gateway and Yahoo! Gateway.
Each can be used to connect to the respective instant messaging
network. To connect to one, right click on a gateway service, and
then click register. Now carry on with the instruction on the next
dialog. At least you will be asked your username and password to
connect to the other network, but sometimes you will be asked more
questions.
3. After successfully registrating with a gateway. The gateway in
question will appear in your roster window. You might need to
authorize it before it can function properly. Watch your roster
window for this.
4. For most network, the gateway will then gather your existing
contact list from the legacy servers. They should appear shortly
after you successfully register with the gateway.
Note
You can instruct Jabber® to connect or disconnect to a specific
instant messaging network by right clicking the gateway name on your
roster and then click Log on or Log off respectively.
Adding Jabber® Contacts
Instant messaging is not useful if you have no contact on your roster.
To add new contact, please do the following steps:
1. Click on the menu button (by default it is on the bottom left
corner). Then click Add a contact.
2. The Add User dialog should appear. Specify the Jabber® ID of your
contact and then click Add.
Note
You will need to wait for his/her authorization before you will see
his/her status on your Jabber® roster
Adding Contacts from Legacy Networks
Adding contacts from a legacy network (AIM, ICQ, Yahoo!, or MSN) is
very similar to adding Jabber® contacts. The difference is that you
need to translate nickname/handle convention used in legacy networks
into Jabber® convention. Conversion examples below:
* For ICQ, the format is 'UIN@icq.gateway'. For example, if your UIN
of your friend is '1277851', then his translated Jabber® ID is:
'1277851@icq.gateway'
* For AIM, the format is 'screenname@aim.gateway'. For example, if
your friend's AIM screen name is 'johndoe', then his translated
Jabber® ID is 'johndoe@aim.gateway'
* For Yahoo!, the format is 'yahoousername@yahoo.gateway'. For
example, if your friend's Yahoo! username is 'johndoe', then his
translated Jabber® ID is johndoe@yahoo.gateway.
* For MSN, the format is 'MSNusername@msn.gateway' but substitute
the '@' sign on every MSN username with '%'. For example, if your
friend's MSN username is 'john@hotmail.com', then his translated
Jabber ID is 'john%hotmail.com@msn.gateway'.
Important
You need to register with gateway before you can add user from the
respective gateway, please see the section called "Using Gateways to
Legacy Networks" for more information.
After figuring out your friend's translated Jabber ID, then you will
be able to add him/her as if he/she is a normal Jabber® user.
Note
Jabber® doesn't support all features offered by legacy clients.
Tips for Using Jabber®
There are free Jabber® servers from all over the world. The list is
available from Jabber® web site. If your (non indoglobal.com customer)
friends want to get into Jabber® bandwagon, you can give them the
server list, so they can register themselves.
Jabber® is an open protocol and therefore easy to program. There are
Jabber® libraries for all popular programming languages, the list is
available from http://www.jabber.org/software/libraries.php. The
possibility is endless, for example you could build a notification
system to notify you when someone submits a form on your web site. For
more example on how these can be done please see
http://www.pipetree.com/jabber/fwj.html. There are also numerous
Jabber® resources on the Internet.
Appendix A. FTP Clients Configuration
Table of Contents
Microsoft Windows My Network Places
FileZilla
KDE Konqueror
GNOME Nautilus
To log on to FTP account, you will need your username and your
password. For more information about FTP and logging on to FTP please
see the section called "Transferring Files Using FTP". The examples
below will assume your domain name is example.com, your account
username is u777 and you are connecting to your main FTP account (not
subdomain FTP account).
Microsoft® Windows® My Network Places
The following is how to connect to FTP server using the built in My
Network Places feature of Microsoft® Windows® XP Professional. Other
versions of Microsoft® Windows® may support My Network Places but the
steps involved could be slightly different.
Before you can use My Network Places to connect to FTP server, you
will need to add a network place first.
1. Click Start and choose My Network Places. My Network Places window
should appear.
2. Click Add a network place. This should present you with Add
Network Place Wizard. Click Next when done with the introduction.
3. Windows will try to fetch information from the Internet. After a
while a menu will appear, choose Choose another network location
and then click Next.
4. On the next screen you need to specify the location of the FTP
server. Assuming your account username is u777 and your domain is
example.com, specify ftp://u777@primary-ip.example.com. Click Next
to contine.
5. On the next screen, you can specify a descriptive name of the
network place you've just created. Click Next and then click
Finish.
After the FTP server has been added to My Network Place, it is easy to
connect to the FTP server.
1. Click Start and choose My Network Places. My Network Places
windows should appear.
2. Double click on the network place you want to connect. You may be
asked for a password.
3. When successful, a window showing your FTP network place should
appear. Now you can use standard file operation (drag and drop, or
cut/copy and paste) on this window.
FileZilla
FileZilla is a free FTP client for windows. It is a free software
under GPL and can be downloaded for free from FileZilla's homepage.
To connect to our FTP server using FileZilla, please do the following
steps, assuming your account username is u777 and your domain name is
example.com.
* Launch FileZilla using Start menu. The FileZilla window should now
appear.
* On the quick launch bar, specify 'primary-ip.example.com' in the
Address field, 'u777' in the User field, and your account password
in the Password field. Click QuickConnect to continue.
* After logged in, you are now able to perform file transfer within
the Local site and Remote site panel.
Tip
On the subsequent connection attempt, you no longer have to type in
your host, user and password every time you log on. FileZilla will
remember your settings automatically. Click the arrow beside
QuickConnect button to show the connections made previously.
KDE Konqueror
Konqueror is a file manager used under KDE. KDE is a desktop
environment for Linux, UNIX and similar operating systems. To connect
to FTP server using Konqueror please do the following steps.
* Open a Konqueror file manager window by clicking on the home icon
on the taskbar.
* On the Location bar, specify ftp://u777@primary-ip.example.com.
You may be asked for a password, specify it as necessary.
* After the window shows the contents of your account, you will be
able to do file transfer by performing standard file operation
like drag and drop or copying and pasting.
Tip
To save the location so you don't have to do the above steps everytime
you want to make a connection, click Bookmarks and then Add bookmark.
If you want to make the connection, you only have to choose the site
in question from the bookmark.
GNOME Nautilus
Nautilus is a file manager for GNOME desktop environment for Linux,
UNIX and similar operating systems. To connect to FTP server using
Nautilus please do the following steps.
* Open a Nautilus file manager window by clicking on Application
menu and then Home Folder. A Nautilus window should then appear.
* On the Location bar, specify
ftp://u777:PASSWORD@primary-ip.example.com. Replace PASSWORD with
your real password.
* After the window shows the contents of your account, you will be
able to do file transfer by performing standard file operation
like drag and drop or copying and pasting.
Tip
To save the location so you don't have to do the above steps everytime
you want to make a connection, click Bookmarks and then Add bookmark.
If you want to make the connection later, you only have to choose the
site in question from the bookmark.
Appendix B. WebDAV Clients Configuration
Table of Contents
Microsoft Windows My Network Places
KDE Konqueror
GNOME Nautilus
Our WebDAV server is located on port 81. Port 444 is also open for
HTTPS based WebDAV connections. For more information about WebDAV
please see the section called "Using WebDAV to Manage Files".
Microsoft® Windows® My Network Places
The following is how to connect to WebDAV server using the built in My
Network Places feature of Microsoft® Windows® XP Professional. Other
versions of Microsoft® Windows® may support My Network Places but the
steps involved could be slightly different.
Before you can use My Network Places to connect to WebDAV server, you
will need to add a network place first.
1. Click Start and choose My Network Places. My Network Places window
should appear.
2. Click Add a network place. This should present you with Add
Network Place Wizard. Click Next when done with the introduction.
3. Windows will try to fetch information from the Internet. After a
while a menu will appear, choose Choose another network location
and then click Next.
4. On the next screen you need to specify the location of the WebDAV
server. If your WebDAV enabled subdomain is 'example.com', then
specify the location as http://example.com:81/. Alternatively you
can also specify https://example.com:444/ if you want to use
secure version of WebDAV server. You will be asked for your
username and password, specify the username and password set from
Web User & Group menu from SiteManager. Press Next to continue.
5. On the next screen, you can specify a descriptive name of the
network place you've just created. Click Next and then click
Finish.
After the FTP server has been added to My Network Place, it is easy to
connect to the FTP server.
1. Click Start and choose My Network Places. My Network Places
windows should appear.
2. Double click on the network place you want to connect. You may be
asked for a password.
3. When successful, a window showing your FTP network place should
appear. Now you can use standard file operation (drag and drop, or
cut/copy and paste) on this window.
KDE Konqueror
Konqueror is a file manager used under KDE. KDE is a desktop
environment for Linux, UNIX and similar operating systems. To connect
to FTP server using Konqueror please do the following steps.
Note
You need at least version 3.0 of KDE to use WebDAV feature.
* Open a Konqueror file manager window by clicking on the home icon
on the taskbar.
* On the Location bar, specify webdav://username@example.com:81.
Alternatively you can also use webdavs://username@example.com:444
if you want to use the secure version of WebDAV server. Replace
username with your username set from Web User & Group menu from
SiteManager. You will be asked for a password, specify it as
necessary.
* After the window shows the contents of your account, you will be
able to do file transfer by performing standard file operation
like drag and drop or copying and pasting.
Tip
To save the location so you don't have to do the above steps everytime
you want to make a connection, click Bookmarks and then Add bookmark.
If you want to make the connection, you only have to choose the site
in question from the bookmark.
GNOME Nautilus
Nautilus is a file manager for GNOME desktop environment for Linux,
UNIX and similar operating systems. To connect to WebDAV server using
Nautilus please do the following steps.
Note
You need to use GNOME at least version 2.0 to use WebDAV feature.
* Open a Nautilus file manager window by clicking on Application
menu and then Home Folder. A Nautilus window should then appear.
* On the Location bar, specify
http://username:password@example.com:81. Replace username and
password with the username and password from Web User & Group menu
from SiteManager. Also replace example.com with your own WebDAV
enabled subdomain. Alternatively, you can also use
https://username:password@example.com:444 to use secure version of
WebDAV server.
* After the window shows the contents of your account, you will be
able to do file transfer by performing standard file operation
like drag and drop or copying and pasting.
Tip
To save the location so you don't have to do the above steps everytime
you want to make a connection, click Bookmarks and then Add bookmark.
If you want to make the connection later, you only have to choose the
site in question from the bookmark.
Appendix C. Email Clients Configuration
Table of Contents
Microsoft Outlook Express
Qualcomm Eudora
KDE KMail
Novell Evolution (formerly Ximian Evolution)
Mozilla Mail
For more information about email please see Email Management. In this
appendix, it is assumed that your domain name is example.com, your
email address is 'username@example.com' and your email password is
'password'. Please note that the email username & password is set from
the Email menu from SiteManager, not your account's username &
password. It is also assumed that you haven't changed the default
subdomain configuration of subdomains pop.example.com,
imap.example.com and smtp.example.com.
Microsoft® Outlook Express®
Microsoft® Outlook Express® is the default email client shipped by
most versions of Microsoft® Windows®. The examples below is done with
Microsoft® Outlook Express® version 6 shipped with Microsoft® Windows®
XP Professional.
Warning
Microsoft® Outlook Express® is often used as carrier of viruses and
worms. Always make sure you have installed the latest security patch
from Microsoft before running Microsoft® Outlook Express®.
Alternatively you can use a better email client.
To configure Microsoft® Outlook Express® to download email from our
server, please do the following steps.
1. Run Microsoft® Outlook Express® from the Start menu.
2. After Microsoft® Outlook Express® window appears, click Tools and
then Accounts.
3. Internet Accounts window will appear, click Add and then Mail.
4. On the Display name field, enter a descriptive text for this email
account, for example "My email account". Click Next to continue.
5. On the Email address field, enter your email address, as in
'username@example.com'. Click Next to continue.
6. On the next screen you need to specify email server names. If you
want to use POP3, specify 'My incoming mail server is a POP3
server', you also need to specify 'pop.example.com' on your
incoming mail server field, substituting 'example.com' with your
real domain name. If you want to use IMAP, specify 'My incoming
mail server is a IMAP server', you also need to specify
'imap.example.com' on your incoming mail server field,
substituting 'example.com' with your real domain name.
7. On the outgoing mail server field, specify 'smtp.example.com'
(substituting example.com with your real domain name) Click Next
to continue.
8. On the next screen, specify your complete email address (as in
username@example.com) in the Account name field. Also specify your
password in the Password field. You need to clear the Log on using
Secure Password Authentication checkbox if it isn't already
cleared. Click Next and then Finish to continue.
9. Select the account name you have just created, and then click
Properties. Click on the Servers tab and on the Outgoing Mail
Server section check the My server requires authentication. Click
on Settings and then select Use same settings as my incoming mail
server. Click OK. Click on the Advanced tab. Specify '8025' or
'587' in the Outgoing mail (SMTP) fields. Click OK and then Close
to finalize the configuration.
Qualcomm Eudora
Eudora is a popular email client available for download from its web
site. To configure Eudora for use with your account, please do the
following steps. On the steps below we are using Eudora version 6
under Microsoft® Windows®.
1. Click Tools and then Personalities.
2. Right click on the personalities area and then click New. The New
Account Wizard will appear.
3. Choose Create a brand new email account and click Next.
4. Enter a text describing the account you want to create in the
Personality name field, for example 'My Email Account'. Click Next
to continue.
5. Enter your name in Your Name field. Click Next to continue.
6. Enter your complete email address as in 'username@example.com' in
the Email Address field. Click Next to continue.
7. Enter your complete email address as in 'username@example.com' in
the Login Name field. Click Next to continue.
8. In the Incoming email server, specify 'pop.example.com' if you
want to use POP3 or 'imap.example.com' if you want to use IMAP
(substituting example.com with your real domain name). Also choose
whether if you want to use POP or IMAP on the selection on the
bottom. Click Next to continue.
9. Specify 'smtp.example.com' (substituting example.com with your
real domain name) as your Outgoing Server and check the Allow
authentication checkbox. Click Next and then Finish.
10. Right click on the account you have just created and then choose
Properties.
11. On the Secure Sockets when Sending section, choose 'Never'. Click
on the Incoming Mail tab. On the Secure Sockets when Receiving
section, choose 'Never'. Click OK to finalize the settings.
Unfortunately Eudora doesn't provide an easy way to change the SMTP
port number which is required if you decide to use indoglobal.com's
SMTP server. Please do the additional steps below if you wish to use
our server's SMTP server for sending emails.
1. Close Eudora if it is running.
2. Look for a file inside your C:\WINDOWS directory (or where you
installed Windows) named 'services' and open it with a text editor
such as notepad. The exact location of this file could be
different with different version of Microsoft® Windows®, use the
search/find function of the operating system to locate the file.
3. Change the line that says 'smtp 25/tcp' to 'smtp 8025/tcp' or
'smtp 587/tcp'. Save the file.
4. Open the directory where you installed Eudora (i.e. C:\Program
Files\Qualcomm\Eudora). Enter the directory extrastuff. Inside
this directory is a file esoteric.epi. Move this file to the main
Eudora directory.
5. Start Eudora. Go to Tools and then Options. Locate the Ports menu
on the left pane and click it. Specify '8025' or '587' in the SMTP
Port field. Click OK to continue.
Warning
Please note that changing the SMTP port number will affect ALL your
personalities including those not hosted on our server.
KDE KMail
KMail is the email client shipped with KDE, a desktop environment for
Linux, UNIX and similar systems. The following steps describes the
steps required to configure email on KMail under KDE 3.
1. Click Settings and then Configure KMail. The Configure KMail
window will then appear.
2. Click on Identities menu on the left pane. Click New to create a
new identity.
3. Enter a descriptive name on the New identity field as in 'My Email
Account'. Select With empty fields and then click OK.
4. Enter your name, organization and email address in the Your Name,
Organization, and Email address fields respectively. Click OK to
continue.
5. Click on Network menu on the left pane. Click the Sending tab and
click Add.
6. Choose SMTP as the transport. Click OK to continue. Enter a
descriptive name on the Name field such as 'SMTP server'. Specify
'smtp.example.com' (replacing example.com with your own domain
name) in the Host field. You also need to specify '8025' or '587'
in the Port field, check Server requires authentication and then
specify your complete email address in the Login field and its
password.
7. Click the Receiving tab and then click Add.
8. You can choose POP3 or IMAP depending if you want to use POP3 or
IMAP for downloading your email. Click OK to continue.
9. Specify your complete email address in the Login field. Specify
'pop.example.com' or 'imap.example.com' in the Host field
substituting example.com with your own domain name. Click OK to
continue.
10. Click OK to finalize the configuration.
Novell Evolution (formerly Ximian Evolution)
Novell Evolution is the default email client in the GNOME desktop
environment. In the steps below, it is assumed that Novell Evolution
version 1.2 is used.
1. Click on Tools menu and then Settings.
2. Click Mail Accounts on the left pane, and then click Add. The
Evolution Account Assistant Wizard will then appear. Click Next to
continue.
3. Specify your full name in the Full name field and your email
address in the Email address field, respectively. Click Next to
continue.
4. Choose POP or IMAP on the Server Type drop down box depending on
whether you want to use POP or IMAP. Specify 'pop.example.com' or
'imap.example.com' (substituting example.com with your real domain
name) on the Host field depending whether you want to use POP or
IMAP. Specify your complete email address (as in
'username@example.com) in the Username field. Click Next to
continue.
5. On the next screen, choose the options accordingly depending on
your own preferences. Click Next to continue.
6. Choose SMTP in the Server Type. Specify 'smtp.example.com:8025' or
'smtp.example.com:587' (substituting example.com with your own
domain name) in the Host field. You also need to check the Server
requires authentication checkbox, and specify your complete email
address (as in 'username@example.com') in the Username field.
Click Next to continue.
7. On the next screen, you can specify a descriptive name for this
account in the Name fields. Click Next to continue. Click Finish
to finalize the settings.
Mozilla Mail
Mozilla Mail is a part of Mozilla web browser available for download
from Mozilla.org. The following steps describe email configuration for
Mozilla Mail version 1.4.
1. Open Mozilla Mail window, either by clicking on its icon from menu
or by clicking the Mail & Newgroups icon on the lower left part of
Mozilla web browser window.
2. Click on Edit and then Mail & Newgroups Account Settings.
3. Click Add Account. On the first screen select Email account and
then click Next.
4. Specify your name in the Your Name field and your email address in
the Email Address field. Click Next to continue.
5. On the next screen you can choose POP or IMAP depending on whether
you want to use POP or IMAP. You also need to specify
'pop.example.com' or 'imap.example.com' (replace example.com with
your own domain name) in the Incoming Server field. Click Next to
continue.
6. Specify your full email address in the User Name field. Click Next
to continue.
7. Specify a descriptive name for this account, for example 'My Email
Account'. Click Next and then Finish to continue.
8. Now you should be taken back to the Mail & Newsgroups Account
Settings menu. Click on Outgoing Server (SMTP).
9. Specify 'smtp.example.com' in the Server Name field. You also need
to specify '8025' or '587' in the Port field and specify your
email address in the User Name field.
10. Click OK to finalize the settings.
Index
Symbols
.asp (see ASP)
.shtml (see Server Side Includes)
A
A records, DNS Record
abuse email address (see mandatory email accounts)
access control, Access Control Configuration
restricting access, Restricting Access to Part of Your Web Site
Active Server Pages (see ASP)
anti spam (see spam filter)
ASCII mode, Transferring Files Using FTP
ASP, Using Active Server Pages (ASP)
components, ASP Components
connecting to database, Difference From Microsoft Windows Version
database support, Difference From Microsoft Windows Version
difference from Windows version, Difference From Microsoft
Windows Version
documentation, Using Active Server Pages (ASP)
asp2php, Using Active Server Pages (ASP), Converting ASP Scripts to
PHP
authentication, Managing Your Web Users and Groups
authentication string, Restricting Access to Part of Your Web Site
auto responder, Types of Email Accounts
AutoCorrect, Using AutoCorrect Feature
correcting CGI scripts, Using CGI Scripts in General
AWStats, Log Files Analysis
B
blackhole, Types of Email Accounts
bounce email address (see mandatory email accounts)
bouncer, Types of Email Accounts
C
C/C++, Using CGI Scripts in General
case sensitivity, Naming Filenames and Directory Locations, Difference
From Microsoft Windows Version
catchall email (see default mail handler)
CDONTS, ASP Components
CGI, Using CGI Scripts in General
CGI script
securing, Securing CGI Scripts in General
CGI scripts (see CGI)
chmod, Managing Files on File Manager
clipboard, Directory Structure, Managing Files on File Manager,
Clipboard Operation
CNAME records, DNS Record
command injection attack, Securing CGI Scripts in General
content migration (see migration)
conversion
ASP to PHP, Using Active Server Pages (ASP), Converting ASP
Scripts to PHP
from Microsoft Access or Microsoft SQL Server, Difference From
Microsoft Windows Version
counter, Creating a Graphical Counter
CPAN, Installing Perl CPAN Modules
cross site scripting, Securing CGI Scripts in General
custom mail handler, Types of Email Accounts
D
data transfer (see resource usage)
databases, Support for More Than One Database
actions for, Creating and Managing Databases
connecting using ASP, Difference From Microsoft Windows Version
creating, Creating and Managing Databases
types of, Types of Database
dated addresses (see extension addresses)
DAV (see WebDAV)
default mail handler, Default Mail Handler
editing, Editing Default Mail Handler
dictionary attack, Default Mail Handler
digits
for graphical counters, Creating a Graphical Counter
directories
location of, Naming Filenames and Directory Locations
directory
structure, Directory Structure
disk space (see resource usage)
DNS records, Types of Subdomains, DNS Record
A records, DNS Record
CNAME records, DNS Record
NS records, DNS Record
zone transfers, DNS Zone Transfers
DomainPOP (see default mail handler)
dynamic DNS, Types of Subdomains, Dynamic DNS
E
email, Email Clients Configuration
global email password, Using Global Email Password to Access Your
User's Account
email account
accessing, Accessing your email account
creating, Creating an Email Account
email accounts
checking, Checking Emails
checking using web based mail, Checking Email Using Webmail
creating, Creating a New Email Account
sending emails, Sending Emails
types of, Types of Email Accounts
email auto responder (see auto responder)
email blackhole (see blackhole)
email bouncer (see bouncer)
email clients, Email Clients Configuration
email forms, Creating HTML to Email Forms
email forwarders, Types of Email Accounts
emails
subdomains, Email and Subdomains
encrypting traffic (see SSL/TLS)
Eudora, Qualcomm Eudora
Evolution, Novell Evolution (formerly Ximian Evolution)
extension addresses, Spam Protection Level 3
extracting files, Managing Files on File Manager
F
file extensions, Naming Filenames and Directory Locations
file manager, Using SiteManager's File Manager
File Transfer Protocol (see FTP)
filenames
extensions, Using CGI Scripts in General, Using AutoCorrect
Feature
naming of, Naming Filenames and Directory Locations
FileZilla, FileZilla
firewalls, Using WebDAV to Manage Files
formmails (see email forms)
forwarders (see email forwarders)
FrontPage (see Microsoft FrontPage)
FrontPage subdomains, Types of Subdomains, Regular and Microsoft
FrontPage subdomains
FTP, Logging in using FTP, Transferring Files Using FTP, FTP Clients
Configuration
FTP clients, FTP Clients Configuration
G
global email password, Using Global Email Password to Access Your
User's Account
GNOME Nautilus (see Nautilus)
graphical counter (see counter)
H
home directory, Directory Structure
hostmaster email address (see mandatory email accounts)
HTML to email forms (see email forms)
I
IMAP, Types of Email Accounts
interpreter
location of, Using CGI Scripts in General
J
Jabber
about, About Jabber
adding contacts, Adding Jabber Contacts, Adding Contacts from
Legacy Networks
creating account, Creating Jabber Account
gateways, Using Gateways to Legacy Networks
resources, Starting With Psi
tips, Tips for Using Jabber
using, Using Jabber Client Psi
K
KDE KMail (see KMail)
KDE Konqueror (see Konqueror)
keyword addresses (see extension addresses)
KMail, KDE KMail
Konqueror, KDE Konqueror, KDE Konqueror
L
language settings
PHP, Configuring PHP
Linbot (see linking errors)
linking errors
checking, Checking Your Web Site from Link Errors
log files, Log Files and Analysis
accessing analysis results, Log Files Analysis
active, Active Log Files
analysis, Log Files Analysis
archived, Archived Log Files
downloading, Archived Log Files
maximum size, Archived Log Files
restricting access to analysis results, Log Files Analysis
rotation, Log Files and Analysis
time zone configuration, Log Files Analysis
M
mailing list, Types of Email Accounts
mandatory email accounts, Mandatory Email Accounts
MDaemon, Default Mail Handler
Microsoft FrontPage, Publishing using Microsoft FrontPage
subdomains, Types of Subdomains
Microsoft Outlook Express, Microsoft Outlook Express
migration, Migrating From Another Server
Mozilla Mail, Mozilla Mail
My Network Places, Microsoft Windows My Network Places, Microsoft
Windows My Network Places
MySQL databases, MySQL Database
creating table, Creating new Table
dropping table, Deleting/Dropping MySQL Table
dumping, Dumping and Restoring MySQL Database
managing, Managing MySQL Database
managing using alternative software, Managing MySQL Database
Using Alternative Software
managing using command line shell, Managing MySQL Database Using
Command Line
manually entering queries, Manually Entering SQL Query
modifying records, Modifying Records inside a MySQL Table
modifying table structure, Modifying Table Structures
repairing & optimizing, Repairing and Optimizing MySQL Database
restoring from dump file, Restoring Database Using SiteManager
using in applications, Using MySQL Database in Your Application
N
Nautilus, GNOME Nautilus, GNOME Nautilus
network security, Network Security
Novell Evolution (see Evolution)
NS records, DNS Record
O
OutLook Express (see Microsoft Outlook Express)
P
PEAR, Installing PEAR Modules
Perl, Using CGI Scripts in General
CPAN modules (see CPAN)
installing module, Installing Perl CPAN Modules
settings, Installing Perl CPAN Modules
PHP, Using PHP Scripts
configuration file, Manually Editing PHP Configuration File
configuration parameters, Inside Configuration Menu
configuring, Configuring PHP
extensions, Inside Configuration Menu, Installing Your Own PHP
Module
modules, Inside Configuration Menu, Installing Your Own PHP
Module
PEAR modules, Installing PEAR Modules
php.ini, Manually Editing PHP Configuration File
securing scripts, Securing PHP Scripts
php.ini, Manually Editing PHP Configuration File
POP3, Types of Email Accounts
PostgreSQL databases, PostgreSQL Database
dumping, Dumping PostgreSQL Database
managing, Managing PostgreSQL Database
restoring from dump file, Restoring PostgreSQL Database
SQL shell, Managing PostgreSQL Database
using in applications, Using PostgreSQL Database in Your
Application
postmaster email address (see mandatory email accounts)
Psi, Using Jabber Client Psi
adding contacts, Adding Jabber Contacts
using, Starting With Psi
publishing, Publishing and Uploading Files
Python, Using CGI Scripts in General
Q
qmail, Types of Email Accounts
R
regular subdomains, Types of Subdomains, Regular and Microsoft
FrontPage subdomains
resource usage, Monitoring Resource Usage
resources, Starting With Psi
rsync, Transferring Files Using scp, sftp and rsync
Ruby, Using CGI Scripts in General
S
scheduler (see task scheduler)
scp, Transferring Files Using scp, sftp and rsync
secure protocols, Use Secure Protocols When Managing Your Account
Secure Sockets Layer (see SSL/TLS)
security
classes of, Classes of Security
improving, Improving Security
network security (see network security)
responding to an incideng, What To Do When a Security Incident
Happens
server security (see server security)
updating software, Keeping Third Party Software Up to Date
user account security (see user account security)
writing scripts, Writing Secure Scripts
sender addresses (see extension addresses)
sender policy framework (see SPF)
server security, Server Security
Server Side Includes, Server Side Includes (SSI)
sftp, Transferring Files Using scp, sftp and rsync
shell account, Logging in to UNIX Shell Account
shell scripts, Using CGI Scripts in General
shtml (see Server Side Includes)
Simple Mail Transport Protocol (see SMTP)
SiteManager
logging in, Logging in to SiteManager, Logging in to SiteManager
SMTP, Sending Emails
spam
challenge and response, Spam Protection Level 3
filtering, Configuring Spam Filter
flagging messages as, Spam Protection Level 2
spam filter, Configuring Spam Filter
SPF, Protecting Your Email With SPF
SQL injection attack, Securing CGI Scripts in General
SSH, Use Secure Protocols When Managing Your Account
SSI (see Server Side Includes)
SSL/TLS, Using SSL/TLS
fully signed certificate, Getting and Installing a Fully Signed
Certificate
getting and installing certificate, Getting and Installing a
Fully Signed Certificate
subdomains, Subdomain and DNS
access to web statistics, Other Types of Subdomains
aliases, Other Types of Subdomains
configuring for WebDAV, Configuring Subdomain for WebDAV Access
creating, Creating new Subdomains
deleting, Deleting Subdomains
DNS records, Types of Subdomains, DNS Record
downloading contents of, Downloading the Whole Subdomain Contents
dynamic DNS, Dynamic DNS
dynamic DNS records, Types of Subdomains
emails, Email and Subdomains
FrontPage subdomains, Types of Subdomains, Regular and Microsoft
FrontPage subdomains
FTP accounts, Subdomain FTP accounts
regular subdomains, Types of Subdomains, Regular and Microsoft
FrontPage subdomains
types of, Types of Subdomains
Webplications, Types of Subdomains, Webplication
Sun ONE ASP (see ASP)
T
task scheduler, Running Scheduled Tasks
telnet, Use Secure Protocols When Managing Your Account
TLS (see SSL/TLS)
Transport Layer Security (see SSL/TLS)
U
uploading, Publishing and Uploading Files
user account security, User Account Security
W
WAP, Checking Email From WAP Devices
WAP mail, Checking Email From WAP Devices
web users and group, Managing Your Web Users and Groups
Webalizer, Log Files Analysis
WebDAV, Using WebDAV to Manage Files, WebDAV Clients Configuration
configuring access control, Configuring DAV Access Control
configuring subdomain for, Configuring Subdomain for WebDAV
Access
enabling, Configuring Subdomain for WebDAV Access
WebDrive (see WebDAV)
WebFolders (see WebDAV)
webmail, Checking Email Using Webmail
Webplications, Types of Subdomains, Webplication
X
Ximian Evolution (see Evolution)
XSS (see cross site scripting)
Z
zone transfers, DNS Zone Transfers