Overview

The Index Manager allows you to customize the way a directory will be viewed on the web. You can select between a default style, no indexes, or two types of indexing. If you do not wish for people to be able to see the files in your directory, choose no indexing.

Incoming search terms:

index manager

Overview

The E-Mail area allows you troubleshoot problematic e-mail addresses, manage your mail queue, and view email statistics for your server.

To access the Email Menu, click on Email, on the main screen of your WebHost Manager interface.

Manage Mail Queue

The Exim Mail Queue area enables you to view all waiting messages in the mail queue, and attempt to deliver or delete all the messages in the queue. The Mail Queue contains all messages that have been sent, but have not yet left your server for one reason or another. Refer to exim.org for more information on the mail queue.

Steps

1. To access the Email Menu, click on Email, on the main screen of your WebHost Manager interface.
2. Click on Manage Mail Queue.
3. View the email as required. Click on the Delete link next to an e-mail if you need to delete it, or click on the Deliver Now link next to an e-mail to deliver it now.
4. Click on the Delete All Messages In Queue link if you need to delete the mail that is currently in the queue.
5. Click on the Attempt To Deliver All Messages In Queue link if you need to send the e-mail now. This is a good method of testing if something is functioning incorrectly with Exim.

Mail Troubleshooter

The Mail Troubleshooter function enables you to send a test e-mail to a problematic address to determine what is wrong. This process will track down the vast majority of e-mail problems that can occur on your server.

Steps

1. To access the Email Menu, click on Email, on the main screen of your WebHost Manager interface.
2. Click on Mail Troubleshooter.
3. Enter the problematic e-mail address in the Email To Trace field.
4. Click on Do It.

Troubleshooting

If the Mail Troubleshooter does not show the source of the problem, you will need to check the mail logs on your server, or the returned messages to the account, if any.

Repair Mailbox Permissions

This function rebuilds mail databases and fixes permission problems on mail databases and mailboxes.

Steps

1. To access the E-mail Menu, click on E-mail, on the main screen of your WebHost Manager interface.
2. Click on Repair Mailbox Permissions.
3. Your mailboxes and databases should now be fixed. Complete! will be displayed.

View Mail Statistics

The View Mail Statistics function displays a wide variety of information about e-mail on your server, including total volumes, how many messages were sent and delivered per hour, the top 50 accounts in terms of mail sent and received, and a list of error messages.

Steps

1. To access the E-mail Menu, click on E-mail, on the main screen of your WebHost Manager interface.
2. Click on View Mail Statistics.
3. Mail Statistics will now be displayed.

View Relayers

This function allows you to see who is relaying mail on your server. For more information on relaying and how to prevent it, refer to: exim help.

Steps

1. To access the E-mail Menu, click on E-mail, on the main screen of your WebHost Manager interface.
2. Click on View Relayers.
3. The users that are relaying mail on your server will be listed in order of messages sent through relaying.
4. Click on a User or Domain Name to see where the messages are being relayed.

Incoming search terms:

how to remove all messages in exim mail queue manager

Note: If you want the latest version of php and apache, it’s recommended you use custombuild:
http://files.directadmin.com/services/custombuild/1.1
The following guide is only to be used if if you still want to use the old apache versions… basically, only if you still need FrontPage.

---

To update to php5, the build script will still work. All that you need to do is swap out the version, compile normally and make a few modifications to your /etc/httpd/conf/httpd.conf file.
1) download the php-5.2.4.tar.gz from php.net into your customapache directory:

cd /usr/local/directadmin/customapache
wget http://files.directadmin.com/services/customapache/php-5.2.4.tar.gz

2) change your build script for the new version:

nano build

change: PHP_VER=4.4.4
to: PHP_VER=5.2.4
3) build php normally:

./build clean
./build php n

If you’re using apache 2.x, use

./build clean
./build php_ap2 n

instead.
4) edit /etc/httpd/conf/httpd.conf
Remove any referce of:

LoadModule php4_module modules/libphp4.so

and make sure they’re replaced with:

LoadModule php5_module modules/libphp5.so

Remove any reference of:

AddModule mod_php4.c

and replace with:

AddModule mod_php5.c

5) find this piece of code:

<IfModule mod_dir.c>
DirectoryIndex index.html index.htm index.shtml index.php index.php4 index.php3 index.phtml index.cgi
</IfModule>

replace with:

<IfModule mod_dir.c>
DirectoryIndex index.html index.htm index.shtml index.php index.php4 index.php5 index.php3 index.phtml index.cgi
</IfModule>

Find this:

<IfModule mod_php4.c>
AddType application/x-httpd-php .inc .php .php4 .php3 .phtml
AddType application/x-httpd-php-source .phps
</IfModule>

(it might have AddHandler instead of AddType)
replace with:

<IfModule mod_php5.c>
AddHandler application/x-httpd-php .inc .php .php5 .php4 .php3 .phtml
AddHandler application/x-httpd-php-source .phps
</IfModule>

Then restart apache.
If you get the following error while compiling php:

checking whether to enable LIBXML support… yes
checking libxml2 install dir… no
checking for xml2-config path…
configure: error: xml2-config not found. Please check your libxml2
installation.
*** There was an error while trying to configure php. Check the configure.php file

Then edit the configure.php file (or configure.php_ap2 if you’re using apache 2), and change:

–with-xml \

to:

–disable-libxml \
–disable-dom \
–disable-xml \
–disable-simplexml \
–disable-xmlreader \
–disable-xmlwriter \

or else install the missing rpms/packages for xml. (libxml2-dev and libxml2-utils on debian). Redhats:

yum -y install libxml2-devel libxslt-devel

FreeBSD:

pkg_add -r libxml2
pkg_add -r libxslt

On debian systems if using apt-get to install libxml2-dev and libxml2-utils doesn’t work, then install from source:

wget http://files.directadmin.com/services/customapache/libxml2-2.6.30.tar.gz
tar xvzf libxml2-2.6.30.tar.gz
cd libxml2-2.6.30
./configure
make && make install

then recompile php as usual.

Incoming search terms:

application/x-httpd-php,httpd conf index php

Overview

With this tool you can create custom error pages to display when a user enters a wrong URL, an outdated URL or when the user is not authorized to access a specific directory of your web space.

Error Pages consists of the following five types of errors:

• 400 (Bad Request)
• 401 (Authorization required)
• 403 (Forbidden)
• 404 (Wrong page)
• 500 (Internal server error)

To customize the error page, you can click on the error page number (400, 401, 403, 404, 500) or the error page name (Bad Request, Authorization required, etc).

When the page loads, you have the following six tags available:

Available Tags

• Referring URL – Displays the url of the web site the visitor was previously viewing.
• Visitor’s IP Address – Displays the IP address of the visitor viewing the error page.
• Requested URL – Displays the intended url the visitor is trying to view.
• Server name – Displays the web site’s server name.
• Visitor’s browser – Displays the visitor’s browser type such as IE, FireFox, Netscape, etc.
• Redirect Status Code – This displays the type of code in the 300-307 range. To learn more about Redirection Status Code, visit the WikiPedia web page at http://en.wikipedia.org/wiki/List_of_HTTP_status_codes.

Incoming search terms:

apa itu http status codes yang ada di cpanel,client server java error

ACTIVE: The registry sets this status. The domain can be modified by the registrar. The domain can be renewed. The domain will be included in the zone if the domain has been delegated to at least one name server.

REGISTRY-LOCK: The registry sets this status. The domain can not be modified or deleted by the registrar. The registry must remove the REGISTRY-LOCK status for the registrar to modify the domain. The domain can be renewed. The domain will be included in the zone if the domain has been delegated to at least one name server.

REGISTRAR-LOCK: The sponsoring registrar sets this status. The domain can not be modified or deleted. The registrar must remove REGISTRAR-LOCK status to modify the domain. The domain can be renewed. The domain will be included in the zone.

REGISTRY-HOLD: The registry sets this status. The domain can not be modified or deleted by the registrar. The registry must remove the REGISTRY-HOLD status for the registrar to modify the domain. The domain can be renewed. The domain will not be included in the zone.

REGISTRAR-HOLD: The sponsoring registrar sets this status. The domain can not be modified or deleted. The registrar must remove REGISTRAR-HOLD status to modify the domain. The domain can be renewed. The domain will not be included in the zone.

REDEMPTIONPERIOD: The registry sets this status when a registrar requests that the domain name be deleted from the registry and the domain has been registered for more than 5 calendar days (if the delete request is received within 5 days of initial domain registration it will instead be deleted immediately). The domain will not be included in the zone. The domain can not be modified or purged; it can only be restored. Any other registrar requests to modify or otherwise update the domain will be rejected. The domain will be held in this status for a maximum of 30 calendar days.

PENDINGRESTORE: The registry sets this status after a registrar requests restoration of a domain that is in REDEMPTIONPERIOD status. The domain will be included in the zone. Registrar requests to modify or otherwise update the domain will be rejected. The domain will be held in this status while the registry waits for the registrar to provide required restoration documentation. If the registrar fails to provide documentation to the registry within 7 calendar days to confirm the restoration request, the domain will revert to REDEMPTIONPERIOD status. The domain status will be set to ACTIVE only if the registrar provides documentation to the registry within 7 calendar days to confirm the restoration request.

PENDINGDELETE: The registry sets this status after a domain has been set in REDEMPTIONPERIOD status and the domain has not been restored by the registrar. The domain will not be included in the zone. Once in this status all registrar requests to modify or otherwise update the domain will be rejected. The domain will be purged from the registry database after being in this status for 5 calendar days.

Incoming search terms:

Guide to Domain Name Status Codes ICANN,tutorial lock domain