ispman-docs Mailing List for ispman

You asked for this in your manual

Dennis Kaplan

Perl Modules with apt-get:

apt-get install perl perl-modules libio-socket-ssl-perl
liblocale-maketext-lexicon-perl liblog-agent-perl libhtml-parser-perl
libtext-iconv-perl libcgi-session-perl make libtext-template-perl
libcgi-perl libimap-admin-perl libnet-ssleay-perl liburi-perl
libcvs-perl libio-socket-ssl-perl libparse-recdescent-perl
libunicode-string-perl libconvert-asn1-perl libio-stringy-perl
libmail-rfc822-address-perl libxml-sax-perl libdns-zoneparse-perl
liblocale-maketext-simple-perl libsoap-lite-perl libnet-perl
libdigest-perl liblocale-maketext-lexicon-perl libmldbm-perl
libsasl2-modules libsasl2 liblog-agent-perl libnet-ldap-perl
libclass-accessor-perl libio-pty-perl libipc-run-perl
libxml-namespacesupport-perl libxml-parser-perl libauthen-sasl-perl

Finn Thain wrote:
> Hi,
> 
> Here are some suggestions for the INSTALL file, in the form of a patch. 
> The changes are improvements to grammar, spelling and consistency.

Hi Finn,

thanks for the corrections.

>
> I'm in the process of setting up ISPman, so I haven't read much of the
> rest of the docs yet. Is it appropriate to send patches against HEAD?

Certainly! Keep posting ;)
If possible, please send your patches as attachments.

Joerg

Hi,

Here are some suggestions for the INSTALL file, in the form of a patch. 
The changes are improvements to grammar, spelling and consistency.

I'm in the process of setting up ISPman, so I haven't read much of the 
rest of the docs yet. Is it appropriate to send patches against HEAD?

Regards
Finn Thain



Index: docs/INSTALL
===================================================================
RCS file: /cvsroot/ispman/ispman/docs/INSTALL,v
retrieving revision 1.8
diff -u -r1.8 INSTALL
--- docs/INSTALL	4 Aug 2004 20:15:39 -0000	1.8
+++ docs/INSTALL	7 Aug 2005 07:28:39 -0000
@@ -3,9 +3,9 @@
 
 ISPMan is developed using OpenLDAP and Apache.
 This file covers
- - necessary requirements
+ - prerequisites
  - basic concepts
- - process for installing
+ - installation process
  - populating a new ldap tree
  - setting up a virtual host for apache.
 
@@ -21,13 +21,13 @@
 ============
 In order to use ISPMan, you will need ...
 
-... a ldap server:
+... A LDAP server:
 This will be preferably OpenLDAP, but actually any LDAP server could
 do the job. The following inststructions are based on OpenLDAP, so
-you'll probably need to adjust the configs and schemas accordingly, if
-you use an alternate LDAP server.
+you'll probably need to adjust the configs and schema accordingly, if
+you use an alternative LDAP server.
 
-... a web server:
+... A web server:
 Apache is the suggested choice. While ISPMan itself will probably run
 on any CGI enabled web server, the managed vhosts within ISPMan are
 generated with apache's vhost.conf style config files.
@@ -35,7 +35,7 @@
 admin may come up with his own interface for some other web server
 type.
 
-... perl:
+... Perl:
 This is mandatory, since ISPMan is written in perl ;)
 Perl 5.6 (or higher) is recommended.
 
@@ -50,13 +50,13 @@
 
 ISPMan Concepts
 ===============
-If you got your requirements in place, you are ready for install.
+If you have your requirements in place, you are ready for install.
 But before starting off, be sure to understand the main principles
 behind ISPMan:
 
-ISPMan consists primarily out of for main parts:
+ISPMan consists primarily of four main parts:
  * Perl libraries providing the business logic
- * Command-Line-Tools for non-web administration
+ * Command-line tools for non-web administration
  * ISPMan agent - The "executive" doing the actual work
  * Web CGIs - Providing an user interface for admin & customers
 
@@ -75,29 +75,29 @@
 This will be the place from which you will install, update and
 customize your ISPMan.
 
-Besides this you will have your *ispman_install_directory* where all
-the files will get installed.
+Besides this, you will have your *ispman_install_directory* where all
+the files will be installed.
 
-That's it! No more "build", "tmp", or whatever directories confusing you.
+That's it! No more "build", "tmp", or whatever directory to confuse you.
 
-See sections below for some more information how to effectively update
+See sections below for some more information as to how to effectively update
 and customize your ISPMan installation.
 
 
 
 Installation Overview
 =====================
-This is quick overview process about the installation process.  See
-the sections below for detailed installation.
+This is quick overview of the installation process. See the sections below
+for detailed installation.
 
 1) Unpack tarball & get latest bugfixes via CVS
 2) Install ISPMan files
 3) Install needed perl modules
 4) Configure ISPMan core (ispman.conf)
-5) Configure ldap server and do the initial load of ISPMan data
-6) Setup the apache vhost for ISPMan
+5) Configure LDAP server and do the initial load of ISPMan data
+6) Set up the Apache vhost for ISPMan
 7) Finish ISPMan configuration through web interface
-8) Prepare your hosts to run ispman-agent
+8) Prepare your host(s) to run ispman-agent
 
 
 1) Unpack tarball & get latest bugfixes via CVS
@@ -106,8 +106,8 @@
 Bugfixes are made available only through CVS updates.
 
 Example:
-ISPMan version 1.2 is realeased as tar package ispman-1.2.tar.gz.
-The cvs tag matching this version is "rel_1_2-bugfixes".
+ISPMan version 1.2 is available as a tar package, ispman-1.2.tar.gz.
+The CVS tag matching this release is "rel_1_2-bugfixes".
 
 As described above (in Concepts), untar the ISPMan package somewhere
 in your software repository.
@@ -115,25 +115,25 @@
         -> cd ispman-1.2
 
 Be sure to have internet access and download the latest bug fixes from
-cvs:
+CVS:
         -> cvs -z3 update -dP
 
 The necessary CVS structures are already contained in the tarball, so
-don't worry about the cvs tags.
+don't worry about the CVS tags.
 
 Result of this section:
-You should have a complete, uptodate copy of that ISPMan version.
+You should have a complete and up-to-date copy of an ISPMan release.
 
 
 2) Install ISPMan files
 -----------------------
-Configure the install.
+Configure the installation.
         -> ./configure --prefix=/path/to/ispman/directory
 
 Specify "--prefix" if your installation directory is not the default
 (/opt/ispman). 
 
-Generate ISPMan core data & schemas 
+Generate ISPMan core data & schemas.
         -> make
 (alternate targets:)
         -> make ldif
@@ -148,11 +148,11 @@
         install-bin     for all CLI tools, including ispman-agent
         install-web     for all files needed for web interface
 
-Depending on your ISPMan deployment scenario (see ARCHITECURE), you'll
-use either one or both.
+Depending on your ISPMan deployment scenario (see ARCHITECTURE), you'll
+use either or both.
 
-For the following initial ISPMan setup, we assume doing a full install
-on this host you are doing this installation.
+For the following initial ISPMan setup, we assume a full install on the
+present host.
         -> make install
 (alternate targets:)
         -> make install-bin
@@ -160,31 +160,31 @@
         -> make install-agent
 
 Notice:
-Every install target includes any necessary common files.
+Every install target includes the necessary common files.
 If you are deploying on several hosts, make sure to either share the
-ISPMan configuration ($install_dir/conf/ispman.conf) or keep it in
+ISPMan configuration (<installdir>/conf/ispman.conf) or keep it in
 sync somehow.
 
 Result of this section:
-You will have a full ISPMan installation in the issued install
-directory (default: /opt/ispman). This dir is clean of any temporary
+You will have a full ISPMan installation in the given install
+directory. This dir is clean of any temporary
 files as well as any CVS files/dirs, because we certainly don't want
-to upgrade our productive installation directly.
-In the $installdir/conf dir, you'll find the following files for
+to upgrade our production installation directly.
+In the <installdir>/conf directory, you'll find the following files for
 further configuration:
  - ispman.conf.example          configuration example
- - ldif/*                       inital ISPMan data
+ - ldif/*                       initial ISPMan data
  - schema/*                     schema files for LDAP
 
 
 3) Install needed perl modules
 ------------------------------
 ISPMan uses quite a bunch of other perl modules that have to be
-available for proper operations.
-In the past, those dependant modules where provided within the ISPMan
+available for proper operation.
+In the past, those dependencies were provided within the ISPMan
 lib directory, which provided a kind of "hardcoded" environment,
-because any installed site perl modules where ignored.
-To overcome this limitation and provide better ways of having uptodate
+because any installed site-perl modules were ignored.
+To overcome this limitation and provide better ways of having up-to-date
 modules, they were removed from the lib directory.
 
 To have all needed modules available though, you can install them
@@ -193,8 +193,8 @@
 
 You have quite a few options here, so let's shed some light on that:
 
-option #1) Perl libs are provided by your system/distribution.
-This is probably the most wanted, but also most difficult option,
+option #1) Use Perl libs provided by your system/distribution.
+This is probably the most desirable, but also the most difficult option,
 since it very much depends on your OS distribution.
 You will find a list of needed perl modules in contrib/perl/modules,
 which you can match to packages in your distribution.
@@ -203,24 +203,24 @@
 developers, which will ease the creation of ISPMan distribution
 packages a lot.
 
-option #2) Perl libs are installed sitewide through CPAN.
-You don't care about distribution packages and just want to install
+option #2) Install Perl libs site-wide using CPAN.
+If you don't care about distribution packages, you may want to install
 any missing perl modules in the perl site directories.
         -> cd contrib/perl
         -> make install-cpan-site
 
-option #3) Perl libs are installed in ISPMan installation directory.
-You want to be independant of any installed site modules but like to
+option #3) Install Perl libs in ISPMan installation directory.
+If you want to be independant of any installed site modules but like to
 use the latest available module versions.
 In fact, this is pretty simmilar to the old way (before 1.3), except
 that it uses the latest versions available.
         -> cd contrib/perl
         -> make install-cpan
 
-option #4) Bundled perl libs are installed in ISPMan installation dir.
+option #4) Use bundled Perl libs installed in ISPMan installation dir.
 ISPMan comes with bundled perl modules, which are installed within the
 ISPMan install directory.
-This is probably the most easiest and convenient option, because you
+This is probably the easiest and most convenient option, because you
 don't need CPAN or an online connection. It uses fixed, but tested
 modules, so be sure to fallback here if you have trouble getting
 things to work.
@@ -245,39 +245,38 @@
 4) Configure ISPMan core
 ------------------------
 Provide a core ISPMan configuration (ispman.conf).
-If you are doing this install the first time, you can get an example
+If you are doing this install for the first time, you can get an example
 ispman.conf.
         -> cd <installdir>/conf
         -> cp ispman.conf.example ispman.conf
 
-Notice:
-If you already used earlier versions of ISPMan, be sure to migrate
+NB: If you already used earlier versions of ISPMan, be sure to migrate
 your old ispman.conf to the new config format.
 
 Edit the config file (ispman.conf) and change it according to your
-environment (esp. ldap server configuration).
+environment (especially the LDAP server configuration).
 
 Finaly, verify that ispman.conf has proper file permissions. It
 contains cleartext password, so no regular user should be able to read
 it (see Appendix about Security)!
 
 
-5) Configure ldap server and do the initial load of ISPMan data
+5) Configure LDAP server and do the initial load of ISPMan data
 ---------------------------------------------------------------
-Configuration of the necessary ldap server is actually an issue for
+Configuration of the necessary LDAP server is actually an issue in
 itself, and to have a secure and fast server, you should make yourself
 familiar with this issue by consulting the manual.
 
 Notice:
-From ISPMan's perspective there is no need to use a LDAP server
-exclusively, so you may in fact use any LDAP server that is already
-present, presumed you are able to adjust it's configuration accordingly.
+From ISPMan's perspective there is no need to have exclusive use of
+the LDAP server, so you may in fact use any LDAP server that is already
+present, presuming you are able to adjust its configuration accordingly.
 
 To give you a good starting point, there are example configurations
 for OpenLDAP bundled with ISPMan (install-data/examples/openldap).
-They can be used to modify or replace your OpenLDAP's server and
-client configuration files, respectively. Note that there may be some
-differences in paths with your unix distribution.
+They can be used to modify or replace your OpenLDAP server and
+client configuration files. Note that there may be some differences in
+paths compared with your unix distribution.
 
 Adjust the schema files to support ISPMan data.
 The needed schema files are provided in <installdir>/conf/schema.
@@ -294,18 +293,18 @@
     pureftpd.schema
     ispman.schema
 
-Restart your ldap server and ensure that it started without
+Restart your LDAP server and ensure that it started without
 errors. Look in the log. OpenLDAP logs to the LOCAL4 syslog facility
-by default, and many unix distributions don't listen or log this by
+by default, and many Unix distributions don't listen or log this by
 default. Starting the server with a debug option will print messages
 to the screen if the server fails to start.
 
 Next step is to populate the base ispman tree.
-We use the installed <installdir>/ldif/ispman.ldif for that, which
+We use the installed <installdir>/ldif/ispman.ldif for this, which
 provides the base LDAP tree for ISPMan data.
 Though this file is basically LDIF, you can't load this directly into
 your LDAP server, because it still contains some placeholders
-(e.g. ldapBaseDN) which have to be substituted with the real values of
+(e.g. ldapBaseDN) which have to be substituted with the real values from
 your core configuration.
 
 The proper way of doing the initial load of ispman.ldif is
@@ -316,20 +315,20 @@
 This should run through smoothly. In case you are getting errors here,
 solve them first before continuing.
 
-Run a test query to ensure ldap is working and the ispman base has been
+Run a test query to ensure LDAP is working and the ISPman base has been
 installed.  Here is an example that should print many variables like
 'ispmanVar:'.  Make sure this works before going any further.
         -> ldapsearch -x -LLL ispmanVar=*
 
 Run an ispman command to test the ispman configuration against the
-ldap tree. Again fix errors before continuing.
+LDAP tree. Again, fix any errors before continuing.
         -> <installdir>/bin/ispman.listVars
 
 
-6) Setup the apache vhost for ISPMan
+6) Set up the Apache vhost for ISPMan
 ------------------------------------
 ISPMan has an Administrator Panel and a Customer Control Panel. Both
-are cgi files installed in the same virtual host or directory
+are CGI files installed in the same virtual host or directory
 tree. These can be installed either with a dedicated webserver or
 appended on to an existing web server.  
 
@@ -397,7 +396,7 @@
 
 7) Finish ISPMan configuration through web interface
 ----------------------------------------------------
-Restart the webserver and visit the following link to get the ispman web
+Restart the web server and visit the following link to get the ispman web
 interface.
     http://ispman.yourdomain.tld
 
@@ -406,17 +405,16 @@
 ISPMan core configuration for LDAP administrator.
 
 IMPORTANT:
-Before going excited and start playing around, click the "Configure"
-menu and finish the ISPMan configuration by supplying proper
-information for all config groups. Especially the "Hosts" and
-"HostGroups" tabs are important.
+Before excitedly playing around, click the "Configure"
+menu and finish the ISPMan configuration by supplying the proper
+information for all config groups.
 
 Without configuring hosts and hostgroups, ISPMan will just be a fancy
 LDAP browser/editor. The hosts and host groups are VERY
 important. They are the linkage between generated processes and
-executed tasks by ispman-agent like creating users, setting up DNS,
-etc. So, if generated processes are not executed by ispman-agent, this
-is the place to check.
+tasks executed by ispman-agent, like creating users, setting up DNS,
+etc. So, if generated processes are not being executed by ispman-agent,
+this is the place to check.
 
 ISPMan's web interface only edits infomation in the LDAP tree. The
 ispman-agents running on each node do the real work. ISPMan creates
@@ -425,7 +423,7 @@
 "modifyDomain" request will go to dnsgroup. An agent on a host sees
 the task in the ldap tree set for its hostgroup and make the change in
 the dns server.  If you have not defined dnsgroup properly, the
-request will be strayed. 
+request will go astray. 
 
 
 8) Prepare your hosts to run ispman-agent
@@ -435,7 +433,7 @@
 connect to the LDAP server to get its task list. Anywhere ISPMan is
 updating files requires the agent. This will be on servers listed
 under "hosts" and "hostgroups" under configuration in the web
-interface. This includes smtp, dns, file and web servers.
+interface. This includes SMTP, DNS, file and web servers.
 
 The easiest way to setup ispman-agent is to just copy the whole ispman
 directory from the first installed host to the next. Then set it up to
@@ -445,8 +443,8 @@
 will ensure that ispman-agent is running on the appropriate
 machines. This can be done quickly, assuming supervise is already
 installed, with the following:
-        -> mkdir /supervise/ispman
-        -> cd /supervise/ispman
+        -> mkdir /service/ispman
+        -> cd /service/ispman
         -> echo '#!/bin/sh' >> run
         -> echo 'echo Starting ispman agent' >> run
         -> echo 'exec /opt/ispman/bin/ispman-agent nodetach' >> run
@@ -461,7 +459,7 @@
 
         -> /opt/ispman/bin/ispman-agent {start|stop|restart|forcerestart|nodetach}
 
-Ispman-agent writes a log file to
+ispman-agent writes a log file to
 /opt/ispman/var/<hostname>.ispman-agent.log. Be sure to clean out this
 file from time to time or use logrotate as it can get LARGE. When the
 agent has been started by booting, manual start or supervisor, review
@@ -478,8 +476,8 @@
 
 a) ISPMan files:
 Requirements: 
- * unix admin user should be able to use the CLI Tools (e.g. "admin")
- * ispman-agent needs to execute ISPMan processes (this usualy must be
+ * Unix admin user should be able to use the CLI Tools (e.g. "admin")
+ * ispman-agent needs to execute ISPMan processes (this usually must be
    "root" to be able to create/chown directories) 
  * web server needs to execute CGIs (running as "www" for example)
  * ispman.conf contains cleartext passwords and thus must not be
@@ -492,26 +490,26 @@
  - change group of all ISPMan files:
         -> cd <installdir>
         -> chgrp -R ispman .
- - if you didn't do ISPMan install as root I suggest reowning all
+ - if you didn't do the ISPMan installation as root I suggest giving all
    files to root:
         -> cd <installdir>
         -> chown -R root .
 
 During the install process all file modes should already be set
-adequately. Basicall only one file is of greater concern, because it
-contains cleartext passwords -> ispman.conf.
+adequately. Basically, only one file is of great concern, because it
+contains cleartext passwords, i.e. ispman.conf.
 Be sure that this file will not be readable by non-admin users!
         -> chmod 640 ispman.conf
 
 
 b) Web:
-Some users where claiming that ISPMan is unsecure, because ISPMan
-files (including ispman.conf) is readable by the webserver and thus
-any CGI programm a users calls could read those files.
-
-Although, this might be correct for some webserver installations, this
-is no security problem with ISPMan but rather the used webserver
-installation.
+Some users were claiming that ISPMan is not secure, because ISPMan
+files (including ispman.conf) are readable by the webserver and thus
+any CGI program a user calls could read those files.
+
+Although this might be correct for some webserver installations, this
+is not a security problem with ISPMan but one with those webserver
+installations.
 There are established techiques for secure CGI execution in place
 (suexec, jails, etc.). With such configured properly, there is no
 security problem with ISPMan at all.
@@ -524,8 +522,8 @@
 
 Simple example:
 You want to build a tar file which can be used to distribute the
-ispman-agent on all of your hosts. The ispman install dir should be
-placed in "/usr/local/ispman".
+ispman-agent on all of your hosts. The ISPman install dir is to be
+"/usr/local/ispman".
 
 Do this as follows:
         -> configure --prefix=/usr/local/ispman
@@ -535,32 +533,31 @@
 /usr/local/ispman only to build the tarball. So do this:
         -> make install-agent DESTDIR=/tmp/install
 
-This will install the complete ISPMan tree necessary to run the agent
-in /tmp/install. Just tar it there and you have a nice little
-distribution package.
+This will install the complete ISPMan tree in /tmp/install. Just tar
+it there and you have a nice little distribution package.
 
 
 Appendix: Customizations
 ========================
 You may have the need to change some of the ISPMan files to fit your
-requirements. Especially the library (*.lib) and template (*.template)
-files are designed for individual customizations.
+requirements. The library (*.lib) and template (*.template) files are
+especially designed for individual customizations.
 
 If that's the case for you, it may be advantageous to plan a litte bit
 ahead.
-Most users go the greedy way and just change the required files in their
+Most users go the obvious way and just change the required files in their
 installation directory. While this may be adequate for some quick
-tests, you should not do this on a permanent basis.
+tests, you cannot do this on a permanent basis.
 On next ISPMan update you'll know why, because the upgrade will
-overwrite all your nice litte changes.
+overwrite all your nice changes.
 
-So, what's the best practice for such changes:
+So, what's the best practice for such changes?
 Well, it's easy! Apply your changes to the *source* directory, not the
 installation directory.
-This has some obvious advantages:
- - Your customizations will persist cvs updates. In fact, any changes
-   in the same file will be merged, presumed it doesn't conflict with
-   your modifications.
+This has some real advantages:
+ - Your customizations will survive CVS updates. In fact, any change
+   to the same file will be merged, presuming that it doesn't conflict
+   with your modifications.
  - Any (upgrade) installation will already contain your modifications.
 
 

> Hi Wil,
>
> I am all for having the POD documentation about the usage.
>
> The documentation I propose is a step by step guide on using the CLI.
>
> Example:
>
> Install ISPMan
> Add a reseller
> Add a client under the reseller
> Add a domain
> Set the client and reseller for the domain
> List domains
> Add a user in the domain
> Add a website in the domain
> List users/websites for the domain
>
> Manipulate DNS information for the domain
> Manipulate site-wide DNS information (very undocumented and powerful
> feature)
>
> etc
>
> best regards

OK Atif et al,

I've posted a first draft of a CLI document. I need help on 3 points, all
of which are indentified by ?? in the doc.

1) Is there a way to set "Extra Configuration" options for a vhost from
the command line? For instance a Redirect Rule, or aliasing a directory?
Do you have to hack ispman.addvhost each time, or just use the web
interface?

2) Is there a way to add secondary and/or nodns domains from the
commandline without hacking ispman.addDomain?

If I understand correctly:
  ispman.addSlaveDomain adds a Slave/Replica domain.
  ispman.addDomain adds a Primary Domain by default. With hacking it can
do any domain type.

3) How does the ispman.dnsset work with SOA records? Under my tests, the
script happy accepted my input but didn't actually change anything,
including LDAP. (Cross posted to ispman-developers).

Any preference on the Documentation License we use? Can I just start
sticking this stuff up on www.ispman.org?

http://www.azxws.com/ispman/


Tony Wasson

> Wil Cooley wrote:
>> I would propose embedding the CLI and API docs as POD and automatically
>> generating them.
>
> Hi Wil,
>
> I am all for having the POD documentation about the usage.
>
> The documentation I propose is a step by step guide on using the CLI.
>
> Example:
>
> Install ISPMan
> Add a reseller
> Add a client under the reseller
> Add a domain
> Set the client and reseller for the domain
> List domains
> Add a user in the domain
> Add a website in the domain
> List users/websites for the domain
>
> Manipulate DNS information for the domain
> Manipulate site-wide DNS information (very undocumented and powerful
> feature)
>
> etc
>
> best regards

Greetings!

Splitting out the CLI information to a different document makes sense.
Many users are only interested in getting it running and then using the
web interface(s). However, some of us want a deeper understanding of the
CLI.

We could include the POD documentation along with the above "Task
Oriented" information.

Tony

Yes, that holds true with postfix 2.x and cyrus 2.x, I will have to take 
a look at the efficiency standpoint, I saw no real problem well into the 
1000's of pieces/min but I didnt test it both ways, mostly because I 
never saw the need to.  Good point, I'll add this info to the howto once 
I'm done testing. 

Jeff Meden

Wil Cooley wrote:

>Both guides by Tony and Jeff recommend for Postfix to deliver to Cyrus:
>
>mailbox_transport=cyrus
>
>I haven't looked at Postfix 2 yet, so maybe it's changed, but on 1.1
>that's defined as:
>
>cyrus     unix  -   n   n   -   -   pipe
>  flags=R user=cyrus argv=/usr/cyrus/bin/deliver -e -m ${extension} ${user}
>
>Delivering through 'deliver' is ineffecient; for one thing, it entails
>invoking another process, but mostly IIRC 'deliver' has to be called
>once for each recipient, so you lose the benefits of single instance
>store.  What the Cyrus people tend to recommend is using LMTP over UNIX
>domain socket:
>
>mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
>
>Wil
>  
>

On Sun, 2004-02-01 at 03:11, Atif Ghaffar wrote:
> Joerg Delker wrote:
>=20
> Hi Joerg, your @delker.de address is getting rejected. you are=20
> subscribed with a different address?

Hi Atif,=20
I thought you changed that last time, I'd the same problems (at least
you told me so ;-)
At least it's working for most of the other ispman lists, so I guess
it's currently just ispman-docs that rejects that address.

> > Since you are refering explicitly to version 1.1 you should use the
> > "rel_1_1-bugfix" branch to only catch the bugfixes and not the untest=
ed
> > development changes.
> > So better add an "-r rel_1_1-bugfixes" to the last line (This will
> > adjust with new releases of course).
>=20
> This is not necessary since the tar ball is built from the bug fixes=20
> branch. All CVS directories have the Branch/Tag informations

Jep, you're right!
Tony: The section is perfectly ok, don't change anything ;)

> best regards
>=20
> PS: Would you like to take responsibility for managing ispman-developer=
s=20
> mailing list?

Well, I'm honored Atif, but my time for ispman is limited to my spare
time right now (and my wife isn't too happy with that ;)
I would prefer to give this job to someone else here.
If you like you may "add" me to the admin list, though, so I can help
out if needed.

Cheers, J=F6rg

Joerg Delker wrote:

Hi Joerg, your @delker.de address is getting rejected. you are 
subscribed with a different address?

> Since you are refering explicitly to version 1.1 you should use the
> "rel_1_1-bugfix" branch to only catch the bugfixes and not the untested
> development changes.
> So better add an "-r rel_1_1-bugfixes" to the last line (This will
> adjust with new releases of course).

This is not necessary since the tar ball is built from the bug fixes 
branch. All CVS directories have the Branch/Tag informations

best regards

PS: Would you like to take responsibility for managing ispman-developers 
mailing list?

best regards

Wil Cooley wrote:
> I would propose embedding the CLI and API docs as POD and automatically
> generating them.

Hi Wil,

I am all for having the POD documentation about the usage.

The documentation I propose is a step by step guide on using the CLI.

Example:

Install ISPMan
Add a reseller
Add a client under the reseller
Add a domain
Set the client and reseller for the domain
List domains
Add a user in the domain
Add a website in the domain
List users/websites for the domain

Manipulate DNS information for the domain
Manipulate site-wide DNS information (very undocumented and powerful 
feature)

etc

best regards

On Sat, 2004-01-31 at 17:39, Atif Ghaffar wrote:

> I would propose to have the CLI documentation as a separate doc.

I would propose embedding the CLI and API docs as POD and automatically
generating them.

Wil
--=20
Wil Cooley                                 wc...@na...
Naked Ape Consulting                        http://nakedape.cc
* * * * Linux, UNIX, Networking and Security Solutions * * * *
* Naked Ape Consulting                   http://nakedape.cc  *
*                   Secure E-mail Server                     *
* Naked Ape Mail Defender           http://nakedape.cc/r/md  *

Hi Tony,

Thanks for your help in documentation.
It would be nice if you can place the files on the ISPMan website on 
sourceforge so they are available from the same place.

Contact me off list so I can give you information about uploading to the 
website.

The documentation looks great and is easily understandable.

I would propose to have the CLI documentation as a separate doc.

I want to write a guide on how to manage ISPMan completely without using 
any GUI. I will start work on it soon since I need to provide it to a 
client and will then integrate it with other documentations.

Would you prefer to keep working in Open office or would you prefer that 
we setup something like WiKi, so it can be managed on line.

best regards.

Tony Wasson wrote:
> Pheew! It's been almost a month since starting on the ISPMan Handbook, so
> I'm giving an update. I've posted a First Draft of the ISPMan Handbook in
> PDF, HTML and OpenOffice format. It is about 30 pages long.
> 
> http://www.azxws.com/ispman/
> 
> Please let me know if you have suggestions or can expand one of the chapters.
> 
> Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've
> also added a section about Migration, with some general tips. This needs
> to be expanded, since I've only done 2 migrations.
> 
> Tony Wasson
> 
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> Ispman-docs mailing list
> Isp...@li...
> https://lists.sourceforge.net/lists/listinfo/ispman-docs

Both guides by Tony and Jeff recommend for Postfix to deliver to Cyrus:

mailbox_transport=3Dcyrus

I haven't looked at Postfix 2 yet, so maybe it's changed, but on 1.1
that's defined as:

cyrus     unix  -   n   n   -   -   pipe
  flags=3DR user=3Dcyrus argv=3D/usr/cyrus/bin/deliver -e -m ${extension} $=
{user}

Delivering through 'deliver' is ineffecient; for one thing, it entails
invoking another process, but mostly IIRC 'deliver' has to be called
once for each recipient, so you lose the benefits of single instance
store.  What the Cyrus people tend to recommend is using LMTP over UNIX
domain socket:

mailbox_transport =3D lmtp:unix:/var/imap/socket/lmtp

Wil
--=20
Wil Cooley                                 wc...@na...
Naked Ape Consulting                        http://nakedape.cc
* * * * * *  Linux Services for Small Businesses  * * * * * *
* Naked Ape Consulting                  http://nakedape.cc  *
* Naked Ape Business Server       http://nakedape.cc/r/smb  *
*       Easy, reliable solutions for small businesses       *

I've updated my install guide, with important information to anyone 
running Perdition under FreeBSD.

http://www.meden.org/ispman-fbsd.htm

Jeff Meden

Looks good, from what i've read so far.  I will start looking for areas 
to contribute to shortly.  Meanwhile, I made up a simple freebsd 4.9 
install guide, of which I'd like some feedback from the community.  I 
tried to write it in a casual narrative style, so the process is 
comfortable from start to finish.  Its laid out to provide a pretty 
comprehensive tutorial for installation on FreeBSD, it's not limited to 
4.9 but I've yet to test it with anything newer.  I also included a 
number of beginners notes on the layout of ISPman, and some 
troubleshooting advice where possible.  I haven't gone through it 
thoroughly to make sure everything is 100% accurate, but I took all the 
information directly from the test servers ive been working with so 
hopefully its pretty close.  I plan to do some finishing cleanup and 
testing in the future.

It's at
http://www.meden.org/ispman-fbsd.htm

Jeff Meden

Tony Wasson wrote:

>Pheew! It's been almost a month since starting on the ISPMan Handbook, so
>I'm giving an update. I've posted a First Draft of the ISPMan Handbook in
>PDF, HTML and OpenOffice format. It is about 30 pages long.
>
>http://www.azxws.com/ispman/
>
>Please let me know if you have suggestions or can expand one of the chapters.
>
>Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've
>also added a section about Migration, with some general tips. This needs
>to be expanded, since I've only done 2 migrations.
>
>Tony Wasson
>
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>Ispman-docs mailing list
>Isp...@li...
>https://lists.sourceforge.net/lists/listinfo/ispman-docs
>
>  
>

On Wed, 2004-01-28 at 10:06, Tony Wasson wrote:

> Ooops.  I was debating switching ALL the examples to "domain.tld"

'example.com' is the recommended domain; they're reserved by RFC for
documentation.

...

> Interesting! I wanted to include several filter examples because I feel
> like everyone is "re-inventing" the wheel.
>=20
> Thanks for all the suggestions Wil. I will try to get these all done when
> I come back from vacation next week. In the mean time, feel free to hack
> on the documentation wherever you see fit and if you have time. I'd like
> this to be a community document.

Is it in CVS (I guess it doesn't matter)?  Partly I'm concerned because
I'm still only running 0.9.7+CVS in production, so I'm afraid I might
not be entirely current.

Wil
--=20
Wil Cooley                                 wc...@na...
Naked Ape Consulting                        http://nakedape.cc
* * * * * *  Linux Services for Small Businesses  * * * * * *
* Naked Ape Consulting                  http://nakedape.cc  *
* Naked Ape Business Server       http://nakedape.cc/r/smb  *
*       Easy, reliable solutions for small businesses       *

Wil Cooley wrote:

>On Wed, 2004-01-28 at 08:25, Tony Wasson wrote:
>  
>
>>Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've
>>also added a section about Migration, with some general tips. This needs
>>to be expanded, since I've only done 2 migrations.
>>    
>>
>
>One thing I've recently done for migration (the only one I've done so
>far) is to modify the migration tool from PADL to generate the entries I
>wanted.  'uid' seems to work okay as a multi-valued attribute, and to
>avoid the trouble of figuring out all the right filters, I just created
>entries with both 'username' and 'username_example_com'.
>  
>

I did this as well... all our users have 3 uids: username, 
username_example_com, and use...@ex....

This is because the "old" server had the users from all domains using 
the same servername (not mail.theirdomain.com) for POP/IMAP/SMTP with 
the short Unix username.

Once the migration is done, we'll probably send them an email to change 
their settings. After a grace period we can drop the extra UIDs so that 
we can have jd...@do... as a a totally seperate entity from 
jd...@do....

Wim

> On Wed, 2004-01-28 at 08:25, Tony Wasson wrote:
>> Pheew! It's been almost a month since starting on the ISPMan Handbook,
>> so
>> I'm giving an update. I've posted a First Draft of the ISPMan Handbook
>> in
>> PDF, HTML and OpenOffice format. It is about 30 pages long.
>>
>> http://www.azxws.com/ispman/
>>
>> Please let me know if you have suggestions or can expand one of the
>> chapters.
>
> Did you use OOo to generate the HTML and PDF?  Could OOo generate links
> from the TOC to the contents?

Yes, I just did "Export to PDF" and "Save as > HTML". If I knew a little
more about OO I could probably make the links work.

> The images seem to be artificially scaled down, which makes the text on
> them illegible.

OK, I will see what I can do.

> Under "Filesystem Layout", /ispman/domains, there are example user
> directories of
>
> example.com/users/atif_domain_com
>
> example.com/users/arno_domain_com
>
> Which should be
>
> example.com/users/atif_example_com
>
> example.com/users/arno_example_com

Ooops.  I was debating switching ALL the examples to "domain.tld"

> Exactly what "processes" are and why they're necessary does not seem to
> be explained (at least, not in the "Processes" section).

You're right, I need to fill this out more.

> The ldapvirtual stuff works for Postfix 1.1 also, if compiled for it.  I
> also set up Postfix to use an LDAP map for 'relay_domains' (the only big
> difference is the query_filter and result_attribute):
>
> http://nakedape.cc/wiki/index.cgi/IspManPostfixRelay
>
> I think you've got the headings for the "PureFTPd" and "ProFTPd"
> sections backwards.
>
> The first two images in chapter 5 are missing in the on-line version:
> missing "1. Click on Add Domain, filling out these pieces of info:" and
> "2. The next screen looks like this".
>
>> Chapter 1 is wrapping up, and the rest of it beginning to take shape.
>> I've
>> also added a section about Migration, with some general tips. This needs
>> to be expanded, since I've only done 2 migrations.
>
> One thing I've recently done for migration (the only one I've done so
> far) is to modify the migration tool from PADL to generate the entries I
> wanted.  'uid' seems to work okay as a multi-valued attribute, and to
> avoid the trouble of figuring out all the right filters, I just created
> entries with both 'username' and 'username_example_com'.

Interesting! I wanted to include several filter examples because I feel
like everyone is "re-inventing" the wheel.

Thanks for all the suggestions Wil. I will try to get these all done when
I come back from vacation next week. In the mean time, feel free to hack
on the documentation wherever you see fit and if you have time. I'd like
this to be a community document.

Tony Wasson

On Wed, 2004-01-28 at 08:25, Tony Wasson wrote:
> Pheew! It's been almost a month since starting on the ISPMan Handbook, so
> I'm giving an update. I've posted a First Draft of the ISPMan Handbook in
> PDF, HTML and OpenOffice format. It is about 30 pages long.
>=20
> http://www.azxws.com/ispman/
>=20
> Please let me know if you have suggestions or can expand one of the chapt=
ers.

Did you use OOo to generate the HTML and PDF?  Could OOo generate links
from the TOC to the contents?

The images seem to be artificially scaled down, which makes the text on
them illegible.

Under "Filesystem Layout", /ispman/domains, there are example user
directories of

example.com/users/atif_domain_com

example.com/users/arno_domain_com

Which should be

example.com/users/atif_example_com

example.com/users/arno_example_com

Exactly what "processes" are and why they're necessary does not seem to
be explained (at least, not in the "Processes" section).

The ldapvirtual stuff works for Postfix 1.1 also, if compiled for it.  I
also set up Postfix to use an LDAP map for 'relay_domains' (the only big
difference is the query_filter and result_attribute):

http://nakedape.cc/wiki/index.cgi/IspManPostfixRelay

I think you've got the headings for the "PureFTPd" and "ProFTPd"
sections backwards.

The first two images in chapter 5 are missing in the on-line version:
missing "1. Click on Add Domain, filling out these pieces of info:" and
"2. The next screen looks like this".

> Chapter 1 is wrapping up, and the rest of it beginning to take shape. I'v=
e
> also added a section about Migration, with some general tips. This needs
> to be expanded, since I've only done 2 migrations.

One thing I've recently done for migration (the only one I've done so
far) is to modify the migration tool from PADL to generate the entries I
wanted.  'uid' seems to work okay as a multi-valued attribute, and to
avoid the trouble of figuring out all the right filters, I just created
entries with both 'username' and 'username_example_com'.

Wil
--=20
Wil Cooley                                 wc...@na...
Naked Ape Consulting                        http://nakedape.cc
* * * * * * * Good, fast and cheap: Pick all 3! * * * * * * *
* Naked Ape Consulting             http://nakedape.cc/r/sg  *
*      SnapGear Linux Firewall/VPN Appliances Reseller      *

On Wed, 2004-01-28 at 17:25, Tony Wasson wrote:
> Pheew! It's been almost a month since starting on the ISPMan Handbook, so
> I'm giving an update. I've posted a First Draft of the ISPMan Handbook in
> PDF, HTML and OpenOffice format. It is about 30 pages long.
> 
> http://www.azxws.com/ispman/
> 
> Please let me know if you have suggestions or can expand one of the chapters.

Hi Tony,

when roughly flying over the manual I noticed the following:

--------------------------------------
3. Go into the unpacked ispman-1.1 direcory and do a cvs update. This
applies the latest bug fixes and patches.

cd ispman-1.1
apt-get install cvs
cvs -z3 update -dP
--------------------------------------
There is a high chance to make your ispman installation unusable by
doing this ;)
Since you are refering explicitly to version 1.1 you should use the
"rel_1_1-bugfix" branch to only catch the bugfixes and not the untested
development changes.
So better add an "-r rel_1_1-bugfixes" to the last line (This will
adjust with new releases of course).

--------------------------------------
4. Configure and make ISPMan.

./configure
make
--------------------------------------
A notice for the "--prefix" option would be nice. Not everyone wants to
install to /opt/ispman.


--------------------------------------
7. For an existing installation, don't initialize LDAP, just copy the
latest schema files over. 

cp /opt/ispman-someversion/tmp/conf/schema/* /etc/ldap/schema/ 
/etc/init.d/slapd restart 
--------------------------------------
That's problably not always sufficient. Please advice on use of
"scripts/ldifupdate" to upgrade/check the LDAP DIT.


Best regards, Joerg

Pheew! It's been almost a month since starting on the ISPMan Handbook, so
I'm giving an update. I've posted a First Draft of the ISPMan Handbook in
PDF, HTML and OpenOffice format. It is about 30 pages long.

http://www.azxws.com/ispman/

Please let me know if you have suggestions or can expand one of the chapters.

Chapter 1 is wrapping up, and the rest of it beginning to take shape. I've
also added a section about Migration, with some general tips. This needs
to be expanded, since I've only done 2 migrations.

Tony Wasson

> I looked over the notes for the documentation.  How much information are
> you looking at in the 'system specific notes' section?  I noticed it
> wasnt in a particular place on the current layout.  Is it targeted at
> the new user?  Is it a complete install guide for the specific system?
> Or just deviance from the normal (i assume debian or similar) install?
> I have a bit of experience with bsd and a few linuxes, and would like to
> help contribute.
>
> Jeff
>

Hi Jeff,

It would be great if you can contribute! I'm thinking we should aim the
ISPMan Handbook at Systems Admins installing and running ISPMan. It should
cover how to get it installed as well as how it works. I expect the reader
to already know how to get around in UN*X. The biggest knowledge gap when
people start installing ISPMan is using LDAP, so we've got a chapter about
that.

As far as "system specific documentation" I'm thinking we should mention
packages for SuSE, Redhat, Debian, FreeBSD (are there any other commonly
used server OS's?) and mention any special notes for the distribution such
as the directory locations and an variances from the steps. I've included
an example, please let me know how it can be better.

One burning question to me is how many distrbutions do we try to cover,
especially concerning RedHat. Do we try to cover RHEL, Fedora, and RH9?

I'm also thinking that we'll end up breaking out the setup instructions by
major version, such as Postfix 1.1, Postfix 2 and Apache 1.3 and Apache 2.
Once other question is how detailed do we get inside the basic steps?
Should we give them just enough to get started and then toss any "extras"
in additional boxes, such as SMTP Auth, TLS, LMTP delivery?

Let's use Postfix 1.1 as example install:
----------------------------------------
These installation steps will help you setup Postfix. If you want to
enable extra functions like TLS and SMTP Authentication, see the
additional notes at the end of the installation.

1) Install Postfix, either from source or your distribution's packages.

Debian
INSTALL: # apt-get install postfix-ldap postfix-tls libsasl-modules-plain
NOTES: The stable slapd does not support SSL LDAP. Use stunnel or a
backported slapd from apt-get.org if you need LDAPS. Setup LMTP
permissions like so:
        # dpkg-statoverride --force --update --add \
          cyrus lmtp 750 /var/run/cyrus/socket

FreeBSD
INSTALL: pkg_add -r postfix1.1
NOTES: none

RedHat
INSTALL:  Download packages from
http://postfix.wl0.org/en/available-packages/
# rpm -i postfix-1.1.13-3.rh9.i386.rpm
NOTES: Make sure your RPM support LDAP.

SuSE
INSTALL: ??
NOTES: ??


2) Configure main.cf like the example in
build/install-data/examples/postfix_configuration/main.cf.reasonable with
these exceptions:

mailbox_transport=cyrus
# NOTE: myorigin MUST match the maildrop hostname in ISPMan.
myorigin = /etc/mailname

#These options gave me trouble, I am not a guru so I commented them out.
#relocated_maps = hash:/etc/postfix/relocated
#smtpd_sender_restrictions = hash:/etc/postfix/access


3) Test it using telnet.
  $telnet localhost 25

You should see something like:

Connected to 10.98.76.54
Escape character is '^]'.
220 test.somewhere.com ESMTP Postfix


If postfix drops the connection, read syslog. Most installation problems
are with improper 'chrooting' or file permissions. If you are using SMTP
auth settings, try commenting that out and restarting Also ensure that
your pam files are correct and that smtpd is NOT in a chroot environment.

If postfix won't deliver mail, verify that you have an LDAP enabled
postfix and that postfix has access to your LDAP directory.

***These would be extra boxes at the end ***
Additional Information:
-----------
LMTP delivery

LMTP delivery allows for much faster mail delivery over the cyrdeliver
command. LMTP requires Cyrus 2.1+ as a backend. It does not work with
Cyrus 1.5 or Courier.

 # addgroup lmtp
 # adduser postfix lmtp

 Make sure the socket directory permissions are acceptable
 #cyrus lmtp 750 /var/run/cyrus/socket

 Restart Postfix and Cyrus and test....
---------------
---------------
SMTP Authentication

It is quites easy to get SMTP Authentication supporting PLAIN and LOGIN
running. You can enable additional authentication mechnisms if you setup
ISPMan to store passwords in cleartext. This example sets up SMTP
Authentication using PAM_LDAP and Cyrus SASL. You will need to setup those
applications first.

1) Setup the pam rules for SMTP Authentication. Most distributions name
this smtpd. /etc/pam.d/smtpd should contain:

  auth    sufficient      pam_ldap.so
  account sufficient      pam_ldap.so

2) Setup the postfix to sasl bridge. Your directories may vary.
#mkdir /etc/postfix/sasl

Then create /etc/postfix/sasl/smtpd.conf like so:
  pwcheck_method: pam

3) Configure master.cf
Make sure smtpd is NOT chrooted -- This lets it do SMTP Auth.

WARNING: SMTP Authentication is an addon to postfix, it does decrease the
overall security. You have been warned. It is possible to run this
chrooted.


4) Configure main.cf with something like this:

# SMTP Auth Stuff see http://killyridols.net/postfixtlssmtpauth.shtml
smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = $myhostname
smtpd_recipient_restrictions = permit_sasl_authenticated,
check_relay_domains


---------------
---------------
TLS Setup

1) Create TLS cert and key in /etc/postfix
   #openssl req -new -x509 -nodes -out cert.pem
   #chown root.postfix *.pem
   #chmod 640 *.pem

2) Add this to main.cf, customize with your directories.

#For STARTTLS SMTP
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_key_file = /etc/postfix/privkey.pem
smtpd_use_tls = yes
tls_random_source = dev:/dev/urandom
tls_daemon_random_source = dev:/dev/urand
---------------

I looked over the notes for the documentation.  How much information are 
you looking at in the 'system specific notes' section?  I noticed it 
wasnt in a particular place on the current layout.  Is it targeted at 
the new user?  Is it a complete install guide for the specific system?  
Or just deviance from the normal (i assume debian or similar) install?  
I have a bit of experience with bsd and a few linuxes, and would like to 
help contribute.

Jeff

Hi Tony,

OO format is fine.

Tony Wasson wrote:
> I played with DocBook for a few hours and doing some output with jade.
> Then I simply started writing in OpenOffice. I should be finishing the
> first chapter by then end of the week. I will post it as an example.
> Here's what information is needed to round out the first release:
> 
>    A clue about the ISPMan RADIUS setup (how do I make a profile? Is there
> anything else I need to know?)
I havent a clue myself about this. Armand coded this part. He is busy at 
the moment so I will try to take a shot at it.


>    and install notes for:
>    *BSD
>    *Courier
>    *djbdns/tinydns
>    *Apache 2.0
Will users using these softwares, please comment so we can add them in 
the book.

cheeers

> Hi Tony,
>
> how are we going with the handbook?
>
> Have you decided on the formats, structure etc?
> I would like to get on with this asap so we have some documentation.
>
> We are soon reaching a 1.1 release. (1.0+bugfixes+missingFeatures)
>
> best regards

I played with DocBook for a few hours and doing some output with jade.
Then I simply started writing in OpenOffice. I should be finishing the
first chapter by then end of the week. I will post it as an example.

I am totally open to doing a DocBook (or any other format), but I'd need
some more pointers.

Here's what information is needed to round out the first release:

   A clue about the ISPMan RADIUS setup (how do I make a profile? Is there
anything else I need to know?)

   and install notes for:
   *BSD
   *Courier
   *djbdns/tinydns
   *Apache 2.0

Tony

Hi Tony,

how are we going with the handbook?

Have you decided on the formats, structure etc?
I would like to get on with this asap so we have some documentation.

We are soon reaching a 1.1 release. (1.0+bugfixes+missingFeatures)

best regards
Tony Wasson wrote:
> Please review this rough outline for an ISPMan 1.0 Handbook. If you can
> help update and write this information, please let me know.
> ------
> Chapter 1: Overview of ISPMan
>         Letter from Atif Ghaffar
> 	Components & Architecture
> 	Network Examples:
> 		Single Server
> 		Typical Installation
> 		Large Setup
> 	Filesystem Layout
> 	Processes
> 		ispman-agent
> 
> Chapter 2:Installing ISPMan
> 	Quickstart
> 	Requirements
> 	Web Setup
> 	Getting help
> 
> Chapter 3: Configuring external apps for ISPMan
> 	Bind 8
> 	Bind 9
> 	Bind 9-SDB
> 	TinyDNS/djbdns
> 	Postfix 1
> 	Postfix 2
> 	Cyrus 2.1
> 	Courier
> 	Apache 1.3
> 	Apache 2
> 	PureFTPd
> 	ProFTPd
> 	RADIUS
> 
> Chapter 4: What you need to know about LDAP
> 	Gentle Introduction to LDAP
> 	Limiting Access
> 	Replication
> 	Filter Examples
> 
> Chapter 5: Day to Day Domain Management
> 	Domains
> 	Users (domain, web, dialup, wireless)
> 	Email Management
> 	Uploading websites
> 	Website Options/ACLs
> 
> Chapter 6: Appendix
> 	A. Glossary
> 	B. Command Line Tools (update & convert from pod)
> 	C. FAQ
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Ispman-docs mailing list
> Isp...@li...
> https://lists.sourceforge.net/lists/listinfo/ispman-docs