summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbwarsaw1998-05-26 16:09:06 +0000
committerbwarsaw1998-05-26 16:09:06 +0000
commit959e7eef87919a490b4fc5609b3a2f7190c14beb (patch)
treed29b0e62284b00878728f96fb8bc778070b54523
parent16350c310e677ae539411d8735c79b74d43cd5ec (diff)
downloadmailman-959e7eef87919a490b4fc5609b3a2f7190c14beb.tar.gz
mailman-959e7eef87919a490b4fc5609b3a2f7190c14beb.tar.zst
mailman-959e7eef87919a490b4fc5609b3a2f7190c14beb.zip
Moved the bulk of the installation instructions to INSTALL. Removed
the RCS $Keyword$ crud.
-rw-r--r--README70
1 files changed, 16 insertions, 54 deletions
diff --git a/README b/README
index a8780bfce..a8736ed0d 100644
--- a/README
+++ b/README
@@ -1,20 +1,18 @@
-Mailman (README $Revision: 539 $, $Date: 1998-05-25 19:14:57 +0100 (Mon, 25 May 1998) $)
-
Mailman - a mailing list management system
Copyright (C) 1998 by the Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
-This is Mailman, maillist management software written mostly in
+This is Mailman, mailing list management system written mostly in
Python. Mailman was originally developed by John Viega. Subsequent
development (through version 1.1) was by Ken Manheimer. Currently,
Mailman development is a group effort, led by John Viega, Ken
-Manheimer and Barry Warsaw.
+Manheimer and Barry Warsaw.
Initial version of Mailman (v. 0.9) written by John Viega Dec 12-15
-1996. Mailman 1.0b3, 2, and 1.1 developments by ken manheimer, 4/98
-and 5/98.
+1996. Mailman 1.0b3, 2, and 1.1 developments by Ken Manheimer, 4/98
+and 5/98. Autoconf support added 5/98 by Barry Warsaw.
-We recommend that you join the mailman user's mailing list. You may
+We recommend that you join the Mailman user's mailing list. You may
do so at the following web address (which also is an example of the
system in action):
@@ -31,66 +29,30 @@ See file DONE for info on changes since v. 0.9
Features:
o Most standard mailing list features, including:
moderation, mail based commands, digests, etc...
- o An extensive web interface customizable on a per-list basis.
+ o An extensive Web interface customizable on a per-list basis.
o Web based list administration interface for *all* admin-type tasks.
- o Automatic web based hypermail-style archives (using pipermail or
+ o Automatic Web based hypermail-style archives (using pipermail or
other external archiver), including provisions for private archives
o Smart bounce detection and correction
o Fast bulk mailing
o Smart spam protection
- o Extendable logging
+ o Extensible logging
o Multiple list owners and moderators
- o Optional MIME-Compliant digests
+ o Optional MIME-compliant digests
o Nice about which machine you subscribed from if you're from the
right domain.
Requirements:
You must be root on a machine running a mail transport program that
- uses an /etc/aliases file, and has a sendmail executable (smail
- should be OK). (We will soon be switching over to use a direct
- SMTP connection to whatever you have running on port 25.)
- The machine really needs to have a web server in order to configure lists.
+ uses an /etc/aliases file, and has a sendmail executable (smail
+ should be OK). We will soon be switching over to use a direct SMTP
+ connection to whatever you have running on port 25. The machine
+ really needs to have a web server in order to configure lists.
Install:
- o Make sure Python is installed as /usr/local/bin/python (currently
- hardcoded -- this obviously needs to change, and should be
- handled by a config program)
- o As root, add a mailman user
- o As mailman, copy the mailman dir to /home/mailman. Currently the
- system requires the source be located there. [I've been running
- with the untarred mailman dir as a subdir of /home/mailman, so eg
- maillist.py, the main mailman list object module, is situated as
- /home/mailman/mailman/modules/maillist.py.]
- o As mailman, in /home/mailman make public_html, cgi-bin, and logs
- directories. Chmod them g+sw.
- o As mailman, in /home/mailman make archives/private and archives/public
- directories. Chmod them g+sw.
- o Copy /home/mailman/mailman/misc/Cookie.py to /home/mailman/cgi-bin
- o As root, Configure your web server to give /home/mailman/cgi-bin
- perms to run cgi in the cgi-bin dir, and restart the web server.
- The line you should add should look something like:
- Exec /mailman/* /home/mailman/cgi-bin/*
- or:
- ScriptAlias /mailman/ /home/mailman/cgi-bin/
-
- (Or whatever is equivalent for your web server)
- o As root, edit /home/mailman/mailman/src/*.c and edit the UID and
- GID const lines as appropriate. (See Troubleshooting, below, for
- hints about determining the proper settings when you're unsure.)
- o As root, cd to /home/mailman/mailman/src and type: make
- o As root, Add mailman as a trusted mail user. This is usually done
- by adding: Tmailman to /etc/sendmail.cf under the line: Troot
- o As root, Restart sendmail.
- o As mailman, cd to /home/mailman/mailman/cron, and add crontab.in
- as your crontab. (probably done w/: crontab crontab.in)
- o Edit mailman/modules/mm_cfg.py - if you don't already have one, make a
- copy from mailman/modules/mm_cfg.py.dist. Include settings in mm_cfg.py
- for any of the defaults in mm_defaults.py that you want to tailor
- for your site.
- o Create the site password, if you don't already have one, using
- 'mailman/bin/mmsitepass password'.
- o Point external archiver at public and private archives (we recommend
- http://starship.skyport.net/crew/amk/maintained/pipermail.html ).
+ Please see the file INSTALL for details on installing Mailman. In
+ the instructions that follow, all file paths are assumed to be
+ relative to the installation directory $prefix.
Adding a new list:
o Run the program bin/newlist