diff options
Diffstat (limited to 'admin/www/mailman-install.txt')
| -rw-r--r-- | admin/www/mailman-install.txt | 49 |
1 files changed, 32 insertions, 17 deletions
diff --git a/admin/www/mailman-install.txt b/admin/www/mailman-install.txt index c7b2dca1..9071639a 100644 --- a/admin/www/mailman-install.txt +++ b/admin/www/mailman-install.txt @@ -1,4 +1,3 @@ - #GNU Mailman - Installation Manual About this document... About this document... @@ -12,7 +11,7 @@ GNU Mailman - Installation Manual barry(at)python.org Release 2.1 - April 16, 2005 + May 12, 2005 Front Matter @@ -53,7 +52,7 @@ GNU Mailman - Installation Manual Mailman requires a unique user and group name which will own its files, and under which its processes will run. Mailman's basic security is based on group ownership permissions, so it's important to - get this step right1. Typically, you will add a new user and a new + get this step right^1. Typically, you will add a new user and a new group, both called mailman. The mailman user must be a member of the mailman group. Mailman will be installed under the mailman user and group, with the set-group-id (setgid) bit enabled. @@ -79,7 +78,7 @@ GNU Mailman - Installation Manual the variable data files and install them in separate directories. This section will describe the available options. - The default is to install all of Mailman to /usr/local/mailman2. You + The default is to install all of Mailman to /usr/local/mailman^2. You can change this base installation directory (referred to here as $prefix) by specifying the directory with the --prefix configure option. If you're upgrading from a previous version of Mailman, you @@ -93,7 +92,7 @@ GNU Mailman - Installation Manual Make sure the installation directory is set to group mailman (or whatever you're going to specify with --with-groupname) and has the - setgid bit set3. You probably also want to guarantee that this + setgid bit set^3. You probably also want to guarantee that this directory is readable and executable by everyone. For example, these shell commands will accomplish this: @@ -241,6 +240,22 @@ GNU Mailman - Installation Manual * Run bin/check_perms -f * Repeat previous step until no more errors are reported! + Warning: If you're running Mailman on a shared multiuser system, and + you have mailing lists with private archives, you may want to hide the + private archive directory from other users on your system. In that + case, you should drop the other execute permission (o-x) from the + archives/private directory. However, the web server process must be + able to follow the symbolic link in public directory, otherwise your + public Pipermail archives will not work. To set this up, become root + and run the following commands: + +# cd <prefix>/archives +# chown <web-server-user> private +# chmod o-x private + + You need to know what user your web server runs as. It may be www, + apache, httpd or nobody, depending on your server's configuration. + 5 Set up your web server Congratulations! You've installed the Mailman software. To get @@ -827,8 +842,8 @@ GNU Mailman - Installation Manual server. 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.py (the default). Sendmail.py has known - security holes and is provided as a proof-of-concept only4. If you are - having problems using SMTPDirect.py fix those instead of using + security holes and is provided as a proof-of-concept only^4. If you + are having problems using SMTPDirect.py fix those instead of using Sendmail.py, or you may open your system up to security exploits. 6.3.1 Sendmail ``smrsh'' compatibility @@ -1056,7 +1071,7 @@ fi Mailman has a large number of site-wide configuration options which you should now review and change according to your needs. Some of the options control how Mailman interacts with your environment, and other - options select defaults for newly created lists5. There are system + options select defaults for newly created lists^5. There are system tuning parameters and integration options. The full set of site-wide defaults lives in the @@ -1254,7 +1269,7 @@ fi Also check for errors in your syslog files, your mail and web server log files and in Mailman's $prefix/logs/error file. If you're still having problems, you should send a message to the - mailman-users@python.org mailing list7; see + mailman-users@python.org mailing list^7; see http://mail.python.org/mailman/listinfo/mailman-users for more information. @@ -1490,7 +1505,7 @@ tar xvf MailmanStartup.tar About this document ... - GNU Mailman - Installation Manual, April 16, 2005, Release 2.1 + GNU Mailman - Installation Manual, May 12, 2005, Release 2.1 This document was generated using the LaTeX2HTML translator. @@ -1506,24 +1521,24 @@ tar xvf MailmanStartup.tar Footnotes - ... right1 + ... right^1 You will be able to check and repair your permissions after installation is complete. - .../usr/local/mailman2 + .../usr/local/mailman^2 This is the default for Mailman 2.1. Earlier versions of Mailman installed everything under /home/mailman by default. - ... set3 + ... set^3 BSD users should see the 15.2 section for additional information. - ... only4 + ... only^4 In fact, in later versions of Mailman, this module is explicitly sabotaged. You have to know what you're doing in order to re-enable it. - ... lists5 + ... lists^5 In general, changing the list defaults described in this section will not affect any already created lists. To make changes after a list has been created, use the web interface or @@ -1537,7 +1552,7 @@ tar xvf MailmanStartup.tar Changing the crontab could mess with other parallel Mailman installations. - ... list7 + ... list^7 You must subscribe to this mailing list in order to post to it, but the mailing list's archives are publicly visible. _________________________________________________________________ @@ -1545,4 +1560,4 @@ tar xvf MailmanStartup.tar Previous Page Up One Level Next Page GNU Mailman - Installation Manual _________________________________________________________________ - Release 2.1, documentation updated on April 16, 2005. + Release 2.1, documentation updated on May 12, 2005. |