small improvements of INSTALL

release archives

ezmlm-web/tags/ezmlm-web-2.2/INSTALL

@@ -1,32 +1,40 @@
-1.   Copy ezmlm-web.cgi to some publically readable directory. It does not
+The following notes will guide you through the installation of ezmlm-web:
+
+0.   IMPORTANT: you need the perl module Mail::Ezmlm and others to use 
+     ezmlm-web! The file README contains the list of necessary modules.
+
+1.   Get ezmlm-web and extract the archive:
+	tar xzf ezmlm-web-2.2.tar.gz
+
+2.   Copy ezmlm-web.cgi to some publically readable directory. It does not
      have to be in a path accessible to your web server, but any user with a
      mailing list must be able to run it (Check the read and execute rights
-     on both the file and directory). We put our copy in
+     on both the file and directory). We put our copy in "/usr/local/bin".
-     /usr/local/bin ...
 
-3.   Edit the ezmlmwebrc file and alter the variables at the top to suit
+     At the top of ezmlm-web.gi you can will probably have to change the 
-     your particular system. In particular, you will probably have to change
+     $ENV{'PATH'} variable. Be careful about what you set as the path. Too 
-     the $ENV{'PATH'} variable. Be particularly careful about what you set
+     much is a security risk and too little will cause the script to 
-     as the path. Too much is a security risk and too little will cause the
+     malfunction. Version 2.0 requires that the following programs be 
-     script to malfunction. Version 2.0 requires that the following programs
+     accessible in your path: mv, rm
-     be accessible in your path; mv, rm
 
-     Also be careful about the $LIST_DIR variable. This script assumes that
+3.   Edit the ezmlmwebrc file and alter the variables to suit your
-     all users store their mailing lists in the same sub directory of the
+     particular system.
-     home directory (eg ~/lists). You can override this for an individual
+     
-     user by recompiling the C wrapper to call ezmlm-web.cgi with a -d
+     Be careful about the $LIST_DIR variable. This script assumes that all 
-     option.
+     users store their mailing lists in the same sub directory of the home 
+     directory (eg ~/lists). You can override this for an individual user 
+     by recompiling the C wrapper to call ezmlm-web.cgi with a -d option.
 
      Other configurable options are documented in the ezmlmwebrc file
      itself. I have tried to keep the amount of information that you need to
      supply to a minimum and also make reasonable guesses about default
      values.
 
-     finally, copy the ezmlmwebrc file and the "lang" directory to one of
+     Finally, copy the ezmlmwebrc file and the "lang" directory to one of
      the following places:
-      - /etc/ezmlm
+	- /etc/ezmlm
-      - the home directory of the user that runs ezmlm-web.cgi
+	- the home directory of the user that runs ezmlm-web.cgi
-      - the directory, that contains your ezmlm-web.cgi file
+	- the directory, that contains your ezmlm-web.cgi file
 
 4.   Edit the index.c file and change the path to the path of your copy
      of ezmlm-web.cgi. Then compile this file. You can do this by issuing
@@ -72,10 +80,10 @@
 
      The format of the .htaccess file should be along the lines of this;
 
-       AuthName EZ Mailing List Manager
+	AuthName EZ Mailing List Manager
-       AuthType Basic
+	AuthType Basic
-       AuthUserFile /path/to/passwordfile
+	AuthUserFile /path/to/passwordfile
-       require valid-user      # or require user username
+	require valid-user      # or require user username
 
      Again, see the ApacheWeek article for details.
 

ezmlm-web/trunk/INSTALL

@@ -1,32 +1,40 @@
-1.   Copy ezmlm-web.cgi to some publically readable directory. It does not
+The following notes will guide you through the installation of ezmlm-web:
+
+0.   IMPORTANT: you need the perl module Mail::Ezmlm and others to use 
+     ezmlm-web! The file README contains the list of necessary modules.
+
+1.   Get ezmlm-web and extract the archive:
+	tar xzf ezmlm-web-2.2.tar.gz
+
+2.   Copy ezmlm-web.cgi to some publically readable directory. It does not
      have to be in a path accessible to your web server, but any user with a
      mailing list must be able to run it (Check the read and execute rights
-     on both the file and directory). We put our copy in
+     on both the file and directory). We put our copy in "/usr/local/bin".
-     /usr/local/bin ...
 
-3.   Edit the ezmlmwebrc file and alter the variables at the top to suit
+     At the top of ezmlm-web.gi you can will probably have to change the 
-     your particular system. In particular, you will probably have to change
+     $ENV{'PATH'} variable. Be careful about what you set as the path. Too 
-     the $ENV{'PATH'} variable. Be particularly careful about what you set
+     much is a security risk and too little will cause the script to 
-     as the path. Too much is a security risk and too little will cause the
+     malfunction. Version 2.0 requires that the following programs be 
-     script to malfunction. Version 2.0 requires that the following programs
+     accessible in your path: mv, rm
-     be accessible in your path; mv, rm
 
-     Also be careful about the $LIST_DIR variable. This script assumes that
+3.   Edit the ezmlmwebrc file and alter the variables to suit your
-     all users store their mailing lists in the same sub directory of the
+     particular system.
-     home directory (eg ~/lists). You can override this for an individual
+     
-     user by recompiling the C wrapper to call ezmlm-web.cgi with a -d
+     Be careful about the $LIST_DIR variable. This script assumes that all 
-     option.
+     users store their mailing lists in the same sub directory of the home 
+     directory (eg ~/lists). You can override this for an individual user 
+     by recompiling the C wrapper to call ezmlm-web.cgi with a -d option.
 
      Other configurable options are documented in the ezmlmwebrc file
      itself. I have tried to keep the amount of information that you need to
      supply to a minimum and also make reasonable guesses about default
      values.
 
-     finally, copy the ezmlmwebrc file and the "lang" directory to one of
+     Finally, copy the ezmlmwebrc file and the "lang" directory to one of
      the following places:
-      - /etc/ezmlm
+	- /etc/ezmlm
-      - the home directory of the user that runs ezmlm-web.cgi
+	- the home directory of the user that runs ezmlm-web.cgi
-      - the directory, that contains your ezmlm-web.cgi file
+	- the directory, that contains your ezmlm-web.cgi file
 
 4.   Edit the index.c file and change the path to the path of your copy
      of ezmlm-web.cgi. Then compile this file. You can do this by issuing
@@ -72,10 +80,10 @@
 
      The format of the .htaccess file should be along the lines of this;
 
-       AuthName EZ Mailing List Manager
+	AuthName EZ Mailing List Manager
-       AuthType Basic
+	AuthType Basic
-       AuthUserFile /path/to/passwordfile
+	AuthUserFile /path/to/passwordfile
-       require valid-user      # or require user username
+	require valid-user      # or require user username
 
      Again, see the ApacheWeek article for details.
 

ezmlm-web/trunk/TODO

@@ -2,9 +2,12 @@ $Id: TODO,v 1.3 2000/09/25 19:58:02 guy Exp $
 
 TODO - ezmlm-web 2.2
 
--  More Documentation
+-  mention in INSTALL, that a missing webusers-file deactivates access control
--  Some nice install method. But then I use FreeBSD and ported it
+-  webusers is not mentioned in INSTALL
-   so that might just count as my nice install method :)
+-  change ./lang/ to /usr/local/share/ezmlm-web/lang
+-  more documentation
+-  some nice install method
 -  Option for a css-stylesheet
  - migrate header and footer in ezmlmwebrc to css
  - improve css-design
+- move unknown.gif to systemausfall.org