CVS: ispman/ispman-web/htdocs/docs addadmin.html,NONE,1.1 addadomain.html,NONE,1.1 addavirtualhost.html,NONE,1.1 addclient.html,NONE,1.1 addemailaccount.html,NONE,1.1 addreseller.html,NONE,1.1 administrator-guide.html,NONE,1.1 commandlinetools.html,NONE,1.1 configuration.html,NONE,1.1 configurationaccountvars.html,NONE,1.1 configurationapache.html,NONE,1.1 configurationdns.html,NONE,1.1 configurationhostgroups.html,NONE,1.1 configurationhosts.html,NONE,1.1 configurationldap.html,NONE,1.1 configurationmail.html,NONE,1.1 configurationsystem.html,NONE,1.1 createhostname.html,NONE,1.1 editadomain.html,NONE,1.1 forwardemail.html,NONE,1.1 managedns.html,NONE,1.1 managemailgroups.html,NONE,1.1 manageusers.html,NONE,1.1 managevirtualhosts.html,NONE,1.1 processes.html,NONE,1.1 reseller-guide.html,NONE,1.1 resetemailaccount.html,NONE,1.1 resetftppassword.html,NONE,1.1
Tony Wasson <[email protected]>
| Newsgroups | gmane.comp.isp.ispman.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/ispman/ispman/ispman-web/htdocs/docs
In directory sc8-pr-cvs1:/tmp/cvs-serv6101
Added Files:
addadmin.html addadomain.html addavirtualhost.html
addclient.html addemailaccount.html addreseller.html
administrator-guide.html commandlinetools.html
configuration.html configurationaccountvars.html
configurationapache.html configurationdns.html
configurationhostgroups.html configurationhosts.html
configurationldap.html configurationmail.html
configurationsystem.html createhostname.html editadomain.html
forwardemail.html managedns.html managemailgroups.html
manageusers.html managevirtualhosts.html processes.html
reseller-guide.html resetemailaccount.html
resetftppassword.html
Log Message:
Base load of online documentation. Includes instructions for most common tasks along with reseller and administrator guides.
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0 col=2>
<tr><td class=menuheader>Adding an administrator</td>
<tr><td>To add an administrator, you must have an authority level of 100. If
this is a new installation, you'll have to be logged in as ispman.
<tr><td><b>To add an Administrator:</b>
<li>Click on Configure then on Administrator accounts.
<li>You will see a list of existing administrators, click on "Add an admin"
<br><img SRC="images/addadmin.png"><br CLEAR=LEFT>
<li>Enter the information about the administrator
<li>Click Add admin when finished
</ul>
<tr><td><b>Administrator Authority Levels</b>
<BR><b>0 to 69</b> - Add Resellers, Clients, Domains, Mailboxes
<BR><b>70 to 99</b> - The above, plus delete domains
<BR><b>100</b> - The above, Add administrators, manage configuration
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Adding a domain</td>
<tr><td><b>Note to Resellers and Administrators:</b> Verify that the customer has a client login so they
can manage their domain. Be sure they are assigned to your reseller account.
<tr><td><b>Note to Client:</b> If logging in as a client, you may be able to create your
own domains. Your Reseller or ISP has an option to allow you to create up to a maximum
number of domains. If you can't add a domain, ask your Reseller for
assistance.
<ul>
<li> Click on Add Domain, filling out these pieces of info:
<br><img SRC="images/addadomain1.png"><br CLEAR=LEFT>
<br><pre>Domain Type = primary
* primary - DNS is managed by ISPMan (default)
* secondary - DNS is managed somewhere else and we are a "slave" server
* nodns - ISPMan should not worry about DNS or DNS is hosted elsewhere
* replica - The domain is a copy of another ISPMan domain
</pre>
<br>TIP: Imagine you just registered customer.org and wanted email and web pages
to mirror what is already setup for customer.com. Make this happen by
choosing Replica Domain when creating customer.org. Then choose customer.com
as the master domain.
<br><pre>
Domain Name = customer.com
Domain Owner = Who pays for this
Domain Customer = Who owns the domain
Select the Domain Client from the drop-down menu
Choose the services needed for this domain -- Web, Mail or both.
</pre>
<li> Then click Next
<br><img SRC="images/addadomain2.png" ALIGN=LEFT BORDER=0><br CLEAR=LEFT>
<br><pre>Home Directory = Don't touch this unless you have a good reason
FTP Password = allows domain wide FTP access and access to the customer
control pannel.
Max Email accounts = Leave blank, unless this account has a limit.
Max Virtual Hosts = Leave blank, unless this account has a limit.
Max Storage Space = 50 is reasonable
Mail Delivery = MX
</pre>
<br>NOTE: If email is NOT handled by ISPMan for this domain, be sure the DNS MX
records have the preferred email server(s) listed.
<li>Click Save Entry
<li>Setup DNS extras:
<br><pre>
Under A:
alias @ to the same IP as www
(useful for making customer.com go to www.customer.com)
</pre>
<li>Be sure to click "Commit session" when done.
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Adding a virtualhost or website</td>
<tr><td>Adding a virtualhost is straightforward.
<ul><li>Select the domain to manage</li>
<li>Under "Manage virtualhosts" click Add virtualhost.</li>
<li>A box pops up, type "www" two times with no quotes.</li>
<li>Set virtualhost aliases to these 2 lines (changing the domain name)
<br>customer.com
<br>*.customer.com</li></ul>
<tr><td>These aliases tell the webserver to always serve the website files at:
/ispman/domains/customer.com/vhosts/www/htdocs
<tr><td>NOTE: If you have multiple virtualhosts/websites, don't use *.customer.com
as an apache alias, use simply www.customer.com. Using *.customer.com may
block access to the second virtual host.
<ul><li>Make sure "FTP Access" is enabled, and set an "FTP password". This is
also the password to the customer control panel.</li>
<li>Click the "Update" button.
<li>Be sure to click "Commit session" when done.
</li>
</ul>
<tr><td>ADVANCED TIP: To add a second virtualhost, like private.customer.com, use
the above steps, but at step 3, type private twice. Your ftp server would be
private.customer.com and FTP username would be private.customer.com.
<tr><td class=menuheader>FTP Upload Information</td>
<tr><td><b>FTP server</b> The hostname of the virtualhost. If you were
editing www.customer.com, the FTP server would be www.customer.com.
<tr><td><b>username</b> The full name of the virtualhost. If you were
editing www.customer.com, the username would be www.customer.com.
<tr><td><b>password</b> Whatever you set above.
<tr><td>The website files should be uploaded to the htdocs folder.
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</PRE>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0 col=2>
<tr><td class=menuheader>Adding a Client</td>
<tr><td>To add an client, you must be logged in as a reseller or be an
ISPMan administrator with an authority level of at least 20.
<tr><td>Each client is associated with a reseller, who can also manage the
client's domains. This allows the reseller to provide support to the client
if a question arises. If there are no resellers in the system, it is impossible
to add a client.
<br><tr><td><b>To add a client:</b>
<li>Click on Clients, then click on "Add a client"
<br><img SRC="images/addclient.png"><br CLEAR=LEFT>
<li>Select the reseller for this client.
<li>Enter the username, password and other information about the client.
<li>Set a maximum number of domains for the client.
<li>Click "Add this client" when finished
</ul>
<tr><td class=menuheader>Client Login Information
<tr><td><b>ISPMan URL</b> Usually ispman.domain.com (depending on your
setup, they may need to click "Login as Administrator")
<tr><td><b>username</b> Whatever you set above.
<tr><td><b>password</b> Whatever you set above.
<tr><td>Remind the user to login as a Client
<p>
<tr><td><A HREF="administrator-guide.html">Return to Reseller Guide</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Adding an email account</td>
<tr><td>To add a wildcard or catchall account set the mail aliases to
@domain.com (where domain.com is the name of the domain).
<BR>
<tr><td>To add an email account in ISPMan follow these steps:
<li>Select the domain to manage.
<li>Click Add user under the Manage users section.
<li>Fill out the information about the new user.
Username can contains characters a - z. No accent characters, numbers or
punctuation marks are allowed. A good username is first character of
firstname concatenated with lastname
<pre>
* UserName - user name
* Surname - last name of the user
* FirstName -first name of the user
* Password - user password
* Create mailbox on server - choose a server from the mailstore group to
create a mailbox, or None (no mailbox, just forwarding)
* FTP Access - enable or disable a private ftp folder
* Max FTP Storage Space (in MB) - set an ftp storage quota
* Max Mail Storage Space (in MB) - set an email storage quota
</pre>
<li>Set the Password field to an agreed upon password with the user or just
assign a password and inform the user.
<li>Click the "Save Entry" button.
<li>Be sure to click "Commit Session" to activate your change.
<tr><td>NOTE: Depending on your configuration, the password field may appear
scrambled the next time you view the user. This is normal.
<tr><td class=menuheader>Email account settings</td>
<tr><td><b>SMTP server</b> Varies per ISP, but it is usually of of these 3:
<br>1) hostname of the server where you created the mailbox.
<br>2) mail.domain.com (where domain.com is the name of your ISP)
<br>3) smtp.domain.com (where domain.com is the name of your ISP)
<tr><td><b>POP3/IMAP server</b> hostname of the server where you created the mailbox.
<tr><td><b>username</b> your email address, OR
username_domain_com if your servers are not setup with Perdition.
<tr><td><b>password</b> Whatever you set above.
<p>
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0 col=2>
<tr><td class=menuheader>Adding a Reseller</td>
<tr><td>To add a reseller, you must be an ISPMan administrator.
<tr><td>Each reseller can create clients and fully manage their clients domains.
<tr><td><b>To add a reseller:</b>
<li>Click on Resellers, then click on "Add a reseller"
<br><img SRC="images/addreseller.png"><br CLEAR=LEFT>
<li>Enter the username, password and other information about the reseller.
<li>Set a maximum number of clients for the reseller.
<li>Click "Add this reseller" when finished
</ul>
<tr><td class=menuheader>Reseller Login Information
<tr><td><b>ISPMan URL</b> Usually ispman.domain.com (depending on your
setup, they may need to click "Login as Administrator")
<tr><td><b>username</b> Whatever you set above.
<tr><td><b>password</b> Whatever you set above.
<tr><td>Remind the user to login as a Reseller
<p>
<tr><td><A HREF="administrator-guide.html">Return to Administrators
Guide</A>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Administrator Guide</td>
<tr><td>Welcome to ISPMan. If you have just installed ISPMan,
congratulations!
<tr><td>From here, you'll need to finish configuring ISPMan,
and add a domain to make sure everything is working.
<br><ul>
<li><a href="configuration.html">Configuring ISPMan</A>
<li><a href="addreseller.html">Adding Resellers</A>
<li><a href="addclient.html">Adding Clients</A>
<li><a href="processes.html">Understanding Processes</A>
<li><a href="commandlinetools.html">Command Line Tools</A>
<tr><td>If you're going to allow resellers or power
customers to manage and create domains, add a "master reseller" account for
the ISP and then add any additional resellers.
<tr><td>TIP: Once ISPMan is configured, use an administrator account with an authority level of less than 70
to prevent ever accidentally deleting a domain.
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>ISPMan Command Line Tools</td>
<tr><td>While many user appreciate the web interface of ISPMan, the
developers have not forgotten about the power of the command line.
<tr><td>Here is list of available command line tools, you can find these
tools in /opt/ispman/bin or the bin directory of your ispman installation.
<pre>
ispman.addAdmin
ispman.addClient
ispman.addDomain
ispman.addDomainService
ispman.addDomainService2Domain
ispman.addHost
ispman.addHost2HostGroup
ispman.addReseller
ispman.addSlaveDomain
ispman.addUser
ispman.addvhost
ispman.commitSession
ispman.createMailbox
ispman.deleteAdmin
ispman.deleteDomain
ispman.deleteDomainService
ispman.deleteHost
ispman.deleteHostGroup
ispman.deleteMailbox
ispman.deleteProcess
ispman.deleteSession
ispman.deleteUser
ispman.deletevhost
ispman.deltree
ispman.dnsdump
ispman.dnsload
ispman.dnsset
ispman.dnsshow
ispman.dnsunset
ispman.domainInfo
ispman.domainmail
ispman.dumpConf
ispman.fixUsers
ispman.getClientsCount
ispman.getConf
ispman.getDomainAttribute
ispman.getMailboxQuota
ispman.getTemplate
ispman.l10n
ispman.ldap2apache
ispman.ldap2named
ispman.ldifdump
ispman.ldifload
ispman.listAdmins
ispman.listClients
ispman.listHostGroupMembers
ispman.listHostGroups
ispman.listHosts
ispman.listMailboxes
ispman.listModules
ispman.listResellers
ispman.listSessionProcesses
ispman.listSessions
ispman.listUserQuotas
ispman.listUsers
ispman.listVars
ispman.listvhosts
ispman.loganalyzer
ispman.makeDomainDirectories
ispman.makelogs
ispman.myhostname
ispman.passwd.user
ispman.postfix.makemaps
ispman.processdump
ispman.processes
ispman.removeEmptySessions
ispman.setDomainAttribute
ispman.setDomainClient
ispman.setDomainReseller
ispman.setMailboxQuota
ispman.setmailtransport
ispman.setVar
ispman.showdomains
ispman.showmailtransport
ispman.zoneparse
</pre>
<p>
<tr><td><A HREF="administrator-guide.html">Return to Administrator Guide</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Configuring ISPMan</td>
<tr><td>ISPMan system configuration is done from the configuration menu,which can be
accessed by clicking the 'configure' button in the top menu bar. There's a
list of subsections in the menu for LDAP configuration, account variables,
mail configuration, apache configuration, system configuration, DNS
settings, hosts and hostgroups.
<tr><td>The bulk of these settings are made upon
first installation and then never changed.
<tr><td><b>Click on an area below for more information</b>
<table class="table" cellspacing=5 border=0>
<tr><th valign=top align=left><a
href="addadmin.html">Administrator accounts</a></th>
<td class=line0><p><font COLOR='BLACK'><i> Here you can
configure admin accounts. These accounts will have access to ISPMan
interface.</i></font></p></td>
</tr>
<tr><th valign=top align=left><a
href="configurationapache.html">Apache
config</a></th>
<td class=line1><p><font COLOR='BLACK'><i> These are Apache-specific
variables </i></font></p></td></tr><tr><th valign=top align=left><a
href="configurationmail.html">Mail
Configuration</a></th>
<td class=line0><p><font COLOR='BLACK'><i> These are SMTP and IMAP server
configuration variables. Currently the only supported SMTP server is Postfix
</i></font></p></td></tr><tr><th valign=top align=left><a
href="configurationdns.html">DNS
Settings</a></th>
<td class=line1><p><font COLOR='BLACK'><i> <br>These are DNS (named)
specific variables<br>will put an empty named.conf.header and
named.conf.footer in /opt/ispman/templates <br>directory for you which you
can later change according to your network.<br>If you already have these
files in place then they will be left untouched.<br>
</i></font></p></td></tr><tr><th valign=top align=left><a
href="configurationldap.html">LDAP
configuration</a></th>
<td class=line0><p><font COLOR='BLACK'><i> LDAP data
</i></font></p></td></tr><tr><th valign=top align=left><a
href="configurationaccountvars.html">Account
variables</a></th>
<td class=line1><p><font COLOR='BLACK'><i> These are variables used when
creating accounts (both users/domains) </i></font></p></td></tr><tr><th
valign=top align=left><a
href="configurationsystem.html">System
Configuration</a></th>
<td class=line0><p><font COLOR='BLACK'><i> Misc system questions
</i></font></p></td></tr>
<tr><th valign=top align=left><a
href="configurationhosts.html">Hosts</a></th>
<td><p><font COLOR='BLACK'><i> Manage hosts that take part in
your ISP </i></font></p></td></tr>
<tr><th valign=top align=left><a
href="configurationhostgroups.html">HostGroups</th>
<td><p><font COLOR='BLACK'><i>Define groups of hosts by tasks
such as mailGroup, httpGroup etc </i></font></p></td></tr>
</table>
<p>
<tr><td><A HREF="administrator-guide.html">Return to Administrator Guide</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Configuring Account variables</td>
<tr><td>This screen allows you to customize the login shell and the default
homedirectory location. For most installations, the defaults are fine.
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Apache Config</td>
<tr><td>Here are the settings I used for Apache 1.3 on Debian:
<pre>ISPMAN - Apache Configuration
Apache stop command - /etc/init.d/apache stop
Webalizer command - /usr/bin/webalizer
Apache vhost file - /etc/apache/vhosts.conf
(Must add "Include /etc/apache/vhosts.conf" to apache's httpd.conf)
Apache start command - /etc/init.d/apache start
Apache graceful reload command - /etc/init.d/apache reload
Default vhost IP -- * (Allows it to work on any machine)
Apache reload command - /etc/init.d/apache reload
</pre>
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>DNS Settings</td>
<tr><td>Here are the settings I used for Bind8 on Debian
<pre>
DNS Config:
Named Start Command - /etc/init.d/bind start
Primary DNS (name) - ns1.domain.com
ISPMan's DNS data directory - ispman/
Primary Mail Server (name) - mail.domain.com
Named data directory - /var/named
Secondary Mail Server (IP) - xxx.xxx.xxx
DNS Backend - bind8
Secondary DNS (IP) - xxx.xxx.xxx.xxx
Reverse Zone directory - rev/
Header file for named.conf - /opt/ispman/templates/named.conf.header
Named Reload Command - /etc/init.d/bind reload
Footer file for named.conf -/opt/ispman/templates/named.conf.footer
Named Stop Command - /etc/init.d/bind stop
Secondary Zone directory - sec/
Named Config File -/etc/named.ispman.conf
Primary DNS (IP) - xxx.xxx.xxx.xxx
Secondary Mail Server (name) - mail2.domain.com
Secondary DNS (name) - ns2.domain.com
Primary Mail Server (IP) - xxx.xxx.xxx.xxx
Catch all CNAME - none
Primary Zone directory - pri/
Hostmaster's email address - hostmaster.domain.com
Named User - root
</pre>
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Configuring Hostgroups</td>
<tr><td>ISPMan uses hostgroups to know what hosts to update when a change
occurs. To make ISPMan fully functional, there must be at least 1 host in each
hostgroup.
<br><IMG SRC=images/configurehostgroups.png>
<tr><td><b>To add Hosts to a group</b>
<ul><li>Edit the group to change
<li>The screen will update, showing details about that group.
<br><IMG SRC=images/configurehostgroupsmtp.png>
<li>Highlight the first host to be a group member</li>
<li>Select any additional hosts, by holding the Ctrl (Control) key down while
clicking</li>
NOTE: On a Macintosh, hold down the Command key to select multiple hosts.
<li>Click Update when finished
</ul>
<tr><td>Update each group with members
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Hosts</td>
<tr><td>All machines, or hosts, that run the ispman-agent need to be listed
in the hosts. Once the host is created, it can be attached to the right
hostgroups.
<tr><td><b>To add a Host</b>
<ul><li>Click Configuration, and click Hosts.
<li>Machine Hostname - Enter the fully qualified
hostname
<li>Host Alias - a short name for the host
<li>IP Address - IP Address in dotted quad format.</li>
<li>Description - Brief description of the machine, such as virtualhost #1
<li>Click Add host when finished.
</ul>
<tr><td>Once all hosts are entered proceed onto host groups.
<br><IMG SRC="images/configurehosts.png">
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>LDAP Configuration</td>
<tr><td>Here you can change the LDAP server (name) and LDAP base DN. This is
only needed if drastically reconfiguring LDAP.
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Mail Configuration</td>
<tr><td>Customize the settings for your SMTP server, usually Postfix, and IMAP
server, usually Cyrus or Courier.
<br><IMG SRC="images/configurationmail.png">
<tr><td>On Debian customize the postfix settings like so:
<PRE>
SMTP Reload command - /etc/init.d/postfix reload
<p>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>System Configuration</td>
<tr><td>The System Configuration Screen allows you to set the
administrator's email address, installaion directory, and password hashing
methods.
<tr><td><b>Understanding Password Hash Methods</b>
The hash method used must balance the protocols, authentication types, and
need for security. Hashing creates a long string of numbers based on the
password. This long string of numbers is called the hash. It is considered one way,
since is is nearly impossible (if not impossible) to tell what the original
password is from the hash.
<ul><li>clear - not a hash method. Stores the password string in base64 in LDAP, easily
viewable. Required for SMTP AUTH using LOGIN.
<li>crypt - standard unix crypt hash
<li>md5 - 128-bit hash, stronger than crypt
<li>sha - 160-bit hash, stronger than md5, but slower
</ul>
<tr><td><A HREF="configuration.html">Return to Configuring ISPMan</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Create a DNS hostname</td>
<tr><td>You can make a DNS hostname by adding a DNS "A Record". <br>Here are the
steps:
<ul><li>Select the domain to manage</li>
<li>Under Manage DNS, click A Records</li>
<li>You'll see a list of all Address Records for the domain. To add a new
record, type in the hostname in the first field and the IP address in the
second field.</li>
<li>Check the Rev. checkbox if you want a Reverse DNS record to be created.
<li>Click Save.</li>
<li>To apply your change, click Commit session.</li>
<tr><td>NOTE: You will only see the Manage DNS section on a domain that is a
primary ISPMan domain. Manage DNS will not appear on replica domain,
secondary/slave domains, or nodns domains.
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Edit a domain</td>
<tr><td>Clicking the Edit domain.com button shows global settings about the
domain. From here you can change mail Delivery options, set maximum email
users, storage quotas.
<PRE>
* Domain Comment - This should store notes and exceptions for about the domain
* Mail Delivery - Should usually be set to deliver to MX host with a matching
DNS MX record.
* FTP Password - This is also the password to the Customer Control Panel
* Domain Services - Each service enabled for the domain must be highlighted
* Max Email accounts - ISP staff can set a maximum number of accounts
* Max Virtual Hosts - ISP staff can set a maximum number of virtualhosts
* Max Storage Space (in MB) - set a space quota
* FTP Access - FTP access can be enabled or disabled
* Locked - Locking a domain means that it cannot be changed unless unlocked by
an administrator.
* Delete Domain - This erases *EVERYTHING* about the domain, including user
email accounts, and websites. BE CAREFUL.
</PRE>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Forwarding Email for a user</td>
<tr><td>ISPMan can be used to provide email forwarding. Here are the steps
to forward email for a user
<li>Select the username from user dropdown.
<li>Under Mail
Forwarding, enter the complete email address where email should go.
<li>Be sure to click
Commit when done.
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Manage DNS</td>
<tr><td>The Manage DNS option appears once you have selected a domain to
manage AND that domain is a Primary domain. Manage DNS does not appear for
replica domains, secondary (slave) domains, or replica domains.
<tr><td>DNS is one of the most misunderstood services on the Internet. If
you are not familiar with DNS, consult your ISP, local guru, or a good book
for help. <B>YOU CAN MESS UP YOUR DOMAIN WEBSITE AND EMAIL WITH WRONG
OPTIONS!</B>
<tr><td><b>SOA Record</b>
<br>The SOA (start of authority) resource record. The SOA indicate that this
name server is the authoritative source of information for this domain.
There can be only one SOA for a domain.
<ul>
<li>Primary - what is the primary Start Of Authority for this domain
<li>rootmail - who is to get mail for the domain master
<li>Expire - seconds for secondary DNS server to expire it's
data after failing to reach master
<li>Retry - how often the secondary DNS server should try to
connect after a refresh connect failure
<li>Refresh - how often the secondary should check to insure
it's data is current
<li>Minimum - the time a RR can be cached before it should be
discarded
</ul>
<tr><td><b>MX Records</b>
<br>The MX Record specifies a mail exchanger, which should match an A
record, that will accept mail for the domain.</pre>
<ul>
<li>Origin - domain mail is for
<li>Host - host that will accept mail
<li>Priority - priority of this server in the list of mail
servers for delivery, lowest priority number is the server that is the final
destination. Higher priority numbers indicate forwarders. Any number is a
valid value. Usually multiples of 10 are used for priority.
</ul>
<tr><td><b>NS Record</b>
<br>The NS (name server) record lists every name server that will answer for
this domain.
<ul>
<li>Origin - domain this record applies
<li>Name Server - name of the DNS server
</ul>
<tr><td><b>A Records</b>
<br>A Records (address records) map host names to IP addresses.
<ul>
<li>Host Name - Authorotative Host Name
<li>IP address - IP of host
<li>check box if you want the address reverse mapped
</ul>
<tr><td><b>CNAME Records</b>
<br>CNAME Records (canonical name records) are aliases for host names.
<br>Here you can add an Alias for a host or another alias. Fully
qualified hostnames should end with a period. Hostnames that do not end with
a period are supposed to be relative names for this domain.
<ul>
<li>Alias - the alias name
<li>Host - the A Record name for this host
</ul>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Manage mailgroups</td>
<tr><td>Mailgroups are like a very simple mailing list, or distribution
email list. They are commonly
used to provide a group of users an easy way to email everyone.
<tr><td>They can
also be used to redirect "role" accounts to the appropriate people. For
instance, many companies have an "info@" account. If you make an info
mailgroup, you can forward any emails sent to info@ to several staff
members.
<tr><td>Say your company has 2 salespeople and the owner would like to have any
emails coming in to sales-3cT1FqDdCvJWk0Htik3J/[email protected] to go to alice, bob and himself.
Here's how to set that up.
<li>Create a new mailgroup by clicking "Add mailgroup"
<li>For the "Mail group name" field enter sales
<li>For the "Mail group members" enter:
<BR>alice-3cT1FqDdCvJWk0Htik3J/[email protected]
<BR>bob-3cT1FqDdCvJWk0Htik3J/[email protected]
<BR>ceo-3cT1FqDdCvJWk0Htik3J/[email protected]
<li>Click the "Add Mailgroup" button. To activate your change, click "Commit
Session".
<tr><td>If you wanted any emails to sales OR info go to this same list of
people, add info-3cT1FqDdCvJWk0Htik3J/[email protected] to the "Mail group aliases"
<P>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Manage users</td>
<tr><td><a href="addemailaccount.html">Follow these steps to add a new user</A>
<tr><td>To manage users of a domain, you must choose a domain from
domain selection box, wait till it refreshes and then use the buttons as
outlined.
<li>Surname</li>
<li>Firstname</li>
<li>Password</li>
<li>Primary Mail Address</li>
<li>Primary Mail Box Address</li>
<li>Mail Forwardings</li>
<li>Mail Aliases</li>
<li>Reset - Delete User - Update User</li>
</ul>
<tr><td>As a domain increases in size, you may need to search for a user by First Name, Last Name or User
ID.
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Manage virtualhosts</td>
<tr><td><a href="addavirtualhost">Add a virtualhost</A>
<tr><td>Edit a virtualhost by following these steps:
<li>Select the domain to edit.
<li>Under Manage virtualhosts, choose the virtualhost to edit.
<li>Here are the options for the virtualhost
<br><pre>
* IP address - Usually * or the IP address of the virtualhost
* DocumentRoot - The path to the website files
* DocumentRoot directory options - Options allowed for website files
* ScriptDirectory (/cgi-bin/) - The path to any scripts
* Script directory options - Options allows for scripts
* Server Aliases - Hostnames that will display the website files
* Extra configurations - Any special configuration lines go here
NOTE: Bad configuration options can break the webserver. Be careful.
* FTP Access - Enable or Disable access to the website files
* Max Storage Space (in MB) - Quota limits
* Password - Password to FTP for this virtualhost
<li>If you changed any options, click "Update", then "Commit session".
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Understanding Processes</td>
<tr><td>ISPMan schedules system changes using processes. Processes are
directed to hosts based on hostgroup membership.
<tr><td>You can view the Processes
"in the queue" by clicking on the Processes tab at the top of the screen.
<br><img src="images/processes.png">
<tr><td>A process can have the status of "new" or "insession".
<ul><li>insession - the process is waiting for the user to click "Commit
session". Clicking Commit session changes the state to new.
<li>new - the process is waiting for the ispman-agent to execute it.
</ul>
<tr><td>If the user logs out before clicking "Commit session" the process
will stay in the "insession" status until it is manually deleted or manually
changed to the "new" status.
<p>
<tr><td><A HREF="administrator-guide.html">Return to Administrator Guide</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Reseller Guide</td>
<tr><td>Welcome to ISPMan! As a reseller, you can easily add clients and
domains for your clients.
<tr><td>ISPMan allows your clients have their own login to
the ISPMan system. Logging in allows your client to manage their own
email accounts and virtualhosting. Of course, you can fully administer their domains if they have a problem or
a question.
<br><ul>
<li><a href="addclient.html">Adding a Client</A>
<li><a href="addadomain.html">Adding a Domain</A>
<li><a href="processes.html">Understanding Processes</A>
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Reset A User's Email Password</td>
<tr><td>To reset a user's password in ISPMan follow these steps:
<li>Select the domain to manage.
<li>Select the username from user dropdown.
<li>Change the password field to an agreed upon password with the user
<li>Click the "Update User" button
<li>Be sure to click "Commit Session" to activate your change.
<tr><td>NOTE: Depending on your configuration, the password field may appear
scrambled the next time you view the user. This is normal.
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
--- NEW FILE ---
<HTML>
<TITLE>ISPMan help</TITLE>
<link HREF="/ispman.css" REL="stylesheet" TYPE="text/css">
<BODY>
<table class="table" cellspacing=5 border=0>
<tr><td class=menuheader>Reset an FTP Password to upload a website</td>
<tr><td>To reset an FTP password in ISPMan follow these steps:
<li>Select the domain to manage.
<li>Select the virtualhost to edit from the "Select virtualhost" dropdown.
This is usually www.
<li>Make sure the FTP Access is set to Enabled.
<li>Change the Password field to an agreed upon password with the user.
<li>Click the "Update" button.
<li>Be sure to click "Commit Session" to activate your change.
<tr><td>NOTE: Depending on your configuration, the password field may appear
scrambled the next time you view the user. This is normal.
<tr><td class=menuheader>FTP Upload Information</td>
<tr><td><b>FTP server</b> The hostname of the virtualhost. If you were
editing www.customer.com, the FTP server would be www.customer.com.
<tr><td><b>username</b> The full name of the virtualhost. If you were
editing www.customer.com, the username would be www.customer.com.
<tr><td><b>password</b> Whatever you set above.
<tr><td>The website files should be uploaded to the htdocs folder.
<p>
<tr><td><A HREF="/help.html">Return to Main Help Screen</A>
</BODY>
</HTML>
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54