diff options
| author | bwarsaw | 2000-11-08 18:43:39 +0000 |
|---|---|---|
| committer | bwarsaw | 2000-11-08 18:43:39 +0000 |
| commit | 9d0b42eb6e44accec416f1c179a6065f3ac3e0cb (patch) | |
| tree | fb616c0ecaa2390dc4dd92c65ff9ca28d4d0dd26 | |
| parent | 58b8b1f5f4d005a201c66e7dd48e0db3734fd889 (diff) | |
| download | mailman-9d0b42eb6e44accec416f1c179a6065f3ac3e0cb.tar.gz mailman-9d0b42eb6e44accec416f1c179a6065f3ac3e0cb.tar.zst mailman-9d0b42eb6e44accec416f1c179a6065f3ac3e0cb.zip | |
New Mailman 2.0 documentation. Uses ht2html site generator, with the
MMGenerator style. The ht2html tool isn't included here, but it's
available from
http://www.wooz.org/users/barry/software/pyware.html
It's not completely filled in, but it's better than it was!
Note that we're checking in both the templates and the generated html
files, so distros contain the final documentation.
49 files changed, 6851 insertions, 530 deletions
diff --git a/admin/www/MMGenerator.py b/admin/www/MMGenerator.py new file mode 100644 index 000000000..6316d1d81 --- /dev/null +++ b/admin/www/MMGenerator.py @@ -0,0 +1,108 @@ +"""Generator for the Mailman on-line documentation. + +Requires ht2html.py, available from + +http://www.wooz.org/users/barry/software/pyware.html +""" + +import os + +from Skeleton import Skeleton +from Sidebar import Sidebar, BLANKCELL +from Banner import Banner +from HTParser import HTParser +from LinkFixer import LinkFixer + + + +sitelinks = [ + # Row 1 + ('%(rootdir)s/index.html', 'Home'), + ('%(rootdir)s/users.html', 'Users'), + ('http://www.list.org/', 'List.Org'), + # Row 2 + ('%(rootdir)s/install-start.html', 'Installation'), + ('%(rootdir)s/mgrs.html', 'List Managers'), + ('http://www.gnu.org/software/mailman/mailman.html', 'Mailman at GNU'), + # Row 3 + ('%(rootdir)s/faq.html', 'FAQ'), + ('%(rootdir)s/admins.html', 'Site Administrators'), + ('http://www.python.org/', 'Python.Org'), + # Row 4 + ('%(rootdir)s/lists.html', 'Discussion Lists'), + ('%(rootdir)s/devs.html', 'Developers'), + ('http://www.gnu.org/', 'Gnu.Org'), + ] + + + +class MMGenerator(Skeleton, Sidebar, Banner): + def __init__(self, file, rootdir, relthis): + self.__body = None + root, ext = os.path.splitext(file) + html = root + '.html' + p = self.__parser = HTParser(file, 'mailman-cabal@python.org') + f = self.__linkfixer = LinkFixer(html, rootdir, relthis) + p.process_sidebar() + p.sidebar.append(BLANKCELL) + # massage our links + self.__d = {'rootdir': rootdir} + self.__linkfixer.massage(p.sidebar, self.__d) + # tweak + p.sidebar.append(('http://www.python.org/', ''' +<center> + <img border=0 src="%(rootdir)s/images/PythonPoweredSmall.png"></center>''' + % self.__d)) + p.sidebar.append(BLANKCELL) + copyright = self.__parser.get('copyright', '1998,1999,2000') + p.sidebar.append((None, '© ' + copyright)) + p.sidebar.append((None, 'Free Software Foundation, Inc.')) + Sidebar.__init__(self, p.sidebar) + # + # fix up our site links, no relthis because the site links are + # relative to the root of my web pages + # + sitelink_fixer = LinkFixer(f.myurl(), rootdir) + sitelink_fixer.massage(sitelinks, self.__d, aboves=1) + Banner.__init__(self, sitelinks, cols=3) + # kludge! +## for i in range(len(p.sidebar)-1, -1, -1): +## if p.sidebar[i] == 'Email Us': +## p.sidebar[i] = 'Email me' +## break + + def get_corner(self): + rootdir = self.__linkfixer.rootdir() + return ''' +<center> + <a href="%(rootdir)s/index.html"> + <img border=0 src="%(rootdir)s/images/logo-70.jpg"></a></center>''' \ + % self.__d + + def get_corner_bgcolor(self): + return 'black' + + def get_banner(self): + return Banner.get_banner(self) + + def get_title(self): + return self.__parser.get('title') + + def get_sidebar(self): + return Sidebar.get_sidebar(self) + + def get_banner_attributes(self): + return 'CELLSPACING=0 CELLPADDING=0' + + def get_body(self): + if self.__body is None: + self.__body = self.__parser.fp.read() + return self.__body + + def get_lightshade(self): + """Return lightest of 3 color scheme shade.""" + return '#99997c' + + def get_darkshade(self): + """Return darkest of 3 color scheme shade.""" + return '#663300' diff --git a/admin/www/Makefile b/admin/www/Makefile new file mode 100644 index 000000000..4a4e0dbec --- /dev/null +++ b/admin/www/Makefile @@ -0,0 +1,28 @@ +HT2HTML = /home/bwarsaw/projects/ht2html/ht2html.py + +HTSTYLE = MMGenerator +HTALLFLAGS = -f -s $(HTSTYLE) +HTROOT = . +HTFLAGS = $(HTALLFLAGS) -r $(HTROOT) +HTRELDIR = . + +SOURCES = $(shell echo *.ht) +EXTRA_TARGETS = faq.html todo.html +TARGETS = $(filter-out *.html,$(SOURCES:%.ht=%.html)) $(EXTRA_TARGETS) +GENERATED_HTML= $(SOURCES:.ht=.html) + +.SUFFIXES: .ht .html +.ht.html: + $(HT2HTML) $(HTFLAGS) $(HTRELDIR)/$< + +all: $(TARGETS) + +faq.ht: ../../FAQ + ../bin/faq2ht.py $< $@ + +todo.ht: ../../TODO + ../bin/mm2do $< $@ + +clean: + -rm $(GENERATED_HTML) + -rm faq.ht todo.ht diff --git a/admin/www/admins.ht b/admin/www/admins.ht new file mode 100644 index 000000000..31eae4f86 --- /dev/null +++ b/admin/www/admins.ht @@ -0,0 +1,219 @@ +Title: Site Administrator Documentation +Links: links.h doco-links.h + +<h3>Site Administrator Documentation</h3> + +By definition, the site administrator has shell access to the Mailman +installation, and the proper permissions for total control over +Mailman at the site. The site admin can edit the +<code>Mailman/mm_cfg.py</code> configuration file, and can run the +various and sundry command line scripts. + +<h3>Command line scripts</h3> + +This is a brief overview of the current crop of command line scripts +available to the site administrator in the <code>bin</code> directory. +For more details, run the script with the <code>--help</code> option, +which will print out the usage synopsis. <em>You must run these +scripts from the bin directory in the Mailman installation location, +usually <code>/home/mailman</code></em>. + +<dl> +<dt><b>add_members</b> +<dd>Use this script to mass add members to a mailing list. Input + files are plain text, with one address per line. Command line + options allow you to add the addresses as digest or regular + members, select whether various notification emails are sent, and + choose which list to add the members to. + +<dt><b>arch</b> +<dd>Use this to rebuild a list's archive. This script can't be used + to modify a list's raw mbox file, but once you've edited the mbox + file some other way, you can use this script to regenerate the + HTML version of the on-line archive. + +<dt><b>check_db</b> +<dd>Use this script to check the integrity of a list's + <code>config.db</code> and <code>config.db.last</code> database + files. + +<dt><b>check_perms</b> +<dd>Use this script to check, and optionally fix, the permissions of + the various files in a Mailman installation. + +<dt><b>clone_member</b> +<dd>Use this script to <em>clone</em> an address on a particular list + into different address. This is useful when someone is changing + email addresses and wants to keep all their old configuration + options. Eventually members will be able to do their own cloning, + but for now, only the site administrator can do this. Command + line options let you remove the old address, clone addresses in + the list managers addresses, etc. + +<dt><b>config_list</b> +<dd>This is a very powerful script which lets you view and modify a + list's configuration variables from the command line. E.g. you + can dump out all the list options into a plain text file (actually + a valid Python file!), complete with comments explaining each + variable. Or you can apply the configuration from such a file to + a particular list. + + <p>Where this might be useful is if you wanted to change the + <code>web_page_url</code> attribute on every list. You could + create a file containing only the line + +<blockquote> +<pre> +web_page_url = 'http://www.mynewsite.com/mailman-relocated/' +</pre> +</blockquote> + + and then feed this file back to <code>config_list</code> for every + list on your system. <code>config_list</code> only sets the + list variables that it finds in the input file. + +<dt><b>digest_arch</b> +<dd>This script is deprecated. + +<dt><b>dumpdb</b> +<dd>This script dumps the plain text representation for any <code>.db</code> + database file. These files usually contain Python marshaled + dictionaries, and can be found in the <code>qfiles</code> + directory, the <code>lists/<em>listname</em></code> directory, + etc. + +<dt><b>find_member</b> +<dd>Use this script to search all the lists, or some subset of lists, + for an address matching a regular expression. command line + options let you also search the list managers as well. + +<dt><b>list_lists</b> +<dd>List all, or some subset of, the mailing lists in the system. + +<dt><b>list_members</b> +<dd>List the members of a mailing list. Command line options let you + print just the regular or just the digest members, print the + case-preserved addresses of the members, etc. + +<dt><b>mmsitepass</b> +<dd>Use this script to set the site password, which can be used any + where in the system a list or user password can be used. + Essentially, the site password trumps any other password, so + choose wisely! + +<dt><b>move_list</b> +<dd>Use this script when you move Mailman to a new installation location. + +<dt><b>newlist</b> +<dd>Use this script to create new mailing lists. + +<dt><b>remove_members</b> +<dd>Use this list to remove members from a mailing list. + +<dt><b>rmlist</b> +<dd>Use this script to remove a mailing list. By default, a list's + archives are not removed unless the <code>--archives</code> option + is given. + +<dt><b>sync_members</b> +<dd>Use this to synchronize mailing lists in a list's database with a + plain text file of addresses, similar to what is used for + <code>add_members</code>. In a sense, this script combines the + functionality of <code>add_members</code> and + <code>remove_members</code>. Any addresses in the file that are + not present in the list roster are added, and any addresses in the + roster that are not present in the file are removed. + + <p>Command line options let you send various notification emails, + preview the changes, etc. + +<dt><b>update</b> +<dd>Don't use this script manually; it is used as part of the + installation and upgrade procedures. + +<dt><b>version</b> +<dd>Prints the Mailman version number. + +<dt><b>withlist</b> +<dd>This is the most powerful and flexible script in Mailman. With it + you can do all manner of programmatic changes to mailing lists, or + look at and interactively inspect almost any aspect of Mailman. + By default, you run this using Python's interactive prompt, like + so: + +<blockquote> +<pre> +% cd /home/mailman +% python -i bin/withlist mylist +Loading list: mylist (unlocked) +>>> +</pre> +</blockquote> + + Here you see that you're left at the Python prompt after the list + has been loaded and instantiated. Note that without the + <code>--lock</code> option, the list is not locked. List must be + locked if you plan to make modifications to any attributes (and + they must be explicitly saved, as <code>withlist</code> does not + automatically save changes to list objects). + + <p>At the prompt, the global object <em>m</em> is the instantiated + list object. It's a Python instance so you can do all the normal + things to it, view or change attributes, or make method calls on + it. + + <p>Have a look also at the <code>--run</code> option, which lets + you put your programmatic changes into a Python module (file) and + run that module over any mailing list you want. This makes + <code>withlist</code> essentially a framework for easily adding + your own list-specific command line scripts. +</dl> + +<h3>Cron scripts</h3> + +Mailman comes with a number of scripts that are typically only run by +cron. However, it is generally okay for the site administrator to run +these scripts manually, say to force a sending of accumulated digests, +or to mail out member passwords, etc. You generally run these by +invoking the Python executable on them, like so: + +<blockquote> +<pre> +% cd /home/mailman +% python -S cron/senddigests +</pre> +</blockquote> + +The <code>-S</code> option is an optimization and (minor) security +recommendation; it inhibits Python's implicit <code>import site</code> +on initialization. Not all of these scripts support the +<code>--help</code> option. Here is a brief description of what the +cron scripts do: + +<dl> +<dt><b>bumpdigests</b> +<dd><em>Bumps</em> the digest volume numbers for the specified lists. + Resets the issue number to 1. + +<dt><b>checkdbs</b> +<dd>Checks for ending list requests (posts and subscriptions) and + mails the list manager if there are any. + +<dt><b>gate_news</b> +<dd>Polls the NNTP servers for messages and forwards any new messages + to their mailing list gateways. + +<dt><b>mailpasswds</b> +<dd>Sends the password reminder emails to all users and all mailing lists. + +<dt><b>nightly_gzip</b> +<dd>Regenerates the Pipermail <code>gzip</code>'d flat archive files. + +<dt><b>qrunner</b> +<dd>This is the primary cron script for processing messages in + Mailman's queue directory <code>qfiles</code>. + +<dt><b>senddigests</b> +<dd>Sends all accumulated digests. + +</dl> diff --git a/admin/www/admins.html b/admin/www/admins.html new file mode 100644 index 000000000..9e77b350b --- /dev/null +++ b/admin/www/admins.html @@ -0,0 +1,388 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:24 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Site Administrator Documentation + +--> + +<HEAD> +<TITLE>Site Administrator Documentation</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<b>Site Administrators</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Documentation +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="users.html">Users</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mgrs.html">List Managers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Site Administrators</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="devs.html">Developers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="otherdocs.html">Other Documentation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Site Administrator Documentation</h3> + +By definition, the site administrator has shell access to the Mailman +installation, and the proper permissions for total control over +Mailman at the site. The site admin can edit the +<code>Mailman/mm_cfg.py</code> configuration file, and can run the +various and sundry command line scripts. + +<h3>Command line scripts</h3> + +This is a brief overview of the current crop of command line scripts +available to the site administrator in the <code>bin</code> directory. +For more details, run the script with the <code>--help</code> option, +which will print out the usage synopsis. <em>You must run these +scripts from the bin directory in the Mailman installation location, +usually <code>/home/mailman</code></em>. + +<dl> +<dt><b>add_members</b> +<dd>Use this script to mass add members to a mailing list. Input + files are plain text, with one address per line. Command line + options allow you to add the addresses as digest or regular + members, select whether various notification emails are sent, and + choose which list to add the members to. + +<dt><b>arch</b> +<dd>Use this to rebuild a list's archive. This script can't be used + to modify a list's raw mbox file, but once you've edited the mbox + file some other way, you can use this script to regenerate the + HTML version of the on-line archive. + +<dt><b>check_db</b> +<dd>Use this script to check the integrity of a list's + <code>config.db</code> and <code>config.db.last</code> database + files. + +<dt><b>check_perms</b> +<dd>Use this script to check, and optionally fix, the permissions of + the various files in a Mailman installation. + +<dt><b>clone_member</b> +<dd>Use this script to <em>clone</em> an address on a particular list + into different address. This is useful when someone is changing + email addresses and wants to keep all their old configuration + options. Eventually members will be able to do their own cloning, + but for now, only the site administrator can do this. Command + line options let you remove the old address, clone addresses in + the list managers addresses, etc. + +<dt><b>config_list</b> +<dd>This is a very powerful script which lets you view and modify a + list's configuration variables from the command line. E.g. you + can dump out all the list options into a plain text file (actually + a valid Python file!), complete with comments explaining each + variable. Or you can apply the configuration from such a file to + a particular list. + + <p>Where this might be useful is if you wanted to change the + <code>web_page_url</code> attribute on every list. You could + create a file containing only the line + +<blockquote> +<pre> +web_page_url = 'http://www.mynewsite.com/mailman-relocated/' +</pre> +</blockquote> + + and then feed this file back to <code>config_list</code> for every + list on your system. <code>config_list</code> only sets the + list variables that it finds in the input file. + +<dt><b>digest_arch</b> +<dd>This script is deprecated. + +<dt><b>dumpdb</b> +<dd>This script dumps the plain text representation for any <code>.db</code> + database file. These files usually contain Python marshaled + dictionaries, and can be found in the <code>qfiles</code> + directory, the <code>lists/<em>listname</em></code> directory, + etc. + +<dt><b>find_member</b> +<dd>Use this script to search all the lists, or some subset of lists, + for an address matching a regular expression. command line + options let you also search the list managers as well. + +<dt><b>list_lists</b> +<dd>List all, or some subset of, the mailing lists in the system. + +<dt><b>list_members</b> +<dd>List the members of a mailing list. Command line options let you + print just the regular or just the digest members, print the + case-preserved addresses of the members, etc. + +<dt><b>mmsitepass</b> +<dd>Use this script to set the site password, which can be used any + where in the system a list or user password can be used. + Essentially, the site password trumps any other password, so + choose wisely! + +<dt><b>move_list</b> +<dd>Use this script when you move Mailman to a new installation location. + +<dt><b>newlist</b> +<dd>Use this script to create new mailing lists. + +<dt><b>remove_members</b> +<dd>Use this list to remove members from a mailing list. + +<dt><b>rmlist</b> +<dd>Use this script to remove a mailing list. By default, a list's + archives are not removed unless the <code>--archives</code> option + is given. + +<dt><b>sync_members</b> +<dd>Use this to synchronize mailing lists in a list's database with a + plain text file of addresses, similar to what is used for + <code>add_members</code>. In a sense, this script combines the + functionality of <code>add_members</code> and + <code>remove_members</code>. Any addresses in the file that are + not present in the list roster are added, and any addresses in the + roster that are not present in the file are removed. + + <p>Command line options let you send various notification emails, + preview the changes, etc. + +<dt><b>update</b> +<dd>Don't use this script manually; it is used as part of the + installation and upgrade procedures. + +<dt><b>version</b> +<dd>Prints the Mailman version number. + +<dt><b>withlist</b> +<dd>This is the most powerful and flexible script in Mailman. With it + you can do all manner of programmatic changes to mailing lists, or + look at and interactively inspect almost any aspect of Mailman. + By default, you run this using Python's interactive prompt, like + so: + +<blockquote> +<pre> +% cd /home/mailman +% python -i bin/withlist mylist +Loading list: mylist (unlocked) +>>> +</pre> +</blockquote> + + Here you see that you're left at the Python prompt after the list + has been loaded and instantiated. Note that without the + <code>--lock</code> option, the list is not locked. List must be + locked if you plan to make modifications to any attributes (and + they must be explicitly saved, as <code>withlist</code> does not + automatically save changes to list objects). + + <p>At the prompt, the global object <em>m</em> is the instantiated + list object. It's a Python instance so you can do all the normal + things to it, view or change attributes, or make method calls on + it. + + <p>Have a look also at the <code>--run</code> option, which lets + you put your programmatic changes into a Python module (file) and + run that module over any mailing list you want. This makes + <code>withlist</code> essentially a framework for easily adding + your own list-specific command line scripts. +</dl> + +<h3>Cron scripts</h3> + +Mailman comes with a number of scripts that are typically only run by +cron. However, it is generally okay for the site administrator to run +these scripts manually, say to force a sending of accumulated digests, +or to mail out member passwords, etc. You generally run these by +invoking the Python executable on them, like so: + +<blockquote> +<pre> +% cd /home/mailman +% python -S cron/senddigests +</pre> +</blockquote> + +The <code>-S</code> option is an optimization and (minor) security +recommendation; it inhibits Python's implicit <code>import site</code> +on initialization. Not all of these scripts support the +<code>--help</code> option. Here is a brief description of what the +cron scripts do: + +<dl> +<dt><b>bumpdigests</b> +<dd><em>Bumps</em> the digest volume numbers for the specified lists. + Resets the issue number to 1. + +<dt><b>checkdbs</b> +<dd>Checks for ending list requests (posts and subscriptions) and + mails the list manager if there are any. + +<dt><b>gate_news</b> +<dd>Polls the NNTP servers for messages and forwards any new messages + to their mailing list gateways. + +<dt><b>mailpasswds</b> +<dd>Sends the password reminder emails to all users and all mailing lists. + +<dt><b>nightly_gzip</b> +<dd>Regenerates the Pipermail <code>gzip</code>'d flat archive files. + +<dt><b>qrunner</b> +<dd>This is the primary cron script for processing messages in + Mailman's queue directory <code>qfiles</code>. + +<dt><b>senddigests</b> +<dd>Sends all accumulated digests. + +</dl> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/bugs.ht b/admin/www/bugs.ht new file mode 100644 index 000000000..270f3f101 --- /dev/null +++ b/admin/www/bugs.ht @@ -0,0 +1,17 @@ +Title: Bugs and Patches +Other-links: + <h3>Exits</h3> + <li><a href="http://sourceforge.net/bugs/?group_id=103">Bug Tracker</a> + <li><a href="http://sourceforge.net/patch/?group_id=103">Patch Manager</a> + <li><a href="http://sourceforge.net/projects/mailman">Mailman Project</a> + +<h3>Bugs and Patches</h3> + +<p>Mailman is being +<a href="http://sourceforge.net/projects/mailman">developed on SourceForge</a>. +Please use the SourceForge +<a href="http://sourceforge.net/bugs/?group_id=103">bug tracker</a> to +report any bugs; I've retired the old Jitterbug database on +python.org. If you have patches you'd like to submit, the best place +to do that is on the SourceForge +<a href="http://sourceforge.net/patch/?group_id=103">patch manager</a>. diff --git a/admin/www/bugs.html b/admin/www/bugs.html new file mode 100644 index 000000000..cbf259806 --- /dev/null +++ b/admin/www/bugs.html @@ -0,0 +1,176 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:24 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Bugs and Patches + +--> + +<HEAD> +<TITLE>Bugs and Patches</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Bugs and Patches</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Exits +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://sourceforge.net/bugs/?group_id=103">Bug Tracker</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://sourceforge.net/patch/?group_id=103">Patch Manager</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://sourceforge.net/projects/mailman">Mailman Project</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Bugs and Patches</h3> + +<p>Mailman is being +<a href="http://sourceforge.net/projects/mailman">developed on SourceForge</a>. +Please use the SourceForge +<a href="http://sourceforge.net/bugs/?group_id=103">bug tracker</a> to +report any bugs; I've retired the old Jitterbug database on +python.org. If you have patches you'd like to submit, the best place +to do that is on the SourceForge +<a href="http://sourceforge.net/patch/?group_id=103">patch manager</a>. + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/devs.ht b/admin/www/devs.ht new file mode 100644 index 000000000..c0ca3fd96 --- /dev/null +++ b/admin/www/devs.ht @@ -0,0 +1,6 @@ +Title: Developer Documentation +Links: links.h doco-links.h + +<h3>Developer Documentation</h3> + +Coming soon, all the gory details... diff --git a/admin/www/devs.html b/admin/www/devs.html new file mode 100644 index 000000000..0963d1090 --- /dev/null +++ b/admin/www/devs.html @@ -0,0 +1,175 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:25 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Developer Documentation + +--> + +<HEAD> +<TITLE>Developer Documentation</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<b>Developers</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Documentation +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="users.html">Users</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mgrs.html">List Managers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="admins.html">Site Administrators</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Developers</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="otherdocs.html">Other Documentation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Developer Documentation</h3> + +Coming soon, all the gory details... + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/doco-links.h b/admin/www/doco-links.h new file mode 100644 index 000000000..0a13d5149 --- /dev/null +++ b/admin/www/doco-links.h @@ -0,0 +1,7 @@ +<!-- -*- html -*- --> +<h3>Documentation</h3> +<li><a href="users.html">Users</a> +<li><a href="mgrs.html">List Managers</a> +<li><a href="admins.html">Site Administrators</a> +<li><a href="devs.html">Developers</a> +<li><a href="otherdocs.html">Other Documentation</a> diff --git a/admin/www/download.ht b/admin/www/download.ht new file mode 100644 index 000000000..ab2931869 --- /dev/null +++ b/admin/www/download.ht @@ -0,0 +1,72 @@ +Title: Downloading Mailman +Other-links: + <h3>SMTP servers</h3> + <li><a href="http://www.postfix.org/">Postfix</a> + <li><a href="http://www.exim.org/">Exim</a> + <li><a href="http://www.qmail.org/">Qmail</a> + <li><a href="http://www.sendmail.org/">Sendmail</a> + <h3>Other software</h3> + <li><a href="http://www.apache.org/">Apache web server</a> + <li><a href="http://www.gnu.org/software/gcc/">GNU C compiler</a> + <h3>Mailman downloads</h3> + <li><a href="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a> + <li><a href="http://www.list.org/mailman.tar.gz">From List.Org</a> + <li><a href="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</a> + +<h3>Requirements</h3> + +<p>Mailman currently runs only on Unix-y systems, such as Linux, +Solaris, *BSD, etc. It does not run on Windows or MacOS (but does +work on MacOSX). + +<p> +Before you can run Mailman, you need to make sure that +<a href="http://www.python.org/">Python</a> is installed. Mailman +requires at least Python 1.5.2 and is known to work with Python 1.6 +and Python 2.0. Most Linux systems come with Python pre-installed, so +you just need to make sure you're running an up-to-date version. You +can do this by executing the following at your shell's command line: + +<pre> +% python +Python 2.0 (#128, Oct 18 2000, 04:48:44) +[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 +Type "copyright", "credits" or "license" for more information. +>>> ^D +</pre> + +<p>You will also need an SMTP server (a.k.a. mail transport agent or +<em>MTA</em>) for mail delivery and reception. +<a href="http://www.sendmail.org/">Sendmail</a> is the oldest and most +widely-used MTA, and comes pre-installed on most Unix systems, however it +is not the recommended MTA to use with Mailman. It works, but you may +get better results from one of the newer MTAs. Good results are +reported on the <a href="lists.html">Mailman mailing lists</a> from +people using <a href="http://www.postfix.org/">Postfix</a>, +<a href="http://www.exim.org/">Exim</a>, and +<a href="http://www.qmail.org/">Qmail</a>. Most Mailman development +is done with Postfix. + +<p>You will need a web server. +<a href="http://www.apache.org/">Apache</a> is certainly the most +popular, is available for all Unix systems, and works great with +Mailman. + +<p>To install Mailman from the sources, you will also need an ANSI C +compiler. The +<a href="http://www.gnu.org/software/gcc/">GNU C compiler</a> +gcc 2.8.1 or later is known to work well. + +<h3>Downloading</h3> + +<p>Version +(<!-VERSION--->2.0rc1<!-VERSION--->, +released on +<!-DATE--->Oct 23 2000<!-DATE--->) +is the current GNU release. It is available from the following mirror sites: + +<ul> + <li><a href="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a> + <li><a href="http://www.list.org/mailman.tar.gz">From List.Org</a> + <li><a href="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</a> +</ul> diff --git a/admin/www/download.html b/admin/www/download.html new file mode 100644 index 000000000..a0d5798b0 --- /dev/null +++ b/admin/www/download.html @@ -0,0 +1,249 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:25 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Downloading Mailman + +--> + +<HEAD> +<TITLE>Downloading Mailman</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Requirements, Download</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +SMTP servers +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.postfix.org/">Postfix</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.exim.org/">Exim</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.qmail.org/">Qmail</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.sendmail.org/">Sendmail</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Other software +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.apache.org/">Apache web server</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.gnu.org/software/gcc/">GNU C compiler</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Mailman downloads +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="ftp://ftp.gnu.org/gnu/mailman/">From GNU</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.list.org/mailman.tar.gz">From List.Org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Requirements</h3> + +<p>Mailman currently runs only on Unix-y systems, such as Linux, +Solaris, *BSD, etc. It does not run on Windows or MacOS (but does +work on MacOSX). + +<p> +Before you can run Mailman, you need to make sure that +<a href="http://www.python.org/">Python</a> is installed. Mailman +requires at least Python 1.5.2 and is known to work with Python 1.6 +and Python 2.0. Most Linux systems come with Python pre-installed, so +you just need to make sure you're running an up-to-date version. You +can do this by executing the following at your shell's command line: + +<pre> +% python +Python 2.0 (#128, Oct 18 2000, 04:48:44) +[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 +Type "copyright", "credits" or "license" for more information. +>>> ^D +</pre> + +<p>You will also need an SMTP server (a.k.a. mail transport agent or +<em>MTA</em>) for mail delivery and reception. +<a href="http://www.sendmail.org/">Sendmail</a> is the oldest and most +widely-used MTA, and comes pre-installed on most Unix systems, however it +is not the recommended MTA to use with Mailman. It works, but you may +get better results from one of the newer MTAs. Good results are +reported on the <a href="lists.html">Mailman mailing lists</a> from +people using <a href="http://www.postfix.org/">Postfix</a>, +<a href="http://www.exim.org/">Exim</a>, and +<a href="http://www.qmail.org/">Qmail</a>. Most Mailman development +is done with Postfix. + +<p>You will need a web server. +<a href="http://www.apache.org/">Apache</a> is certainly the most +popular, is available for all Unix systems, and works great with +Mailman. + +<p>To install Mailman from the sources, you will also need an ANSI C +compiler. The +<a href="http://www.gnu.org/software/gcc/">GNU C compiler</a> +gcc 2.8.1 or later is known to work well. + +<h3>Downloading</h3> + +<p>Version +(<!-VERSION--->2.0rc1<!-VERSION--->, +released on +<!-DATE--->Oct 23 2000<!-DATE--->) +is the current GNU release. It is available from the following mirror sites: + +<ul> + <li><a href="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a> + <li><a href="http://www.list.org/mailman.tar.gz">From List.Org</a> + <li><a href="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</a> +</ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/faq.ht b/admin/www/faq.ht new file mode 100644 index 000000000..058b20f10 --- /dev/null +++ b/admin/www/faq.ht @@ -0,0 +1,170 @@ +Title: Mailman Frequently Asked Questions + + <h3>Mailman Frequently Asked Questions</h3> + +<b> Q. How do you spell this program? + +</b><br> A. You spell it "Mailman", with a leading capital "M" and a lowercase + second "m". It is incorrect to spell it "MailMan" (i.e. you should + not use StudlyCaps). +<p> <b> Q. What if I get "document contains no data" from the web server, or + mail isn't getting delivered, or I see "Premature end of script + headers" or "Mailman CGI error!!!" + +</b><br> A. The most likely cause of this is that the GID that is compiled into + the C wrappers does not match the GID that your Web server invokes + CGI scripts with. Note that a similar error could occur if your + mail system invokes filter programs under a GID that does not match + the one compiled into the C mail wrapper. +<p> To fix this you will need to re-configure Mailman using the + --with-cgi-gid and --with-mail-gid options. See the INSTALL file + for details. +<p> These errors are logged to syslog and they do not show up in the + Mailman log files. Problems with the CGI wrapper do get reported + in the Web browser though, and include the expected GID, so that + should help a lot. +<p> You may want to have syslog running and configured to log the + mail.error log class somewhere; on Solaris systems, the line +<p> mail.debug /var/log/syslog +<p> causes the messages to go to them in /var/log/syslog, for example. + (The distributed syslog.conf forwards the message to the loghost, + when present. See the syslog man page for more details.) +<p> If your system is set like this, and you get a failure trying to + visit the mailman/listinfo web page, and it's due to a UID or GID + mismatch, then you should get an entry at the end of + /var/log/syslog identifying the expected and received values. +<p> <b> Q. Why do my web pages hang? + +</b><br> A. CERN Web servers might leave Python processes running, and in some + cases might hang the CGI completely. In that case, switch to + Apache. +<p> It is also possible that you have stale locks. Mailman tries to + be very careful about the lock files it creates to ensure the + integrity of its databases, but sometimes system faults can + cause stale locks to persist. Look in $prefix/locks for any + stale list locks and remove them (you can determine if they're + stale by getting the pid from the file contents and using ps to + see if those processes are still running or not). +<p> <b> Q. What should I check periodically? + +</b><br> A. Many of the scripts have their standard error logged to + ~mailman/logs/error, and some of the modules write caught errors + there, as well, so you should check there at least occasionally to + look for bugs in the code and problems in your setup. +<p> One thing that is *not* caught by the standard error hook is syntax + errors, but any of these should have been caught in the + installation phase, which byte-compiles all .py files in the + distribution. There may be syntax errors lurking if you hacked the + code, or in the scripts that are not modules. +<p> You can always use the Python module `compile' or `compileall' to + force byte compilation of a file, or just fire up the Python + interpreter and try importing the module. +<p> <b> Q. Why doesn't the archive link work? + +</b><br> A. Have any messages been posted to the list? This is a known buglet; + the archive link doesn't work until at least one message has been + posted. +<p> <b> Q. Okay, the archive link works, but I can't access the public + archives. Why? + +</b><br> A. If you are using Apache, you must make sure that FollowSymLinks is + enabled for the path to the public archives. Note that the actual + archives always reside in the private tree, and only when archives + are public, is the symlink followed. See this archive message for + more details: +<p> <a href="http://www.python.org/pipermail/mailman-users/1998-November/000173.html">http://www.python.org/pipermail/mailman-users/1998-November/000173.html</a> +<p> <b> Q. Still having problems? Running QMail? + +</b><br> A. Make sure that you are using "preline" before calling "wrapper": +<p> |preline /home/mailman/mail/wrapper post listname +<p> "preline" adds a Unix-style "From " header which the archiver requires. + You can fix the archive mbox files by adding: +<p> From somebody Mon Oct 9 12:27:34 MDT 2000 +<p> before every message and re-running the archive command + "bin/arch listname". The archives should now exist. See README.QMAIL + for more information. +<p> <b> Q. Still having problems? Running on GNU/Linux? + +</b><br> A. See the README.LINUX file. +<p> <b> Q. I want to get rid of some messages in my archive. How do I do + this? + +</b><br> A. David Rocher posts the following recipe: +<p> <li> + remove $prefix/archives/private/<em>listname</em> +<li> + edit $prefix/archives/private/<em>listname</em>.mbox/<em>listname</em>.mbox [optional] +<li> + run $prefix/bin/arch <em>listname</em> +<p> <b> Q. I set member_posting_only to yes because I want to limit posts to + members only, however it seems like all messages coming from + members are held for approval. Why? + +</b><br> A. There appears to be a problem on some systems where the envelope + sender (e.g. the Unix "From " line) is set incorrectly. This will + cause a negative match when checking to see if the sender is a + member of the list. Until 1.0b12, Mailman defaulted to using the + envelope sender before the sender (i.e. "From:" header) because the + former is set by the SMTP agent while the latter is easily + spoofable by the end user. +<p> [ The possible causes for envelope sender munging taking place are + many, but the "owner-alias" sendmail feature probably deserves + special mention: +<p> If mail arrives for list "foo", and there is an alias entry for + "owner-foo" as well, the envelope sender of the message will be + changed to the single-level expansion of the "owner-foo" alias. +<p> Code has been included in post-1.0rc2 Mailman releases to try + working around the problem this (unconfigurable) sendmail feature + constitutes. Prior to this, some people worked around the + problem by not including the suggested "owner-LISTNAME" alias + entries for Mailman lists in their alias files. ] +<p> However, if you are having this problem, you may opt to favor the + From: header over the envelope sender. Do this by adding the + following line to your mm_cfg.py file: +<p> USE_ENVELOPE_SENDER=0 +<p> if you want (arguably) more security, add this to your mm_cfg.py + file: +<p> USE_ENVELOPE_SENDER=1 +<p> However, read the comments about this variable in the Defaults.py + file for a full discussion of the issues. By default, Mailman 2.0 + relies on the From: header for doing address matching. +<p> <b> Q. How secure are the authentication mechanisms used in Mailman's web + interface? + +</b><br> A. If your Mailman installation run on an SSL-enabled web server + (i.e. you access the Mailman web pages with "https://..." URLs), + you should be as safe as SSL itself is. +<p> However, most Mailman installation run under standard, + encryption-unaware servers. There's nothing wrong with that for + most applications, but a sufficiently determined cracker *could* + get unauthorized access by: +<p> <li> + Packet sniffing: The password used to do the initial + authentication for any non-public Mailman page is sent as clear + text over the net. If you consider this to be a big problem, you + really should use an SSL-enabled server. +<p> <li> + Stealing a valid cookie: After successful password + authentication, Mailman sends a "cookie" back to the user's + browser. This cookie will be used for "automatic" authentication + when browsing further within the list's protected pages. Mailman + employs "session cookies" which are set until you quit your + browser or explicitly log out. +<p> Gaining access to the user's cookie (e.g. by being able to read + the user's browser cookie database, or by means of packet + sniffing, or maybe even by some broken browser offering all it's + cookies to any and all sites the user accesses), and at the same + time being able to fulfill the other criteria for using the + cookie could result in unauthorized access. +<p> Note that this problem is more easily exploited when users browse + the web via proxies -- in that case, the cookie would be valid + for any connections made through that proxy, and not just for + connections made from the particular machine the user happens to + be accessing the proxy from. +<p> <li> + Getting access to the user's terminal: This is really just + another kind of cookie stealing. The short cookie expiration + time is supposed to help defeat this problem. It can be + considered the price to pay for the convenience of not having to + type the password in every time. +<p>
\ No newline at end of file diff --git a/admin/www/faq.html b/admin/www/faq.html index 2acbd694b..83d423a22 100644 --- a/admin/www/faq.html +++ b/admin/www/faq.html @@ -1,277 +1,320 @@ -<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> -<html> - <head> - <title>Mailman FAQ</title> - </head> +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:33 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Mailman Frequently Asked Questions - <body bgcolor="f6f6f6"> - <table cols=1 border=0 celspacing=4 cellpadding=5> - <tr> - <td width=100% bgcolor="#99cff"> - <center><font size=+2><strong>The Mailman Frequently Asked - Questions</strong></font></center> - </td> - </tr> - <tr> - <td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 1. How do you spell this program?</strong></font> - </td></tr> - <tr><td> - You spell it <strong>Mailman</strong>, with a leading capital - <em>M</em> and a lowercase second <em>m</em>. It is - <strong>incorrect</strong> to spell it "MailMan" (i.e. you - should not use StudlyCaps). - </tr> - <tr> - <td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 2. If from the web you get "document contains no data", or<br> - if mail isn't getting delivered, or<br> - if you see "Premature end of script headers", or<br> - if you see "Mailman CGI error!!!"<br> - </strong></font> - </td></tr> - <tr><td> - The most likely cause of this is that the GID that is compiled - into the C wrappers does not match the GID that your Web server - invokes CGI scripts with. Note that a similar error could occur - if your mail system invokes filter programs under a GID that - does not match the one compiled into the C mail wrapper. +--> - <p>To fix this you will need to re-configure Mailman using the - <tt>--with-cgi-gid</tt> and <tt>--with-mail-gid</tt> options. - See <tt>INSTALL</tt> for details. +<HEAD> +<TITLE>Mailman Frequently Asked Questions</TITLE> - These errors are logged to syslog and they do not show up in the - Mailman log files. Problems with the CGI wrapper do get - reported in the Web browser though, and include the expected - GID, so that should help a lot. +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> - You may want to have syslog running and configured to log the - mail.error log class somewhere; on Solaris systems, the line +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<b>FAQ</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> - <blockquote><pre> - mail.debug /var/log/syslog - </pre></blockquote> +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Frequently Asked Questions</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> - causes the messages to go to them in <tt>/var/log/syslog</tt>, for - example. (The distributed syslog.conf forwards the message to - the loghost, when present. See the syslog man page for more - details.) +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> + <h3>Mailman Frequently Asked Questions</h3> - If your system is set like this, and you get a failure trying to - visit the mailman/listinfo web page, and it's due to a UID or - GID mismatch, then you should get an entry at the end of - <tt>/var/log/syslog</tt> identifying the expected and received values. - </td></tr> +<b> Q. How do you spell this program? - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 3. If the web pages hang... - </strong></font> - </td></tr> - <tr><td>CERN Web servers might leave Python processes running, and in - some cases might hang the CGI completely. In that case, switch - to Apache. - </td></tr> +</b><br> A. You spell it "Mailman", with a leading capital "M" and a lowercase + second "m". It is incorrect to spell it "MailMan" (i.e. you should + not use StudlyCaps). +<p> <b> Q. What if I get "document contains no data" from the web server, or + mail isn't getting delivered, or I see "Premature end of script + headers" or "Mailman CGI error!!!" - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 4. Check ~mailman/logs/error periodically... - </strong></font> - </td></tr> - <tr><td> - Many of the scripts have their stderr logged to - <tt>~mailman/logs/error</tt>, and some of the modules write caught errors - there, as well, so you should check there at least occasionally - to look for bugs in the code and problems in your setup. +</b><br> A. The most likely cause of this is that the GID that is compiled into + the C wrappers does not match the GID that your Web server invokes + CGI scripts with. Note that a similar error could occur if your + mail system invokes filter programs under a GID that does not match + the one compiled into the C mail wrapper. +<p> To fix this you will need to re-configure Mailman using the + --with-cgi-gid and --with-mail-gid options. See the INSTALL file + for details. +<p> These errors are logged to syslog and they do not show up in the + Mailman log files. Problems with the CGI wrapper do get reported + in the Web browser though, and include the expected GID, so that + should help a lot. +<p> You may want to have syslog running and configured to log the + mail.error log class somewhere; on Solaris systems, the line +<p> mail.debug /var/log/syslog +<p> causes the messages to go to them in /var/log/syslog, for example. + (The distributed syslog.conf forwards the message to the loghost, + when present. See the syslog man page for more details.) +<p> If your system is set like this, and you get a failure trying to + visit the mailman/listinfo web page, and it's due to a UID or GID + mismatch, then you should get an entry at the end of + /var/log/syslog identifying the expected and received values. +<p> <b> Q. Why do my web pages hang? - <p>One thing that is <em>not</em> caught by stderr hook is syntax errors, - but any of these should have been caught in the installation - phase, which byte-compiles all .py files in the distribution. - There may be syntax errors lurking if you hacked the code, or in - the scripts that are not modules. +</b><br> A. CERN Web servers might leave Python processes running, and in some + cases might hang the CGI completely. In that case, switch to + Apache. +<p> It is also possible that you have stale locks. Mailman tries to + be very careful about the lock files it creates to ensure the + integrity of its databases, but sometimes system faults can + cause stale locks to persist. Look in $prefix/locks for any + stale list locks and remove them (you can determine if they're + stale by getting the pid from the file contents and using ps to + see if those processes are still running or not). +<p> <b> Q. What should I check periodically? - <p>You can always use the Python module <tt>compile</tt> or - <tt>compileall</tt> - to force byte compilation of a file, or just fire up the Python - interpreter and try importing the module! - </td></tr> +</b><br> A. Many of the scripts have their standard error logged to + ~mailman/logs/error, and some of the modules write caught errors + there, as well, so you should check there at least occasionally to + look for bugs in the code and problems in your setup. +<p> One thing that is *not* caught by the standard error hook is syntax + errors, but any of these should have been caught in the + installation phase, which byte-compiles all .py files in the + distribution. There may be syntax errors lurking if you hacked the + code, or in the scripts that are not modules. +<p> You can always use the Python module `compile' or `compileall' to + force byte compilation of a file, or just fire up the Python + interpreter and try importing the module. +<p> <b> Q. Why doesn't the archive link work? - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 5. Other debugging aids - </strong></font> - </td></tr> - <tr><td> - If you get exceptions in the log and/or Web pages, and these are - complaining that files could not be opened, you might like to - see which files Mailman is trying to open! +</b><br> A. Have any messages been posted to the list? This is a known buglet; + the archive link doesn't work until at least one message has been + posted. +<p> <b> Q. Okay, the archive link works, but I can't access the public + archives. Why? - <p>In Python 1.5.2, this will be a standard part of the exception - message. In Python 1.5.1 the best you can do is to comment out - the code in <tt>$prefix/scripts/driver</tt> where it is redefining the - built-in <tt>open()</tt> function. This simulates what Python 1.5.2 will - do when it raises an <tt>IOError</tt> exception, however this only works - for <tt>open()</tt>. While this is the most common case, Python 1.5.2 - will handle many other cases where files are unsuccessfully - referenced. - </td></tr> +</b><br> A. If you are using Apache, you must make sure that FollowSymLinks is + enabled for the path to the public archives. Note that the actual + archives always reside in the private tree, and only when archives + are public, is the symlink followed. See this archive message for + more details: +<p> <a href="http://www.python.org/pipermail/mailman-users/1998-November/000173.html">http://www.python.org/pipermail/mailman-users/1998-November/000173.html</a> +<p> <b> Q. Still having problems? Running QMail? - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 6. Why doesn't the archive link work? - </strong></font> - </td></tr> - <tr><td> - Have any messages been posted to the list? This is a known - buglet; the archive link doesn't work until at least one message - has been posted. - </td></tr> +</b><br> A. Make sure that you are using "preline" before calling "wrapper": +<p> |preline /home/mailman/mail/wrapper post listname +<p> "preline" adds a Unix-style "From " header which the archiver requires. + You can fix the archive mbox files by adding: +<p> From somebody Mon Oct 9 12:27:34 MDT 2000 +<p> before every message and re-running the archive command + "bin/arch listname". The archives should now exist. See README.QMAIL + for more information. +<p> <b> Q. Still having problems? Running on GNU/Linux? - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 7. Okay, the archive link works, but I can't access the public - archives. - </strong></font> - </td></tr> - <tr><td> - If you are using Apache, you must make sure that <tt>FollowSymLinks</tt> - is enabled for the path to the public archives. Note that the - actual archives always reside in the private tree, and only when - archives are public, is the symlink followed. See this archive - message for more details: +</b><br> A. See the README.LINUX file. +<p> <b> Q. I want to get rid of some messages in my archive. How do I do + this? - <p><a href="http://www.python.org/pipermail/mailman-users/1998-November/000173.html"> - http://www.python.org/pipermail/mailman-users/1998-November/000173.html - </a></td></tr> +</b><br> A. David Rocher posts the following recipe: +<p> <li> + remove $prefix/archives/private/<em>listname</em> +<li> + edit $prefix/archives/private/<em>listname</em>.mbox/<em>listname</em>.mbox [optional] +<li> + run $prefix/bin/arch <em>listname</em> +<p> <b> Q. I set member_posting_only to yes because I want to limit posts to + members only, however it seems like all messages coming from + members are held for approval. Why? - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 8. Still having problems? Running on GNU/Linux? - </strong></font> - </td></tr> - <tr><td> - See the file <tt>README.LINUX</tt> in the distribution. - </td></tr> +</b><br> A. There appears to be a problem on some systems where the envelope + sender (e.g. the Unix "From " line) is set incorrectly. This will + cause a negative match when checking to see if the sender is a + member of the list. Until 1.0b12, Mailman defaulted to using the + envelope sender before the sender (i.e. "From:" header) because the + former is set by the SMTP agent while the latter is easily + spoofable by the end user. +<p> [ The possible causes for envelope sender munging taking place are + many, but the "owner-alias" sendmail feature probably deserves + special mention: +<p> If mail arrives for list "foo", and there is an alias entry for + "owner-foo" as well, the envelope sender of the message will be + changed to the single-level expansion of the "owner-foo" alias. +<p> Code has been included in post-1.0rc2 Mailman releases to try + working around the problem this (unconfigurable) sendmail feature + constitutes. Prior to this, some people worked around the + problem by not including the suggested "owner-LISTNAME" alias + entries for Mailman lists in their alias files. ] +<p> However, if you are having this problem, you may opt to favor the + From: header over the envelope sender. Do this by adding the + following line to your mm_cfg.py file: +<p> USE_ENVELOPE_SENDER=0 +<p> if you want (arguably) more security, add this to your mm_cfg.py + file: +<p> USE_ENVELOPE_SENDER=1 +<p> However, read the comments about this variable in the Defaults.py + file for a full discussion of the issues. By default, Mailman 2.0 + relies on the From: header for doing address matching. +<p> <b> Q. How secure are the authentication mechanisms used in Mailman's web + interface? - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 9. I want to get rid of some messages in my archive. How do I do - this? - </strong></font> - </td></tr> - <tr><td> - David Rocher posts the following recipe: - - <pre><blockquote> - . remove $prefix/archives/private/<em>listname</em> - . edit $prefix/archives/private/<em>listname</em>.mbox/<em>listname</em>.mbox [optional] - . run $prefix/bin/arch <em>listname</em> - </blockquote></pre> - </td></tr> - - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 10. I set member_posting_only to yes because I want to limit posts to - members only, however it seems like all messages coming from - members are held for approval. - </strong></font> - </td></tr> - <tr><td> - There appears to be a problem on some systems where the envelope - sender (e.g. the Unix "From " line) is set incorrectly. This will - cause a negative match when checking to see if the sender is a - member of the list. Until 1.0b12, Mailman defaulted to using the - envelope sender before the sender (i.e. "From:" header) because the - former is set by the SMTP agent while the latter is easily - spoofable by the end user. - - <p> - <blockquote> - The possible causes for envelope sender munging taking place are - many, but the <em>owner-alias</em> sendmail feature probably deserves - special mention: - - <p>If mail arrives for list <em>foo</em>, and there is an alias entry for - <em>owner-foo</em> as well, the envelope sender of the message will be - changed to the single-level expansion of the <em>owner-foo</em> alias. - - <p>Code has been included in post-1.0rc2 Mailman releases to try - working around the problem this (unconfigurable) sendmail feature - constitutes. Prior to this, some people worked around the - problem by not including the suggested <em>owner-LISTNAME</em> alias - entries for Mailman lists in their alias files. - </blockquote> - - <p> - However, if you are having this problem, you may opt to favor the - From: header over the envelope sender. Do this by adding the - following line to your mm_cfg.py file: - - <p>USE_ENVELOPE_SENDER=0 - - <p>if you want (arguably) more security, add this to your mm_cfg.py - file: - - <p>USE_ENVELOPE_SENDER=1 - - <p>However, read the comments about this variable in the Defaults.py - file for a full discussion of the issues. - </td></tr> - - <tr><td width=100% bgcolor="fff0d0"> - <font size=+1><strong> - 11. How secure are the authentication mechanisms used in Mailman's web - interface? - </strong></font></td></tr> - <tr><td> - If your Mailman installation run on an SSL-enabled web server - (i.e. you access the Mailman web pages with "https://..." URLs), - you should be as safe as SSL itself is. - - <p>However, most Mailman installation run under standard, - encryption-unaware servers. There's nothing wrong with that for - most applications, but a sufficiently determined cracker <b>could</b> - get unauthorized access by: - - <p><ul> - <li><b>Packet sniffing:</b> The password used to do the initial - authentication for any non-public Mailman page is sent as clear - text over the net. If you consider this to be a big problem, you - really should use an SSL-enabled server. - - <p><li><b>Stealing a valid cookie:</b> After successful password - authentication, Mailman sends a cookie back to the user's - browser. This cookie will be used for automatic authentication - when browsing further within the list's protected pages. The - cookie will only work for a limited time, and only on connections - made from the same IP number as the password-authenticating - connection. - - <p>Gaining access to the user's cookie (e.g. by being able to read - the user's browser cookie database, or by means of packet - sniffing, or maybe even by some broken browser offering all it's - cookies to any and all sites the user accesses), and at the same - time being able to fulfill the other criteria for using the - cookie could result in unauthorized access. - - <p> Note that this problem is easier exploitable when users browse - the web via proxies -- in that case, the cookie would be valid - for any connections made through that proxy, and not just for - connections made from the particular machine the user happens to - be accessing the proxy from. - - <li><b>Getting access to the user's terminal:</b> This is really just - another kind of cookie stealing. The short cookie expiry time is - supposed to help defeat this problem. It can be considered the - price to pay for the convenience of not having to type the - password in every time. - </ul> - - </td></tr> - - </table> - </body> -</html> +</b><br> A. If your Mailman installation run on an SSL-enabled web server + (i.e. you access the Mailman web pages with "https://..." URLs), + you should be as safe as SSL itself is. +<p> However, most Mailman installation run under standard, + encryption-unaware servers. There's nothing wrong with that for + most applications, but a sufficiently determined cracker *could* + get unauthorized access by: +<p> <li> + Packet sniffing: The password used to do the initial + authentication for any non-public Mailman page is sent as clear + text over the net. If you consider this to be a big problem, you + really should use an SSL-enabled server. +<p> <li> + Stealing a valid cookie: After successful password + authentication, Mailman sends a "cookie" back to the user's + browser. This cookie will be used for "automatic" authentication + when browsing further within the list's protected pages. Mailman + employs "session cookies" which are set until you quit your + browser or explicitly log out. +<p> Gaining access to the user's cookie (e.g. by being able to read + the user's browser cookie database, or by means of packet + sniffing, or maybe even by some broken browser offering all it's + cookies to any and all sites the user accesses), and at the same + time being able to fulfill the other criteria for using the + cookie could result in unauthorized access. +<p> Note that this problem is more easily exploited when users browse + the web via proxies -- in that case, the cookie would be valid + for any connections made through that proxy, and not just for + connections made from the particular machine the user happens to + be accessing the proxy from. +<p> <li> + Getting access to the user's terminal: This is really just + another kind of cookie stealing. The short cookie expiration + time is supposed to help defeat this problem. It can be + considered the price to pay for the convenience of not having to + type the password in every time. +<p> +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/features.ht b/admin/www/features.ht new file mode 100644 index 000000000..6496d4c67 --- /dev/null +++ b/admin/www/features.ht @@ -0,0 +1,52 @@ +Title: Mailman Features +Other-links: + <h3>Exits</h3> + <li><a href="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</a> + +<h3>Mailman Features</h3> + +<ul> +<li>Web based list administration for nearly all tasks, including list + configuration, moderation (post approvals), management of user + accounts. + +<li>Web based subscribing and unsubscribing, and user configuration + management. Users can temporarily disable their accounts, select + digest modes, hide their email addresses from other members, etc. + +<li>A customizable <em>home page</em> for each mailing list. + +<li>Per-list privacy features, such as closed-subscriptions, private + archives, private membership rosters, etc. + +<li>Configurable (per-list and per-user) delivery mode + <ul><li>Regular (immediate) delivery + <li>MIME digest + <li>Plain (RFC 934) digests + </ul> + +<li>Integrated bounce detection within an extensible framework. + Automatic disposition of bouncing addresses (disable, + unsubscribe). + +<li>Integrated spam filters. + +<li>Automatic web-based Hypermail-style archiving, with hooks for + external archivers such as + <a href="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</a>. + +<li>Integrated Usenet gatewaying. + +<li>Integrated auto-replies. + +<li>Majordomo-style email based commands. + +<li>Multiple list owners and moderators are possible. + +<li>Support for virtual domains. + +<li>Runs on most Un*x-like systems, compatible with most web + servers and browsers, and most SMTP servers. Requires Python + 1.5.2 or newer (works with Python 1.6 and 2.0). + +<li>An extensible mail delivery pipeline. diff --git a/admin/www/features.html b/admin/www/features.html index d8be8ea26..250d6f857 100644 --- a/admin/www/features.html +++ b/admin/www/features.html @@ -1,90 +1,207 @@ -<!-- Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:25 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Mailman Features -This program is free software; you can redistribute it and/or -modify it under the terms of the GNU General Public License -as published by the Free Software Foundation; either version 2 -of the License, or (at your option) any later version. +--> -This program is distributed in the hope that it will be useful, -but WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -GNU General Public License for more details. +<HEAD> +<TITLE>Mailman Features</TITLE> -You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software -Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. ---> +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> -<html> -<head> -<title>Mailman Feature list</title> -</head> -<BODY bgcolor="F6F6F6"> -<table cols=1 border=0 cellspacing=4 cellpadding=5> -<tr> -<td width=100% bgcolor="#99cff"> +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Features</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Exits +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> <center> -<font size=+2><strong>Mailman Features</strong></font> -</center> -</td> -</tr> -<tr> -<td width=100% bgcolor="FFF0D0"> -<font size=+1><strong>Brief Overview</strong></font> -</td> -</tr> -<tr> -<td> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Mailman Features</h3> + <ul> - <li>Most standard mailing list features, including list moderation, - mail based commands, MIME and RFC 934 (plain) digests, and so on. +<li>Web based list administration for nearly all tasks, including list + configuration, moderation (post approvals), management of user + accounts. - <p><li>An extensive web-based user interface that is customizable on a - per-list basis. This allows users to manage their own - subscriptions, with support for temporarily disabling their - accounts, selecting digest modes, hiding their email addresses - from other members, etc. +<li>Web based subscribing and unsubscribing, and user configuration + management. Users can temporarily disable their accounts, select + digest modes, hide their email addresses from other members, etc. - <p><li>A web-based list administration interface for almost all - admin-type tasks, including list configuration, moderation (post - approvals), selection of posting and subscribing rules, management - of user accounts via the web, etc. +<li>A customizable <em>home page</em> for each mailing list. - <p>Privacy features such as closed-subscriptions, private archives, - private membership rosters, etc. +<li>Per-list privacy features, such as closed-subscriptions, private + archives, private membership rosters, etc. - <p><li>Automatic web-based Hypermail-style archiving, including - provisions for private archives. External archivers such as - <a href="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</a> - can be easily integrated. - - <p><li>Integrated Usenet gatewaying. +<li>Configurable (per-list and per-user) delivery mode + <ul><li>Regular (immediate) delivery + <li>MIME digest + <li>Plain (RFC 934) digests + </ul> + +<li>Integrated bounce detection within an extensible framework. + Automatic disposition of bouncing addresses (disable, + unsubscribe). - <p><li>Smart bounce detection with automatic disposition - (i.e. configurable disabling, unsubscribing). +<li>Integrated spam filters. - <p><li>Integrated spam detection. +<li>Automatic web-based Hypermail-style archiving, with hooks for + external archivers such as + <a href="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</a>. + +<li>Integrated Usenet gatewaying. - <p><li>Integrated auto-replies. +<li>Integrated auto-replies. - <p><li>Multiple list owners and moderators are possible. +<li>Majordomo-style email based commands. + +<li>Multiple list owners and moderators are possible. - <p><li>Support for virtual domains. +<li>Support for virtual domains. - <p><li>Runs on most Un*x-like systems, compatible with most web +<li>Runs on most Un*x-like systems, compatible with most web servers and browsers, and most SMTP servers. Requires Python 1.5.2 or newer (works with Python 1.6 and 2.0). -</ul> -</td> -</tr> -</table> -<hr> -Copyright (C) 1999,2000 Free Software Foundation, Inc., -59 Temple Place - Suite 330, Boston, MA 02111, USA -<P> -Verbatim copying and distribution of this entire article is -permitted in any medium, provided this notice is preserved. -</body> -</head> -</html>
\ No newline at end of file +<li>An extensible mail delivery pipeline. + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/index.ht b/admin/www/index.ht new file mode 100644 index 000000000..a45971716 --- /dev/null +++ b/admin/www/index.ht @@ -0,0 +1,77 @@ +Title: Mailman, the GNU Mailing List Manager +Links: links.h doco-links.h +Other-links: + <h3>Exits</h3> + <li><a href="http://www.python.org/">Python</a> + <li><a href="http://www.gnu.org/">GNU/FSF</a> + <li><a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + <li><a href="http://www.list.org/">List.Org mirror</a> + <li><a href="http://www.wooz.org/barry/">Barry Warsaw</a> + + +<h3>Mailman, the GNU Mailing List Manager</h3> + +Mailman is software to help manage electronic mail discussion lists, +much like Majordomo or Smartmail. Mailman gives each mailing list a +unique web page and allows users to subscribe, unsubscribe, and change +their account options over the web. Even the list manager can +administer his or her list entirely via the web. Mailman has most of +the features that people want in a mailing list management system, +including built-in archiving, mail-to-news gateways, spam filters, +bounce detection, digest delivery, and so on. See the +<a href="features.html">features page</a> for more detail. + +<p>Mailman is free software. It is distributed under the +<a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public +License</a>. The canonical Mailman home page is at +<a href="http://www.gnu.org/software/mailman/mailman.html"> +www.gnu.org/software/mailman/mailman.html</a>, with more information +available at <a href="http://www.list.org/">www.list.org</a>. Mailman +is written in the <a href="http://www.python.org/">Python</a> +programming language, with a little bit of C code for security. + +<p>By the way, the name of this software is spelled <em>Mailman</em> +with a capital leading <em>M</em> and a lowercase second <em>m</em>. +It is incorrect to spell it "MailMan" (i.e. you should not use +StudlyCaps). + +<h3>Acknowledgements</h3> + +<p>Mailman is brought to you by the <em>Mailman Cabal</em>, currently +composed of the following core developers: +<a href="http://www.wooz.org/barry/">Barry Warsaw</a>, Harald +Meland, Ken Manheimer, Scott Cotton, and John Viega. Mailman was +originally written by John Viega. + +<p>The Cabal would like to thank the following other developers for +their important contributions (in no particular order): Juan Carlos +Rey Anaya, Victoriano Giralt, Mads Kiilerich, The Dragon De Monsyne, +Timothy O'Malley, Balazs Nagy, Michael Mclay, Greg Stein, Gergely +Madarasz, Andrew Kuchling, Jeff Hahn, Paul Hebble, Christopher +P. Lindsey, Chris Kolar, J C Lawrence, Jeremy Hylton, Nigel +Metheringham, Dan Mick, Jim Tittsler, Ricardo Kustner, Bernhard +Reiter, Thomas Wouters, Jeff Berliner, Ted Cabeen, Michael Yount, Ron +Jarrell, Chris Snell, David Champion, Darrell Fuhriman, Owen Taylor, +Fil. +<em>We have a extensive wish list and welcome anyone else who would +like to contribute!</em> + +<h3>Papers</h3> + +<p>A number of papers and other material presented at +<a href="http://www.foretec.com/python/workshops/1998-11/proceedings.html"> +the 7th International Python Conference</a> and the 12th Usenix LISA +conference are available <a href="mailman-docs.tar.gz">here</a>. + +<h3>Logos</h3> + +The Dragon De Monsyne created and donated two logos for Mailman which +you can use to link back to the Mailman website. + +<table> +<tr><td><img src="images/logo-sm.jpg"></td> + <td><img src="images/logo-lg.jpg"></td> +</tr><tr><td><center>Small Logo (110x35)</center></td> + <td><center>Large Logo (247x93)</center></td> +</tr> +</table> diff --git a/admin/www/index.html b/admin/www/index.html index 23ba146d0..a900ef3b5 100644 --- a/admin/www/index.html +++ b/admin/www/index.html @@ -1,48 +1,221 @@ <HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:26 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Mailman, the GNU Mailing List Manager + +--> + <HEAD> -<TITLE>The Mailman Mailing List Manager</TITLE> +<TITLE>Mailman, the GNU Mailing List Manager</TITLE> + </HEAD> -<BODY bgcolor="F6F6F6"> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + <center> -<img width=608 height=400 src=images/mailman.jpg> -</center> -<table cols=1 border=0 cellspacing=4 cellpadding=5> -<tr> -<td width=100% bgcolor="#99cff"> -<center><font size=+2><strong>The GNU Mailing List Manager</strong></font></center> -</td> -</tr> -<tr> -<td width=100% bgcolor="FFF0D0"> -<font size=+1><strong> What is Mailman? </strong></font> -</td> -</tr> -<tr> -<td> -Mailman is software to help manage email discussion lists, much like -Majordomo and Smartmail. Unlike most similar products, Mailman gives -each mailing list a web page, and allows users to subscribe, -unsubscribe, etc. over the web. Even the list manager can administer -his or her list entirely from the web. Mailman also integrates most things -people want to do with mailing lists, including archiving, -mail-to-news -gateways, and so on. See the -<a href="features.html">features page</a> -for a brief overview of features. + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<b>Home</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Home</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Documentation +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="users.html">Users</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mgrs.html">List Managers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="admins.html">Site Administrators</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="devs.html">Developers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="otherdocs.html">Other Documentation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Exits +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/">Python</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.gnu.org/">GNU/FSF</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.list.org/">List.Org mirror</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.wooz.org/barry/">Barry Warsaw</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> -<p>Mailman has all of the features you expect from such a product, plus -integrated support for the web (including web based archiving), -automated bounce handling and integrated spam prevention. +<h3>Mailman, the GNU Mailing List Manager</h3> + +Mailman is software to help manage electronic mail discussion lists, +much like Majordomo or Smartmail. Mailman gives each mailing list a +unique web page and allows users to subscribe, unsubscribe, and change +their account options over the web. Even the list manager can +administer his or her list entirely via the web. Mailman has most of +the features that people want in a mailing list management system, +including built-in archiving, mail-to-news gateways, spam filters, +bounce detection, digest delivery, and so on. See the +<a href="features.html">features page</a> for more detail. <p>Mailman is free software. It is distributed under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>. The canonical Mailman home page is at <a href="http://www.gnu.org/software/mailman/mailman.html"> www.gnu.org/software/mailman/mailman.html</a>, with more information -available at <a href="http://www.list.org/">www.list.org</a>. +available at <a href="http://www.list.org/">www.list.org</a>. Mailman +is written in the <a href="http://www.python.org/">Python</a> +programming language, with a little bit of C code for security. + +<p>By the way, the name of this software is spelled <em>Mailman</em> +with a capital leading <em>M</em> and a lowercase second <em>m</em>. +It is incorrect to spell it "MailMan" (i.e. you should not use +StudlyCaps). + +<h3>Acknowledgements</h3> <p>Mailman is brought to you by the <em>Mailman Cabal</em>, currently -composed of the following core developers: Barry Warsaw, Harald +composed of the following core developers: +<a href="http://www.wooz.org/barry/">Barry Warsaw</a>, Harald Meland, Ken Manheimer, Scott Cotton, and John Viega. Mailman was originally written by John Viega. @@ -54,150 +227,32 @@ Madarasz, Andrew Kuchling, Jeff Hahn, Paul Hebble, Christopher P. Lindsey, Chris Kolar, J C Lawrence, Jeremy Hylton, Nigel Metheringham, Dan Mick, Jim Tittsler, Ricardo Kustner, Bernhard Reiter, Thomas Wouters, Jeff Berliner, Ted Cabeen, Michael Yount, Ron -Jarrell, Chris Snell, David Champion, Darrell Fuhriman, Owen Taylor. -<b>We have a extensive wish list and welcome anyone else who would -like to contribute!</b> - -</td> -</tr> -<tr> -<td width=100% bgcolor="FFF0D0"> -<font size=+1><strong>Getting Mailman</strong></font> -</td> -</tr> -<tr> -<td> -Before you can run Mailman, you need to download and install the -<a href="http://www.python.org/">Python -programming language</a>. You need at least Python 1.5.2, but Mailman -also works fine with Python 1.6 and -<a href="http://www.pythonlabs.com/products/python2.0/">Python 2.0</a>. +Jarrell, Chris Snell, David Champion, Darrell Fuhriman, Owen Taylor, +Fil. +<em>We have a extensive wish list and welcome anyone else who would +like to contribute!</em> -<p>Version -(<!-VERSION--->2.0rc1<!-VERSION--->, -released on -<!-DATE--->Oct 23 2000<!-DATE--->) -is the current GNU release. It is available -<A HREF="mailman.tar.gz">here</a>. +<h3>Papers</h3> <p>A number of papers and other material presented at <a href="http://www.foretec.com/python/workshops/1998-11/proceedings.html"> the 7th International Python Conference</a> and the 12th Usenix LISA conference are available <a href="mailman-docs.tar.gz">here</a>. -</td> -</tr> -<tr> -<td width=100% bgcolor="FFF0D0"> -<font size=+1><strong>Support</strong></font> -</td></tr> -<tr> -<td> -<a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made -available <a href="http://www.aurora.edu/~ckolar/mailman/">Mailman -documentation</a>, primarily for list owners who are not necessarily -technical, but who own Mailman mailing lists. - -<p>The <a href="faq.html">Frequently Asked Questions (FAQ)</a> is -available to answer most questions. For issues not covered in the -FAQ, please post your questions to the -<a href="http://www.python.org/mailman/listinfo/mailman-users"> -Mailman-Users</a> -mailing list. You might also want to check out the -<a href="http://www.python.org/pipermail/mailman-users/"> -Mailman Users mailing list archive</a> to see if your problem has -already been addressed. - -<p>Mailman is being developed on -<a href="http://sourceforge.net/projects/mailman">SourceForge</a>. -Please use the SourceForge -<a href="http://sourceforge.net/bugs/?group_id=103">bug tracker</a> to -report any bugs; I've retired the old Jitterbug database on -python.org. If you have patches you'd like to submit, the best place -to do that is on the SourceForge -<a href="http://sourceforge.net/patch/?group_id=103">patch manager</a>. - -<p>Nigel Metheringham has posted a -<a href="http://www.exim.org/howto/mailman.html">HOWTO on using Exim -and Mailman</a> together. If you're using the -<a href="http://www.exim.org">Exim MTA</a> you should check this out. - -</td> -</tr> -<tr> -<td width=100% bgcolor="FFF0D0"> -<font size=+1><strong>Mailing Lists</strong></font> -</td> -</tr> -<tr> -<td> -We have several mailing lists devoted to Mailman, which also provide a -nice demonstration of Mailman! - -<ul> -<li><a href="http://www.python.org/mailman/listinfo/mailman-announce"> - Mailman Announce</a> is a read-only list that you can subscribe to - if you are only interested in release notices and other important - news. Only the core Mailman developers can post messages to this - list. - -<p><li><a href="http://www.python.org/mailman/listinfo/mailman-users"> - Mailman Users</a> is the mailing list to subscribe to if you are - using Mailman at your site, and may have problems or questions - relating to installation, use, etc. We'll try to keep the deep - technical discussions off this list. - -<p><li><a href="http://www.python.org/mailman/listinfo/mailman-developers"> - Mailman Developers</a> is the mailing list to use if you are - interested in helping us develop Mailman, discuss future - directions, etc. This is the list for more in-depth technical - issues. - <p>You may also want to find a project on our Mailman - <a href="todo.html">TODO list</a>. +<h3>Logos</h3> -<p><li><a href="http://www.python.org/mailman/listinfo/mailman-i18n"> - Mailman Internationalization</a> is the list for discussing the - multi-lingual extensions to Mailman, which will likely be folded - into the standard distribution after the 2.0 release. Once - integrated, this list will be a way for language translators to - submit new translation files. +The Dragon De Monsyne created and donated two logos for Mailman which +you can use to link back to the Mailman website. -<p><li><a href="http://www.python.org/mailman/listinfo/mailman-checkins"> - Mailman Checkins</a> is an adjunct list to the publically - accessible read-only CVS repository. This list is for the - hardcore developers, or anybody else submitting patches, since we - really prefer such patches to be generated against the latest - snapshot. This is a read-only list; only the core Mailman - developers can post messages to this list. There is no archive. - -</ul> -</td> +<table> +<tr><td><img src="images/logo-sm.jpg"></td> + <td><img src="images/logo-lg.jpg"></td> +</tr><tr><td><center>Small Logo (110x35)</center></td> + <td><center>Large Logo (247x93)</center></td> </tr> -<tr><td width=100% bgcolor="fff0d0"> -<font size=+1><strong>Mailman in the News</strong></font> -</td></tr> -<tr><td> -Mailman was featured in a -<a href="http://www.sunworld.com/swol-03-1999/swol-03-mailtools.html"> -cover story article</a> in the March 1999 issue -of SunWorld. The article was written by Cameron Laird and Kathryn -Soraiz. - -<p>Mailman was briefly mentioned in -<a href="http://www.zdnet.com/sr/stories/issue/0,4537,387506,00.html"> -a ZDNet article</a> on Linux. This was picked up by -<a href="http://www.msnbc.com/news/244979.asp">MSNBC</a> (I won't -comment on the irony there). -</td></tr> </table> -<hr> -Copyright (C) 1999, 2000 Free Software Foundation, Inc., -59 Temple Place - Suite 330, Boston, MA 02111, USA -<P> -Verbatim copying and distribution of this entire article is -permitted in any medium, provided this notice is preserved. - -</BODY> -</HTML> -> +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-check.ht b/admin/www/install-check.ht new file mode 100644 index 000000000..571c89897 --- /dev/null +++ b/admin/www/install-check.ht @@ -0,0 +1,34 @@ +Title: Check your installation +Links: links.h install-links.h + +<h3>Check your installation</h3> + + To check that your installation has all the correct permissions + and group ownerships, you should run the <code>check_perms</code> + script: + +<blockquote> +<pre> +% cd $prefix +% bin/check_perms +</pre> +</blockquote> + + <p>Don't try to run <code>check_perms</code> from the source + directory; it will only run from the install + (i.e. <code>$prefix</code>) directory. + + <p>If this reports no problems, then it's very likely that your + installation is set up correctly <tt>:)</tt> If it reports + problems, then you can either fix them manually, re-run the + installation, or use <code>check_perms</code> to fix the problems + (probably the easiest solution): + + <ul> + <li>You need to become the user that did the installation (and that + owns all the files in <code>$prefix</code>), or <b>root</b>. + + <li>Run <code>bin/check_perms -f</code> + + <li>Repeat previous step until no more errors are reported! + </ul> diff --git a/admin/www/install-check.html b/admin/www/install-check.html new file mode 100644 index 000000000..83ca71dec --- /dev/null +++ b/admin/www/install-check.html @@ -0,0 +1,215 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:26 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Check your installation + +--> + +<HEAD> +<TITLE>Check your installation</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Check your installation</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Check your installation</h3> + + To check that your installation has all the correct permissions + and group ownerships, you should run the <code>check_perms</code> + script: + +<blockquote> +<pre> +% cd $prefix +% bin/check_perms +</pre> +</blockquote> + + <p>Don't try to run <code>check_perms</code> from the source + directory; it will only run from the install + (i.e. <code>$prefix</code>) directory. + + <p>If this reports no problems, then it's very likely that your + installation is set up correctly <tt>:)</tt> If it reports + problems, then you can either fix them manually, re-run the + installation, or use <code>check_perms</code> to fix the problems + (probably the easiest solution): + + <ul> + <li>You need to become the user that did the installation (and that + owns all the files in <code>$prefix</code>), or <b>root</b>. + + <li>Run <code>bin/check_perms -f</code> + + <li>Repeat previous step until no more errors are reported! + </ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-config.ht b/admin/www/install-config.ht new file mode 100644 index 000000000..c5e4cd5ee --- /dev/null +++ b/admin/www/install-config.ht @@ -0,0 +1,119 @@ +Title: Running configure +Links: links.h install-links.h + +<h3>Running configure</h3> + + <em>TAKE SPECIAL NOTE OF THE <code>--with-mail-gid</code> AND + <code>--with-cgi-gid</code> OPTIONS BELOW. YOU WILL PROBABLY NEED + TO USE THESE!</em> + + <p>You should <b>not be root</b> while performing the + steps in this section. Do them under your own login, or whatever + account you typically install software as. You do not need to do + these steps as user <code>mailman</code>, but you could. + + <p>Make sure that you have write permissions to the target + installation directory, and permission to create a setgid file in + the file system where it resides (NFS and other mounts can be + configured to inhibit setgid settings). + + <p>If you've installed other GNU software, you should be familiar + with the <code>configure</code> script. Usually you can just + cd to the directory you unpacked Mailman into, and run + <code>configure</code> with no arguments: + +<blockquote> +<pre> +% cd mailman-version +% ./configure +% make install +</pre> +</blockquote> + +<h3>Configure options</h3> + + The following options allow you to customize your Mailman + installation. + + <dl> + <dt>--prefix=<em>dir</em> + <dd>Standard GNU configure option which changes the base + directory that Mailman is installed into. By default + <code>$prefix</code> is <code>/home/mailman</code>. This + directory must already exist, and be set up as described in + section 1 above. + + <dt>--exec-prefix=<em>dir</em> + <dd>Standard GNU configure option which lets you specify a + different installation directory for architecture dependent + binaries. + + <dt>--with-var-prefix=<em>dir</em> + <dd>Store mutable data under <em>dir</em> instead of under + <code>$prefix</code> or <code>$exec_prefix</code>. + + <dt>--with-python=<em>/path/to/python</em> + <dd>Specify an alternative Python interpreter to use for the + wrapper programs. The default is to use the interpreter + found first on your shell's <code>$PATH</code>. Note that + when running the scripts from the command line, the first + Python interpreter found on <code>$PATH</code> is always + used. + + <dt>--with-username=<em>username-or-uid</em> + <dd>Specify a different username than <code>mailman</code> to use as a + default. Use this only if the username <code>mailman</code> + is already in use by somebody (e.g. Mark Ailman's login + name). Can take an integer user id. Be sure your + <code>$prefix</code> directory is owned by this user. + + <dt>--with-groupname=<em>groupname-or-gid</em> + <dd>Specify a different groupname than <code>mailman</code> to use as a + default. Use this only if the groupname + <code>mailman</code> is already in use. Can take an integer + group id. Be sure your <code>$prefix</code> directory is + group-owned by this group. + + <dt>--with-mail-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + mail wrapper. <em>group-or-groups</em> can be a list of one + or more integer group ids or symbolic group names. The + first value in the list that resolves to an existing group + is used. By default, the value is the list <code>other, + daemon</code>. + + <p>This is highly system dependent and you must get this + right, because the group id is compiled into the mail + wrapper program for added security. On systems using + sendmail, the <code>sendmail.cf</code> configuration file + designates the group id of sendmail processes using the + <em>DefaultUser</em> option. (If commented out, it still + may be indicating the default...) + + <dt>--with-cgi-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + CGI wrapper. <em>group-or-groups</em> can be a list of one + or more integer group ids or symbolic group names. The + first value in the list that resolves to an existing group + is used. By default, the value is the the list + <code>www, www-data, nobody</code>. + + <p>The proper value for this is dependent on your web server + configuration. You must get this right, because the group + id is compiled into the CGI wrapper program for added + security, and no Mailman CGI scripts will run if this is + incorrect. + + <p>If you're using Apache, check the values for the <em>Group</em> + option in your <code>httpd.conf</code> file. + + <dt>--with-cgi-ext=<em>extension</em> + <dd>Specify an extension for cgi-bin programs. The CGI + wrappers placed in <code>$PREFIX/cgi-bin</code> will have this + extension (some web servers require an extension). + <em>extension</em> must include the dot. + + <dt>--with-gcc=no + <dd>Don't use gcc, even if it is found. cc must be found on + your <code>$PATH</code> + </dl> diff --git a/admin/www/install-config.html b/admin/www/install-config.html new file mode 100644 index 000000000..0d64fe299 --- /dev/null +++ b/admin/www/install-config.html @@ -0,0 +1,300 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:27 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Running configure + +--> + +<HEAD> +<TITLE>Running configure</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Running configure</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Running configure</h3> + + <em>TAKE SPECIAL NOTE OF THE <code>--with-mail-gid</code> AND + <code>--with-cgi-gid</code> OPTIONS BELOW. YOU WILL PROBABLY NEED + TO USE THESE!</em> + + <p>You should <b>not be root</b> while performing the + steps in this section. Do them under your own login, or whatever + account you typically install software as. You do not need to do + these steps as user <code>mailman</code>, but you could. + + <p>Make sure that you have write permissions to the target + installation directory, and permission to create a setgid file in + the file system where it resides (NFS and other mounts can be + configured to inhibit setgid settings). + + <p>If you've installed other GNU software, you should be familiar + with the <code>configure</code> script. Usually you can just + cd to the directory you unpacked Mailman into, and run + <code>configure</code> with no arguments: + +<blockquote> +<pre> +% cd mailman-version +% ./configure +% make install +</pre> +</blockquote> + +<h3>Configure options</h3> + + The following options allow you to customize your Mailman + installation. + + <dl> + <dt>--prefix=<em>dir</em> + <dd>Standard GNU configure option which changes the base + directory that Mailman is installed into. By default + <code>$prefix</code> is <code>/home/mailman</code>. This + directory must already exist, and be set up as described in + section 1 above. + + <dt>--exec-prefix=<em>dir</em> + <dd>Standard GNU configure option which lets you specify a + different installation directory for architecture dependent + binaries. + + <dt>--with-var-prefix=<em>dir</em> + <dd>Store mutable data under <em>dir</em> instead of under + <code>$prefix</code> or <code>$exec_prefix</code>. + + <dt>--with-python=<em>/path/to/python</em> + <dd>Specify an alternative Python interpreter to use for the + wrapper programs. The default is to use the interpreter + found first on your shell's <code>$PATH</code>. Note that + when running the scripts from the command line, the first + Python interpreter found on <code>$PATH</code> is always + used. + + <dt>--with-username=<em>username-or-uid</em> + <dd>Specify a different username than <code>mailman</code> to use as a + default. Use this only if the username <code>mailman</code> + is already in use by somebody (e.g. Mark Ailman's login + name). Can take an integer user id. Be sure your + <code>$prefix</code> directory is owned by this user. + + <dt>--with-groupname=<em>groupname-or-gid</em> + <dd>Specify a different groupname than <code>mailman</code> to use as a + default. Use this only if the groupname + <code>mailman</code> is already in use. Can take an integer + group id. Be sure your <code>$prefix</code> directory is + group-owned by this group. + + <dt>--with-mail-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + mail wrapper. <em>group-or-groups</em> can be a list of one + or more integer group ids or symbolic group names. The + first value in the list that resolves to an existing group + is used. By default, the value is the list <code>other, + daemon</code>. + + <p>This is highly system dependent and you must get this + right, because the group id is compiled into the mail + wrapper program for added security. On systems using + sendmail, the <code>sendmail.cf</code> configuration file + designates the group id of sendmail processes using the + <em>DefaultUser</em> option. (If commented out, it still + may be indicating the default...) + + <dt>--with-cgi-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + CGI wrapper. <em>group-or-groups</em> can be a list of one + or more integer group ids or symbolic group names. The + first value in the list that resolves to an existing group + is used. By default, the value is the the list + <code>www, www-data, nobody</code>. + + <p>The proper value for this is dependent on your web server + configuration. You must get this right, because the group + id is compiled into the CGI wrapper program for added + security, and no Mailman CGI scripts will run if this is + incorrect. + + <p>If you're using Apache, check the values for the <em>Group</em> + option in your <code>httpd.conf</code> file. + + <dt>--with-cgi-ext=<em>extension</em> + <dd>Specify an extension for cgi-bin programs. The CGI + wrappers placed in <code>$PREFIX/cgi-bin</code> will have this + extension (some web servers require an extension). + <em>extension</em> must include the dot. + + <dt>--with-gcc=no + <dd>Don't use gcc, even if it is found. cc must be found on + your <code>$PATH</code> + </dl> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-custom.ht b/admin/www/install-custom.ht new file mode 100644 index 000000000..76feeeed8 --- /dev/null +++ b/admin/www/install-custom.ht @@ -0,0 +1,42 @@ +Title: Customize Mailman +Links: links.h install-links.h + +<h3>Customize Mailman</h3> + + You should do these steps using the account you installed Mailman + under in section 2 above. + + <ul> + <li>The file <code>$prefix/Mailman/Defaults.py</code> contains a number of + defaults for your installation. If any of these are incorrect, + override them in <code>$prefix/Mailman/mm_cfg.py</code>, <b>NOT + IN</b> <code>Defaults.py</code>! See the comments in + <code>Defaults.py</code> for details. Once a list is created, + editing many of these variables will have no effect (you need to + configure your lists through the web admin interface or through + the command line script <code>bin/config_list</code>). + + <p>Specifically check to make sure the variables + <em>DEFAULT_HOST_NAME</em> and <em>DEFAULT_URL</em> are correct. + + <p>The install process will not overwrite an existing + <code>mm_cfg.py</code> file so you can freely make changes to + this file. + + <p><b>Note:</b> Do <b>not</b> change <em>HOME_DIR</em> or + <em>MAILMAN_DIR</em>. These are set automatically by the + configure script. + + <p><li>Create the site password using: + +<blockquote> +<pre> +$prefix/bin/mmsitepass your-site-password +</pre> +</blockquote> + + <p>This password can be used anywhere that individual user or + mailing list administrator passwords are required, giving the + mailman site administrator the ability to adjust these things + when necessary. + </ul> diff --git a/admin/www/install-custom.html b/admin/www/install-custom.html new file mode 100644 index 000000000..4e7fcc532 --- /dev/null +++ b/admin/www/install-custom.html @@ -0,0 +1,223 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:27 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Customize Mailman + +--> + +<HEAD> +<TITLE>Customize Mailman</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Customize Mailman</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Customize Mailman</h3> + + You should do these steps using the account you installed Mailman + under in section 2 above. + + <ul> + <li>The file <code>$prefix/Mailman/Defaults.py</code> contains a number of + defaults for your installation. If any of these are incorrect, + override them in <code>$prefix/Mailman/mm_cfg.py</code>, <b>NOT + IN</b> <code>Defaults.py</code>! See the comments in + <code>Defaults.py</code> for details. Once a list is created, + editing many of these variables will have no effect (you need to + configure your lists through the web admin interface or through + the command line script <code>bin/config_list</code>). + + <p>Specifically check to make sure the variables + <em>DEFAULT_HOST_NAME</em> and <em>DEFAULT_URL</em> are correct. + + <p>The install process will not overwrite an existing + <code>mm_cfg.py</code> file so you can freely make changes to + this file. + + <p><b>Note:</b> Do <b>not</b> change <em>HOME_DIR</em> or + <em>MAILMAN_DIR</em>. These are set automatically by the + configure script. + + <p><li>Create the site password using: + +<blockquote> +<pre> +$prefix/bin/mmsitepass your-site-password +</pre> +</blockquote> + + <p>This password can be used anywhere that individual user or + mailing list administrator passwords are required, giving the + mailman site administrator the ability to adjust these things + when necessary. + </ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-faq.ht b/admin/www/install-faq.ht new file mode 100644 index 000000000..5f69c4f2f --- /dev/null +++ b/admin/www/install-faq.ht @@ -0,0 +1,132 @@ +Title: Common problems FAQ +Links: links.h install-links.h + +<h3>Common Problems FAQ</h3> + + <b>Problem:</b> All Mailman web pages give a <em>404 File not + found</em> error. + + <br><b>Solution:</b> Your web server has not been set up properly + for handling Mailman's cgi commands. Make sure you've: + + <ol><li>Configured the web server to give permissions to + <code>$prefix/cgi-bin</code> + <li>Restarted the web server properly. + </ol> + Consult your web server's documentation for instructions + on how to do these things. + + <p><b>Problem:</b> All Mailman web pages give an <em>Internal + Server Error</em>. + + <br><b>Solution:</b> The likely problem is that you are using the + wrong GID or UID for CGI scripts. Check your syslog. If you + see, for example, a line like: + +<blockquote> +<pre> +Attempt to exec script with invalid gid 51, expected 99 +</pre> +</blockquote> + + You need to reinstall Mailman, and specify + <code>$CGI_GID</code> to be 51, as described in the + installation instructions. + + <p><b>Problem:</b> I send mail to the list, and get back mail saying the + list is not found! + + <br><b>Solution:</b> You probably didn't add the necessary aliases + to the system alias database, given to you when you ran the + <code>newlist</code> command. If you did add them, you likely + did not update the alias database, or your system requires you + to run <code>newaliases</code> explicitly. Refer to section 5 + above for more information. + + + <p><b>Problem:</b> I send mail to the list, and get back mail saying, + <em>unknown mailer error</em>. + + <br><b>Solution:</b> The likely problem is that you are using the + wrong GID or UID for mail. Check your syslog. If you see, for + example, a line like: + +<blockquote> +<pre> +Attempt to exec script with invalid gid 51, expected 99 +</pre> +</blockquote> + + You need to reinstall Mailman, and specify + <code>$MAIL_GID</code> to be 51, as described in the + installation instructions. see notes on Postfix below, as by + default it will create these problems on installation. + + + <p><b>Problem:</b> I use Postfix for my MTA and the mail wrapper programs + are logging complaints about the wrong GID. + + <br><b>Solution:</b> Create a separate aliases file for Postfix in its + <code>main.cf</code> config file under the variable + <em>alias_maps</em>. Put the file somewhere in Mailman's home + directory, or somewhere else where the user + <code>mailman</code> has write access to it; <em>as user + mailman</em> call Postfix's <code>postalias</code> on the + alias file. + +<blockquote> +<pre> +% postalias the-alias-file +</pre> +</blockquote> + + Also as user mailman, run + +<blockquote> +<pre> +% python -c'import os; print os.getgid()' +</pre> +</blockquote> + + <p>This should print out the group id that Mailman should be + configured to expect when the mail wrapper programs are run. + Call it <em>thegid</em>. Rebuild Mailman with + +<blockquote> +<pre> +% ./configure --with-mail-gid=thegid +</pre> +</blockquote> + + <p><b>Problem:</b> I send mail to the list, and get back mail saying, + <em>sh: wrapper not available for sendmail programs</em> + + <br><b>Solution:</b> Your system uses sendmail restricted shell + (smrsh). You need to configure smrsh by creating a symbolic + link from the mail wrapper (<code>$prefix/mail/wrapper</code>) + to the directory identifying executables allowed to run under + smrsh. + + <p>Some common names for this directory are + <code>/var/admin/sm.bin</code>, <code>/usr/admin/sm.bin</code> + or <code>/etc/smrsh</code>. + + <p>Note that on Debian Linux, the system makes + <code>/usr/lib/sm.bin</code>, which is wrong, you will need to + create the directory <code>/usr/admin/sm.bin</code> and add + the link there. Note further that any aliases + <code>newaliases</code> spits out will need to be adjusted to + point to the secure link to the wrapper. + + <p><b>Problem:</b> I messed up when I called configure. How do I clean + things up and re-install? + + <br><b>Solution:</b> + +<blockquote> +<pre> +% make clean +% ./configure --with-the-right-options +% make install +</pre> +</blockquote> diff --git a/admin/www/install-faq.html b/admin/www/install-faq.html new file mode 100644 index 000000000..07be076e6 --- /dev/null +++ b/admin/www/install-faq.html @@ -0,0 +1,313 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:28 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Common problems FAQ + +--> + +<HEAD> +<TITLE>Common problems FAQ</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Common problems FAQ</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Common Problems FAQ</h3> + + <b>Problem:</b> All Mailman web pages give a <em>404 File not + found</em> error. + + <br><b>Solution:</b> Your web server has not been set up properly + for handling Mailman's cgi commands. Make sure you've: + + <ol><li>Configured the web server to give permissions to + <code>$prefix/cgi-bin</code> + <li>Restarted the web server properly. + </ol> + Consult your web server's documentation for instructions + on how to do these things. + + <p><b>Problem:</b> All Mailman web pages give an <em>Internal + Server Error</em>. + + <br><b>Solution:</b> The likely problem is that you are using the + wrong GID or UID for CGI scripts. Check your syslog. If you + see, for example, a line like: + +<blockquote> +<pre> +Attempt to exec script with invalid gid 51, expected 99 +</pre> +</blockquote> + + You need to reinstall Mailman, and specify + <code>$CGI_GID</code> to be 51, as described in the + installation instructions. + + <p><b>Problem:</b> I send mail to the list, and get back mail saying the + list is not found! + + <br><b>Solution:</b> You probably didn't add the necessary aliases + to the system alias database, given to you when you ran the + <code>newlist</code> command. If you did add them, you likely + did not update the alias database, or your system requires you + to run <code>newaliases</code> explicitly. Refer to section 5 + above for more information. + + + <p><b>Problem:</b> I send mail to the list, and get back mail saying, + <em>unknown mailer error</em>. + + <br><b>Solution:</b> The likely problem is that you are using the + wrong GID or UID for mail. Check your syslog. If you see, for + example, a line like: + +<blockquote> +<pre> +Attempt to exec script with invalid gid 51, expected 99 +</pre> +</blockquote> + + You need to reinstall Mailman, and specify + <code>$MAIL_GID</code> to be 51, as described in the + installation instructions. see notes on Postfix below, as by + default it will create these problems on installation. + + + <p><b>Problem:</b> I use Postfix for my MTA and the mail wrapper programs + are logging complaints about the wrong GID. + + <br><b>Solution:</b> Create a separate aliases file for Postfix in its + <code>main.cf</code> config file under the variable + <em>alias_maps</em>. Put the file somewhere in Mailman's home + directory, or somewhere else where the user + <code>mailman</code> has write access to it; <em>as user + mailman</em> call Postfix's <code>postalias</code> on the + alias file. + +<blockquote> +<pre> +% postalias the-alias-file +</pre> +</blockquote> + + Also as user mailman, run + +<blockquote> +<pre> +% python -c'import os; print os.getgid()' +</pre> +</blockquote> + + <p>This should print out the group id that Mailman should be + configured to expect when the mail wrapper programs are run. + Call it <em>thegid</em>. Rebuild Mailman with + +<blockquote> +<pre> +% ./configure --with-mail-gid=thegid +</pre> +</blockquote> + + <p><b>Problem:</b> I send mail to the list, and get back mail saying, + <em>sh: wrapper not available for sendmail programs</em> + + <br><b>Solution:</b> Your system uses sendmail restricted shell + (smrsh). You need to configure smrsh by creating a symbolic + link from the mail wrapper (<code>$prefix/mail/wrapper</code>) + to the directory identifying executables allowed to run under + smrsh. + + <p>Some common names for this directory are + <code>/var/admin/sm.bin</code>, <code>/usr/admin/sm.bin</code> + or <code>/etc/smrsh</code>. + + <p>Note that on Debian Linux, the system makes + <code>/usr/lib/sm.bin</code>, which is wrong, you will need to + create the directory <code>/usr/admin/sm.bin</code> and add + the link there. Note further that any aliases + <code>newaliases</code> spits out will need to be adjusted to + point to the secure link to the wrapper. + + <p><b>Problem:</b> I messed up when I called configure. How do I clean + things up and re-install? + + <br><b>Solution:</b> + +<blockquote> +<pre> +% make clean +% ./configure --with-the-right-options +% make install +</pre> +</blockquote> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-final.ht b/admin/www/install-final.ht new file mode 100644 index 000000000..05fbbf82e --- /dev/null +++ b/admin/www/install-final.ht @@ -0,0 +1,136 @@ +Title: Final system setup +Links: links.h install-links.h + +<h3>Final system set-up</h3> + + Congratulations! You've installed the Mailman software. To get + everything running you need to hook Mailman up to both your web + server and your mail system. + + <ul> + <li>If you plan on running your MTA and web server on different + machines, sharing Mailman installations via NFS, be sure that + the clocks on those two machines are synchronized closely. + You might take a look at the file + <code>Mailman/LockFile.py</code>; the constant + <code>CLOCK_SLOP</code> helps the locking mechanism compensate + for clock skew in this type of environment. + + <p><li>Configure your web server to give <code>$prefix/cgi-bin</code> + permission to run CGI scripts. You probably need to be <b>root</b> + to do this. + + <p>The line you should add might look something like one of + the following (with the real absolute directory substituted + for <code>$prefix</code>, of course), depending on your web + server: + +<blockquote> +<pre> +ScriptAlias /mailman/ $prefix/cgi-bin/ +Exec /mailman/* $prefix/cgi-bin/* +</pre> +</blockquote> + + <p>Consult your web server's documentation for details. + + <p><li><b>IMPORTANT:</b> You want to be very sure that the user id + under which your CGI scripts run is <b>not</b> in the + <code>mailman</code> group you created above, otherwise + private archives will be accessible to anyone. + + <p><li>Copy the Mailman, Python, and GNU logos to a location accessible + to your web server. E.g. with Apache, you've usually got an + <code>icons</code> directory that you can drop the images + into. You want to copy + <code>$prefix/icons/mailman.jpg</code>, + <code>$prefix/icons/PythonPowered.png</code>, and + <code>$prefix/icons/gnu-head-tiny.jpg</code> to this + directory. + + <p>You then want to add a line to your + <code>$prefix/Mailman/mm_cfg.py</code> file which sets the + base URL for the logos. For example: + +<blockquote> +<pre> +IMAGE_LOGOS = '/images/' +</pre> +</blockquote> + + <p>The default value for <code>IMAGE_LOGOS</code> is + <code>/icons/</code>. Read the + comment in <code>Defaults.py.in</code> for details. + + <p><li>Configure your web server to point to the Pipermail public + mailing list archives: + + For example, in Apache: + +<blockquote> +<pre> +Alias /pipermail/ $varprefix/archives/public/ +</pre> +</blockquote> + + <p>where <code>$varprefix</code> is usually + <code>$prefix</code> unless you've used the + <code>--with-var-prefix</code> option to configure. + + <p>Consult your web server's documentation for details. Also + be sure to configure your web server to follow symbolic links + in this directory, otherwise public Pipermail archives won't + be accessible. For Apache users, consult the + <em>FollowSymLinks</em> option. + + <p>Now restart your web server. + + <p><li><b>IMPERATIVE! IMPORTANT! DO THIS! YOU'LL BE SORRY IF + YOU DON'T!</b> + + <p>Set up the crontab entries. Mailman runs a number of cron + jobs for its basic functionality. You need to be user + <code>mailman</code> (or whatever you specified as + <code>--with-ownername</code>) to perform this step. Add + <code>$prefix/cron/crontab.in</code> as a crontab entry by + executing these commands: + +<blockquote> +<pre> +% su - mailman +% cd $prefix/cron +% crontab crontab.in +</pre> +</blockquote> + + <p><li>Look to see if there is special instructions about hooking your + MTA up to Mailman. If so, there will be a + README.<em>yourMTA</em> file in the Mailman source directory. + + <p><li>Add aliases for <code>mailman</code> and + <code>mailman-owner</code> to the system's mail alias + database. These aliases should point to whoever is ultimately + responsible for the Mailman installation. Here are + instructions for those running Sendmail: + + <ol> + <li>su to root. + <li>Assuming your email is <code>fred@flintstone.com</code>, + add the following lines to the file + <code>/etc/aliases</code>: + +<blockquote> +<pre> +mailman: fred@flintstone.com +mailman-owner: mailman +</pre> +</blockquote> + + <li>Some versions of sendmail require you to run the program + <code>newaliases</code> explicitly. + </ol> + + <p>If you don't run sendmail, consult the documentation of + your mail transport program for information on adding these + aliases. + </ul> diff --git a/admin/www/install-final.html b/admin/www/install-final.html new file mode 100644 index 000000000..9a9135e4e --- /dev/null +++ b/admin/www/install-final.html @@ -0,0 +1,317 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:28 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Final system setup + +--> + +<HEAD> +<TITLE>Final system setup</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Final system setup</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Final system set-up</h3> + + Congratulations! You've installed the Mailman software. To get + everything running you need to hook Mailman up to both your web + server and your mail system. + + <ul> + <li>If you plan on running your MTA and web server on different + machines, sharing Mailman installations via NFS, be sure that + the clocks on those two machines are synchronized closely. + You might take a look at the file + <code>Mailman/LockFile.py</code>; the constant + <code>CLOCK_SLOP</code> helps the locking mechanism compensate + for clock skew in this type of environment. + + <p><li>Configure your web server to give <code>$prefix/cgi-bin</code> + permission to run CGI scripts. You probably need to be <b>root</b> + to do this. + + <p>The line you should add might look something like one of + the following (with the real absolute directory substituted + for <code>$prefix</code>, of course), depending on your web + server: + +<blockquote> +<pre> +ScriptAlias /mailman/ $prefix/cgi-bin/ +Exec /mailman/* $prefix/cgi-bin/* +</pre> +</blockquote> + + <p>Consult your web server's documentation for details. + + <p><li><b>IMPORTANT:</b> You want to be very sure that the user id + under which your CGI scripts run is <b>not</b> in the + <code>mailman</code> group you created above, otherwise + private archives will be accessible to anyone. + + <p><li>Copy the Mailman, Python, and GNU logos to a location accessible + to your web server. E.g. with Apache, you've usually got an + <code>icons</code> directory that you can drop the images + into. You want to copy + <code>$prefix/icons/mailman.jpg</code>, + <code>$prefix/icons/PythonPowered.png</code>, and + <code>$prefix/icons/gnu-head-tiny.jpg</code> to this + directory. + + <p>You then want to add a line to your + <code>$prefix/Mailman/mm_cfg.py</code> file which sets the + base URL for the logos. For example: + +<blockquote> +<pre> +IMAGE_LOGOS = '/images/' +</pre> +</blockquote> + + <p>The default value for <code>IMAGE_LOGOS</code> is + <code>/icons/</code>. Read the + comment in <code>Defaults.py.in</code> for details. + + <p><li>Configure your web server to point to the Pipermail public + mailing list archives: + + For example, in Apache: + +<blockquote> +<pre> +Alias /pipermail/ $varprefix/archives/public/ +</pre> +</blockquote> + + <p>where <code>$varprefix</code> is usually + <code>$prefix</code> unless you've used the + <code>--with-var-prefix</code> option to configure. + + <p>Consult your web server's documentation for details. Also + be sure to configure your web server to follow symbolic links + in this directory, otherwise public Pipermail archives won't + be accessible. For Apache users, consult the + <em>FollowSymLinks</em> option. + + <p>Now restart your web server. + + <p><li><b>IMPERATIVE! IMPORTANT! DO THIS! YOU'LL BE SORRY IF + YOU DON'T!</b> + + <p>Set up the crontab entries. Mailman runs a number of cron + jobs for its basic functionality. You need to be user + <code>mailman</code> (or whatever you specified as + <code>--with-ownername</code>) to perform this step. Add + <code>$prefix/cron/crontab.in</code> as a crontab entry by + executing these commands: + +<blockquote> +<pre> +% su - mailman +% cd $prefix/cron +% crontab crontab.in +</pre> +</blockquote> + + <p><li>Look to see if there is special instructions about hooking your + MTA up to Mailman. If so, there will be a + README.<em>yourMTA</em> file in the Mailman source directory. + + <p><li>Add aliases for <code>mailman</code> and + <code>mailman-owner</code> to the system's mail alias + database. These aliases should point to whoever is ultimately + responsible for the Mailman installation. Here are + instructions for those running Sendmail: + + <ol> + <li>su to root. + <li>Assuming your email is <code>fred@flintstone.com</code>, + add the following lines to the file + <code>/etc/aliases</code>: + +<blockquote> +<pre> +mailman: fred@flintstone.com +mailman-owner: mailman +</pre> +</blockquote> + + <li>Some versions of sendmail require you to run the program + <code>newaliases</code> explicitly. + </ol> + + <p>If you don't run sendmail, consult the documentation of + your mail transport program for information on adding these + aliases. + </ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-links.h b/admin/www/install-links.h new file mode 100644 index 000000000..5774631fa --- /dev/null +++ b/admin/www/install-links.h @@ -0,0 +1,11 @@ +<!-- -*- html -*- --> +<h3>Installing Mailman</h3> +<li><a href="install-start.html">Start installing</a> +<li><a href="install-system.html">System setup</a> +<li><a href="install-config.html">Running configure</a> +<li><a href="install-check.html">Check your installation</a> +<li><a href="install-final.html">Final system setup</a> +<li><a href="install-custom.html">Customize Mailman</a> +<li><a href="install-test.html">Create a test list</a> +<li><a href="install-trouble.html">Troubleshooting</a> +<li><a href="install-faq.html">Common problems FAQ</a> diff --git a/admin/www/install-start.ht b/admin/www/install-start.ht new file mode 100644 index 000000000..e2ce9d2a5 --- /dev/null +++ b/admin/www/install-start.ht @@ -0,0 +1,22 @@ +Title: Start installing Mailman +Links: links.h install-links.h + +<h3>Start installing Mailman</h3> + +These are the on-line instructions for installing Mailman from source. +You should always double check the README, INSTALL, and UPGRADING +files in your Mailman distribution for the most up-to-date +information. + +<p>Mailman is configured using the standard GNU autoconf software. +You first need to prepare your system as outlined in the sections +below, and then configure and install the Mailman software. + +<p><em>IMPORTANT: Pay special attention to the step below where +you have to set up your crontab entries. If you do not do this, +Mailman will not work.</em> + +<p><em>UPGRADING: Upgrading is usually as easy as just installing the +new version over the existing installation. However, you should read +the notes in the file UPGRADING for important information before you +upgrade.</em> diff --git a/admin/www/install-start.html b/admin/www/install-start.html new file mode 100644 index 000000000..69c1a53d3 --- /dev/null +++ b/admin/www/install-start.html @@ -0,0 +1,203 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:28 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Start installing Mailman + +--> + +<HEAD> +<TITLE>Start installing Mailman</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<b>Installation</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Installation</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Start installing</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Start installing Mailman</h3> + +These are the on-line instructions for installing Mailman from source. +You should always double check the README, INSTALL, and UPGRADING +files in your Mailman distribution for the most up-to-date +information. + +<p>Mailman is configured using the standard GNU autoconf software. +You first need to prepare your system as outlined in the sections +below, and then configure and install the Mailman software. + +<p><em>IMPORTANT: Pay special attention to the step below where +you have to set up your crontab entries. If you do not do this, +Mailman will not work.</em> + +<p><em>UPGRADING: Upgrading is usually as easy as just installing the +new version over the existing installation. However, you should read +the notes in the file UPGRADING for important information before you +upgrade.</em> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-system.ht b/admin/www/install-system.ht new file mode 100644 index 000000000..a43f8bca2 --- /dev/null +++ b/admin/www/install-system.ht @@ -0,0 +1,59 @@ +Title: System setup +Links: links.h install-links.h + +<h3>System setup</h3> + + <p><em>You will need to be <b>root</b> to perform the steps in this + section.</em> + + <p>Before installing the Mailman software, you need to prepare your + system by adding certain users and groups. + + <ul> + + <li>Add a new user called <code>mailman</code>. Typically + this is added to your <code>/etc/passwd</code> file. If + username <code>mailman</code> is already in use, choose + something else unique and see the + <code>--with-ownername</code> flag below. + + <p><li>Add a new group called <code>mailman</code>. Typically this + is added to your <code>/etc/group</code> file. The Mailman + files will be installed under the <code>mailman</code> group, + with the <em>set-group-id</em> bit. This is so both the web + based and mail based programs will have the proper write + permissions. If groupname <code>mailman</code> is already in + use, choose something else unique and see the + <code>--with-ownergroup</code> below. + + <p><li>Create an installation directory (called <code>$prefix</code> + in the documentation that follows). All of the Mailman files + will be installed under <code>$prefix</code>. Run + <code>configure --help</code> for ways to split the + installation up based on read-only vs. read/write files. + + <p>The default directory for installing is + <code>/home/mailman</code>, but some sites do things like + mount <code>/home</code> with the <em>nosuid</em> option. + This will break Mailman, which relies on setgid programs for + its security. If this describes your environment, simply + install Mailman in a location that allows setgid programs. + + <p>Make sure this directory is set to group <code>mailman</code> + (or whatever you're going to specify as + <code>--with-ownergroup</code>) and has the setgid bit set + (but see the README.BSD file in the source distribution if + you're on a BSD system). You probably also want to guarantee + that this directory is readable and executable by everyone. + For example, these shell commands will accomplish this: + +<blockquote> +<pre> +% cd $prefix +% chgrp mailman . +% chmod a+rx,g+ws . +</pre> +</blockquote> + + You are now ready to configure and install the Mailman software. + </ul> diff --git a/admin/www/install-system.html b/admin/www/install-system.html new file mode 100644 index 000000000..671ecc726 --- /dev/null +++ b/admin/www/install-system.html @@ -0,0 +1,240 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:29 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: System setup + +--> + +<HEAD> +<TITLE>System setup</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>System setup</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>System setup</h3> + + <p><em>You will need to be <b>root</b> to perform the steps in this + section.</em> + + <p>Before installing the Mailman software, you need to prepare your + system by adding certain users and groups. + + <ul> + + <li>Add a new user called <code>mailman</code>. Typically + this is added to your <code>/etc/passwd</code> file. If + username <code>mailman</code> is already in use, choose + something else unique and see the + <code>--with-ownername</code> flag below. + + <p><li>Add a new group called <code>mailman</code>. Typically this + is added to your <code>/etc/group</code> file. The Mailman + files will be installed under the <code>mailman</code> group, + with the <em>set-group-id</em> bit. This is so both the web + based and mail based programs will have the proper write + permissions. If groupname <code>mailman</code> is already in + use, choose something else unique and see the + <code>--with-ownergroup</code> below. + + <p><li>Create an installation directory (called <code>$prefix</code> + in the documentation that follows). All of the Mailman files + will be installed under <code>$prefix</code>. Run + <code>configure --help</code> for ways to split the + installation up based on read-only vs. read/write files. + + <p>The default directory for installing is + <code>/home/mailman</code>, but some sites do things like + mount <code>/home</code> with the <em>nosuid</em> option. + This will break Mailman, which relies on setgid programs for + its security. If this describes your environment, simply + install Mailman in a location that allows setgid programs. + + <p>Make sure this directory is set to group <code>mailman</code> + (or whatever you're going to specify as + <code>--with-ownergroup</code>) and has the setgid bit set + (but see the README.BSD file in the source distribution if + you're on a BSD system). You probably also want to guarantee + that this directory is readable and executable by everyone. + For example, these shell commands will accomplish this: + +<blockquote> +<pre> +% cd $prefix +% chgrp mailman . +% chmod a+rx,g+ws . +</pre> +</blockquote> + + You are now ready to configure and install the Mailman software. + </ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-test.ht b/admin/www/install-test.ht new file mode 100644 index 000000000..401913714 --- /dev/null +++ b/admin/www/install-test.ht @@ -0,0 +1,23 @@ +Title: Create a test list +Links: links.h install-links.h + +<h3>Create a test list</h3> + +Create a list named <em>test</em>. To do so, run the program +<code>$prefix/bin/newlist</code>. You will be prompted for the name +of the list, as well as the email address of the person running the +list. Put your own email address as the list administrator's address. + +<p>Running newlist will generate a list of aliases that must be added +to the system. If you are running Sendmail, you may add the lines +output directly to the file <code>/etc/aliases</code>. You may need +to run the command <code>newaliases</code> (all as <b>root</b>). Now +the mailing address for your list as well as its administrative +addresses will be set up. If you are not running Sendmail, consult +your MTA's documentation for information on adding aliases. + +<p>You will receive email instructions on how to visit the list you +just created. Using these instructions, subscribe to the mailing +list. Once you have subscribed (which requires a confirmation step!), +send a message to the list, and see if you get it. If so, then you +have successfully installed Mailman, and set up your first list! diff --git a/admin/www/install-test.html b/admin/www/install-test.html new file mode 100644 index 000000000..3eecee871 --- /dev/null +++ b/admin/www/install-test.html @@ -0,0 +1,204 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:29 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Create a test list + +--> + +<HEAD> +<TITLE>Create a test list</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Create a test list</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-trouble.html">Troubleshooting</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Create a test list</h3> + +Create a list named <em>test</em>. To do so, run the program +<code>$prefix/bin/newlist</code>. You will be prompted for the name +of the list, as well as the email address of the person running the +list. Put your own email address as the list administrator's address. + +<p>Running newlist will generate a list of aliases that must be added +to the system. If you are running Sendmail, you may add the lines +output directly to the file <code>/etc/aliases</code>. You may need +to run the command <code>newaliases</code> (all as <b>root</b>). Now +the mailing address for your list as well as its administrative +addresses will be set up. If you are not running Sendmail, consult +your MTA's documentation for information on adding aliases. + +<p>You will receive email instructions on how to visit the list you +just created. Using these instructions, subscribe to the mailing +list. Once you have subscribed (which requires a confirmation step!), +send a message to the list, and see if you get it. If so, then you +have successfully installed Mailman, and set up your first list! + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/install-trouble.ht b/admin/www/install-trouble.ht new file mode 100644 index 000000000..b5bbfb932 --- /dev/null +++ b/admin/www/install-trouble.ht @@ -0,0 +1,22 @@ +Title: Troubleshooting +Links: links.h install-links.h + +<h3>Troubleshooting</h3> + + If you encounter problems with running Mailman, first check the + "Common Problems" section, below. If your problem is not covered + there, check the file <a href="faq.html">FAQ</a> and FAQ.LINUX. + Then check for a log entry from Mailman in your syslog. + + <p>Where syslog lives on your particular machine may vary. It may + be in <code>/var/log/maillog</code>. It may also be in + <code>/var/log/syslog</code>. On many machines, syslog files live + in <code>/adm/log/</code> instead of <code>/var/log</code>. + + <p>If you encounter an error, send an error report to + <a + href="mailto:mailman-users@python.org">mailman-users@python.org</a>. + Include a description of what you're + doing to cause the problem, and the relevant lines from your + syslog. Also include information on your operating system and + version of Python. diff --git a/admin/www/install-trouble.html b/admin/www/install-trouble.html new file mode 100644 index 000000000..4725271b7 --- /dev/null +++ b/admin/www/install-trouble.html @@ -0,0 +1,203 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:30 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Troubleshooting + +--> + +<HEAD> +<TITLE>Troubleshooting</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Installing Mailman +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Start installing</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-system.html">System setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-config.html">Running configure</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-check.html">Check your installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-final.html">Final system setup</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-custom.html">Customize Mailman</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-test.html">Create a test list</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Troubleshooting</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-faq.html">Common problems FAQ</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Troubleshooting</h3> + + If you encounter problems with running Mailman, first check the + "Common Problems" section, below. If your problem is not covered + there, check the file <a href="faq.html">FAQ</a> and FAQ.LINUX. + Then check for a log entry from Mailman in your syslog. + + <p>Where syslog lives on your particular machine may vary. It may + be in <code>/var/log/maillog</code>. It may also be in + <code>/var/log/syslog</code>. On many machines, syslog files live + in <code>/adm/log/</code> instead of <code>/var/log</code>. + + <p>If you encounter an error, send an error report to + <a + href="mailto:mailman-users@python.org">mailman-users@python.org</a>. + Include a description of what you're + doing to cause the problem, and the relevant lines from your + syslog. Also include information on your operating system and + version of Python. + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/inthenews.ht b/admin/www/inthenews.ht new file mode 100644 index 000000000..fe04db6a7 --- /dev/null +++ b/admin/www/inthenews.ht @@ -0,0 +1,128 @@ +Title: Mailman in Use and in the News + +<h3>Mailman in Use and in the News</h3> + +Mailman was featured in a +<a href="http://www.sunworld.com/swol-03-1999/swol-03-mailtools.html"> +cover story article</a> in the March 1999 issue +of SunWorld. The article was written by Cameron Laird and Kathryn +Soraiz. + +<p>Mailman was briefly mentioned in +<a href="http://www.zdnet.com/sr/stories/issue/0,4537,387506,00.html"> +a ZDNet article</a> on Linux. This was picked up by +<a href="http://www.msnbc.com/news/244979.asp">MSNBC</a> (I won't +comment on the irony there). + +<p>The following sites (in no particular order) are known to use +Mailman or Mailman technology to run their mailing lists. If you'd +like to be included in this list, please +<a href="mailto:mailman-cabal@python.org">let us know</a>. + +<ul> + <!-- Chuq von Rospach --> + <li><a href="http://lists.apple.com/">Apple Computer, Inc.</a> + <!-- Keith Packard --> + <li><a href="http://xfree86.org/">The XFree86 Project, Inc.</a> + <!-- Marc Merlin --> + <li><a href="http://valinux.com/">VA Linux</a> + <li><a href="http://sourceforge.net/">SourceForge</a> + <!-- Ricardo Kustner --> + <li><a href="http://www.freshmeat.net/">FreshMeat</a> + <!-- Jeff Barger --> + <li><a href="http://www.listserve.com/">ListServe.com</a> + <!-- Sean Reifschneider --> + <li><a href="http://tummy.com/">tummy.com</a> (lots of Linux + lists) + <!-- Roger Pena --> + <li><a href="http://www.redhat.com/">RedHat, Inc.</a> + <li><a href="http://lists.samba.org/">Samba</a> + + <!-- Barry Warsaw --> + <li><a href="http://www.python.org/sigs/">Python.Org</a> + <!-- Owen Taylor --> + <li><a href="http://mail.gnome.org/">GNOME.Org</a> + <!-- Nigel Metheringham --> + <li><a href="http://www.exim.org/">Exim.Org</a> (see also Nigel's + <a href="http://www.exim.org/pipermail/exim-users">htdig + extensions</a> in action for searchable archives) + <li><a href="http://list.wylug.org.uk/mailman/listinfo">Yorkshire + Linux User Group mailing lists</a> + <!-- Marc Merlin --> + <li><a href="http://linuxia64.org/">IA-64 Linux Project</a> + <!-- Jim Hebert --> + <li><a href="http://www.cosource.com/">Cosource.com</a> + <li><a href="http://www.vistasource.com/">VistaSource.com</a> + (private lists only, currently) + <!-- Bill Bradford --> + <li><a href="http://www.sunhelp.org/mailman/listinfo/">SunHelp.Org</a> + + <!-- J C Lawrence + -- <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a> + -- currently having h/w problems + --> + + <!-- Michael Dunston --> + <li><a href="http://www.music.vt.edu">Music and Technology + Department, Virginia Tech School of the Arts</a> + <!-- Nick Marouf --> + <li><a href="http://www.earlham.edu">Earlham College</a> + <!-- Mike Richardson --> + <li><a href="http://lists.man.ac.uk/mailman/listinfo">University + of Manchester</a> + <!-- Jeff Berliner --> + <li><a href="http://endeavor.med.nyu.edu/mailman/listinfo">New York + University School of Medicine</a> + + <!-- Chuq von Rospach's alter ego --> + <li><a href="http://www.hockeyfanz.com/">HockeyFanz.com</a> + <!-- Johnny Fuerst --> + <li><a href="http://mail.cathat.net/mailman/listinfo/">The CatHat + Republic</a> + <!-- Phil Barnett --> + <li><a + href="http://www.matrixlist.com/mailman/listinfo">www.matrixlist.com</a> + <!-- John A. Martin --> + <li><a href="http://lists.essential.org/">lists.essential.org</a> + <!-- Dan Mick --> + <li><a href="http://socal-raves.org/">SoCal-Raves.org</a> + <!-- Peter Murray --> + <li><a href="http://www.ravedata.com/">ravedata.com</a> + <!-- Satya --> + <li><a href="http://txr.cjb.net/ml.html">TSEC mailing list</a> + <li><a href="http://quickapps.cjb.net/ml.html">GRE (grad studies) + mailing list</a> + <!-- tim --> + <li><a href="http://www.hal2001.org">HAL (Hackers at Large) 2001</a> + <!-- Rodrigo Moya --> + <li><a href="http://www.essential-is.com/">www.essential-is.com</a> + <!-- Kevin N. Carpenter --> + <li><a href="http://www.seaplace.org/">FishRoom</a> + <!-- Dan Ohnesorg --> + <li><a href="http://www.debian.cz/">www.debian.cz</a> + <li><a href="http://dali.feld.cvut.cz/">dali.feld.cvut.cz</a> + <!-- Stephan Berndts --> + <li><a href="http://lists.spline.de/">lists.spline.de</a> + <!-- W. Reilly Cooley --> + <li><a href="http://mail.wirex.com/">mail.wirex.com</a> + <!-- Roger Pena --> + <li><a href="http://www.linux.cu/">linux.cu</a> + <!-- Ricardo Kustner --> + <li><a href="http://www.miss-janet.com/">www.miss-janet.com</a> + <!-- I.Ioannou --> + <li><a href="http://lists.hellug.gr">Greek LUG</a> + <!-- George Dinwiddie --> + <li><a href="http://www.alberg30.org/">alberg30.org</a> + <!-- Jeff Berliner --> + <li><a href="http://www.anthem2000.com/">anthem2000.com</a> + <!-- Mentor Cana --> + <li><a href="http://www.alb-net.com/mailman/listinfo">www.alb-net.com</a> + <!-- Les Niles --> + <li><a + href="http://www.aviating.com/mooney/">www.aviating.com</a> + <li><a href="http://www.kjsl.com/">www.kjsl.com</a> + <!-- Brian Edmonds --> + <li><a href="http://gweep.ca/">gweep.ca</a> + <li><a href="http://antarti.ca/">antarti.ca</a> + +</ul> diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html new file mode 100644 index 000000000..66a32ca1a --- /dev/null +++ b/admin/www/inthenews.html @@ -0,0 +1,279 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:30 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Mailman in Use and in the News + +--> + +<HEAD> +<TITLE>Mailman in Use and in the News</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Mailman in Use</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Mailman in Use and in the News</h3> + +Mailman was featured in a +<a href="http://www.sunworld.com/swol-03-1999/swol-03-mailtools.html"> +cover story article</a> in the March 1999 issue +of SunWorld. The article was written by Cameron Laird and Kathryn +Soraiz. + +<p>Mailman was briefly mentioned in +<a href="http://www.zdnet.com/sr/stories/issue/0,4537,387506,00.html"> +a ZDNet article</a> on Linux. This was picked up by +<a href="http://www.msnbc.com/news/244979.asp">MSNBC</a> (I won't +comment on the irony there). + +<p>The following sites (in no particular order) are known to use +Mailman or Mailman technology to run their mailing lists. If you'd +like to be included in this list, please +<a href="mailto:mailman-cabal@python.org">let us know</a>. + +<ul> + <!-- Chuq von Rospach --> + <li><a href="http://lists.apple.com/">Apple Computer, Inc.</a> + <!-- Keith Packard --> + <li><a href="http://xfree86.org/">The XFree86 Project, Inc.</a> + <!-- Marc Merlin --> + <li><a href="http://valinux.com/">VA Linux</a> + <li><a href="http://sourceforge.net/">SourceForge</a> + <!-- Ricardo Kustner --> + <li><a href="http://www.freshmeat.net/">FreshMeat</a> + <!-- Jeff Barger --> + <li><a href="http://www.listserve.com/">ListServe.com</a> + <!-- Sean Reifschneider --> + <li><a href="http://tummy.com/">tummy.com</a> (lots of Linux + lists) + <!-- Roger Pena --> + <li><a href="http://www.redhat.com/">RedHat, Inc.</a> + <li><a href="http://lists.samba.org/">Samba</a> + + <!-- Barry Warsaw --> + <li><a href="http://www.python.org/sigs/">Python.Org</a> + <!-- Owen Taylor --> + <li><a href="http://mail.gnome.org/">GNOME.Org</a> + <!-- Nigel Metheringham --> + <li><a href="http://www.exim.org/">Exim.Org</a> (see also Nigel's + <a href="http://www.exim.org/pipermail/exim-users">htdig + extensions</a> in action for searchable archives) + <li><a href="http://list.wylug.org.uk/mailman/listinfo">Yorkshire + Linux User Group mailing lists</a> + <!-- Marc Merlin --> + <li><a href="http://linuxia64.org/">IA-64 Linux Project</a> + <!-- Jim Hebert --> + <li><a href="http://www.cosource.com/">Cosource.com</a> + <li><a href="http://www.vistasource.com/">VistaSource.com</a> + (private lists only, currently) + <!-- Bill Bradford --> + <li><a href="http://www.sunhelp.org/mailman/listinfo/">SunHelp.Org</a> + + <!-- J C Lawrence + -- <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a> + -- currently having h/w problems + --> + + <!-- Michael Dunston --> + <li><a href="http://www.music.vt.edu">Music and Technology + Department, Virginia Tech School of the Arts</a> + <!-- Nick Marouf --> + <li><a href="http://www.earlham.edu">Earlham College</a> + <!-- Mike Richardson --> + <li><a href="http://lists.man.ac.uk/mailman/listinfo">University + of Manchester</a> + <!-- Jeff Berliner --> + <li><a href="http://endeavor.med.nyu.edu/mailman/listinfo">New York + University School of Medicine</a> + + <!-- Chuq von Rospach's alter ego --> + <li><a href="http://www.hockeyfanz.com/">HockeyFanz.com</a> + <!-- Johnny Fuerst --> + <li><a href="http://mail.cathat.net/mailman/listinfo/">The CatHat + Republic</a> + <!-- Phil Barnett --> + <li><a + href="http://www.matrixlist.com/mailman/listinfo">www.matrixlist.com</a> + <!-- John A. Martin --> + <li><a href="http://lists.essential.org/">lists.essential.org</a> + <!-- Dan Mick --> + <li><a href="http://socal-raves.org/">SoCal-Raves.org</a> + <!-- Peter Murray --> + <li><a href="http://www.ravedata.com/">ravedata.com</a> + <!-- Satya --> + <li><a href="http://txr.cjb.net/ml.html">TSEC mailing list</a> + <li><a href="http://quickapps.cjb.net/ml.html">GRE (grad studies) + mailing list</a> + <!-- tim --> + <li><a href="http://www.hal2001.org">HAL (Hackers at Large) 2001</a> + <!-- Rodrigo Moya --> + <li><a href="http://www.essential-is.com/">www.essential-is.com</a> + <!-- Kevin N. Carpenter --> + <li><a href="http://www.seaplace.org/">FishRoom</a> + <!-- Dan Ohnesorg --> + <li><a href="http://www.debian.cz/">www.debian.cz</a> + <li><a href="http://dali.feld.cvut.cz/">dali.feld.cvut.cz</a> + <!-- Stephan Berndts --> + <li><a href="http://lists.spline.de/">lists.spline.de</a> + <!-- W. Reilly Cooley --> + <li><a href="http://mail.wirex.com/">mail.wirex.com</a> + <!-- Roger Pena --> + <li><a href="http://www.linux.cu/">linux.cu</a> + <!-- Ricardo Kustner --> + <li><a href="http://www.miss-janet.com/">www.miss-janet.com</a> + <!-- I.Ioannou --> + <li><a href="http://lists.hellug.gr">Greek LUG</a> + <!-- George Dinwiddie --> + <li><a href="http://www.alberg30.org/">alberg30.org</a> + <!-- Jeff Berliner --> + <li><a href="http://www.anthem2000.com/">anthem2000.com</a> + <!-- Mentor Cana --> + <li><a href="http://www.alb-net.com/mailman/listinfo">www.alb-net.com</a> + <!-- Les Niles --> + <li><a + href="http://www.aviating.com/mooney/">www.aviating.com</a> + <li><a href="http://www.kjsl.com/">www.kjsl.com</a> + <!-- Brian Edmonds --> + <li><a href="http://gweep.ca/">gweep.ca</a> + <li><a href="http://antarti.ca/">antarti.ca</a> + +</ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/links.h b/admin/www/links.h new file mode 100644 index 000000000..f1351f0f9 --- /dev/null +++ b/admin/www/links.h @@ -0,0 +1,11 @@ +<!-- -*- html -*- --> +<h3>Overview</h3> +<li><a href="index.html">Home</a> +<li><a href="features.html">Features</a> +<li><a href="download.html">Requirements, Download</a> +<li><a href="install-start.html">Installation</a> +<li><a href="lists.html">Discussion Lists</a> +<li><a href="bugs.html">Bugs and Patches</a> +<li><a href="faq.html">Frequently Asked Questions</a> +<li><a href="inthenews.html">Mailman in Use</a> +<li><a href="todo.html">Wishlist!</a> diff --git a/admin/www/lists.ht b/admin/www/lists.ht new file mode 100644 index 000000000..de9691c7a --- /dev/null +++ b/admin/www/lists.ht @@ -0,0 +1,50 @@ +Title: Mailman mailing lists + +<h3>Mailman mailing lists</h3> + +We have several mailing lists devoted to Mailman, which also provide a +nice demonstration of Mailman! + +<ul> +<li><a href="http://www.python.org/mailman/listinfo/mailman-announce"> + Mailman Announce</a> is a read-only list that you can subscribe to + if you are only interested in release notices and other important + news. Only the core Mailman developers can post messages to this + list. + (<a href="http://www.python.org/pipermail/mailman-announce/"><em>archives</em></a>) + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-users"> + Mailman Users</a> is the mailing list to subscribe to if you are + using Mailman at your site, and may have problems or questions + relating to installation, use, etc. We'll try to keep the deep + technical discussions off this list. + (<a href="http://www.python.org/pipermail/mailman-users/"><em>archives</em></a>) + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-developers"> + Mailman Developers</a> is the mailing list to use if you are + interested in helping us develop Mailman, discuss future + directions, etc. This is the list for more in-depth technical + issues. + (<a href="http://www.python.org/pipermail/mailman-developers/"><em>archives</em></a>) + + <p>You may also want to find a project on our Mailman + <a href="todo.html">TODO list</a>. + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-i18n"> + Mailman Internationalization</a> is the list for discussing the + multi-lingual extensions to Mailman, which will likely be folded + into the standard distribution after the 2.0 release. Once + integrated, this list will be a way for language translators to + submit new translation files. + (<a href="http://www.python.org/pipermail/mailman-i18n/"><em>archives</em></a>) + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-checkins"> + Mailman Checkins</a> is an adjunct list to the publically + accessible read-only CVS repository. This list is for the + hardcore developers, or anybody else submitting patches, since we + really prefer such patches to be generated against the latest + snapshot. This is a read-only list; only the core Mailman + developers can post messages to this list. There is no archive. + (<a href="http://www.python.org/pipermail/mailman-checkins/"><em>archives</em></a>) + +</ul> diff --git a/admin/www/lists.html b/admin/www/lists.html new file mode 100644 index 000000000..cc716e5d3 --- /dev/null +++ b/admin/www/lists.html @@ -0,0 +1,201 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:31 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Mailman mailing lists + +--> + +<HEAD> +<TITLE>Mailman mailing lists</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<b>Discussion Lists</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Discussion Lists</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Mailman mailing lists</h3> + +We have several mailing lists devoted to Mailman, which also provide a +nice demonstration of Mailman! + +<ul> +<li><a href="http://www.python.org/mailman/listinfo/mailman-announce"> + Mailman Announce</a> is a read-only list that you can subscribe to + if you are only interested in release notices and other important + news. Only the core Mailman developers can post messages to this + list. + (<a href="http://www.python.org/pipermail/mailman-announce/"><em>archives</em></a>) + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-users"> + Mailman Users</a> is the mailing list to subscribe to if you are + using Mailman at your site, and may have problems or questions + relating to installation, use, etc. We'll try to keep the deep + technical discussions off this list. + (<a href="http://www.python.org/pipermail/mailman-users/"><em>archives</em></a>) + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-developers"> + Mailman Developers</a> is the mailing list to use if you are + interested in helping us develop Mailman, discuss future + directions, etc. This is the list for more in-depth technical + issues. + (<a href="http://www.python.org/pipermail/mailman-developers/"><em>archives</em></a>) + + <p>You may also want to find a project on our Mailman + <a href="todo.html">TODO list</a>. + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-i18n"> + Mailman Internationalization</a> is the list for discussing the + multi-lingual extensions to Mailman, which will likely be folded + into the standard distribution after the 2.0 release. Once + integrated, this list will be a way for language translators to + submit new translation files. + (<a href="http://www.python.org/pipermail/mailman-i18n/"><em>archives</em></a>) + +<p><li><a href="http://www.python.org/mailman/listinfo/mailman-checkins"> + Mailman Checkins</a> is an adjunct list to the publically + accessible read-only CVS repository. This list is for the + hardcore developers, or anybody else submitting patches, since we + really prefer such patches to be generated against the latest + snapshot. This is a read-only list; only the core Mailman + developers can post messages to this list. There is no archive. + (<a href="http://www.python.org/pipermail/mailman-checkins/"><em>archives</em></a>) + +</ul> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/mgrs.ht b/admin/www/mgrs.ht new file mode 100644 index 000000000..80fde9be6 --- /dev/null +++ b/admin/www/mgrs.ht @@ -0,0 +1,8 @@ +Title: List Manager Documentation +Links: links.h doco-links.h + +<h3>List Manager Documentation</h3> + +<p><a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made +available <a href="http://www.aurora.edu/~ckolar/mailman/">list +manager documentation</a> for Mailman. diff --git a/admin/www/mgrs.html b/admin/www/mgrs.html new file mode 100644 index 000000000..331e6c76f --- /dev/null +++ b/admin/www/mgrs.html @@ -0,0 +1,177 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:31 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: List Manager Documentation + +--> + +<HEAD> +<TITLE>List Manager Documentation</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<b>List Managers</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Documentation +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="users.html">Users</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>List Managers</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="admins.html">Site Administrators</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="devs.html">Developers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="otherdocs.html">Other Documentation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>List Manager Documentation</h3> + +<p><a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made +available <a href="http://www.aurora.edu/~ckolar/mailman/">list +manager documentation</a> for Mailman. + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/otherdocs.ht b/admin/www/otherdocs.ht new file mode 100644 index 000000000..6b55d271e --- /dev/null +++ b/admin/www/otherdocs.ht @@ -0,0 +1,23 @@ +Title: Other Documentation +Links: links.h doco-links.h + +<h3>Other Documentation</h3> + +<p>The <a href="faq.html">Frequently Asked Questions (FAQ)</a> is +available to answer most questions. For issues not covered in the +FAQ, please post your questions to the +<a href="lists.html">Mailman-Users</a> mailing list. + +<p><a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made +available <a href="http://www.aurora.edu/~ckolar/mailman/">Mailman +documentation</a>, primarily for list owners who are not necessarily +technical, but who own Mailman mailing lists. + +<p>Nigel Metheringham has posted a +<a href="http://www.exim.org/howto/mailman.html">HOWTO on using Exim +and Mailman</a> together. If you're using the +<a href="http://www.exim.org">Exim MTA</a> you should check this out. + +<p>The <a href="download.html">Mailman source distribution</a> itself +contains many README files for discussion of issues specific to +operating system, mail transport agent, or web server. diff --git a/admin/www/otherdocs.html b/admin/www/otherdocs.html new file mode 100644 index 000000000..f31946d60 --- /dev/null +++ b/admin/www/otherdocs.html @@ -0,0 +1,192 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:31 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: Other Documentation + +--> + +<HEAD> +<TITLE>Other Documentation</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Documentation +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="users.html">Users</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mgrs.html">List Managers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="admins.html">Site Administrators</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="devs.html">Developers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Other Documentation</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>Other Documentation</h3> + +<p>The <a href="faq.html">Frequently Asked Questions (FAQ)</a> is +available to answer most questions. For issues not covered in the +FAQ, please post your questions to the +<a href="lists.html">Mailman-Users</a> mailing list. + +<p><a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made +available <a href="http://www.aurora.edu/~ckolar/mailman/">Mailman +documentation</a>, primarily for list owners who are not necessarily +technical, but who own Mailman mailing lists. + +<p>Nigel Metheringham has posted a +<a href="http://www.exim.org/howto/mailman.html">HOWTO on using Exim +and Mailman</a> together. If you're using the +<a href="http://www.exim.org">Exim MTA</a> you should check this out. + +<p>The <a href="download.html">Mailman source distribution</a> itself +contains many README files for discussion of issues specific to +operating system, mail transport agent, or web server. + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/todo.ht b/admin/www/todo.ht new file mode 100644 index 000000000..44d69c667 --- /dev/null +++ b/admin/www/todo.ht @@ -0,0 +1,139 @@ +Title: The Mailman Wishlist + +<h3> The Mailman Wishlist +</h3> + You should consider this list of items a good basis for the requirements for Mailman 3.0. It essentially contains a dream list of all the things that are too painful or destabilizing for the 2.x series. <p> +<h3> Email Handling +</h3> +<ul> + <li> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly (optional). + <li> Plain text digests should conform to RFC 1153. +</ul> +<h3> Documentation +</h3> +<ul> + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron +</ul> +<h3> General Web UI +</h3> +<ul> + <li> NO DEAD ENDS + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using a template language/system like Quixote or PHP. + <li> Default UI should add a navigation sidebar to all web pages. + <li> A heirarchy of page designs and information: e.g. the most specialized of the following wins: site, virtual host, list, language, user. + <li> Web pages should never mention turned-off features. +</ul> +<h3> List Admin UI +</h3> +<ul> + <li> Separate list admin role from list moderator role + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the message was edited by the moderator). + <li> Allow "urgent" postings to all members by the list admin which bypasses normal digest delivery. + <li> A button that will bundled and deliver a digest Right Now. + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) + <li> Member management page should display case-preserved email addresses (but still sort case-insensitively). + <li> Member management page should work better for humongous lists, both in terms of performance, and in usability + <li> Searching for members/addresses with regular expressions from both the command line and web interface. + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Ability to set the next digest volume and issue number from the web +</ul> +<h3> List Member UI +</h3> +<ul> + <li> Editing your user options should put you back to the edit-options page + <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out duplicate deliveries. + <li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever address they want to whichever list, with different options per subscription. + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + <li> Allow users to subscribe without selecting a password and have Mailman create a password for them. + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. +</ul> +<h3> Site Administrator's UI +</h3> +<ul> + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their list. + <li> Full creation, deletion, renaming, etc. of lists through the web (and email?), including fixing aliases file updates. + <li> add_members should have a switch to disable admin notifications +</ul> +<h3> Other Usability Improvments +</h3> +<ul> + <li> Allow individuals to turn off password reminders + <li> Confirmations should be both email and web based, and be used for both subscription and unsubscription (configurable by the list admin). + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and authorization to modify the sub & superlists. Majordomo2 is reported to have some good features in this regard. + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + <li> Don't use the first public mailing list as the `originator' of password reminders. +</ul> +<h3> Mailcmd interface +</h3> +<ul> + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control this. Also, adding a confirmation with hit-reply to resubscribe + <li> Add -join and -remove addresses for easy subscription, unsubscription + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation message. Helps track down subscribe bombs. + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. +</ul> +<h3> Portability & architecture +</h3> +<ul> + <li> Replace cron stuff with our own scheduling mechanism. + <li> Get rid of the one-shot process model altogether in favor of a multithreaded monolithic architecture. + <li> Better support for distributed processing + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a relational database, ZODB, LDAP, etc) + <li> Keep a members Real Name with their email address + <li> Member profiles + <li> Do a serious and thorough security audit + <li> Allow lists of the same name in two different virtual domains + <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to include URLs, etc. Should be admin configurable based on MIME type. Check out Bill Bumgarner's work on this. + <li> Should include a --with-username=NAME option to configure (and not require it be literally "mailman"). + <li> Should be able to gather statistics, such as deliveries/day, performance, number of subscribers over time, etc. + <li> Implement something like Roundup's nosy lists, maybe even integrate with Roundup. + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. +</ul> +<h3> Bounce handling +</h3> +<ul> + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + <li> Add more patterns for bounce handling (never ending) + <li> Occasionally remove stale bounce entries + <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. We may want to do this for explicitly disabled addrs too, but perhaps with a different schedule. + <li> Delete bounce disabled address after some period of retry +</ul> +<h3> Pipermail + Archiving mechanism +</h3> +<ul> + <li> Search engine for archives + <li> Provide downloadable tar.gz's of the html archives + <li> sort by date should go most-recent to oldest + <li> allow list owner to edit archive messages + <li> archive link should do *something* reasonable before the first message has been posted to the list. + <li> optional form front-end to public interfaces as a filter to address harvesters. + <li> clobber_date should support third option: only munge the date if the Date: field is unreasonable (far in the future or far in the past). + <li> In general the whole Pipermail subsystem needs a good rewrite. +</ul> +<h3> Code cleanup +</h3> +<ul> + <li> Use all the new wizzy Python 2.0 features + <li> Use the re module where regexp and regsub are used (not many left) + <li> Refine any remaining unqualified exception guards to specify target exceptions, when appropriate. + <li> Turn all remaining string exceptions into class exceptions + <li> Remove dead code. + <li> Unit and system test suite! +</ul> diff --git a/admin/www/todo.html b/admin/www/todo.html index 5217f7659..87332243a 100644 --- a/admin/www/todo.html +++ b/admin/www/todo.html @@ -1,16 +1,163 @@ -<html><head><title>The Mailman TODO list</title></head> -<body bgcolor="#ffffff"> -<h1> The Mailman TODO List -</h1> +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:33 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: The Mailman Wishlist + +--> + +<HEAD> +<TITLE>The Mailman Wishlist</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./users.html">Users</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Wishlist!</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3> The Mailman Wishlist +</h3> You should consider this list of items a good basis for the requirements for Mailman 3.0. It essentially contains a dream list of all the things that are too painful or destabilizing for the 2.x series. <p> -<h1> Email Handling -</h1> +<h3> Email Handling +</h3> <ul> <li> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. - <li> Use multiple subprocesses for MTA handoff, or divorce it entirely from the rest of Mailman. Multi-threading doesn't seem to help much, possibly because of Python's global interpreter lock. The problem here is coordinating access to the list database. + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly (optional). + <li> Plain text digests should conform to RFC 1153. </ul> -<h1> Documentation -</h1> +<h3> Documentation +</h3> <ul> <li> A detailed feature list <li> A user's guide @@ -20,8 +167,8 @@ <li> A developer's guide w/ architecture and API information <li> manpages for the scripts in bin and cron </ul> -<h1> General Web UI -</h1> +<h3> General Web UI +</h3> <ul> <li> NO DEAD ENDS <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using a template language/system like Quixote or PHP. @@ -29,8 +176,8 @@ <li> A heirarchy of page designs and information: e.g. the most specialized of the following wins: site, virtual host, list, language, user. <li> Web pages should never mention turned-off features. </ul> -<h1> List Admin UI -</h1> +<h3> List Admin UI +</h3> <ul> <li> Separate list admin role from list moderator role <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the message was edited by the moderator). @@ -47,10 +194,11 @@ <li> New moderation choice: annotate and send to author for resubmittal. <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. - <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Ability to set the next digest volume and issue number from the web </ul> -<h1> List Member UI -</h1> +<h3> List Member UI +</h3> <ul> <li> Editing your user options should put you back to the edit-options page <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out duplicate deliveries. @@ -60,15 +208,15 @@ <li> Allow users to subscribe without selecting a password and have Mailman create a password for them. <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. </ul> -<h1> Site Administrator's UI -</h1> +<h3> Site Administrator's UI +</h3> <ul> <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their list. <li> Full creation, deletion, renaming, etc. of lists through the web (and email?), including fixing aliases file updates. <li> add_members should have a switch to disable admin notifications </ul> -<h1> Other Usability Improvments -</h1> +<h3> Other Usability Improvments +</h3> <ul> <li> Allow individuals to turn off password reminders <li> Confirmations should be both email and web based, and be used for both subscription and unsubscription (configurable by the list admin). @@ -76,8 +224,8 @@ <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). <li> Don't use the first public mailing list as the `originator' of password reminders. </ul> -<h1> Mailcmd interface -</h1> +<h3> Mailcmd interface +</h3> <ul> <li> Provide an email interface to all administrative commands <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control this. Also, adding a confirmation with hit-reply to resubscribe @@ -86,8 +234,8 @@ <li> Investigate Majordomo2's email admin capabilities. <li> Support the `which' command. </ul> -<h1> Portability & architecture -</h1> +<h3> Portability & architecture +</h3> <ul> <li> Replace cron stuff with our own scheduling mechanism. <li> Get rid of the one-shot process model altogether in favor of a multithreaded monolithic architecture. @@ -103,8 +251,8 @@ <li> Implement something like Roundup's nosy lists, maybe even integrate with Roundup. <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. </ul> -<h1> Bounce handling -</h1> +<h3> Bounce handling +</h3> <ul> <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address <li> Add more patterns for bounce handling (never ending) @@ -113,8 +261,8 @@ <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. We may want to do this for explicitly disabled addrs too, but perhaps with a different schedule. <li> Delete bounce disabled address after some period of retry </ul> -<h1> Pipermail + Archiving mechanism -</h1> +<h3> Pipermail + Archiving mechanism +</h3> <ul> <li> Search engine for archives <li> Provide downloadable tar.gz's of the html archives @@ -123,11 +271,10 @@ <li> archive link should do *something* reasonable before the first message has been posted to the list. <li> optional form front-end to public interfaces as a filter to address harvesters. <li> clobber_date should support third option: only munge the date if the Date: field is unreasonable (far in the future or far in the past). - <li> In general the whole Pipermail subsystem needs a good rewrite. - <li> Ability to set the next digest volume and issue number from the web + <li> In general the whole Pipermail subsystem needs a good rewrite. </ul> -<h1> Code cleanup -</h1> +<h3> Code cleanup +</h3> <ul> <li> Use all the new wizzy Python 2.0 features <li> Use the re module where regexp and regsub are used (not many left) @@ -136,4 +283,8 @@ <li> Remove dead code. <li> Unit and system test suite! </ul> -</body></html> + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> diff --git a/admin/www/users.ht b/admin/www/users.ht new file mode 100644 index 000000000..840da1764 --- /dev/null +++ b/admin/www/users.ht @@ -0,0 +1,8 @@ +Title: User Documentation +Links: links.h doco-links.h + +<h3>User Documentation</h3> + +<p><a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made +available a <a href="http://www.aurora.edu/~ckolar/mailman/">Mailman +user guide</a> for end-users interacting with a Mailman system. diff --git a/admin/www/users.html b/admin/www/users.html new file mode 100644 index 000000000..d95280926 --- /dev/null +++ b/admin/www/users.html @@ -0,0 +1,177 @@ +<HTML> +<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> +<!-- Wed Nov 8 13:38:32 2000 --> +<!-- USING HT2HTML 1.1 --> +<!-- SEE http://www.python.org/~bwarsaw/software/pyware.html --> +<!-- User-specified headers: +Title: User Documentation + +--> + +<HEAD> +<TITLE>User Documentation</TITLE> + +</HEAD> +<BODY BGCOLOR="#ffffff" TEXT="#000000" + TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0" + LINK="#0000bb" VLINK="#551a8b" + ALINK="#ff0000"> +<!-- start of page table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0> +<!-- start of banner row --> +<TR> +<!-- start of corner cells --> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> + +<center> + <a href="./index.html"> + <img border=0 src="./images/logo-70.jpg"></a></center> </TD> +<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<!-- end of corner cells --> +<!-- start of banner --> +<TD WIDTH="90%" BGCOLOR="#99997c"> +<!-- start of site links table --> +<TABLE WIDTH="100%" BORDER=0 +CELLSPACING=0 CELLPADDING=0 + COLS=3 ROWS=4 BGCOLOR="#ffffff"> +<TR> + <TD BGCOLOR="#99997c"> +<a href="./index.html">Home</a> + </TD> + <TD BGCOLOR="#99997c"> +<b>Users</b> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.list.org/">List.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./install-start.html">Installation</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./mgrs.html">List Managers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./faq.html">FAQ</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./admins.html">Site Administrators</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.python.org/">Python.Org</a> + </TD> +</TR><TR> + <TD BGCOLOR="#99997c"> +<a href="./lists.html">Discussion Lists</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="./devs.html">Developers</a> + </TD> + <TD BGCOLOR="#99997c"> +<a href="http://www.gnu.org/">Gnu.Org</a> + </TD> +</TR> +</TABLE><!-- end of site links table --> + +</TD><!-- end of banner --> +</TR><!-- end of banner row --> +<TR><!-- start of sidebar/body row --> +<!-- start of sidebar cells --> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<!-- start of sidebar table --> +<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 + BGCOLOR="#ffffff"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Overview +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="index.html">Home</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="features.html">Features</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="download.html">Requirements, Download</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="install-start.html">Installation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="lists.html">Discussion Lists</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="bugs.html">Bugs and Patches</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="faq.html">Frequently Asked Questions</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="inthenews.html">Mailman in Use</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="todo.html">Wishlist!</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Documentation +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<b>Users</b> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mgrs.html">List Managers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="admins.html">Site Administrators</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="devs.html">Developers</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="otherdocs.html">Other Documentation</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +Email Us +</FONT></B></TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="mailto:mailman-cabal@python.org">mailman-cabal@python.org</A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +<A HREF="http://www.python.org/"> +<center> + <img border=0 src="./images/PythonPoweredSmall.png"></center></A> +</TD></TR> +<TR><TD BGCOLOR="#99997c"> + +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +© 1998,1999,2000 +</TD></TR> +<TR><TD BGCOLOR="#99997c"> +Free Software Foundation, Inc. +</TD></TR> +</TABLE><!-- end of sidebar table --> + +</TD> +<TD WIDTH=15> </TD><!--spacer--> +<!-- end of sidebar cell --> +<!-- start of body cell --> +<TD VALIGN=TOP WIDTH="90%"><BR> +<h3>User Documentation</h3> + +<p><a href="http://www.aurora.edu/~ckolar">Chris Kolar</a> has made +available a <a href="http://www.aurora.edu/~ckolar/mailman/">Mailman +user guide</a> for end-users interacting with a Mailman system. + +</TD><!-- end of body cell --> +</TR><!-- end of sidebar/body row --> +</TABLE><!-- end of page table --> +</BODY></HTML> |