Moved the bulk of installation instructions, along with mail server and

operating system specific notes into a new latex manual.  This process isn't
complete, but I'm tired and want to get this stuff into CVS asap.  This should
provide much better documentation organization for Mailman 2.1.6 and for the
list.org web site.

6 files changed, 0 insertions, 475 deletions

diff --git a/README b/README
index 287a0dfd..b2758703 100644
--- a/README
+++ b/README
@@ -114,60 +114,6 @@ REQUIREMENTS
     fancy plugins.
 
 
-CREATE YOUR FIRST LIST
-
-    These instructions assume that you've installed and configured Mailman
-    according to the instructions in the INSTALL file.  To create and test
-    your first list, try the following:
-
-    - First, initialize the site administrator's password by cd'ing to the
-      install directory (by default /usr/local/mailman) and typing
-
-      % bin/mmsitepass
-      New site password: [yourpassword]
-      Again to confirm password: [yourpassword]
-      Password changed.
-
-    - Visit the url:
-
-        http://my.dom.ain/mailman/create
-
-      Fill out the form as described in the on-screen instructions, and in the
-      "List creator's password" field, type the password you entered above.
-      Type your own email address for the "Initial list owner address", and
-      select "Yes" to notify the list administrator.
-
-    - Hit "Create List"
-
-    - Check your email for a message from Mailman informing you that your new
-      mailing list was created.
-
-    - NOTE: You should consult the README for the specific MTA you are using.
-      Most can be set up to provide through-the-web creation of mailing lists,
-      but each configuration is different.
-
-    - Now visit the list's admin page (either by following the link on the web
-      page or entering the link from the email Mailman just sent you).
-      Typically the url will be something like
-
-        http://my.dom.ain/mailman/admin/mysitelist
-
-      Type in the list's password and click on "Let me in..."
-
-    - Click on "Membership Management" and then on "Mass Subscription".
-
-    - Enter your email address in the big text field, and click on "Submit
-      Your Changes"
-
-    - Now go to your email and send a message to yourlist@my.dom.ain.  Within
-      a minute or two you should see your message reflected back to you via
-      Mailman.
-
-    Congratulations!  You've just set up and tested your first Mailman mailing
-    list.  If you had any problems along the way, please see the section below
-    on FOR MORE INFORMATION.
-
-
 FOR MORE INFORMATION
 
     The online documentation can be found in
diff --git a/README.BSD b/README.BSD
deleted file mode 100644
index f5b6a0eb..00000000
--- a/README.BSD
+++ /dev/null
@@ -1,27 +0,0 @@
-Mailman - The GNU Mailing List Management System
-Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-
-BSD ISSUES
-
-1. Vivek Khera writes that BSD does nightly security scans for setuid
-   file changes.  Setgid directories also come up on the scan when
-   they change.  He says that setgid bit is not necessary on BSD
-   systems because group ownership is automatically inherited on files
-   created in directories.  On other Un*xes, this only happens when
-   the directory has the setgid bit turned on.
-
-   To install without turning on the setgid bit on directories, simply
-   pass in the DIRSETGID variable to make, like so:
-
-     % make DIRSETGID=: install
-
-   This turns off the chmod g+s on each directory as they are
-   installed.
-
-
-
-Local Variables:
-mode: text
-indent-tabs-mode: nil
-End:
diff --git a/README.LINUX b/README.LINUX
deleted file mode 100644
index eb410785..00000000
--- a/README.LINUX
+++ /dev/null
@@ -1,56 +0,0 @@
-Mailman - The GNU Mailing List Management System
-Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-
-
-GNU/LINUX ISSUES
-
-    GNU/Linux seems to be the most popular platform on which to run
-    Mailman.  Here are some hints on getting Mailman to run on Linux:
-
-    If you are getting errors with hard link creations and/or you are using
-    a special secure kernel (securelinux/openwall/grsecurity), see
-    contrib/README.check_perms_grsecurity.
-
-    Note that if you are using Linux Mandrake in secure mode, you are probably
-    concerned by this.
-
-    Apparently Mandrake 9.0 changed the permissions on gcc, so if you
-    build as the mailman user, you need to be sure mailman is in the
-    cctools group.
-
-
-PYTHON PACKAGES
-
-    Note that if you installed Python from your Linux distribution's
-    package manager (e.g. .rpms for Redhat-derived systems or .deb for
-    Debian), you must install the `development' package of Python, or
-    you may not get everything you need.
-
-    For example, using Python 2.2 on Debian, you will need to install
-    the python2.2-dev package.  On Redhat, you probably need the
-    python2-devel package.
-
-    If you install Python from source, you should be fine.
-
-    One symptom of this problem, although for unknown reasons, is that
-    you might get an error such as this during your install:
-
-        Traceback (most recent call last):
-          File "bin/update", line 44, in ?
-            import paths
-        ImportError: No module named paths
-        make: *** [update] Error 1
-
-    If this happens, install the Python development package and try
-    "configure ; make install" again.
-
-    This problem can manifest itself in other Linux distributions in
-    different ways, although usually it appears as ImportErrors.
-
-
-
-Local Variables:
-mode: text
-indent-tabs-mode: nil
-End:
diff --git a/README.MACOSX b/README.MACOSX
deleted file mode 100644
index f1397a7c..00000000
--- a/README.MACOSX
+++ /dev/null
@@ -1,36 +0,0 @@
-Mailman - The GNU Mailing List Management System
-Copyright (C) 2002-2004 by the Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-
-
-MacOSX ISSUES
-
-    Mailman should run on MacOSX, although I have not personally had
-    time to try it yet.  Here are some pointers we've collected on
-    getting Mailman to run on MacOSX.
-
-    - Jaguar (MacOSX 10.2) comes with Python 2.2.  While this isn't
-      the very latest stable version of Python, it ought to be
-      sufficient to run Mailman 2.1.
-
-    - David B. O'Donnell has a web page describing his configuration
-      of Mailman 2.0.13 and Postfix on MacOSX Server.
-
-      http://www.afp548.com/Articles/mail/python-mailman.html
-
-    - Kathleen Webb posted her experiences in getting Mailman running
-      on Jaguar using Sendmail.
-
-      http://mail.python.org/pipermail/mailman-users/2002-October/022944.html
-
-    - Apple has a tech document about a problem you might encounter running
-      Mailman on Mac OS X Server 10.3:
-
-      http://docs.info.apple.com/article.html?artnum=107889
-
-
-
-Local Variables:
-mode: text
-indent-tabs-mode: nil
-End:
diff --git a/README.POSTFIX b/README.POSTFIX
deleted file mode 100644
index d5da5d57..00000000
--- a/README.POSTFIX
+++ /dev/null
@@ -1,222 +0,0 @@
-Mailman - The GNU Mailing List Management System
-Copyright (C) 2001-2004 by the Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-
-
-GENERAL SETUP INFORMATION
-
-    Mailman should work pretty much out of the box with a standard
-    Postfix installation.  As of this writing I've tested it with
-    Postfix 19991231 up to pl13, 200010228 up to pl08, and up to
-    Postfix 2.0.15.
-
-    By default, Postfix treats -owner and -request addresses
-    specially.  Since we want Postfix to deliver such messages to
-    Mailman, you should turn off this option by adding this to your
-    main.cf file:
-
-        owner_request_special = no
-
-    In order to support Mailman's optional VERP delivery, you will
-    want to disable luser_relay (the default) and you will want to set
-    recipient_delimiter for extended address semantics.  You should
-    comment out any luser_relay value in your main.cf and just go with
-    the defaults.  Also, add this to your main.cf file:
-
-        recipient_delimiter = +
-
-    Using + as the delimiter works well with the default values for
-    VERP_FORMAT and VERP_REGEXP in Defaults.py.
-
-    When attempting to deliver a message to a non-existent local address,
-    Postfix may return a 450 error code.  Since this is a transient error
-    code, Mailman will continue to attempt to deliver the message for
-    DELIVERY_RETRY_PERIOD (5 days by default).  You might want to set Postfix
-    up so that it returns permanent error codes for non-existent local users
-    by adding the following to your main.cf file:
-
-        unknown_local_recipient_reject_code = 550
-
-    Finally, if you are using Postfix-style virtual domains, read the
-    section on virtual domain support below.
-
-
-INTEGRATING POSTFIX AND MAILMAN
-
-    You can integrate Postfix and Mailman such that when new lists are
-    created, or lists are removed, Postfix's alias database will be
-    automatically updated.  The following are the steps you need to
-    take to make this work.
-
-    In the description below, we assume that you've installed Mailman
-    in the default location, i.e. /usr/local/mailman.  If that's not
-    the case, adjust the instructions according to your use of
-    configure's --prefix and --with-var-prefix options.
-
-    - If you are using virtual domains and you want Mailman to honor
-      your virtual domains, read the section below first!
-
-    - Add this to the bottom of the $prefix/Mailman/mm_cfg.py file:
-
-      MTA = 'Postfix'
-
-      The MTA variable names a module in Mailman/MTA which contains the
-      MTA-specific functions to be executed when a list is created or
-      removed.
-
-    - Look at the Defaults.py file for the variables POSTFIX_ALIAS_CMD
-      and POSTFIX_MAP_CMD command.  Make sure these point to your
-      postalias and postmap programs respectively.  Remember that if
-      you need to make changes, do it in mm_cfg.py.
-
-    - Run the genaliases script to initialize your aliases file.
-
-      % cd /usr/local/mailman
-      % bin/genaliases
-
-      Make sure that the owner of the data/aliases and data/aliases.db
-      file is `mailman' and that the group owner for those files is
-      `mailman'.  E.g.:
-
-      % su
-      % chown mailman:mailman data/aliases*
-
-    - Hack your Postfix's main.cf file to include the following path
-      in your alias_maps variable:
-
-          /usr/local/mailman/data/aliases
-
-      (no trailing .db).  Do not include this in your alias_database
-      variable.  This is because you do not want Postfix's newaliases
-      command to modify Mailman's aliases.db file, but you do want
-      Postfix to consult aliases.db when looking for local addresses.
-
-      You probably want to use a hash: style database for this entry.
-      Here's an example:
-
-      alias_maps = hash:/etc/postfix/aliases,
-          hash:/usr/local/mailman/data/aliases
-
-    - When you configure Mailman, use the --with-mail-gid=mailman
-      switch (actually, this will be the default if you configured
-      Mailman after adding the `mailman' owner).  Because the owner of
-      the aliases.db file is `mailman', Postfix will execute Mailman's
-      wrapper program as uid and gid mailman.
-
-    That's it!  One caveat: when you add or remove a list, the
-    aliases.db file will updated, but it will not automatically run
-    "postfix reload".  This is because you need to be root to run this
-    and suid-root scripts are not secure.  The only effect of this is
-    that it will take about a minute for Postfix to notice the change
-    to the aliases.db file and update its tables.  I consider this a
-    minor inconvenience.
-
-
-VIRTUAL DOMAINS
-
-    Postfix 2.0 supports "virtual alias domains", essentially what
-    used to be called Postfix-style virtual domains in earlier Postfix
-    versions.  To make virtual alias domains work with Mailman, you
-    need to do some setup in both Postfix and Mailman.  Mailman will
-    write all virtual alias mappings to a file called, by default,
-    /usr/local/mailman/data/virtual-mailman.  It will also use postmap
-    to create the virtual-mailman.db file that Postfix will actually
-    use.
-
-    First, you need to set up the Postfix virtual alias domains as
-    described in the Postfix documentation (see Postfix's virtual(5)
-    manpage).  Note that it's your responsibility to include the
-    "virtual-alias.domain anything" line as described manpage; Mailman
-    will not include this line in virtual-mailman.  I highly encourage
-    you to make sure your virtual alias domains are working properly
-    before integrating with Mailman.
-
-    Next, add a path to Postfix's virtual_alias_maps variable,
-    pointing to the virtual-mailman file, e.g.:
-
-    virtual_alias_maps = <your normal virtual alias files>,
-        hash:/usr/local/mailman/data/virtual-mailman
-
-    assuming you've installed Mailman in the default location.  If
-    you're using an older version of Postfix which doesn't have the
-    virtual_alias_maps variable, use the virtual_maps variable
-    instead.
-
-    Next, in your mm_cfg.py file, you will want to set the variable
-    POSTFIX_STYLE_VIRTUAL_DOMAINS to the list of virtual domains that
-    Mailman should update.  This may not be all of the virtual alias
-    domains that your Postfix installation supports!  The values in
-    this list will be matched against the host_name attribute of
-    mailing lists objects, and must be an exact match.
-
-    Here's an example:
-
-    Let's say I've set up Postfix to handle the virtual domains
-    dom1.ain, dom2.ain, and dom3.ain.  Let's say further that in
-    main.cf you've got the following settings:
-
-        myhostname = mail.dom1.ain
-        mydomain = dom1.ain
-        mydestination = $myhostname, localhost.$mydomain
-        virtual_alias_maps =
-            hash:/some/path/to/virtual-dom1,
-            hash:/some/path/to/virtual-dom2,
-            hash:/some/path/to/virtual-dom2
-
-    Let's say further that in virtual-dom1, you've got the following
-    lines:
-
-        dom1.ain  IGNORE
-        @dom1.ain @mail.dom1.ain
-
-    This tells Postfix to deliver anything addressed to dom1.ain to
-    the same mailbox at mail.dom1.com, its default destination.
-
-    In this case you would not include dom1.ain in
-    POSTFIX_STYLE_VIRTUAL_DOMAINS because otherwise Mailman will write
-    entries for mailing lists in the dom1.ain domain as
-
-        mylist@dom1.ain         mylist
-        mylist-request@dom1.ain mylist-request
-        # and so on...
-
-    The more specific entries trump your more general entries, thus
-    breaking the delivery of any dom1.ain mailing list.
-
-    However, you would include dom2.ain and dom3.ain in mm_cfg.py:
-
-        POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom2.ain', 'dom3.ain']
-
-    Now, any list that Mailman creates in either of those two domains,
-    will have the correct entries written to
-    /usr/local/mailman/data/virtual-mailman
-
-    As above with the data/aliases* files, you want to make sure that
-    both data/virtual-mailman and data/virtual-mailman.db are user and
-    group owned by the `mailman' user/group.  So to get things
-    started, set up your virtual domains, run bin/genaliases, and
-    check the ownerships of the files.  From here on out, you should
-    be good to go.
-
-
-AN ALTERNATIVE APPROACH
-
-    Fil <fil@rezo.net> has an alternative approach based on virtual
-    maps and regular expressions, as described at:
-
-    (French)  http://listes.rezo.net/comment.php
-    (English) http://listes.rezo.net/how.php
-
-    This is a good (and simpler) alternative if you don't mind
-    exposing an additional hostname in the domain part of the
-    addresses people will use to contact your list.  I.e. if people
-    should use mylist@lists.dom.ain instead of mylist@dom.ain.
-
-    I have not extensively tested this approach however.
-
-
-
-Local Variables:
-mode: text
-indent-tabs-mode: nil
-End:
diff --git a/README.SENDMAIL b/README.SENDMAIL
deleted file mode 100644
index 3d9a8138..00000000
--- a/README.SENDMAIL
+++ /dev/null
@@ -1,80 +0,0 @@
-Mailman - The GNU Mailing List Management System
-Copyright (C) 1998-2004 by the Free Software Foundation, Inc.
-59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-
-SECURITY NOTE
-
-    You may be tempted to set the DELIVERY_MODULE configuration
-    variable in mm_cfg.py to `Sendmail' when using the Sendmail MTA.
-    Don't.  The Sendmail.py module is misnamed -- it's really a
-    command line based message handoff scheme as opposed to the SMTP
-    scheme used in SMTPDirect (the default).  Sendmail.py has known
-    security holes and is provided as a proof-of-concept only.  If you
-    are having problems using SMTPDirect.py please fix those instead
-    of using Sendmail.py, or you may open your system up to security
-    exploits.
-
-
-SENDMAIL `smrsh' COMPATIBILITY
-
-    Many newer versions of Sendmail come with a restricted execution
-    utility called "smrsh", which limits the executables that Sendmail
-    will allow to be used as mail filter programs.  You need to
-    explicitly allow Mailman's wrapper program to be used with smrsh
-    or Mailman will not work.  If mail is not getting delivered to
-    Mailman's wrapper program and you're getting an "operating system
-    error" in your mail syslog, this could be your problem.
-
-    One good way of doing this is to:
-
-        - Find out where your Sendmail executes its smrsh wrapper
-
-           % grep smrsh /etc/mail/sendmail.cf
-
-        - Figure out where smrsh expects symlinks for allowable filter
-          programs.  At the very beginning of the following output you will
-          see a full path to some directory, e.g. /var/adm/sm.bin or similar:
-
-          % strings $path_to_smrsh | less
-
-        - cd into /var/adm/sm.bin, or where ever it happens to reside on your
-          system, such as /etc/smrsh, /var/smrsh or /usr/local/smrsh.
-
-          % cd /var/adm/sm.bin
-
-        - create a symbolic link to Mailman's wrapper program
-
-          % ln -s /usr/local/mailman/mail/mailman mailman
-
-
-INTEGRATING SENDMAIL AND MAILMAN
-
-    David Champion has contributed a recipe for more closely
-    integrating Sendmail and Mailman, such that Sendmail will
-    automatically recognize and deliver to new mailing lists as they
-    are created, without having to manually edit alias tables.
-
-    In the contrib directory, you will find four files
-
-    mm-handler.readme - an explanation of how to set everything up
-    mm-handler        - the mail delivery agent (MDA)
-    mailman.mc        - a toy configuration file sample
-    virtusertable     - a sample for RFC 2142 address exceptions
-
-
-PERFORMANCE NOTES
-
-    One of the surest performance killers for Sendmail users is when
-    Sendmail is configured to synchronously verify the recipient's
-    host via DNS.  If it does this for messages posted to it from
-    Mailman, you will get horrible performance.  Since Mailman usually
-    connects via localhost (i.e. 127.0.0.1) to the SMTP port of
-    Sendmail, you should be sure to configure Sendmail /not/ to do DNS
-    verification synchronously for localhost connections.
-
-
-
-Local Variables:
-mode: text
-indent-tabs-mode: nil
-End: