This commit was manufactured by cvs2svn to create branch

'Release_2_1-maint'.

60 files changed, 7641 insertions, 0 deletions

diff --git a/admin/bin/Release.py b/admin/bin/Release.py
new file mode 100755
index 00000000..227cdb5a
--- /dev/null
+++ b/admin/bin/Release.py
@@ -0,0 +1,229 @@
+#! /usr/bin/env python
+#
+# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
+#
+# 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.
+#
+# 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.
+
+"""Manage releases of Mailman.
+
+Usage: %(program)s [options] tagname
+
+Where `options' are:
+
+    --tag
+    -t
+        Tag all release files with tagname.
+
+    --TAG
+    -T
+        Like --tag, but relocates any existing tag.  See `cvs tag -F'.  Only
+        one of --tag or --TAG can be given on the command line.
+
+    --package
+    -p
+        create the distribution package
+
+    --bump
+    -b
+        Bump the revision number in key files to tagname.  This is done by
+        textual substitution.
+
+    --help
+    -h
+        Print this help message.
+
+    tagname is used in the various commands above.  It should essentially be
+    the version number for the release, and is required.
+"""
+
+import sys
+import os
+import errno
+import re
+import time
+import tempfile
+import getopt
+
+program = sys.argv[0]
+
+def usage(code, msg=''):
+    print >> sys.stderr, __doc__ % globals()
+    if msg:
+        print >> sys.stderr, msg
+    sys.exit(code)
+
+
+
+_releasedir = None
+def releasedir(tagname=None):
+    global _releasedir
+    if not _releasedir:
+        tmpdir = tempfile.gettempdir()
+        _releasedir = os.path.join(tmpdir, 'mailman-' + tagname)
+    return _releasedir
+
+
+
+# CVS related commands
+
+def tag2rel(tagname):
+    return '"Release_%s"' % tagname.replace('.', '_')
+
+def cvsdo(cvscmd):
+    # I don't know why -d is suddenly required -- $CVSROOT used to work just
+    # fine but now (RH7.3) doesn't at all.
+    cmd = 'cvs -d %s %s' % (os.environ['CVSROOT'], cvscmd)
+    os.system(cmd)
+
+def tag_release(tagname, retag):
+    # Convert dots in tagname to underscores
+    relname = tag2rel(tagname)
+    print 'Tagging release with', relname, '...'
+    option = ''
+    if retag:
+        option = '-F'
+    cvsdo('tag %s %s' % (option, relname))
+
+def checkout(tagname, tail):
+    print 'checking out...',
+    relname = tag2rel(tagname)
+    cvsdo('export -k kv -r %s -d %s mailman' % (relname, tail))
+    os.rename('%s/doc' % tail, 'mailman-doc')
+
+
+
+def make_pkg(tagname):
+    dir = releasedir(tagname)
+    print 'Exporting release dir', dir, '...'
+    head, tail = os.path.split(dir)
+    # this can't be done from a working directory
+    curdir = os.getcwd()
+    try:
+        os.chdir(head)
+        checkout(tagname, tail)
+        print 'making tarball...'
+        relname = 'mailman-' + tagname
+        os.system('tar cvzf %s --exclude .cvsignore %s' %
+                  (relname + '.tgz', relname))
+        os.system('tar cvzf mailman-doc.tgz --exclude .cvsignore mailman-doc')
+    finally:
+        os.chdir(curdir)
+
+
+VERSIONMARK = '<!-VERSION--->'
+DATEMARK    = '<!-DATE--->'
+
+
+def do_bump(newvers):
+    print 'doing bump...',
+    # hack some files
+    for file in ('index.ht', 'version.ht'):
+        print '%s...' % file,
+        fp = open(os.path.join('admin', 'www', file), 'r+')
+        text = fp.read()
+        parts = text.split(VERSIONMARK)
+        parts[1] = newvers
+        text = VERSIONMARK.join(parts)
+        parts = text.split(DATEMARK)
+        parts[1] = time.strftime('%d-%b-%Y', time.localtime(time.time()))
+        text = DATEMARK.join(parts)
+        fp.seek(0)
+        fp.write(text)
+        fp.close()
+    # hack the configure.in file
+    print 'Version.py...',
+    infp = open('Mailman/Version.py')
+    outfp = open('Mailman/Version.py.new', 'w')
+    matched = 0
+    cre = re.compile(r'^VERSION(?P<ws>[ \t]*)=')
+    while 1:
+        line = infp.readline()
+        if not line:
+            if not matched:
+                print 'Error! VERSION line not found'
+            break
+        mo = cre.search(line)
+        if matched or not mo:
+            outfp.write(line)
+        else:
+            outfp.write('VERSION%s= "%s"\n' % (mo.group('ws'), newvers))
+            matched = 1
+    infp.close()
+    outfp.close()
+    os.rename('Mailman/Version.py.new', 'Mailman/Version.py')
+
+
+
+def main():
+    try:
+        opts, args = getopt.getopt(sys.argv[1:], 'btTph',
+                                   ['bump', 'tag', 'TAG', 'package', 'help'])
+    except getopt.error, msg:
+        usage(1, msg)
+
+    # required minor rev number
+    if len(args) <> 1:
+        usage(1, 'tagname argument is required')
+
+    tagname = args[0]
+
+    # We need a $CVSROOT
+    if not os.environ.get('CVSROOT'):
+        try:
+            fp = open('CVS/Root')
+            os.environ['CVSROOT'] = fp.read().strip()
+            fp.close()
+        except IOError, e:
+            if e.errno <> errno.ENOENT: raise
+            usage(1, 'CVSROOT is not set and could not be guessed')
+    print 'Using CVSROOT:', os.environ['CVSROOT']
+
+    # default options
+    tag = 0
+    retag = 0
+    package = 0
+    bump = 0
+
+    for opt, arg in opts:
+        if opt in ('-h', '--help'):
+            usage(0)
+        elif opt in ('-t', '--tag'):
+            tag = 1
+        elif opt in ('-T', '--TAG'):
+            tag = 1
+            retag = 1
+        elif opt in ('-p', '--package'):
+            package = 1
+        elif opt in ('-b', '--bump'):
+            bump = 1
+
+    # very important!!!
+    omask = os.umask(0)
+    try:
+        if tag:
+            tag_release(tagname, retag)
+
+        if package:
+            make_pkg(tagname)
+
+        if bump:
+            do_bump(tagname)
+    finally:
+        os.umask(omask)
+
+
+
+if __name__ == '__main__':
+    main()
diff --git a/admin/bin/faq2ht.py b/admin/bin/faq2ht.py
new file mode 100755
index 00000000..29db9ea7
--- /dev/null
+++ b/admin/bin/faq2ht.py
@@ -0,0 +1,102 @@
+#! /usr/bin/env python
+
+"""Convert the plain text FAQ file to its .ht template.
+"""
+
+import sys
+import os
+import re
+
+
+
+def main():
+    faqfile = sys.argv[1]
+    fp = open(faqfile)
+    lines = fp.readlines()
+    fp.close()
+
+    outfile = sys.argv[2]
+    if outfile == '-':
+        closep = 0
+        out = sys.stdout
+    else:
+        closep = 1
+        out = open(outfile, 'w')
+
+    # skip over cruft in FAQ file
+    lineno = 0
+    while not lines[lineno].startswith('FREQUENTLY'):
+        lineno += 1
+    lineno += 1
+
+    # skip blanks
+    while not lines[lineno].strip():
+        lineno += 1
+
+    # first print out standard .ht boilerplate
+    print >> out, '''\
+Title: Mailman Frequently Asked Questions
+
+See also the <a href="http://www.python.org/cgi-bin/faqw-mm.py">Mailman
+FAQ Wizard</a> for more information.
+
+ <h3>Mailman Frequently Asked Questions</h3>
+'''
+    first = 1
+    question = []
+    answer = []
+    faq = []
+    while 1:
+        line = lines[lineno][:-1]
+
+        if line.startswith('Q.'):
+            inquestion = 1
+            if not first:
+                faq.append((question, answer))
+                question = []
+                answer = []
+            else:
+                first = 0
+        elif line.startswith('A.'):
+            inquestion = 0
+        elif line.startswith('\f'):
+            break
+
+        if inquestion:
+            question.append(line)
+        else:
+            # watch for lists
+            if line.lstrip().startswith('*'):
+                answer.append('<li>')
+                line = line.replace('*', '', 1)
+            # substitute <...>
+            line = re.sub(r'<(?P<var>[^>]+)>',
+                          '<em>\g<var></em>',
+                          line)
+            # make links active
+            line = re.sub(r'(?P<url>http://\S+)',
+                          '<a href="\g<url>">\g<url></a>',
+                          line)
+            answer.append(line)
+
+        lineno += 1
+    faq.append((question, answer))
+
+    for question, answer in faq:
+        print >> out, '<b>',
+        for line in question:
+            print >> out, line
+        print >> out, '</b><br>',
+        for line in answer:
+            if not line:
+                print >> out, '<p>',
+            else:
+                print >> out, line
+
+    if closep:
+        out.close()
+
+
+
+if __name__ == '__main__':
+    main()
diff --git a/admin/bin/mm2do b/admin/bin/mm2do
new file mode 100755
index 00000000..661a25f4
--- /dev/null
+++ b/admin/bin/mm2do
@@ -0,0 +1,76 @@
+#! /usr/bin/env python
+#
+# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
+#
+# 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.
+#
+# 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.
+
+"""Generate the todo.ht file from the plain-text TODO file."""
+
+import sys
+
+infp = open(sys.argv[1])
+outfp = open(sys.argv[2], 'w')
+
+SPACE = ' '
+
+print >> outfp, 'Title: The Mailman Wishlist\n'
+
+def dumpsection(header, items, hasitems):
+    # We're looking at a header
+    if header:
+        # output the previous section
+        print >> outfp, '<h3>', header, '</h3>'
+    if hasitems:
+        print >> outfp, '<ul>'
+        for item in items:
+            if item:
+                print >> outfp, '    <li>', SPACE.join(item)
+        print >> outfp, '</ul>'
+    else:
+        for item in items:
+            print >> outfp, SPACE.join(item), '<p>'
+
+
+
+header = ''
+items = [['']]
+hasitems = False
+inpreamble = True
+while True:
+    line = infp.readline()
+    if not line or line[0] == '\f':
+        break
+    # Skip the legalese preamble
+    if inpreamble:
+        if line.strip():
+            continue
+        else:
+            inpreamble = False
+    if not line[0].isspace():
+        dumpsection(header, items, hasitems)
+        header = line
+        items = [[]]
+        continue
+    # find out what the first non-ws character on the line is
+    line = line.lstrip()
+    if line and line[0] == '-':
+        items.append([line[2:-1]])
+        hasitems = True
+    else:
+        if not line:
+            continue
+        items[-1].append(line)
+
+dumpsection(header, items, hasitems)
diff --git a/admin/www/MMGenerator.py b/admin/www/MMGenerator.py
new file mode 100644
index 00000000..df632984
--- /dev/null
+++ b/admin/www/MMGenerator.py
@@ -0,0 +1,110 @@
+"""Generator for the Mailman on-line documentation.
+
+Requires ht2html.py, available from http://ht2html.sourceforge.net
+"""
+
+import os
+import time
+
+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/docs.html',     'Documentation'),
+    ('%(rootdir)s/lists.html',    'Mailing lists'),
+    ('%(rootdir)s/help.html',     'Help'),
+    ('%(rootdir)s/download.html', 'Download'),
+    ('%(rootdir)s/devs.html',     'Developers'),
+    ]
+
+
+
+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-users@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((None,
+                          '''<a href="http://www.python.org/"><img border=0
+                          src="%(rootdir)s/images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>'''
+                          % self.__d))
+        p.sidebar.append(BLANKCELL)
+        thisyear = time.localtime()[0]
+        copyright = self.__parser.get('copyright', '1998-%s' % thisyear)
+        p.sidebar.append((None, '&copy; ' + copyright + """
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+"""))
+        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 'white'
+
+    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."""
+        # The Mailman logo's foreground is approximately #da7074
+        #return '#99997c'
+        #return '#a39c82'
+        #return '#caa08f'
+        return '#eecfa1'
+
+    def get_darkshade(self):
+        """Return darkest of 3 color scheme shade."""
+        #return '#545454'
+        return '#36648b'
diff --git a/admin/www/Makefile b/admin/www/Makefile
new file mode 100644
index 00000000..23e5eeff
--- /dev/null
+++ b/admin/www/Makefile
@@ -0,0 +1,28 @@
+HT2HTML = $(HOME)/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 00000000..b227a8c2
--- /dev/null
+++ b/admin/www/admins.ht
@@ -0,0 +1,8 @@
+Title: List Manager Documentation
+Links: doco-links.h
+
+<h3>List Manager Documentation</h3>
+
+<p><a href="http://staff.imsa.edu/~ckolar">Chris Kolar</a> has made
+available <a href="http://staff.imsa.edu/~ckolar/mailman/">list
+manager documentation</a> for Mailman.
diff --git a/admin/www/admins.html b/admin/www/admins.html
new file mode 100644
index 00000000..520ea223
--- /dev/null
+++ b/admin/www/admins.html
@@ -0,0 +1,134 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:21 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: List Manager Documentation
+
+-->
+
+<head>
+<title>List Manager Documentation</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Documentation
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="docs.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>List Managers</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="site.html">Site Administrators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="i18n.html">Translators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>List Manager Documentation</h3>
+
+<p><a href="http://staff.imsa.edu/~ckolar">Chris Kolar</a> has made
+available <a href="http://staff.imsa.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/bugs.ht b/admin/www/bugs.ht
new file mode 100644
index 00000000..b39ecd5d
--- /dev/null
+++ b/admin/www/bugs.ht
@@ -0,0 +1,25 @@
+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..  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>Be sure to select the right <em>group</em> for your bug or patch,
+e.g. <em>Mailman 2.1</em>.  Failing to do so may cause your submission
+to get overlooked.  It is also recommended that you email a note about
+your submission to the
+<a href="http://mail.python.org/mailman/listinfo/mailman-developers"
+>mailman-developers</a> mailing list, but don't rely on just the email
+to get the attention of the Mailman developers.
+
diff --git a/admin/www/bugs.html b/admin/www/bugs.html
new file mode 100644
index 00000000..8c174924
--- /dev/null
+++ b/admin/www/bugs.html
@@ -0,0 +1,166 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:31:20 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Bugs and Patches
+
+-->
+
+<head>
+<title>Bugs and Patches</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Bugs and Patches</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://sourceforge.net/bugs/?group_id=103">Bug Tracker</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://sourceforge.net/patch/?group_id=103">Patch Manager</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://sourceforge.net/projects/mailman">Mailman Project</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><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..  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>Be sure to select the right <em>group</em> for your bug or patch,
+e.g. <em>Mailman 2.1</em>.  Failing to do so may cause your submission
+to get overlooked.  It is also recommended that you email a note about
+your submission to the
+<a href="http://mail.python.org/mailman/listinfo/mailman-developers"
+>mailman-developers</a> mailing list, but don't rely on just the email
+to get the attention of the Mailman developers.
+
+
+</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 00000000..937a6af9
--- /dev/null
+++ b/admin/www/devs.ht
@@ -0,0 +1,93 @@
+Title: Mailman Developer Resources
+Links:
+Other-links:
+    <h3>Developer Exits</h3>
+    <li><a href="http://sourceforge.net/projects/mailman">SourceForge Project Page</a>
+    <li><a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/">Mailman Wiki</a>
+    <li><a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanThreePointOh">Mailman 3.0 Wiki</a>
+    <li><a href="http://mail.python.org/mailman/listinfo/mailman-developers">mailman-developers list</a>
+    <li><a href="http://demo.iuveno-net.de/iuveno/Products/ZMailman/">ZMailman</a>
+    
+<h3>Developer Resources</h3>
+
+If you're the kind of person who loves to get elbow deep in code,
+there are lots of opportunities to dig into Mailman.  You may want to
+find a project on our Mailman
+<a href="todo.html">TODO list</a> or on the
+<a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/">Mailman
+design notes wiki</a>.  Because Wikis are intended to be
+collaborative, you're free to contribute to this page in true Wiki
+fashion.  You will also definitely want to subscribe
+to the <a href="http://mail.python.org/mailman/listinfo/mailman-developers"
+>mailman-developers</a> mailing list.
+
+<h3>SourceForge Project Page</h3>
+
+Developers should start with the
+<a href="http://sourceforge.net/projects/mailman">Mailman project at
+SourceForge</a>.  All patches and bugs should be submitted here so
+they won't get lost, although it is also requested that you inform the
+mailman-developers list about your submissions.
+
+<h3>IRC</h3>
+
+Some of the Mailman developers also occasionally hang out on the
+<em>mailman</em> IRC channel at openprojects.net, though attendance
+has been spotty lately.
+
+<!--table-stop-->
+
+<h3>Future plans</h3>
+
+Now that Mailman 2.1 has been released, I want to start thinking about
+what will be in <a
+href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanThreePointOh">Mailman
+3.0</a>.  I intend to use the wiki for most design artifacts, and the
+mailman-developers mailing list for most discussions.  The items that
+are high on my list (which is by no means complete or definitive)
+include:
+
+<ul>
+<li><b>Consolidated user database</b> -- A user should have just one
+account for every mailing list they are members of at a site, and they
+should be able to manage all their options through this account.
+It should be possible to integrate these databases with a site's
+existing user management system to reduce duplication of data and
+effort.
+
+<p><li><b>Unified template system</b> -- Mailman has a somewhat fractured
+and inconvenient templating system, using both a homegrown HTML object
+model in Python and coarse templates filled in with data at rendering
+time.  It can be near impossible to change the look and feel of the
+administration pages, and a small change to the u/i of other pages
+requires updates in all supported languages.  I want to use a
+templating system like
+<a href="http://dev.zope.org/Wikis/DevSite/Projects/ZPT/">ZPT</a> or
+<a href="http://www.mems-exchange.org/software/quixote/">Quixote</a>.
+Actually, I plan to generalize the web interface so that many different
+templating systems could be used, although we'll pick one to ship by
+default.
+
+<p><li><b>A Real Database</b> -- Mailman uses an inefficient persistency
+system based on Python pickles, and every mailing list has its own
+pickled state.  This has several disadvantages, including poor
+scalability, difficulty in doing cross-mailing list operations, and
+the virtual host limitation on list names.  Mailman 3.0 will use a
+real database, perhaps based on
+<a href="http://www.zope.org/Wikis/ZODB/">ZODB</a> or
+<a href="http://www.sleepycat.com">BerkeleyDB</a>.  Again, the goal is
+to generalize the interface to the backend database so that others can
+be used, but choose one and ship it by default.
+
+<p><li><b>Component Architecture</b> -- Zope3's
+<a href="http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/"
+>component architecture</a> provides some very nice organizational
+tools and software development methodologies.  We'll be adopting many
+of these for Mailman 3.0, which will allow us to do the kinds of
+templating and database generalization described above.
+</ul>
+
+Stephan Richter has let an effort called
+<a href="http://demo.iuveno-net.de/iuveno/Products/ZMailman/"
+>ZMailman</a> for integrating Zope and Mailman.  I consider this a
+proof of concept of some of the ideas outlined above.
diff --git a/admin/www/devs.html b/admin/www/devs.html
new file mode 100644
index 00000000..41d1eb3f
--- /dev/null
+++ b/admin/www/devs.html
@@ -0,0 +1,212 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:21 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Developer Resources
+
+-->
+
+<head>
+<title>Mailman Developer Resources</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<b>Developers</b>
+    </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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Developer Exits
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://sourceforge.net/projects/mailman">SourceForge Project Page</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/">Mailman Wiki</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanThreePointOh">Mailman 3.0 Wiki</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://mail.python.org/mailman/listinfo/mailman-developers">mailman-developers list</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://demo.iuveno-net.de/iuveno/Products/ZMailman/">ZMailman</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Developer Resources</h3>
+
+If you're the kind of person who loves to get elbow deep in code,
+there are lots of opportunities to dig into Mailman.  You may want to
+find a project on our Mailman
+<a href="todo.html">TODO list</a> or on the
+<a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/">Mailman
+design notes wiki</a>.  Because Wikis are intended to be
+collaborative, you're free to contribute to this page in true Wiki
+fashion.  You will also definitely want to subscribe
+to the <a href="http://mail.python.org/mailman/listinfo/mailman-developers"
+>mailman-developers</a> mailing list.
+
+<h3>SourceForge Project Page</h3>
+
+Developers should start with the
+<a href="http://sourceforge.net/projects/mailman">Mailman project at
+SourceForge</a>.  All patches and bugs should be submitted here so
+they won't get lost, although it is also requested that you inform the
+mailman-developers list about your submissions.
+
+<h3>IRC</h3>
+
+Some of the Mailman developers also occasionally hang out on the
+<em>mailman</em> IRC channel at openprojects.net, though attendance
+has been spotty lately.
+
+<!--table-stop-->
+
+<h3>Future plans</h3>
+
+Now that Mailman 2.1 has been released, I want to start thinking about
+what will be in <a
+href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanThreePointOh">Mailman
+3.0</a>.  I intend to use the wiki for most design artifacts, and the
+mailman-developers mailing list for most discussions.  The items that
+are high on my list (which is by no means complete or definitive)
+include:
+
+<ul>
+<li><b>Consolidated user database</b> -- A user should have just one
+account for every mailing list they are members of at a site, and they
+should be able to manage all their options through this account.
+It should be possible to integrate these databases with a site's
+existing user management system to reduce duplication of data and
+effort.
+
+<p><li><b>Unified template system</b> -- Mailman has a somewhat fractured
+and inconvenient templating system, using both a homegrown HTML object
+model in Python and coarse templates filled in with data at rendering
+time.  It can be near impossible to change the look and feel of the
+administration pages, and a small change to the u/i of other pages
+requires updates in all supported languages.  I want to use a
+templating system like
+<a href="http://dev.zope.org/Wikis/DevSite/Projects/ZPT/">ZPT</a> or
+<a href="http://www.mems-exchange.org/software/quixote/">Quixote</a>.
+Actually, I plan to generalize the web interface so that many different
+templating systems could be used, although we'll pick one to ship by
+default.
+
+<p><li><b>A Real Database</b> -- Mailman uses an inefficient persistency
+system based on Python pickles, and every mailing list has its own
+pickled state.  This has several disadvantages, including poor
+scalability, difficulty in doing cross-mailing list operations, and
+the virtual host limitation on list names.  Mailman 3.0 will use a
+real database, perhaps based on
+<a href="http://www.zope.org/Wikis/ZODB/">ZODB</a> or
+<a href="http://www.sleepycat.com">BerkeleyDB</a>.  Again, the goal is
+to generalize the interface to the backend database so that others can
+be used, but choose one and ship it by default.
+
+<p><li><b>Component Architecture</b> -- Zope3's
+<a href="http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/"
+>component architecture</a> provides some very nice organizational
+tools and software development methodologies.  We'll be adopting many
+of these for Mailman 3.0, which will allow us to do the kinds of
+templating and database generalization described above.
+</ul>
+
+Stephan Richter has let an effort called
+<a href="http://demo.iuveno-net.de/iuveno/Products/ZMailman/"
+>ZMailman</a> for integrating Zope and Mailman.  I consider this a
+proof of concept of some of the ideas outlined above.
+
+</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 00000000..29ac84ba
--- /dev/null
+++ b/admin/www/doco-links.h
@@ -0,0 +1,7 @@
+<!-- -*- html -*- -->
+<h3>Documentation</h3>
+<li><a href="docs.html">Overview</a>
+<li><a href="users.html">Users</a>
+<li><a href="admins.html">List Managers</a>
+<li><a href="site.html">Site Administrators</a>
+<li><a href="i18n.html">Translators</a>
diff --git a/admin/www/docs.ht b/admin/www/docs.ht
new file mode 100644
index 00000000..6372be36
--- /dev/null
+++ b/admin/www/docs.ht
@@ -0,0 +1,66 @@
+Title: Mailman Documentation
+Links: doco-links.h
+Other-links:
+    <h3>Exits</h3>
+    <li><a href="http://www.python.org/cgi-bin/faqw-mm.py">FAQ Wizard</a>
+    <li><a href="http://staff.imsa.edu/~ckolar/mailman">Chris Kolar's Docs</a>
+    <li><a href="http://www.exim.org/howto/mailman.html">Exim HOWTO</a>
+
+<h3>Mailman Documentation</h3>
+
+On-line documentation for Mailman 2.1 is still under construction, but
+is organized among the following audiences:
+
+<ul>
+<li><a href="users.html"><b>Users</b></a> -- anybody who is a member
+    of a mailing list managed by Mailman.  This documentation explains
+    how you can subscribe and unsubscribe from mailing lists, how to
+    change your personal options, and how to interact with other parts
+    of the Mailman system.
+
+<p><li><a href="admins.html"><b>List Managers</b></a> -- anybody who
+    is a list administrator or moderator for a mailing list.  This
+    documentation goes into all the gory details about how to set up
+    your lists, what the various options mean and control, and how to
+    manage the membership of your mailing list.
+
+<p><li><a href="site.html"><b>Site Administrators</b></a> -- anybody
+    who is setting up a Mailman site.  This documentation contains all
+    the information about installing Mailman, integrating it with your
+    mail and web servers, setting list defaults, configuring virtual
+    domains, and enabling various options for your list
+    administrators.  This documentation also gives some hints on how
+    to tune Mailman for optimal performance.
+
+<p><li><a href="i18n.html"><b>Translators</b></a> -- anybody who is
+    contributing to internationalization support for Mailman.  This
+    describes contact addresses for the current language champions and
+    tells you what you need to do if you want to contribute a new
+    language translation to the project (more are always welcome!).
+</ul>
+
+<h3>Other Resources</h3>
+
+<p>The <a href="faq.html">Frequently Asked Questions (FAQ)</a> is
+available to answer the most common questions.  See also the community
+driven <a href="http://www.python.org/cgi-bin/faqw-mm.py">Mailman
+FAQ Wizard</a>.  Feel free to add or correct entries in the FAQ Wizard
+-- this is your resource for helping your colleagues.  The password is
+<em>Mailman</em> (yes, we use the honor system here).
+
+<p>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://staff.imsa.edu/~ckolar/index.htm">Chris Kolar</a> has made
+available <a href="http://staff.imsa.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 mailer</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/docs.html b/admin/www/docs.html
new file mode 100644
index 00000000..35f1ffc7
--- /dev/null
+++ b/admin/www/docs.html
@@ -0,0 +1,200 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:21 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Documentation
+
+-->
+
+<head>
+<title>Mailman Documentation</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<b>Documentation</b>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Documentation
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Overview</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="admins.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="site.html">Site Administrators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="i18n.html">Translators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/cgi-bin/faqw-mm.py">FAQ Wizard</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://staff.imsa.edu/~ckolar/mailman">Chris Kolar's Docs</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.exim.org/howto/mailman.html">Exim HOWTO</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Mailman Documentation</h3>
+
+On-line documentation for Mailman 2.1 is still under construction, but
+is organized among the following audiences:
+
+<ul>
+<li><a href="users.html"><b>Users</b></a> -- anybody who is a member
+    of a mailing list managed by Mailman.  This documentation explains
+    how you can subscribe and unsubscribe from mailing lists, how to
+    change your personal options, and how to interact with other parts
+    of the Mailman system.
+
+<p><li><a href="admins.html"><b>List Managers</b></a> -- anybody who
+    is a list administrator or moderator for a mailing list.  This
+    documentation goes into all the gory details about how to set up
+    your lists, what the various options mean and control, and how to
+    manage the membership of your mailing list.
+
+<p><li><a href="site.html"><b>Site Administrators</b></a> -- anybody
+    who is setting up a Mailman site.  This documentation contains all
+    the information about installing Mailman, integrating it with your
+    mail and web servers, setting list defaults, configuring virtual
+    domains, and enabling various options for your list
+    administrators.  This documentation also gives some hints on how
+    to tune Mailman for optimal performance.
+
+<p><li><a href="i18n.html"><b>Translators</b></a> -- anybody who is
+    contributing to internationalization support for Mailman.  This
+    describes contact addresses for the current language champions and
+    tells you what you need to do if you want to contribute a new
+    language translation to the project (more are always welcome!).
+</ul>
+
+<h3>Other Resources</h3>
+
+<p>The <a href="faq.html">Frequently Asked Questions (FAQ)</a> is
+available to answer the most common questions.  See also the community
+driven <a href="http://www.python.org/cgi-bin/faqw-mm.py">Mailman
+FAQ Wizard</a>.  Feel free to add or correct entries in the FAQ Wizard
+-- this is your resource for helping your colleagues.  The password is
+<em>Mailman</em> (yes, we use the honor system here).
+
+<p>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://staff.imsa.edu/~ckolar/index.htm">Chris Kolar</a> has made
+available <a href="http://staff.imsa.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 mailer</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/download-links.h b/admin/www/download-links.h
new file mode 100644
index 00000000..635a577c
--- /dev/null
+++ b/admin/www/download-links.h
@@ -0,0 +1,6 @@
+<!-- -*- html -*- -->
+<h3>Downloading</h3>
+<li><a href="download.html">Downloading</a>
+<li><a href="version.html">Latest Version</a>
+<li><a href="requirements.html">Requirements</a>
+<li><a href="install.html">Installing</a>
diff --git a/admin/www/download.ht b/admin/www/download.ht
new file mode 100644
index 00000000..617b15b8
--- /dev/null
+++ b/admin/www/download.ht
@@ -0,0 +1,38 @@
+Title: Downloading Mailman
+Links: download-links.h
+
+<h3>Downloading</h3>
+
+Mailman is available from the following sources:
+
+<ul>
+    <li><a href="http://sourceforge.net/project/showfiles.php?group_id=103">SourceForge</a>
+    <li><a href="http://ftp.gnu.org/gnu/mailman/">GNU</a>
+    <li><a href="http://www.list.org/mailman.tar.gz">List.Org</a>
+</ul>
+
+<em>If you're using a command line FTP client, be sure to set the mode
+to binary</em>.  Once you've downloaded the source tarball, you can
+unpack it with the following commands:
+
+<blockquote>
+<pre>
+% cd /usr/local/src
+% tar zxf mailman.tar.gz
+</pre>
+</blockquote>
+
+Note that the file name may have the version number in it,
+e.g. <code>mailman-2.1.tar.gz</code>.
+
+<p>Mailman's tarball unpacks into a directory called
+<code>mailman-xyz</code> where <em>xyz</em> is the version number.
+Note also that some versions of <code>tar</code> don't accept the
+<em>z</em> option.  In that case, you'll need to use the
+<code>gunzip</code> program like so:
+
+<blockquote>
+<pre>
+% gunzip -c mailman.tar.gz | tar xf -
+</pre>
+</blockquote>
diff --git a/admin/www/download.html b/admin/www/download.html
new file mode 100644
index 00000000..3ca2be31
--- /dev/null
+++ b/admin/www/download.html
@@ -0,0 +1,161 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:22 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Downloading Mailman
+
+-->
+
+<head>
+<title>Downloading Mailman</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<b>Download</b>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Downloading
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Downloading</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="version.html">Latest Version</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="requirements.html">Requirements</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="install.html">Installing</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Downloading</h3>
+
+Mailman is available from the following sources:
+
+<ul>
+    <li><a href="http://sourceforge.net/project/showfiles.php?group_id=103">SourceForge</a>
+    <li><a href="http://ftp.gnu.org/gnu/mailman/">GNU</a>
+    <li><a href="http://www.list.org/mailman.tar.gz">List.Org</a>
+</ul>
+
+<em>If you're using a command line FTP client, be sure to set the mode
+to binary</em>.  Once you've downloaded the source tarball, you can
+unpack it with the following commands:
+
+<blockquote>
+<pre>
+% cd /usr/local/src
+% tar zxf mailman.tar.gz
+</pre>
+</blockquote>
+
+Note that the file name may have the version number in it,
+e.g. <code>mailman-2.1.tar.gz</code>.
+
+<p>Mailman's tarball unpacks into a directory called
+<code>mailman-xyz</code> where <em>xyz</em> is the version number.
+Note also that some versions of <code>tar</code> don't accept the
+<em>z</em> option.  In that case, you'll need to use the
+<code>gunzip</code> program like so:
+
+<blockquote>
+<pre>
+% gunzip -c mailman.tar.gz | tar xf -
+</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/faq.ht b/admin/www/faq.ht
new file mode 100644
index 00000000..2fd281d2
--- /dev/null
+++ b/admin/www/faq.ht
@@ -0,0 +1,301 @@
+Title: Mailman Frequently Asked Questions
+
+See also the <a href="http://www.python.org/cgi-bin/faqw-mm.py">Mailman
+FAQ Wizard</a> for more information.
+
+ <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. I'm getting really terrible performance for outgoing messages.  It
+   seems that if the MTA has trouble resolving DNS for any recipients,
+   qrunner just gets really slow clearing the queue.  Any ideas?
+
+</b><br> A. What's likely happening is that your MTA is doing DNS resolution on
+   recipients for messages delivered locally (i.e. from Mailman to
+   your MTA via SMTPDirect.py).  This is a Bad Thing.  You need to
+   turn off synchronous DNS resolution for messages originating from
+   the local host.
+<p>    In Exim, the value to edit is receiver_verify_hosts.  See
+   README.EXIM for details.  Other MTAs have (of course) different
+   parameters and defaults that control this.  First check the README
+   file for your MTA and then consult your MTA's own documentation.
+<p> <b> Q. My list members are complaining about Mailman's List-* headers!
+   What can I do about this?
+
+</b><br> A. These headers are described in RFC 2369 and are added by Mailman
+   for the long-term benefit of end-users.  While discouraged, the
+   list admin can disable these via the General Options page.  See
+   also README.USERAGENT for more information.
+<p> <b> Q. Can I put the user's address in the footer that Mailman adds to
+   each message?
+
+</b><br> A. Yes, in Mailman 2.1.  The site admin needs to enable
+   personalization by setting the following variables in the mm_cfg.py
+   file:
+<p>     VERP_PASSWORD_REMINDERS = 1
+    VERP_PERSONALIZED_DELIVERIES = 1
+    VERP_DELIVERY_INTERVAL = 1
+    VERP_CONFIRMATIONS = 1
+<p>    Once this is done, list admins can enable personalization for
+   regular delivery members (digest deliveries can't be
+   personalized currently).  A personalized list can include the
+   user's address in the footer.
+<p> <b> Q. My users hate HTML in their email and for security reasons, I want
+   to strip out all MIME attachments.  How can I do this?
+
+</b><br> A. Mailman 2.1 has this feature built-in.  See the Content Filtering
+   Options page in the admin interface.
+<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 (unless STEALTH_MODE is enabled), 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>    If you are not getting any log messages in syslog, or in Mailman's
+   own log files, but messages are still not being delivered, then it
+   is likely that qrunner is not running (qrunner is the process that
+   handles all mail in the system).  In Mailman 2.0, qrunner was
+   invoked from cron so make sure your crontab entries for the
+   `mailman' user have been installed.  In Mailman 2.1, qrunner is
+   started with the bin/mailmanctl script, which can be invoked
+   manually, or merged with your OS's init scripts.
+<p> <b> Q. What should I check periodically?
+
+</b><br> A. Many of the scripts have their standard error logged to
+   $prefix/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>    You may want to periodically check the other log files in the logs/
+   directory, perhaps occasionally rotating them with something like
+   the Linux logrotate script.
+<p> <b> Q. 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://mail.python.org/pipermail/mailman-users/1998-November/000150.html">http://mail.python.org/pipermail/mailman-users/1998-November/000150.html</a>
+<p> <b> Q. Still having problems?  Running QMail?
+
+</b><br> A. Make sure that you are using "preline" before calling the "mailman"
+   wrapper:
+<p>        |preline /home/mailman/mail/mailman 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. 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> <b> Q. I want to backup my lists.  What do I need to save?
+
+</b><br> A. See this FAQ wizard entry:
+   <a href="http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.006.htp">http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.006.htp</a>
+<p> <b> Q. How do I rename a list?
+
+</b><br> A. Renaming a list is currently a bit of a pain to do completely
+   correctly, especially if you want to make sure that the old list
+   contacts are automatically forwarded to the new list.  This ought
+   to be easier. :(
+<p>    The biggest problem you have is how to stop mail and web traffic to
+   your list during the transition, and what to do about any mail
+   undelivered to the old list after the move.  I don't think there
+   are any foolproof steps, but here's how you can reduce the risk:
+<p>    - Temporarily disable qrunner.  To do this, you need to edit the
+     user `mailman's crontab entry.  Execute the following command,
+     commenting out the qrunner line when you're dropped into your
+     editor.  Then save the file and quit the editor.
+<p>      % crontab -u mailman -e
+<p>    - Turn off your mail server.  This is mostly harmless since remote
+     MTAs will just keep retrying until you turn it back on, and it's
+     not going to be off for very long.
+<p>    - Next turn off your web server if possible.  This of course means
+     your entire site will be off-line while you make the switch and
+     this may not be acceptable to you.  The next best suggestion is
+     to set up your permanent redirects now for the list you're
+     moving.  This means that anybody looking for the list under its
+     old name will be redirected to the new name, but they'll get
+     errors until you've completed the move.
+<p>      Let's say the old name is "oldname" and the new name is
+     "newname".  Here are some Apache directives that will do the
+     trick, though YMMV:
+<p>      RedirectMatch permanent /mailman/(.*)/oldname(.*) <a href="http://www.dom.ain/mailman/$1/newname$2">http://www.dom.ain/mailman/$1/newname$2</a>
+     RedirectMatch permanent /pipermail/oldname(.*)    <a href="http://www.dom.ain/pipermail/newname$1">http://www.dom.ain/pipermail/newname$1</a>
+<p>      Add these to your httpd.conf file and restart Apache.
+<p>    - Now cd to the directory where you've installed Mailman.  Let's
+     say it's /usr/local/mailman:
+<p>      % cd /usr/local/mailman
+<p>      and cd to the `lists' subdirectory:
+<p>      % cd lists
+<p>      You should now see the directory `oldname'.  Move this to
+     `newname':
+<p>      % mv oldname newname
+<p>    - Now cd to the private archives directory:
+<p>      % cd ../archives/private
+<p>      You will need to move the oldname's .mbox directory, and the
+     .mbox file within that directory.  Don't worry about the public
+     archives; the next few steps will take care of them without
+     requiring you to fiddle around in the file system:
+<p>      % mv oldname.mbox newname.mbox
+     % mv newname.mbox/oldname.mbox newname.mbox/newname.mbox
+<p>    - You now need to run the `bin/move_list' script to update some of
+     the internal archiver paths.  IMPORTANT: Skip this step if you
+     are using Mailman 2.1!
+<p>      % cd ../..
+     % bin/move_list newname
+<p>    - You should now regenerate the public archives:
+<p>      % bin/arch newname
+<p>    - You'll likely need to change some of your list's configuration
+     options, especially if you want to accept postings addressed to
+     the old list on the new list.  Visit the admin interface for your
+     new list:
+<p>      o Go to the General options
+<p>      o Change the "real_name" option to reflect the new list's name,
+       e.g. "Newname"
+<p>      o Change the subject prefix to reflect the new list's name,
+       e.g. "[Newname] " (yes, that's a trailing space character).
+<p>      o Optionally, update other configuration fields like info,
+       description, or welcome_msg.  YMMV.
+<p>      o Save your changes
+<p>      o Go to the Privacy options
+<p>      o Add the old list's address to acceptable_aliases.
+       E.g. "oldname@dom.ain".  This way, (after the /etc/aliases
+       changes described below) messages posted to the old list will
+       not be held by the new list for "implicit destination"
+       approval.
+<p>      o Save your changes
+<p>    - Now you want to update your /etc/aliases file to include the
+     aliases for the new list, and forwards for the old list to the
+     new list.  Note that these instructions are for Sendmail style
+     alias files, adjust to the specifics of how your MTA is set up.
+<p>      o Find the lines defining the aliases for your old list's name
+<p>      o Copy and paste them just below the originals.
+<p>      o Change all the references of "oldname" to "newname" in the
+       pasted stanza.
+<p>      o Now change the targets of the original aliases to forward to
+       the new aliases.  When you're done, you will end up with
+       /etc/aliases entries like the following (YMMV):
+<p>        XXX This needs updating for MM2.1!
+<p>        # Forward the oldname list to the newname list
+       oldname:         newname@dom.ain
+       oldname-request: newname-request@dom.ain
+       oldname-admin:   newname-admin@dom.ain
+       oldname-owner:   newname-owner@dom.ain
+<p>        newname:         "|/usr/local/mailman/mail/mailman post newname"
+       newname-admin:   "|/usr/local/mailman/mail/mailman mailowner newname"
+       newname-request: "|/usr/local/mailman/mail/mailman mailcmd newname"
+       newname-owner:   newname-admin
+<p>      o Run newaliases
+<p>    - Before you restart everything, you want to make one last check.
+     You're looking for files in the qfiles/ directory that may have
+     been addressed to the old list but weren't delivered before you
+     renamed the list.  Do something like the following:
+<p>      % cd /usr/local/mailman/qfiles
+     % grep oldname *.msg
+<p>      If you get no hits, skip to the next step, you've got nothing to
+     worry about.
+<p>      If you did get hits, then things get complicated.  I warn you
+     that the rest of this step is untested. :(
+<p>      For each of the .msg files that were destined for the old list,
+     you need to change the corresponding .db file.  Unfortunately
+     there's no easy way to do this.  Anyway...
+<p>      Save the following Python code in a file called 'hackdb.py':
+<p>      -------------------------hackdb.py
+     import sys
+     import marshal
+     fp = open(sys.argv[1])
+     d = marshal.load(fp)
+     fp.close()
+     d['listname'] = sys.argv[2]
+     fp = open(sys.argv[1], 'w')
+     marshal.dump(d, fp)
+     fp.close()
+     -------------------------
+<p>      And then for each file that matched your grep above, do the
+     following:
+<p>      % python hackdb.py reallylonghexfilenamematch1.db newname
+<p>    - It's now safe to turn your MTA back on.
+<p>    - Turn your qrunner back on by running
+<p>      % crontab -u mailman -e
+<p>      again and this time uncommenting the qrunner line.  Save the file
+     and quit your editor.
+<p>    - Rejoice, you're done.  Send $100,000 in shiny new pennies to the
+     Mailman cabal as your downpayment toward making this easier for
+     the next list you have to rename. :)
+<p> <p>
\ No newline at end of file
diff --git a/admin/www/faq.html b/admin/www/faq.html
new file mode 100644
index 00000000..60c0ec7e
--- /dev/null
+++ b/admin/www/faq.html
@@ -0,0 +1,433 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:25 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Frequently Asked Questions
+
+-->
+
+<head>
+<title>Mailman Frequently Asked Questions</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+See also the <a href="http://www.python.org/cgi-bin/faqw-mm.py">Mailman
+FAQ Wizard</a> for more information.
+
+ <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. I'm getting really terrible performance for outgoing messages.  It
+   seems that if the MTA has trouble resolving DNS for any recipients,
+   qrunner just gets really slow clearing the queue.  Any ideas?
+
+</b><br> A. What's likely happening is that your MTA is doing DNS resolution on
+   recipients for messages delivered locally (i.e. from Mailman to
+   your MTA via SMTPDirect.py).  This is a Bad Thing.  You need to
+   turn off synchronous DNS resolution for messages originating from
+   the local host.
+<p>    In Exim, the value to edit is receiver_verify_hosts.  See
+   README.EXIM for details.  Other MTAs have (of course) different
+   parameters and defaults that control this.  First check the README
+   file for your MTA and then consult your MTA's own documentation.
+<p> <b> Q. My list members are complaining about Mailman's List-* headers!
+   What can I do about this?
+
+</b><br> A. These headers are described in RFC 2369 and are added by Mailman
+   for the long-term benefit of end-users.  While discouraged, the
+   list admin can disable these via the General Options page.  See
+   also README.USERAGENT for more information.
+<p> <b> Q. Can I put the user's address in the footer that Mailman adds to
+   each message?
+
+</b><br> A. Yes, in Mailman 2.1.  The site admin needs to enable
+   personalization by setting the following variables in the mm_cfg.py
+   file:
+<p>     VERP_PASSWORD_REMINDERS = 1
+    VERP_PERSONALIZED_DELIVERIES = 1
+    VERP_DELIVERY_INTERVAL = 1
+    VERP_CONFIRMATIONS = 1
+<p>    Once this is done, list admins can enable personalization for
+   regular delivery members (digest deliveries can't be
+   personalized currently).  A personalized list can include the
+   user's address in the footer.
+<p> <b> Q. My users hate HTML in their email and for security reasons, I want
+   to strip out all MIME attachments.  How can I do this?
+
+</b><br> A. Mailman 2.1 has this feature built-in.  See the Content Filtering
+   Options page in the admin interface.
+<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 (unless STEALTH_MODE is enabled), 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>    If you are not getting any log messages in syslog, or in Mailman's
+   own log files, but messages are still not being delivered, then it
+   is likely that qrunner is not running (qrunner is the process that
+   handles all mail in the system).  In Mailman 2.0, qrunner was
+   invoked from cron so make sure your crontab entries for the
+   `mailman' user have been installed.  In Mailman 2.1, qrunner is
+   started with the bin/mailmanctl script, which can be invoked
+   manually, or merged with your OS's init scripts.
+<p> <b> Q. What should I check periodically?
+
+</b><br> A. Many of the scripts have their standard error logged to
+   $prefix/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>    You may want to periodically check the other log files in the logs/
+   directory, perhaps occasionally rotating them with something like
+   the Linux logrotate script.
+<p> <b> Q. 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://mail.python.org/pipermail/mailman-users/1998-November/000150.html">http://mail.python.org/pipermail/mailman-users/1998-November/000150.html</a>
+<p> <b> Q. Still having problems?  Running QMail?
+
+</b><br> A. Make sure that you are using "preline" before calling the "mailman"
+   wrapper:
+<p>        |preline /home/mailman/mail/mailman 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. 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> <b> Q. I want to backup my lists.  What do I need to save?
+
+</b><br> A. See this FAQ wizard entry:
+   <a href="http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.006.htp">http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.006.htp</a>
+<p> <b> Q. How do I rename a list?
+
+</b><br> A. Renaming a list is currently a bit of a pain to do completely
+   correctly, especially if you want to make sure that the old list
+   contacts are automatically forwarded to the new list.  This ought
+   to be easier. :(
+<p>    The biggest problem you have is how to stop mail and web traffic to
+   your list during the transition, and what to do about any mail
+   undelivered to the old list after the move.  I don't think there
+   are any foolproof steps, but here's how you can reduce the risk:
+<p>    - Temporarily disable qrunner.  To do this, you need to edit the
+     user `mailman's crontab entry.  Execute the following command,
+     commenting out the qrunner line when you're dropped into your
+     editor.  Then save the file and quit the editor.
+<p>      % crontab -u mailman -e
+<p>    - Turn off your mail server.  This is mostly harmless since remote
+     MTAs will just keep retrying until you turn it back on, and it's
+     not going to be off for very long.
+<p>    - Next turn off your web server if possible.  This of course means
+     your entire site will be off-line while you make the switch and
+     this may not be acceptable to you.  The next best suggestion is
+     to set up your permanent redirects now for the list you're
+     moving.  This means that anybody looking for the list under its
+     old name will be redirected to the new name, but they'll get
+     errors until you've completed the move.
+<p>      Let's say the old name is "oldname" and the new name is
+     "newname".  Here are some Apache directives that will do the
+     trick, though YMMV:
+<p>      RedirectMatch permanent /mailman/(.*)/oldname(.*) <a href="http://www.dom.ain/mailman/$1/newname$2">http://www.dom.ain/mailman/$1/newname$2</a>
+     RedirectMatch permanent /pipermail/oldname(.*)    <a href="http://www.dom.ain/pipermail/newname$1">http://www.dom.ain/pipermail/newname$1</a>
+<p>      Add these to your httpd.conf file and restart Apache.
+<p>    - Now cd to the directory where you've installed Mailman.  Let's
+     say it's /usr/local/mailman:
+<p>      % cd /usr/local/mailman
+<p>      and cd to the `lists' subdirectory:
+<p>      % cd lists
+<p>      You should now see the directory `oldname'.  Move this to
+     `newname':
+<p>      % mv oldname newname
+<p>    - Now cd to the private archives directory:
+<p>      % cd ../archives/private
+<p>      You will need to move the oldname's .mbox directory, and the
+     .mbox file within that directory.  Don't worry about the public
+     archives; the next few steps will take care of them without
+     requiring you to fiddle around in the file system:
+<p>      % mv oldname.mbox newname.mbox
+     % mv newname.mbox/oldname.mbox newname.mbox/newname.mbox
+<p>    - You now need to run the `bin/move_list' script to update some of
+     the internal archiver paths.  IMPORTANT: Skip this step if you
+     are using Mailman 2.1!
+<p>      % cd ../..
+     % bin/move_list newname
+<p>    - You should now regenerate the public archives:
+<p>      % bin/arch newname
+<p>    - You'll likely need to change some of your list's configuration
+     options, especially if you want to accept postings addressed to
+     the old list on the new list.  Visit the admin interface for your
+     new list:
+<p>      o Go to the General options
+<p>      o Change the "real_name" option to reflect the new list's name,
+       e.g. "Newname"
+<p>      o Change the subject prefix to reflect the new list's name,
+       e.g. "[Newname] " (yes, that's a trailing space character).
+<p>      o Optionally, update other configuration fields like info,
+       description, or welcome_msg.  YMMV.
+<p>      o Save your changes
+<p>      o Go to the Privacy options
+<p>      o Add the old list's address to acceptable_aliases.
+       E.g. "oldname@dom.ain".  This way, (after the /etc/aliases
+       changes described below) messages posted to the old list will
+       not be held by the new list for "implicit destination"
+       approval.
+<p>      o Save your changes
+<p>    - Now you want to update your /etc/aliases file to include the
+     aliases for the new list, and forwards for the old list to the
+     new list.  Note that these instructions are for Sendmail style
+     alias files, adjust to the specifics of how your MTA is set up.
+<p>      o Find the lines defining the aliases for your old list's name
+<p>      o Copy and paste them just below the originals.
+<p>      o Change all the references of "oldname" to "newname" in the
+       pasted stanza.
+<p>      o Now change the targets of the original aliases to forward to
+       the new aliases.  When you're done, you will end up with
+       /etc/aliases entries like the following (YMMV):
+<p>        XXX This needs updating for MM2.1!
+<p>        # Forward the oldname list to the newname list
+       oldname:         newname@dom.ain
+       oldname-request: newname-request@dom.ain
+       oldname-admin:   newname-admin@dom.ain
+       oldname-owner:   newname-owner@dom.ain
+<p>        newname:         "|/usr/local/mailman/mail/mailman post newname"
+       newname-admin:   "|/usr/local/mailman/mail/mailman mailowner newname"
+       newname-request: "|/usr/local/mailman/mail/mailman mailcmd newname"
+       newname-owner:   newname-admin
+<p>      o Run newaliases
+<p>    - Before you restart everything, you want to make one last check.
+     You're looking for files in the qfiles/ directory that may have
+     been addressed to the old list but weren't delivered before you
+     renamed the list.  Do something like the following:
+<p>      % cd /usr/local/mailman/qfiles
+     % grep oldname *.msg
+<p>      If you get no hits, skip to the next step, you've got nothing to
+     worry about.
+<p>      If you did get hits, then things get complicated.  I warn you
+     that the rest of this step is untested. :(
+<p>      For each of the .msg files that were destined for the old list,
+     you need to change the corresponding .db file.  Unfortunately
+     there's no easy way to do this.  Anyway...
+<p>      Save the following Python code in a file called 'hackdb.py':
+<p>      -------------------------hackdb.py
+     import sys
+     import marshal
+     fp = open(sys.argv[1])
+     d = marshal.load(fp)
+     fp.close()
+     d['listname'] = sys.argv[2]
+     fp = open(sys.argv[1], 'w')
+     marshal.dump(d, fp)
+     fp.close()
+     -------------------------
+<p>      And then for each file that matched your grep above, do the
+     following:
+<p>      % python hackdb.py reallylonghexfilenamematch1.db newname
+<p>    - It's now safe to turn your MTA back on.
+<p>    - Turn your qrunner back on by running
+<p>      % crontab -u mailman -e
+<p>      again and this time uncommenting the qrunner line.  Save the file
+     and quit your editor.
+<p>    - Rejoice, you're done.  Send $100,000 in shiny new pennies to the
+     Mailman cabal as your downpayment toward making this easier for
+     the next list you have to rename. :)
+<p> <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 00000000..dca77bf9
--- /dev/null
+++ b/admin/www/features.ht
@@ -0,0 +1,80 @@
+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>
+
+Here's a brief description of the new features in Mailman 2.1
+The <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/NEWS?rev=HEAD&content-type=text/vnd.viewcvs-markup"
+>NEWS</a> file contains a detailed summary of all new features.
+
+<ul>
+<li>Through-the-web list creation and removal (with automatic
+    support depending on the MTA)
+<li>Multi-lingual support: list web pages and email notices can be in
+    any of nearly two dozen supported language, configurable
+    per-site, per-list, and per-user
+<li> "Real name" support for members
+<li>Much better password-less operation for simple user tasks.
+<li>Support for personalized deliveries and
+    <a href="http://cr.yp.to/proto/verp.txt">VERP</a>-like message
+    delivery for foolproof bounce detection
+<li>Emergency moderation
+<li>MIME-based content filtering, with demime/stripmime like options
+<li>Regular expression based topic filtering
+<li>Better membership management, including searching
+<li>Re-organized administrative requests pages
+<li>Moderated newsgroup support
+<li>A new architecture for the mail delivery subsystem, removing
+    the dependence on cron, for better responsiveness and
+    scalability
+<li>New moderation and privacy controls
+<li>Invitations
+<li>Autoresponse governors
+<li>Users can now change some of their delivery options globally,
+    for all lists at a site, including their password, delivery
+    status, real name, etc.
+<li>Much better MIME and I18n support in the archiver
+<li>A separate "list moderator" role has been added
+<li>Urgent: header support (bypasses digests to reach all users
+    immediately).
+</ul>
+
+Here is a short summary of other features in Mailman.  For details,
+please see the <a href="docs.html">on-line documentation</a>.
+
+<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, and sender-based posting
+    rules.
+<li>Configurable (per-list and per-user) delivery mode
+    <ul><li>Regular (immediate) delivery
+        <li>MIME digest
+        <li>Plain (<a href="http://www.faqs.org/rfcs/rfc1153.html">RFC
+        1153</a>) digests
+    </ul>
+<li>Integrated bounce detection within an extensible framework.
+    Automatic disposition of bouncing addresses (disable,
+    unsubscribe).
+<li>Integrated spam filters
+<li>Built-in web-based 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 GNU/Linux and most Un*x-like systems, compatible with most
+    web servers and browsers, and most SMTP servers.  Requires Python
+    2.1.3 or newer.
+<li>An extensible mail delivery pipeline.
+<li>High-performance mail delivery, with a scalable architecture.
+</ul>
diff --git a/admin/www/features.html b/admin/www/features.html
new file mode 100644
index 00000000..878be8de
--- /dev/null
+++ b/admin/www/features.html
@@ -0,0 +1,217 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:22 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Features
+
+-->
+
+<head>
+<title>Mailman Features</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Features</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Mailman Features</h3>
+
+Here's a brief description of the new features in Mailman 2.1
+The <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/NEWS?rev=HEAD&content-type=text/vnd.viewcvs-markup"
+>NEWS</a> file contains a detailed summary of all new features.
+
+<ul>
+<li>Through-the-web list creation and removal (with automatic
+    support depending on the MTA)
+<li>Multi-lingual support: list web pages and email notices can be in
+    any of nearly two dozen supported language, configurable
+    per-site, per-list, and per-user
+<li> "Real name" support for members
+<li>Much better password-less operation for simple user tasks.
+<li>Support for personalized deliveries and
+    <a href="http://cr.yp.to/proto/verp.txt">VERP</a>-like message
+    delivery for foolproof bounce detection
+<li>Emergency moderation
+<li>MIME-based content filtering, with demime/stripmime like options
+<li>Regular expression based topic filtering
+<li>Better membership management, including searching
+<li>Re-organized administrative requests pages
+<li>Moderated newsgroup support
+<li>A new architecture for the mail delivery subsystem, removing
+    the dependence on cron, for better responsiveness and
+    scalability
+<li>New moderation and privacy controls
+<li>Invitations
+<li>Autoresponse governors
+<li>Users can now change some of their delivery options globally,
+    for all lists at a site, including their password, delivery
+    status, real name, etc.
+<li>Much better MIME and I18n support in the archiver
+<li>A separate "list moderator" role has been added
+<li>Urgent: header support (bypasses digests to reach all users
+    immediately).
+</ul>
+
+Here is a short summary of other features in Mailman.  For details,
+please see the <a href="docs.html">on-line documentation</a>.
+
+<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, and sender-based posting
+    rules.
+<li>Configurable (per-list and per-user) delivery mode
+    <ul><li>Regular (immediate) delivery
+        <li>MIME digest
+        <li>Plain (<a href="http://www.faqs.org/rfcs/rfc1153.html">RFC
+        1153</a>) digests
+    </ul>
+<li>Integrated bounce detection within an extensible framework.
+    Automatic disposition of bouncing addresses (disable,
+    unsubscribe).
+<li>Integrated spam filters
+<li>Built-in web-based 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 GNU/Linux and most Un*x-like systems, compatible with most
+    web servers and browsers, and most SMTP servers.  Requires Python
+    2.1.3 or newer.
+<li>An extensible mail delivery pipeline.
+<li>High-performance mail delivery, with a scalable architecture.
+</ul>
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/help.ht b/admin/www/help.ht
new file mode 100644
index 00000000..fa6fe4bd
--- /dev/null
+++ b/admin/www/help.ht
@@ -0,0 +1,24 @@
+Title: Mailman Help
+Other-links:
+    <h3>Help</h3>
+    <li><a href="faq.html">FAQ</a>
+    <li><a href="http://www.python.org/cgi-bin/faqw-mm.py">FAQ
+        Wizard</a> (Exit)
+    <li><a href="lists.html">Mailing lists</a>
+
+<h3>Help</h3>
+
+There are many resources available for those who need help with
+Mailman, beyond the <a href="docs.html">on-line documentation</a>.  If
+you are having problems installing or configuring Mailman, or if you
+have questions about what Mailman can do, you should probably start
+with the <a href="faq.html">FAQ</a>, and the community driven
+<a href="http://www.python.org/cgi-bin/faqw-mm.py">FAQ Wizard</a>.
+
+<p>Beyond that, please use the <a href="lists.html">discussion
+lists</a> for asking questions.  There are lots of very helpful and
+knowledgeable people on the lists who can help.  Probably the most
+helpful will be the <a href="http://listowner.org/">Listowners</a>
+mailing list and the
+<a href="http://mail.python.org/mailman/listinfo/mailman-users"
+>mailman-users</a> mailing lists.
diff --git a/admin/www/help.html b/admin/www/help.html
new file mode 100644
index 00000000..e70186b2
--- /dev/null
+++ b/admin/www/help.html
@@ -0,0 +1,165 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:22 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Help
+
+-->
+
+<head>
+<title>Mailman Help</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<b>Help</b>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Help
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="faq.html">FAQ</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/cgi-bin/faqw-mm.py">FAQ
+ Wizard</a> (Exit)
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="lists.html">Mailing lists</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Help</h3>
+
+There are many resources available for those who need help with
+Mailman, beyond the <a href="docs.html">on-line documentation</a>.  If
+you are having problems installing or configuring Mailman, or if you
+have questions about what Mailman can do, you should probably start
+with the <a href="faq.html">FAQ</a>, and the community driven
+<a href="http://www.python.org/cgi-bin/faqw-mm.py">FAQ Wizard</a>.
+
+<p>Beyond that, please use the <a href="lists.html">discussion
+lists</a> for asking questions.  There are lots of very helpful and
+knowledgeable people on the lists who can help.  Probably the most
+helpful will be the <a href="http://listowner.org/">Listowners</a>
+mailing list and the
+<a href="http://mail.python.org/mailman/listinfo/mailman-users"
+>mailman-users</a> mailing lists.
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/i18n.ht b/admin/www/i18n.ht
new file mode 100644
index 00000000..b40d3393
--- /dev/null
+++ b/admin/www/i18n.ht
@@ -0,0 +1,167 @@
+Title: Internationalization
+Links: doco-links.h
+
+<h3>Internationalization</h3>
+
+Mailman 2.1 is fully internationalized.  This means you can add
+translations of all the email and web templates so that your users can
+interact with your mailing lists in their native language.
+Internationalization is handled as follows:
+
+<ul>
+    <li>Each Mailman installation has a server default language.
+    Mailman ships with US English as the server default.
+
+    <p><li>Mailman comes with many supported languages, and if your
+    language is on that list, it will just work.
+
+    <p><li>Individual list owners can choose which languages they'd
+    like their mailing list to support from the suite of site-enabled
+    languages.  The list owner can also select the list's default
+    language.  Mailing lists can thus be monolingual (with English or
+    any other installed language as the default), or they can be
+    multilingual.
+
+    <p><li>Individual users can choose what their preferred language
+    is, from the set of list-enabled languages.  Thus, if a list is
+    multilingual, the user can choose which language they'd prefer
+    when interacting with Mailman.
+</ul>
+
+It must be noted that Mailman never actually translates the messages
+that flow through its mailing lists.  It's up to the list members to
+adhere to their community's language conventions.
+
+<h3>Mailman Language Champions</h3>
+
+Each language translation has a champion who coordinates updates and
+submits them to the Mailman project.  If the language you are
+interested is listed here, please contact the champion for details.
+If your language is not listed here, or if you have general questions
+about I18N Mailman, please contact the
+<a href="http://mail.python.org/mailman/listinfo/mailman-i18n"
+>mailman-i18n@python.org</a> mailing list.
+
+<p>We are investigating using the
+<a href="http://www.iro.umontreal.ca/contrib/po/HTML/">Translation
+Project</a> for future language support.
+
+<dl>
+    <p><dt><b>Catalan</b></dt>
+    <dd><a href="mailto:jordi@debian.org">Jordi Mallach</a> is heading
+    up the Catalan translation effort.
+
+    <p><dt><b>Chinese</b> Simplified (GB), and Big5</dt>
+    <dd><a href="mailto:max.yu@turbolinux.com.cn">Max Yu</a> heads up
+    the Simplified Chinese translation effort.  Michael Fang
+    contributed a Big5 mailman.po file, but I've had some trouble
+    converting it to a .mo file with msgfmt.  Assistance would be
+    greatly appreciated!
+
+    <p><dt><b>Czech</b></dt>
+    <dd><a href="mailto:dan@ohnesorg.cz">Dan Ohnesorg</a> heads up
+    the Czech translation effort, which has been assisted by
+    <a href="mailto:stan@krnovsko.cz">V. Stanovsky</a>.</dd>
+
+    <p><dt><b>Dutch</b></dt>
+    <dd><a href="mailto:danny@terweij.nl">Danny Terweij</a> and
+    <a href="mailto:sander@steffann.nl">Sander Steffann</a> head up
+    the Dutch translation.
+
+    <p><dt><b>Estonian</b></dt>
+    <dd><a href="mailto:duke@linux.ee">Anti Veeranna</a> heads up the
+    Estonian translation effort.
+
+    <p><dt><b>Finnish</b></dt>
+    <dd><a href="mailto:pekka.haavisto@mtt.fi">Pekka Haavisto</a>
+    heads up the Finnish translation effort.
+
+    <p><dt><b>French</b></dt>
+    <dd><a href="mailto:george@lyon.inserm.fr">Pascal GEORGE</a> and
+    <a href="mailto:wilane@yahoo.com">Ousmane Wilane</a> head up the
+    French translation effort, with a mailing list hosted by
+    <a href="mailto:Fil@rezo.net">Fil</a> at
+    <a href="http://listes.rezo.net/mailman/listinfo/mailman-fr"
+    >http://listes.rezo.net/mailman/listinfo/mailman-fr</a>.
+
+    <p><dt><b>German</b></dt>
+    <dd><a href="mailto:p.heinlein@jpberlin.de">Peer Heinlein</a> is
+    now the German translation champion.
+
+    <p><dt><b>Hungarian</b></dt>
+    <dd><a href="mailto:vizisz@freemail.hu">Vizi Szilard</a>
+    heads up the Hungarian translation effort, with
+    some help from Szabolcs Szigeti and
+    <a href="mailto:Funk.Gabor@hunetkft.hu">Gabor Funk</a>.
+
+    <p><dt><b>Italian</b></dt>
+    <dd><a href="mailto:pioppo@ferrara.linux.it">Simone Piunno</a> is
+    heading up the Italian translations, with help from many others.
+    Simone has created an Italian mailing list for those wishing to
+    help: <a href="http://mailman.ferrara.linux.it/listinfo/mailman-it/"
+    >http://mailman.ferrara.linux.it/listinfo/mailman-it/</a>
+
+    <p><dt><b>Japanese</b></dt>
+    <dd>Tokio Kikuchi maintains the
+    <a href="http://mm.tkikuchi.net/"><em>Japanized Mailman Page</em></a>
+    and also runs a mailing list for Japanese Mailman users, for which
+    the <a href="http://mm.tkikuchi.net/pipermail/mmjp-users/">archives</a>
+    are publically available.
+
+    <p><dt><b>Korean</b></dt>
+    <dd><a href="mailto:song@yaimma.co.kr">song@yaimma.co.kr</a> has
+    volunteered to head up the Korean translation effort.</dd>
+
+    <p><dt><b>Lithuanian</b></dt>
+    <dd><a href="mailto:mantas@akl.lt">Mantas Kriauciunas</a> has
+    contributed a Lithuanian translation.
+
+    <p><dt><b>Norwegian</b></dt>
+    <dd><a href="mailto:Daniel.Buchmann@bibsys.no">Daniel Buchmann</a>
+    heads up the Norwegian translation effort.  See also his
+    <a href="http://www.bibsys.no/~db/MM21">Norwegian Mailman Page</a>.
+    </dd>
+
+    <p><dt><b>Polish</b></dt>
+    <dd>Contrary to what you might think knowing my last name, I don't
+    know a word of Polish. :)  Fortunately,
+    <a href="mailto:Pawel.Kolodziejczyk@comarch.pl">Pawel
+    Kolodziejczyk</a>, <a href="mailto:wanted@mwd.pl">Marcin
+    Sochacki</a>, and
+    <a href="mailto:m.zaborowski@il.pw.edu.pl">Marcin Zaborowski</a>
+    have volunteered to spearhead the Polish
+    translations.
+
+    <p><dt><b>Portuguese</b></dt>
+    <dd>The following folks are working on the Portuguese
+    translations:
+    <ul>
+    <li><a href="mailto:gleydson.mazioli@ima.sp.gov.br">Gleydson
+        Mazioli da Silva</a>
+    <li><a href="mailto:samarta@ci.uc.pt">João Sá Marta</a>
+    <li><a href="mailto:queiroz@ccuec.unicamp.br">Rubens Queiroz de
+        Almeida</a>,
+    <li><a href="mailto:aleck@unesp.br">Aleck Zander</a>
+    <li><a href="mailto:joseroberto@dicaslinux.com.br">Jose Roberto Kerne</a>.
+    </ul>
+    They are working on both the Brazilian (pt_BR) and Portuguese (pt_PT)
+    translations.
+
+    <p><dt><b>Russian</b></dt>
+    <dd><a href="mailto:mss@mawhrin.net">Mikhail Sobolev</a>
+    has volunteered to head up the Russian translation effort.  There
+    is also a <a href="mailto:mailman-ru@only.mawhrin.net">Russian
+    Mailman list</a> for discussion of the Russian translation.
+
+    <p><dt><b>Spanish</b></dt>
+    <dd><a href="mailto:jcrey@uma.es">Juan Carlos Rey Anaya</a> heads
+    up the Spanish translations.
+
+    <p><dt><b>Swedish</b></dt>
+    <dd><a href="mailto:information@arvika.se">Eva &Ouml;sterlind</a>
+    heads up the Swedish translation effort, with help from our
+    Norwegian champion
+    <a href="mailto:Daniel.Buchmann@bibsys.no">Daniel Buchmann</a>.
+
+</dl>
+
diff --git a/admin/www/i18n.html b/admin/www/i18n.html
new file mode 100644
index 00000000..55249df5
--- /dev/null
+++ b/admin/www/i18n.html
@@ -0,0 +1,293 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Mon Dec 30 23:25:30 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Internationalization
+
+-->
+
+<head>
+<title>Internationalization</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Documentation
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="docs.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="admins.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="site.html">Site Administrators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Translators</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Internationalization</h3>
+
+Mailman 2.1 is fully internationalized.  This means you can add
+translations of all the email and web templates so that your users can
+interact with your mailing lists in their native language.
+Internationalization is handled as follows:
+
+<ul>
+    <li>Each Mailman installation has a server default language.
+    Mailman ships with US English as the server default.
+
+    <p><li>Mailman comes with many supported languages, and if your
+    language is on that list, it will just work.
+
+    <p><li>Individual list owners can choose which languages they'd
+    like their mailing list to support from the suite of site-enabled
+    languages.  The list owner can also select the list's default
+    language.  Mailing lists can thus be monolingual (with English or
+    any other installed language as the default), or they can be
+    multilingual.
+
+    <p><li>Individual users can choose what their preferred language
+    is, from the set of list-enabled languages.  Thus, if a list is
+    multilingual, the user can choose which language they'd prefer
+    when interacting with Mailman.
+</ul>
+
+It must be noted that Mailman never actually translates the messages
+that flow through its mailing lists.  It's up to the list members to
+adhere to their community's language conventions.
+
+<h3>Mailman Language Champions</h3>
+
+Each language translation has a champion who coordinates updates and
+submits them to the Mailman project.  If the language you are
+interested is listed here, please contact the champion for details.
+If your language is not listed here, or if you have general questions
+about I18N Mailman, please contact the
+<a href="http://mail.python.org/mailman/listinfo/mailman-i18n"
+>mailman-i18n@python.org</a> mailing list.
+
+<p>We are investigating using the
+<a href="http://www.iro.umontreal.ca/contrib/po/HTML/">Translation
+Project</a> for future language support.
+
+<dl>
+    <p><dt><b>Catalan</b></dt>
+    <dd><a href="mailto:jordi@debian.org">Jordi Mallach</a> is heading
+    up the Catalan translation effort.
+
+    <p><dt><b>Chinese</b> Simplified (GB), and Big5</dt>
+    <dd><a href="mailto:max.yu@turbolinux.com.cn">Max Yu</a> heads up
+    the Simplified Chinese translation effort.  Michael Fang
+    contributed a Big5 mailman.po file, but I've had some trouble
+    converting it to a .mo file with msgfmt.  Assistance would be
+    greatly appreciated!
+
+    <p><dt><b>Czech</b></dt>
+    <dd><a href="mailto:dan@ohnesorg.cz">Dan Ohnesorg</a> heads up
+    the Czech translation effort, which has been assisted by
+    <a href="mailto:stan@krnovsko.cz">V. Stanovsky</a>.</dd>
+
+    <p><dt><b>Dutch</b></dt>
+    <dd><a href="mailto:danny@terweij.nl">Danny Terweij</a> and
+    <a href="mailto:sander@steffann.nl">Sander Steffann</a> head up
+    the Dutch translation.
+
+    <p><dt><b>Estonian</b></dt>
+    <dd><a href="mailto:duke@linux.ee">Anti Veeranna</a> heads up the
+    Estonian translation effort.
+
+    <p><dt><b>Finnish</b></dt>
+    <dd><a href="mailto:pekka.haavisto@mtt.fi">Pekka Haavisto</a>
+    heads up the Finnish translation effort.
+
+    <p><dt><b>French</b></dt>
+    <dd><a href="mailto:george@lyon.inserm.fr">Pascal GEORGE</a> and
+    <a href="mailto:wilane@yahoo.com">Ousmane Wilane</a> head up the
+    French translation effort, with a mailing list hosted by
+    <a href="mailto:Fil@rezo.net">Fil</a> at
+    <a href="http://listes.rezo.net/mailman/listinfo/mailman-fr"
+    >http://listes.rezo.net/mailman/listinfo/mailman-fr</a>.
+
+    <p><dt><b>German</b></dt>
+    <dd><a href="mailto:p.heinlein@jpberlin.de">Peer Heinlein</a> is
+    now the German translation champion.
+
+    <p><dt><b>Hungarian</b></dt>
+    <dd><a href="mailto:vizisz@freemail.hu">Vizi Szilard</a>
+    heads up the Hungarian translation effort, with
+    some help from Szabolcs Szigeti and
+    <a href="mailto:Funk.Gabor@hunetkft.hu">Gabor Funk</a>.
+
+    <p><dt><b>Italian</b></dt>
+    <dd><a href="mailto:pioppo@ferrara.linux.it">Simone Piunno</a> is
+    heading up the Italian translations, with help from many others.
+    Simone has created an Italian mailing list for those wishing to
+    help: <a href="http://mailman.ferrara.linux.it/listinfo/mailman-it/"
+    >http://mailman.ferrara.linux.it/listinfo/mailman-it/</a>
+
+    <p><dt><b>Japanese</b></dt>
+    <dd>Tokio Kikuchi maintains the
+    <a href="http://mm.tkikuchi.net/"><em>Japanized Mailman Page</em></a>
+    and also runs a mailing list for Japanese Mailman users, for which
+    the <a href="http://mm.tkikuchi.net/pipermail/mmjp-users/">archives</a>
+    are publically available.
+
+    <p><dt><b>Korean</b></dt>
+    <dd><a href="mailto:song@yaimma.co.kr">song@yaimma.co.kr</a> has
+    volunteered to head up the Korean translation effort.</dd>
+
+    <p><dt><b>Lithuanian</b></dt>
+    <dd><a href="mailto:mantas@akl.lt">Mantas Kriauciunas</a> has
+    contributed a Lithuanian translation.
+
+    <p><dt><b>Norwegian</b></dt>
+    <dd><a href="mailto:Daniel.Buchmann@bibsys.no">Daniel Buchmann</a>
+    heads up the Norwegian translation effort.  See also his
+    <a href="http://www.bibsys.no/~db/MM21">Norwegian Mailman Page</a>.
+    </dd>
+
+    <p><dt><b>Polish</b></dt>
+    <dd>Contrary to what you might think knowing my last name, I don't
+    know a word of Polish. :)  Fortunately,
+    <a href="mailto:Pawel.Kolodziejczyk@comarch.pl">Pawel
+    Kolodziejczyk</a>, <a href="mailto:wanted@mwd.pl">Marcin
+    Sochacki</a>, and
+    <a href="mailto:m.zaborowski@il.pw.edu.pl">Marcin Zaborowski</a>
+    have volunteered to spearhead the Polish
+    translations.
+
+    <p><dt><b>Portuguese</b></dt>
+    <dd>The following folks are working on the Portuguese
+    translations:
+    <ul>
+    <li><a href="mailto:gleydson.mazioli@ima.sp.gov.br">Gleydson
+        Mazioli da Silva</a>
+    <li><a href="mailto:samarta@ci.uc.pt">João Sá Marta</a>
+    <li><a href="mailto:queiroz@ccuec.unicamp.br">Rubens Queiroz de
+        Almeida</a>,
+    <li><a href="mailto:aleck@unesp.br">Aleck Zander</a>
+    <li><a href="mailto:joseroberto@dicaslinux.com.br">Jose Roberto Kerne</a>.
+    </ul>
+    They are working on both the Brazilian (pt_BR) and Portuguese (pt_PT)
+    translations.
+
+    <p><dt><b>Russian</b></dt>
+    <dd><a href="mailto:mss@mawhrin.net">Mikhail Sobolev</a>
+    has volunteered to head up the Russian translation effort.  There
+    is also a <a href="mailto:mailman-ru@only.mawhrin.net">Russian
+    Mailman list</a> for discussion of the Russian translation.
+
+    <p><dt><b>Spanish</b></dt>
+    <dd><a href="mailto:jcrey@uma.es">Juan Carlos Rey Anaya</a> heads
+    up the Spanish translations.
+
+    <p><dt><b>Swedish</b></dt>
+    <dd><a href="mailto:information@arvika.se">Eva &Ouml;sterlind</a>
+    heads up the Swedish translation effort, with help from our
+    Norwegian champion
+    <a href="mailto:Daniel.Buchmann@bibsys.no">Daniel Buchmann</a>.
+
+</dl>
+
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/images/PythonPoweredSmall.png b/admin/www/images/PythonPoweredSmall.png
new file mode 100644
index 00000000..081f72e8
--- /dev/null
+++ b/admin/www/images/PythonPoweredSmall.png
diff --git a/admin/www/images/dragonlogo.jpg b/admin/www/images/dragonlogo.jpg
new file mode 100644
index 00000000..e184f3c6
--- /dev/null
+++ b/admin/www/images/dragonlogo.jpg
diff --git a/admin/www/images/logo-70.jpg b/admin/www/images/logo-70.jpg
new file mode 100644
index 00000000..20e19389
--- /dev/null
+++ b/admin/www/images/logo-70.jpg
diff --git a/admin/www/images/logo-lg.jpg b/admin/www/images/logo-lg.jpg
new file mode 100644
index 00000000..e184f3c6
--- /dev/null
+++ b/admin/www/images/logo-lg.jpg
diff --git a/admin/www/images/logo-sm.jpg b/admin/www/images/logo-sm.jpg
new file mode 100644
index 00000000..94a4c011
--- /dev/null
+++ b/admin/www/images/logo-sm.jpg
diff --git a/admin/www/images/mailman.jpg b/admin/www/images/mailman.jpg
new file mode 100644
index 00000000..83c3e8f2
--- /dev/null
+++ b/admin/www/images/mailman.jpg
diff --git a/admin/www/index.ht b/admin/www/index.ht
new file mode 100644
index 00000000..4b97f45d
--- /dev/null
+++ b/admin/www/index.ht
@@ -0,0 +1,59 @@
+Title: Mailman, the GNU Mailing List Manager
+Other-links:
+    <h3>Exits</h3>
+    <li><a href="http://sf.net/projects/mailman">SF Project Page</a>
+    <li><a href="lists.html">Discussion Lists</a>
+    <li><a href="http://www.python.org/">Python</a>
+    <li><a href="http://www.gnu.org/">GNU</a>
+    <li><a href="http://barry.warsaw.us/">Barry Warsaw</a>
+
+
+<h3>Mailman, the GNU Mailing List Manager</h3>
+
+Mailman is free software for managing electronic mail discussion and
+e-newsletter lists.  Mailman is integrated with the web, making it
+easy for users to manage their accounts and for list owners to
+administer their lists.  Mailman supports built-in archiving,
+automatic bounce processing, content filtering, digest delivery, spam
+filters, and more.  See the <a href="features.html">features page</a>
+for details.
+
+<p>Mailman is free software, distributed under the
+<a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public
+License</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>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).
+<!-- Mailman is gender neutral, low carb, kid safe, drug
+free, high octane, slightly lemony flavored... and easier to remember
+than <a href="http://www.eve-golden.com/images/FloobsOPT--OK.jpg">Floob
+Boober Bab Boober Bubs</a>. -->
+
+<h3>Current Version</h3>
+
+<p>Version
+<!-VERSION--->2.1<!-VERSION--->,
+(released on
+<!-DATE--->30-Dec-2002<!-DATE--->)
+is the current released version of Mailman, in production at many
+sites.
+
+<h3>Acknowledgements</h3>
+
+<p>Mailman's lead developer is
+<a href="http://barry.warsaw.us">Barry Warsaw</a> who can be contacted
+at <a href="mailto:barry@python.org">barry@python.org</a>.
+
+<p>Thanks go to
+<a href="http://www.control.com/">Control.com</a> for their
+sponsorship of new Mailman 2.1 features such as the topic filters,
+external membership sources, and "virtual" mailing lists.  Also, a
+huge thanks goes out to my employer <a href="http://www.zope.com">Zope
+Corporation</a> for their support, as well as the
+<a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/ACKNOWLEDGMENTS?rev=HEAD&content-type=text/vnd.viewcvs-markup"
+>list of contributors</a>, bug hunters, big idea people, and others
+who have helped immensely with Mailman's development.
diff --git a/admin/www/index.html b/admin/www/index.html
new file mode 100644
index 00000000..903e9e49
--- /dev/null
+++ b/admin/www/index.html
@@ -0,0 +1,204 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Mon Dec 30 23:30:18 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman, the GNU Mailing List Manager
+
+-->
+
+<head>
+<title>Mailman, the GNU Mailing List Manager</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<b>Home</b>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Home</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://sf.net/projects/mailman">SF Project Page</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/">Python</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.gnu.org/">GNU</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://barry.warsaw.us/">Barry Warsaw</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+
+<h3>Mailman, the GNU Mailing List Manager</h3>
+
+Mailman is free software for managing electronic mail discussion and
+e-newsletter lists.  Mailman is integrated with the web, making it
+easy for users to manage their accounts and for list owners to
+administer their lists.  Mailman supports built-in archiving,
+automatic bounce processing, content filtering, digest delivery, spam
+filters, and more.  See the <a href="features.html">features page</a>
+for details.
+
+<p>Mailman is free software, distributed under the
+<a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public
+License</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>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).
+<!-- Mailman is gender neutral, low carb, kid safe, drug
+free, high octane, slightly lemony flavored... and easier to remember
+than <a href="http://www.eve-golden.com/images/FloobsOPT--OK.jpg">Floob
+Boober Bab Boober Bubs</a>. -->
+
+<h3>Current Version</h3>
+
+<p>Version
+<!-VERSION--->2.1<!-VERSION--->,
+(released on
+<!-DATE--->30-Dec-2002<!-DATE--->)
+is the current released version of Mailman, in production at many
+sites.
+
+<h3>Acknowledgements</h3>
+
+<p>Mailman's lead developer is
+<a href="http://barry.warsaw.us">Barry Warsaw</a> who can be contacted
+at <a href="mailto:barry@python.org">barry@python.org</a>.
+
+<p>Thanks go to
+<a href="http://www.control.com/">Control.com</a> for their
+sponsorship of new Mailman 2.1 features such as the topic filters,
+external membership sources, and "virtual" mailing lists.  Also, a
+huge thanks goes out to my employer <a href="http://www.zope.com">Zope
+Corporation</a> for their support, as well as the
+<a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/ACKNOWLEDGMENTS?rev=HEAD&content-type=text/vnd.viewcvs-markup"
+>list of contributors</a>, bug hunters, big idea people, and others
+who have helped immensely with Mailman's development.
+
+</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 00000000..5774631f
--- /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.ht b/admin/www/install.ht
new file mode 100644
index 00000000..1db5cb81
--- /dev/null
+++ b/admin/www/install.ht
@@ -0,0 +1,17 @@
+Title: Installing Mailman
+Links: download-links.h
+
+<h3>Installing Mailman</h3>
+
+For detailed installation instructions, please see the
+<code>INSTALL</code> file in the source distribution.
+
+<!-- Commented out, but I hope to make this true soon
+
+For detailed installation instructions, see the <em>Installing</em>
+chapter of the <a href="site.html">Site Administrator's Guide</a>. 
+-->
+
+Be sure to read the <code>README</code> and <code>UPGRADING</code>
+files in the source distribution for additional instructions, hints,
+and warnings.
diff --git a/admin/www/install.html b/admin/www/install.html
new file mode 100644
index 00000000..3894dbba
--- /dev/null
+++ b/admin/www/install.html
@@ -0,0 +1,140 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Mon Dec 30 23:25:30 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Installing Mailman
+
+-->
+
+<head>
+<title>Installing Mailman</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Downloading
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="download.html">Downloading</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="version.html">Latest Version</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="requirements.html">Requirements</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Installing</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Installing Mailman</h3>
+
+For detailed installation instructions, please see the
+<code>INSTALL</code> file in the source distribution.
+
+<!-- Commented out, but I hope to make this true soon
+
+For detailed installation instructions, see the <em>Installing</em>
+chapter of the <a href="site.html">Site Administrator's Guide</a>. 
+-->
+
+Be sure to read the <code>README</code> and <code>UPGRADING</code>
+files in the source distribution for additional instructions, hints,
+and warnings.
+
+</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 00000000..f3a20348
--- /dev/null
+++ b/admin/www/inthenews.ht
@@ -0,0 +1,504 @@
+Title: Mailman in Use and in the News
+
+<h3>Mailman in Use and in the News</h3>
+
+Mailman was featured as the Project of the Month in the
+<a href="http://www.linux-mag.com/2002-05/toc.html">May 2002 issue of
+Linux Magazine</a>.
+
+<p>Mailman was featured in a cover story article in the March 1999
+issue of SunWorld (apparently no longer on-line).  The article was
+written by Cameron Laird and Kathryn Soraiz.
+
+<p>Mailman was briefly mentioned in a ZDNet article on GNU/Linux.
+This was picked up by MSNBC.  Unfortunately, both these links also
+appear to be dead now too.
+
+<p>Below are the lists of sites using Mailman or providing list hosting
+services using Mailman.  If you'd like to be included in this list,
+please <a href="mailto:mailman-cabal@python.org">let us know</a>.
+
+<p>The following sites provide mailing list hosting services using
+Mailman.  If you like Mailman but still don't want to install it on
+your own systems, you might consider having your list hosted at one of
+these sites.  Inclusion in this list does <em>not</em> construe an
+endorsement or recommendation by the Mailman development team, nor is
+there any relationship between them and us, beyond their use of our
+free software.  Some of these services may have restrictions or fees
+for use.
+
+<ul>
+    <li><a href="http://www.pair.com/pair/pairlist/">Pair List</a>
+    <!-- Sheryl Coe -->
+    <li><a href="http://www.reportica.net/">Reportica Service
+        Bureau</a>.  Reportica has put up a <a
+        href="http://www.reportica.net/services/lists/host/screen-index.html"
+        >demo of their service</a>.
+    <!-- CarlC -->
+    <li><a href="http://www.carlc.com/">CarlC Internet Services</a>
+</ul>
+
+
+<p>The following sites (in no particular order) are known to use
+Mailman or Mailman technology to run their mailing lists.
+
+<ul>
+    <!-- Chuq von Rospach -->
+    <li><a href="http://lists.apple.com/">Apple Computer, Inc.</a>
+    <!-- Luke Tymowski -->
+    <li><a href="http://lists.us.dell.com/mailman/listinfo">Dell Computers</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.net</a>
+    <!-- Ricardo Kustner -->
+    <li><a href="http://www.freshmeat.net/">FreshMeat</a>
+    <!-- Jason R. Mastaler -->
+    <li><a href="http://www.xemacs.org/">XEmacs.Org</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>
+    <!-- Chris Howells -->
+    <li><a href="http://mail.kde.org/mailman/listinfo">KDE Project</a>
+    <!-- Barry Warsaw -->
+    <li><a href="http://www.python.org/sigs/">Python.Org</a>
+    <li><a href="http://lists.zope.org/">Zope.org</a>
+    <li><a href="http://www.zope.com/">Zope.com</a> (<em>Yay!</em>)
+    <!-- Owen Taylor -->
+    <li><a href="http://mail.gnome.org/">GNOME.Org</a>
+    <!-- Sarah Stapleton-Gray -->
+    <li><a href="http://www.now.org/">National Organization of Women</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>
+    <!-- Markus Grundmann -->
+    <li><a href="http://www.orsn.org/">ORSN, Open Root Server Network
+    in Europe</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>
+    <li><a href="http://www.sunmanagers.org/mailman/listinfo">Sun Managers</a>
+    <li><a href="http://www.linuxmanagers.org/mailman/listinfo">Linux
+    Managers</a>
+    <!-- Bill Hoffman -->
+    <li><a href="http://public.kitware.com/">Visualization Tool Kit
+    (VTK)</a>
+    <!-- J C Lawrence -->
+    <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a>
+    <!-- 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>
+    <!-- Marco Obaid -->
+    <li><a href="http://lists.MUW.Edu/">Mississippi University for Women</a>
+    <!-- Carel Braam -->
+    <li><a href="http://pegasus.tue.nl">Eindhoven University of Technology</a>
+    <!-- Prof. Marcelo Maia Sobral -->
+    <li>University of vale do Itajai, Sao Jose, Brasil
+    <!-- Conal Garrity -->
+    <li><a href="http://www.kvsc.org/">KVSC Radio, St. Cloud State
+    University, MN</a>
+    <!-- Babak Mostaghassi -->
+    <li><a href="http://ill.iut.ac.ir/">Linux Lab of Isfahan
+    University Of Technology</a>
+    <!-- Aly S.P Dharshi -->
+    <li>University of Lethbridge Organization of Residence Students
+    <!-- Courtney V. Bearse -->
+    <li><a href="http://linux.uky.edu/mailman/listinfo/">University of
+    Kentucky</a>
+    <!-- Jonathan Abela -->
+    <li><a href="http://engsoc.queensu.ca">Queen's Engineering</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>
+    <!-- Adam J -->
+    <li><a href="http://dumpshock.com/">dumpshock.com</a>
+    <!-- Christopher Schulte -->
+    <li><a href="http://lists.schulte.org/">home of the linux pptp
+    server (among others)</a>
+    <!-- Matthias Saou -->
+    <li><a href="http://www.aldil.org/">ALDIL, a French free software
+    user group</a>
+    <!-- Bruno Unna -->
+    <li><a href="http://www.iac.com.mx/">Internet de Alta Calidad</a>
+    with some
+    <a href="http://iac.com.mx/mailman/listinfo/">public mailing lists</a>.
+    <!-- Johannes B. Ullrich -->
+    <li><a href="http://dsheild.org/">dsheild.org</a>
+    <!-- Luca "Ghedo" Ghedini -->
+    <li><a href="http://ing.unibo.it">ing.unibo.it</a> and
+    <a href="http://deis.unibo.it">deis.unibo.it</a>, and "lots of
+    virtual domains".
+    <!-- Fred Herman -->
+    <li><a href="http://www.pplug.org/">Pikes Peak Linux Users
+    Group</a> and
+    <li><a href="http://www.springsdanceclub.com">Colorado Springs Dance
+    Club</a>
+    <!-- Matthew Enger -->
+    <li><a href="http://www.dhs.org">www.dhs.org</a>
+    <!-- Jason Wood -->
+    <li><a href="http://lists.ccil.org/">Chester County InterLink</a>
+    (also supporting a number of other non-profits, including the
+    National Associate of Social Workers, Philadelphia region.
+    <!-- Krzysztof Wychowalek -->
+    <li><a href="http://www.most.org.pl">MOST - Polish provider for 
+    Environmental Movement</a>
+    <!-- Ken Kyler -->
+    <li><a href="http://www.elists.org/">eLists.org</a>
+    <!-- kellan -->
+    <li><a href="http://lists.indymedia.org/">IndyMedia</a>
+    <!-- Yasha Harari -->
+    <li><a href="http://mail.anywhereyougo.com/">mail.anywhereyougo.com</a>
+    <!-- Gary Coulbourne -->
+    <li><a href="http://bears.org/">The bearfolks mailing list</a>
+    <!-- Hong Feng -->
+    <li><a href="http://www.rons.net.cn/">Free software site in China</a>
+    <!-- Julio Calvo -->
+    <li><a href="http://listas.unt.edu.ar/mailman/listinfo">Universidad
+    Nacional de Tucuman, Argentina</a>
+    <!-- Christopher VanOosterhout -->
+    <li><a href="http://www.torresen.com/">Torresen Marine, Inc.</a>
+    including their <a href="http://www.torresen.com/newsletters/">primary
+    newsletter</a>
+    <!-- Ned Lilly -->
+    <li><a href="http://www.greatbridge.org/">www.greatbridge.org</a>
+    <!-- Chris Abraham -->
+    <li><a href="http://www.memes.org/mailman/admin">www.memes.org</a>
+    <!-- Joachim, BaWue-Net -->
+    <li><a href="http://www.bawue.de/">BaWue-Net</a>, a local specialty
+    ISP in Southern Germany</a>
+    <!-- Karsten Thygesen -->
+    <li><a href="http://sunsite.dk/">SunSITE.dk</a>
+    <!-- Bob Valiant -->
+    <li><a href="http://seactc.net">Seattle Community Technology Alliance
+    (SCTA)</a>
+    <!-- Chris Dagdigian -->
+    <li><a href="http://www.bioperl.org/">www.bioperl.org</a>,
+    <a href="http://www.biojava.org/">www.biojava.org</a>,
+    <a href="http://www.bioXML.org/">www.bioXML.org</a>,
+    <a href="http://www.biocorba.org/">www.biocorba.org</a>,
+    <a href="http://www.biopython.org/">www.biopython.org</a>,
+    <a href="http://www.open-bio.org/">www.open-bio.org</a>
+    <!-- David Parr -->
+    <li><a href="http://lists.dalsemi.com/">lists.dalsemi.com</a>
+    <!-- Lic. Vladimir Valdespino Mojena -->
+    <li><a href="http://www.cmw.sld.cu/">www.cmw.sld.cu</a>
+    <!-- Parag Mehta -->
+    <li><a href="http://www.ilug-bom.org.in/">Indian Linux Users Group
+    - Mumbai Chapter</a>
+    <!-- Daniel James -->
+    <li><a href="http://linux.org.uk/">linux.org.uk (Alan Cox's
+    site)</a> and <a href="http://linuxuser.co.uk/">linuxuser.co.uk</a>
+    <!-- Richard Shilling -->
+    <li><a href="http://www.beowulf.org/mailman/listinfo/beowulf">Beowulf</a>
+    <!-- Jeff @ SpamCop -->
+    <li><a href="http://spamcop.net">SpamCop</a>, along with
+    <a href="http://news.spamcop.net">Mailman and the archives</a>
+    <!-- Andreas Hasenack -->
+    <li><a href="http://distro.conectiva.com/">distro.conectiva.com</a>
+    <!-- Kathleen Weaver -->
+    <li><a href="http://www.click-l.com/">www.click-l.com</a>
+    <!-- Gregory Keefe -->
+    <li><a href="http://www.hn.org/">Hammernode Internet Services, Int'l</a>
+    <!-- Mop Da Floors -->
+    <li><a href="http://www.wi2600.org/">www.wi2600.org</a>
+    <!-- Jason McGillivray -->
+    <li><a href="http://www.opensourcedirectory.org/">Open-Source Directory</a>
+    <!-- Patrick Lacson -->
+    <li><a href="http://hidetheword.org">hidetheword.org</a>
+    <!-- David Hallowell -->
+    <li><a href="http://www.guardian.co.uk/">Guardian Unlimited (the
+    site of the UK newspaper <em>The Guardian</em>)</a>.
+    <!-- President @ chatster -->
+    <li><a href="http://www.chatster.org/mailman/listinfo/">chatser.org</a>
+    <!-- Jason Kaufman -->
+    <li><a href="http://www.cleaning.com/">Clean Media, Inc.</a>
+    <!-- Daniel Robbins -->
+    <li><a href="http://www.gentoo.org/">Gentoo Linux</a>
+    <!-- Rolando Guerra -->
+    <li><a href="http://listas.rcp.net.pe/">rcp.net.pe</a>
+    <!-- Bharath Chari -->
+    <li><a href="http://www.arachnis.com/">www.arachnis.com</a>
+    <!-- Supreet Sethi -->
+    <li><a href="http://www.sarai.net/">Sarai (New Media Initiative)</a>
+    <!-- Pankaj Kaushal -->
+    <li><a href="http://www.gnu-india.org">The Hurd
+    development/hacking group in India</a>
+    <!-- Quique -->
+    <li><a href="http://www.sindominio.net">sindominio.net</a>
+    <!-- Mike Watterson -->
+    <li><a href="http://www.chesapeakechurch.org">Chesapeake Church</a>
+    <!-- Marcos Rodrigues -->
+    <li><a href="http://www.unc-ct.rct-sc.br">Universidade do
+    Contestado-UnC Curitibanos/SC/Brasil</a>
+    <!-- Quique -->
+    <li><a href="http://sindominio.net">sindominio.net</a>
+    <!-- Damir Horvat -->
+    <li><a href="http://www.voljatel.si">VOLJATEL telekomunikacije d.d.</a>
+    <!-- Rod (Gentle) Ellis -->
+    <li><a href="http://www.JesusList.com">JesusList.com</a>
+    <!-- Jeffery Cann -->
+    <li><a href="http://clue.denver.co.us/">CLUE - Colorado Linux
+    Users and Enthusiasts</a>
+    <!-- Zoltan Arpadffy -->
+    <li><a href="http://www.polarhome.com/">www.polarhome.com</a>
+    <!-- webmaster@closeadeal.com -->
+    <li><a
+    href="http://www.closeadeal.com/mailman/listinfo/eureka_closeadeal.com"
+    >CloseADeal.com</a>
+    <!-- Jim Reisert -->
+    <li><a href="http://lists.contesting.com/mailman/listinfo"
+    >Contesting.com</a>, Amateur ("Ham") Radio lists.
+    <!-- Stephen McKeown -->
+    <li><a href="http://www.jmbarrie.net">http://www.jmbarrie.net</a>
+    <!-- Dennis Du Bois -->
+    <li><a href="http://freelance-seattle.net/">Freelance-Seattle.net</a>
+    <!-- Charles Tucker -->
+    <li><a href="http://www.riverbend.com/">Riverbend Church</a>
+    <!-- Ben Dyer -->
+    <li><a href="http://lists.evolt.org/">Evolt.org</a>
+    <!-- munindo -->
+    <li><a href="http://mail2.factsoft.de/mailman/listinfo/national"
+        >http://mail2.factsoft.de/mailman/listinfo/national</a>
+    <!-- Ignacio Valdez -->
+    <li><a href="http://www.linuxmednews.com">Linux Medical News</a>
+    <!-- Dean Strik -->
+    <li><a href="http://lists.stack.nl/">stack.nl</a>
+    <!-- Jim Goltz -->
+    <li>NFR Security
+    <!-- Stephan Richter -->
+    <li><a href="http://iuveno-net.de/">iuveno-net.de</a>
+    <!-- Johnny Fuerst -->
+    <li><a href="http://mailman.cathat.net/">cathat.net</a>
+    <!-- gulli -->
+    <li><a href="http://www.heise.de/bin/newsletter/listinfo/newsticker"
+    >heise-newsletter</a>, the biggest news-website for
+    it-professionals in Germany.
+    <!-- Alden Gillespy -->
+    <li><a href="http://www.thetestpattern.com/">Test Pattern Radio</a>
+    <!-- Roberto Mogliotti -->
+    <li><a href="http://lists.atlink.it/">ATLink SRL</a>
+    <!-- Daniel Buchmann -->
+    <li><a href="http://www.bibsys.com/english.html">BIBSYS (Library
+    Automation System, Norway)</a>
+    <!-- Tim Lyons -->
+    <li><a href="http://www.digitalvoodoo.org">www.digitalvoodoo.org</a>
+    <!-- Michael Neil Felzien -->
+    <li><a href="http://www.pied.com/">Process Integrated Engineering
+    Design (PIED)</a>
+    <!-- mark roberts -->
+    <li>BBSRC (Bioscience and Biotechnical Scientific Research Council)
+    <!-- Joshua Erdman -->
+    <li><a href="http://www.ernestallen.com">Ernest & Allen</a>
+    <!-- Hank Roth -->
+    <li><a href="http://pnews.org/">pnews.org</a>
+    <!-- Rene Lange -->
+    <li><a href="http://www.tlug.de">Linux Users Group, Germany</a>
+    <!-- switzerland -->
+    <li><a href="http://lists.indymedia.org">indymedia</a>
+    <!-- Keith Patton -->
+    <li><a href="http://www.ethicalmedia.com">Ethical Media Ltd</a>
+    <!-- Leandro Rache Sanchez -->
+    <li><a href="http://www.hipertek.net">Hipertek Ltda</a>, Bogota,
+    Columbia</a>
+    <!-- Yann Forget -->
+    <li><a href="http://mail.ynternet.net/mailman/listinfo"
+    >ynternet.org</a>
+    <!-- Renn -->
+    <li><a href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+    >National Central University, Dept. of Civil Engineering, the 83th</a>
+    <!-- Jesse Trucks -->
+    <li><A HREF="http://list.cyberius.net">Cyberius' Network lists</A>
+    <!-- Erik J. Heels -->
+    <li><a href="http://www.iserver.com">iServer</a> and
+    <a href="http://www.lawlawlaw.com">www.lawlawlaw.com</a>
+    <!-- Peter Verhas -->
+    <li><a href="http://Scriptbasic.com">Scriptbasic.com</a>
+    <!-- webmaster@itxzone.com -->
+    <li><a href="http://www.itxzone.com/">ITXZONE: The Indian IT Zone</a>
+    <!-- renn@cy1000.com.tw -->
+    <li><a
+    href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+    >National Central University, Dept. of Civil Engineering, the 83th</a>
+    <!-- Jerry Feldman -->
+    <li><a href="http://www.blu.org/">Boston Linux and Unix user group</a>
+    <!-- Leandro Rache Sanchez -->
+    <li><a href="http://www.hipertek.net/">Hipertek Ltda.</a>
+    <!-- Jan Kampherbeek -->
+    <li><a href="http://spiderpro.com/">SpiderPro</a>
+    <!-- Porfirio Trincheiras -->
+    <li><a href="http://www.fmh.utl.pt">Faculdade de Motricidade
+    Humana</a> and
+    <a href="http://www.fmv.utl.pt">Faculdade de Medicina Veterinária</a>
+    <!-- info@compamerica.com -->
+    <li><a href="http://www.american-computer.com">American Computer</a>
+    <!-- Bob Radvanovsky -->
+    <li><a href="http://www.unixworks.net">Unixworks</a>
+    <!-- Mats Brante -->
+    <li><a href="http://www.osthyvel.net">Osthyvel.net</a>
+    <!-- Nemeth Tamas -->
+    <li><a href="http://lists.sek.nyme.hu">University of West Hungary</a>
+    <!-- Marc MERLIN -->
+    <li><a href="http://lists.svlug.org/lists/listinfo/">Silicon Valley
+    Linux Users' Group</a>
+    <!-- Bernardo Bernal González -->
+    <li><a href="http://www.fundaciongsr.es">German Sanchez Ruiperez
+    Foundation, Spain</a>
+    <!-- Alejandro G. Sánchez Martínez -->
+    <li><a href="http://www.red-libre.com">www.red-libre.com</a>
+    <!-- Randy Stoeker -->
+    <li><a href="http://comm-org.utoledo.edu">COMM-ORG: The On-Line
+    Conference on Community Organizing</a>
+    <!-- Josenivaldo Benito Junior -->
+    <li>FAI - Faculdades Adamantinenses Integradas
+    <!-- Ravi Starzl -->
+    <li><a href="http://www.oddzz.com">Oddzz</a> and <a
+    href="http://www.casinozz.com">Casinozz</a>.
+    <!-- Don Sizemore -->
+    <li><a href="http://www.ibiblio.org">ibiblio</a>
+    <!-- Marc Bitner -->
+    <li><a href="http://shrplist.umsmed.edu/mailman/listinfo/him-l">University
+    of Mississippi Medical Center HIM Listserve</a>
+    <!-- Eli Caul -->
+    <li><a href="http://www.mirafiori.com">the Fiat Page</a>
+    (automotive), with mailing lists at
+    <a href="http://www.mirafiori.com/lists">this url</a>.
+    <!-- Art Jones -->
+    <li><a href="http://www.meteoritecentral.com/">Meteorite
+    Central</a> via the mailing lists at Pair Networks.
+    <!-- Alstair Hutchinson -->
+    <li><a href="http://www.deviantpc.com">DeviantPC</a>
+    <!-- George D. Holmes -->
+    <li><a href="http://mailman.csce.uark.edu">The Computer Science &
+    Computer Engineering</a> department at the University of Arkansas.
+    <!-- steven -->
+    <li><a href="http://www.shakespeare-monologues.org/">Shakespeare's
+    Monologues</a> with mailing lists at
+    <a
+    href="http://lists.shakespeare-monologues.org/mailman/listinfo/discussion">this url</a>.
+    <!-- Kenneth Irving -->
+    <li><a href="http://www.fq.edu.uy">Universidad de la República,
+    Facultad de Química, Uruguay</a>
+    <!-- Ian McCormack -->
+    <li><a href="http://www.ne4x4.org.uk/">North East 4x4 club</a>
+    <!-- Jörn Nettingsmeier -->
+    <li><a href="http://www.linuxdj.com/audio/lad/">Linux Audio
+    Mailing Lists</a>
+    <!-- Dirk H. Shulz -->
+    <li><a href="http://www.multibyte.de">MultiByte GmbH</a>
+    <!-- Justin Yunke -->
+    <li><a href="http://www.elists.org/">Elists Online</a>
+    <!-- John C. Amodeo -->
+    <li><a href="http://fas.rutgers.edu">FAS - Rutgers, The State
+    University of New Jersey</a>
+    <!-- Lucian Daniel Kafka -->
+    <li><a href="http://www.conexim.com.au">Conexim web hosting Australia</a>
+    <!-- zainul bakri -->
+    <li>National Institute of Health Research and Development, Indonesia.
+    <!-- Chris Olson -->
+    <li><a href="http://astcomm.net/">AST Communications, Inc.</a>
+    <!-- Derek Colley -->
+    <li><a href="http://listserv.sap.com/">SAP</a>
+    <!-- Christian Thamer -->
+    <li><a href="http://www.iwl.com/Support/lists.html">InterWorking Labs</a>
+    <!-- A. Sajjad Zaidi -->
+    <li><a href="http://www.tokyopc.org/">Tokyo PC Users Group</a>
+        with mailing lists <a
+        href="http://www.tokyopc.org/mailman/listinfo/">here</a>.
+    <!-- Dr. David A. Zatz -->
+    <li><a href="http://allpar.com/">Allpar.com (Chrysler enthusiasts)</a>
+    <!-- Donna Hanlon -->
+    <li><a href="http://brainmap.wustl.edu">Van Essen Lab at Washington
+    University School of Medicine</a>
+    <!-- Matt Helsley -->
+    <li><a href="http://linux.ucla.edu">UCLA LUG</a> with mailing
+        lists <a href="http://linux.ucla.edu/mailman/listinfo">here</a>.
+    <!-- Erisian Saint Vinge -->
+    <li><a href="http://www.azone.org/">Azone</a>
+    <!-- Nicolas Cartron -->
+    <li><a href="http://squirrelmail-fr.org">SquirrelMail (French)</a>
+    <!-- Shakaraji Thakor -->
+    <li><a href="http://mail.gnvfc.com/mailman/listinfo">GNFC Ltd</a>
+    <!-- Peter Turner -->
+    <li><a href="http://www.edow.org">Diocese of Washington</a>
+    <!-- Gottfried Hamm -->
+    <li><a href="http://lists.ghks.de/">Gottfried Hamm
+        KommunikationsSysteme</a>
+    <!-- Richard Lippmann -->
+    <li><a href="http://www.zirndorf.de">Cultural events in Zirndorf,
+        Bavaria</a>
+    <!-- Gualter Barbas Baptista -->
+    <li><a href="http://gaia.org.pt">GAIA</a>, with mailing lists at
+        <a href="http://gaia.org.pt/listas/">here</a>.
+    <!-- Ansgar Schmidt -->
+    <li><a href="http://auriga.wearlab.de">Free Mobile Software System</a>
+</ul>
diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html
new file mode 100644
index 00000000..4ff788e5
--- /dev/null
+++ b/admin/www/inthenews.html
@@ -0,0 +1,637 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:23 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman in Use and in the News
+
+-->
+
+<head>
+<title>Mailman in Use and in the News</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Mailman in Use</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Mailman in Use and in the News</h3>
+
+Mailman was featured as the Project of the Month in the
+<a href="http://www.linux-mag.com/2002-05/toc.html">May 2002 issue of
+Linux Magazine</a>.
+
+<p>Mailman was featured in a cover story article in the March 1999
+issue of SunWorld (apparently no longer on-line).  The article was
+written by Cameron Laird and Kathryn Soraiz.
+
+<p>Mailman was briefly mentioned in a ZDNet article on GNU/Linux.
+This was picked up by MSNBC.  Unfortunately, both these links also
+appear to be dead now too.
+
+<p>Below are the lists of sites using Mailman or providing list hosting
+services using Mailman.  If you'd like to be included in this list,
+please <a href="mailto:mailman-cabal@python.org">let us know</a>.
+
+<p>The following sites provide mailing list hosting services using
+Mailman.  If you like Mailman but still don't want to install it on
+your own systems, you might consider having your list hosted at one of
+these sites.  Inclusion in this list does <em>not</em> construe an
+endorsement or recommendation by the Mailman development team, nor is
+there any relationship between them and us, beyond their use of our
+free software.  Some of these services may have restrictions or fees
+for use.
+
+<ul>
+    <li><a href="http://www.pair.com/pair/pairlist/">Pair List</a>
+    <!-- Sheryl Coe -->
+    <li><a href="http://www.reportica.net/">Reportica Service
+        Bureau</a>.  Reportica has put up a <a
+        href="http://www.reportica.net/services/lists/host/screen-index.html"
+        >demo of their service</a>.
+    <!-- CarlC -->
+    <li><a href="http://www.carlc.com/">CarlC Internet Services</a>
+</ul>
+
+
+<p>The following sites (in no particular order) are known to use
+Mailman or Mailman technology to run their mailing lists.
+
+<ul>
+    <!-- Chuq von Rospach -->
+    <li><a href="http://lists.apple.com/">Apple Computer, Inc.</a>
+    <!-- Luke Tymowski -->
+    <li><a href="http://lists.us.dell.com/mailman/listinfo">Dell Computers</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.net</a>
+    <!-- Ricardo Kustner -->
+    <li><a href="http://www.freshmeat.net/">FreshMeat</a>
+    <!-- Jason R. Mastaler -->
+    <li><a href="http://www.xemacs.org/">XEmacs.Org</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>
+    <!-- Chris Howells -->
+    <li><a href="http://mail.kde.org/mailman/listinfo">KDE Project</a>
+    <!-- Barry Warsaw -->
+    <li><a href="http://www.python.org/sigs/">Python.Org</a>
+    <li><a href="http://lists.zope.org/">Zope.org</a>
+    <li><a href="http://www.zope.com/">Zope.com</a> (<em>Yay!</em>)
+    <!-- Owen Taylor -->
+    <li><a href="http://mail.gnome.org/">GNOME.Org</a>
+    <!-- Sarah Stapleton-Gray -->
+    <li><a href="http://www.now.org/">National Organization of Women</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>
+    <!-- Markus Grundmann -->
+    <li><a href="http://www.orsn.org/">ORSN, Open Root Server Network
+    in Europe</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>
+    <li><a href="http://www.sunmanagers.org/mailman/listinfo">Sun Managers</a>
+    <li><a href="http://www.linuxmanagers.org/mailman/listinfo">Linux
+    Managers</a>
+    <!-- Bill Hoffman -->
+    <li><a href="http://public.kitware.com/">Visualization Tool Kit
+    (VTK)</a>
+    <!-- J C Lawrence -->
+    <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a>
+    <!-- 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>
+    <!-- Marco Obaid -->
+    <li><a href="http://lists.MUW.Edu/">Mississippi University for Women</a>
+    <!-- Carel Braam -->
+    <li><a href="http://pegasus.tue.nl">Eindhoven University of Technology</a>
+    <!-- Prof. Marcelo Maia Sobral -->
+    <li>University of vale do Itajai, Sao Jose, Brasil
+    <!-- Conal Garrity -->
+    <li><a href="http://www.kvsc.org/">KVSC Radio, St. Cloud State
+    University, MN</a>
+    <!-- Babak Mostaghassi -->
+    <li><a href="http://ill.iut.ac.ir/">Linux Lab of Isfahan
+    University Of Technology</a>
+    <!-- Aly S.P Dharshi -->
+    <li>University of Lethbridge Organization of Residence Students
+    <!-- Courtney V. Bearse -->
+    <li><a href="http://linux.uky.edu/mailman/listinfo/">University of
+    Kentucky</a>
+    <!-- Jonathan Abela -->
+    <li><a href="http://engsoc.queensu.ca">Queen's Engineering</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>
+    <!-- Adam J -->
+    <li><a href="http://dumpshock.com/">dumpshock.com</a>
+    <!-- Christopher Schulte -->
+    <li><a href="http://lists.schulte.org/">home of the linux pptp
+    server (among others)</a>
+    <!-- Matthias Saou -->
+    <li><a href="http://www.aldil.org/">ALDIL, a French free software
+    user group</a>
+    <!-- Bruno Unna -->
+    <li><a href="http://www.iac.com.mx/">Internet de Alta Calidad</a>
+    with some
+    <a href="http://iac.com.mx/mailman/listinfo/">public mailing lists</a>.
+    <!-- Johannes B. Ullrich -->
+    <li><a href="http://dsheild.org/">dsheild.org</a>
+    <!-- Luca "Ghedo" Ghedini -->
+    <li><a href="http://ing.unibo.it">ing.unibo.it</a> and
+    <a href="http://deis.unibo.it">deis.unibo.it</a>, and "lots of
+    virtual domains".
+    <!-- Fred Herman -->
+    <li><a href="http://www.pplug.org/">Pikes Peak Linux Users
+    Group</a> and
+    <li><a href="http://www.springsdanceclub.com">Colorado Springs Dance
+    Club</a>
+    <!-- Matthew Enger -->
+    <li><a href="http://www.dhs.org">www.dhs.org</a>
+    <!-- Jason Wood -->
+    <li><a href="http://lists.ccil.org/">Chester County InterLink</a>
+    (also supporting a number of other non-profits, including the
+    National Associate of Social Workers, Philadelphia region.
+    <!-- Krzysztof Wychowalek -->
+    <li><a href="http://www.most.org.pl">MOST - Polish provider for 
+    Environmental Movement</a>
+    <!-- Ken Kyler -->
+    <li><a href="http://www.elists.org/">eLists.org</a>
+    <!-- kellan -->
+    <li><a href="http://lists.indymedia.org/">IndyMedia</a>
+    <!-- Yasha Harari -->
+    <li><a href="http://mail.anywhereyougo.com/">mail.anywhereyougo.com</a>
+    <!-- Gary Coulbourne -->
+    <li><a href="http://bears.org/">The bearfolks mailing list</a>
+    <!-- Hong Feng -->
+    <li><a href="http://www.rons.net.cn/">Free software site in China</a>
+    <!-- Julio Calvo -->
+    <li><a href="http://listas.unt.edu.ar/mailman/listinfo">Universidad
+    Nacional de Tucuman, Argentina</a>
+    <!-- Christopher VanOosterhout -->
+    <li><a href="http://www.torresen.com/">Torresen Marine, Inc.</a>
+    including their <a href="http://www.torresen.com/newsletters/">primary
+    newsletter</a>
+    <!-- Ned Lilly -->
+    <li><a href="http://www.greatbridge.org/">www.greatbridge.org</a>
+    <!-- Chris Abraham -->
+    <li><a href="http://www.memes.org/mailman/admin">www.memes.org</a>
+    <!-- Joachim, BaWue-Net -->
+    <li><a href="http://www.bawue.de/">BaWue-Net</a>, a local specialty
+    ISP in Southern Germany</a>
+    <!-- Karsten Thygesen -->
+    <li><a href="http://sunsite.dk/">SunSITE.dk</a>
+    <!-- Bob Valiant -->
+    <li><a href="http://seactc.net">Seattle Community Technology Alliance
+    (SCTA)</a>
+    <!-- Chris Dagdigian -->
+    <li><a href="http://www.bioperl.org/">www.bioperl.org</a>,
+    <a href="http://www.biojava.org/">www.biojava.org</a>,
+    <a href="http://www.bioXML.org/">www.bioXML.org</a>,
+    <a href="http://www.biocorba.org/">www.biocorba.org</a>,
+    <a href="http://www.biopython.org/">www.biopython.org</a>,
+    <a href="http://www.open-bio.org/">www.open-bio.org</a>
+    <!-- David Parr -->
+    <li><a href="http://lists.dalsemi.com/">lists.dalsemi.com</a>
+    <!-- Lic. Vladimir Valdespino Mojena -->
+    <li><a href="http://www.cmw.sld.cu/">www.cmw.sld.cu</a>
+    <!-- Parag Mehta -->
+    <li><a href="http://www.ilug-bom.org.in/">Indian Linux Users Group
+    - Mumbai Chapter</a>
+    <!-- Daniel James -->
+    <li><a href="http://linux.org.uk/">linux.org.uk (Alan Cox's
+    site)</a> and <a href="http://linuxuser.co.uk/">linuxuser.co.uk</a>
+    <!-- Richard Shilling -->
+    <li><a href="http://www.beowulf.org/mailman/listinfo/beowulf">Beowulf</a>
+    <!-- Jeff @ SpamCop -->
+    <li><a href="http://spamcop.net">SpamCop</a>, along with
+    <a href="http://news.spamcop.net">Mailman and the archives</a>
+    <!-- Andreas Hasenack -->
+    <li><a href="http://distro.conectiva.com/">distro.conectiva.com</a>
+    <!-- Kathleen Weaver -->
+    <li><a href="http://www.click-l.com/">www.click-l.com</a>
+    <!-- Gregory Keefe -->
+    <li><a href="http://www.hn.org/">Hammernode Internet Services, Int'l</a>
+    <!-- Mop Da Floors -->
+    <li><a href="http://www.wi2600.org/">www.wi2600.org</a>
+    <!-- Jason McGillivray -->
+    <li><a href="http://www.opensourcedirectory.org/">Open-Source Directory</a>
+    <!-- Patrick Lacson -->
+    <li><a href="http://hidetheword.org">hidetheword.org</a>
+    <!-- David Hallowell -->
+    <li><a href="http://www.guardian.co.uk/">Guardian Unlimited (the
+    site of the UK newspaper <em>The Guardian</em>)</a>.
+    <!-- President @ chatster -->
+    <li><a href="http://www.chatster.org/mailman/listinfo/">chatser.org</a>
+    <!-- Jason Kaufman -->
+    <li><a href="http://www.cleaning.com/">Clean Media, Inc.</a>
+    <!-- Daniel Robbins -->
+    <li><a href="http://www.gentoo.org/">Gentoo Linux</a>
+    <!-- Rolando Guerra -->
+    <li><a href="http://listas.rcp.net.pe/">rcp.net.pe</a>
+    <!-- Bharath Chari -->
+    <li><a href="http://www.arachnis.com/">www.arachnis.com</a>
+    <!-- Supreet Sethi -->
+    <li><a href="http://www.sarai.net/">Sarai (New Media Initiative)</a>
+    <!-- Pankaj Kaushal -->
+    <li><a href="http://www.gnu-india.org">The Hurd
+    development/hacking group in India</a>
+    <!-- Quique -->
+    <li><a href="http://www.sindominio.net">sindominio.net</a>
+    <!-- Mike Watterson -->
+    <li><a href="http://www.chesapeakechurch.org">Chesapeake Church</a>
+    <!-- Marcos Rodrigues -->
+    <li><a href="http://www.unc-ct.rct-sc.br">Universidade do
+    Contestado-UnC Curitibanos/SC/Brasil</a>
+    <!-- Quique -->
+    <li><a href="http://sindominio.net">sindominio.net</a>
+    <!-- Damir Horvat -->
+    <li><a href="http://www.voljatel.si">VOLJATEL telekomunikacije d.d.</a>
+    <!-- Rod (Gentle) Ellis -->
+    <li><a href="http://www.JesusList.com">JesusList.com</a>
+    <!-- Jeffery Cann -->
+    <li><a href="http://clue.denver.co.us/">CLUE - Colorado Linux
+    Users and Enthusiasts</a>
+    <!-- Zoltan Arpadffy -->
+    <li><a href="http://www.polarhome.com/">www.polarhome.com</a>
+    <!-- webmaster@closeadeal.com -->
+    <li><a
+    href="http://www.closeadeal.com/mailman/listinfo/eureka_closeadeal.com"
+    >CloseADeal.com</a>
+    <!-- Jim Reisert -->
+    <li><a href="http://lists.contesting.com/mailman/listinfo"
+    >Contesting.com</a>, Amateur ("Ham") Radio lists.
+    <!-- Stephen McKeown -->
+    <li><a href="http://www.jmbarrie.net">http://www.jmbarrie.net</a>
+    <!-- Dennis Du Bois -->
+    <li><a href="http://freelance-seattle.net/">Freelance-Seattle.net</a>
+    <!-- Charles Tucker -->
+    <li><a href="http://www.riverbend.com/">Riverbend Church</a>
+    <!-- Ben Dyer -->
+    <li><a href="http://lists.evolt.org/">Evolt.org</a>
+    <!-- munindo -->
+    <li><a href="http://mail2.factsoft.de/mailman/listinfo/national"
+        >http://mail2.factsoft.de/mailman/listinfo/national</a>
+    <!-- Ignacio Valdez -->
+    <li><a href="http://www.linuxmednews.com">Linux Medical News</a>
+    <!-- Dean Strik -->
+    <li><a href="http://lists.stack.nl/">stack.nl</a>
+    <!-- Jim Goltz -->
+    <li>NFR Security
+    <!-- Stephan Richter -->
+    <li><a href="http://iuveno-net.de/">iuveno-net.de</a>
+    <!-- Johnny Fuerst -->
+    <li><a href="http://mailman.cathat.net/">cathat.net</a>
+    <!-- gulli -->
+    <li><a href="http://www.heise.de/bin/newsletter/listinfo/newsticker"
+    >heise-newsletter</a>, the biggest news-website for
+    it-professionals in Germany.
+    <!-- Alden Gillespy -->
+    <li><a href="http://www.thetestpattern.com/">Test Pattern Radio</a>
+    <!-- Roberto Mogliotti -->
+    <li><a href="http://lists.atlink.it/">ATLink SRL</a>
+    <!-- Daniel Buchmann -->
+    <li><a href="http://www.bibsys.com/english.html">BIBSYS (Library
+    Automation System, Norway)</a>
+    <!-- Tim Lyons -->
+    <li><a href="http://www.digitalvoodoo.org">www.digitalvoodoo.org</a>
+    <!-- Michael Neil Felzien -->
+    <li><a href="http://www.pied.com/">Process Integrated Engineering
+    Design (PIED)</a>
+    <!-- mark roberts -->
+    <li>BBSRC (Bioscience and Biotechnical Scientific Research Council)
+    <!-- Joshua Erdman -->
+    <li><a href="http://www.ernestallen.com">Ernest & Allen</a>
+    <!-- Hank Roth -->
+    <li><a href="http://pnews.org/">pnews.org</a>
+    <!-- Rene Lange -->
+    <li><a href="http://www.tlug.de">Linux Users Group, Germany</a>
+    <!-- switzerland -->
+    <li><a href="http://lists.indymedia.org">indymedia</a>
+    <!-- Keith Patton -->
+    <li><a href="http://www.ethicalmedia.com">Ethical Media Ltd</a>
+    <!-- Leandro Rache Sanchez -->
+    <li><a href="http://www.hipertek.net">Hipertek Ltda</a>, Bogota,
+    Columbia</a>
+    <!-- Yann Forget -->
+    <li><a href="http://mail.ynternet.net/mailman/listinfo"
+    >ynternet.org</a>
+    <!-- Renn -->
+    <li><a href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+    >National Central University, Dept. of Civil Engineering, the 83th</a>
+    <!-- Jesse Trucks -->
+    <li><A HREF="http://list.cyberius.net">Cyberius' Network lists</A>
+    <!-- Erik J. Heels -->
+    <li><a href="http://www.iserver.com">iServer</a> and
+    <a href="http://www.lawlawlaw.com">www.lawlawlaw.com</a>
+    <!-- Peter Verhas -->
+    <li><a href="http://Scriptbasic.com">Scriptbasic.com</a>
+    <!-- webmaster@itxzone.com -->
+    <li><a href="http://www.itxzone.com/">ITXZONE: The Indian IT Zone</a>
+    <!-- renn@cy1000.com.tw -->
+    <li><a
+    href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+    >National Central University, Dept. of Civil Engineering, the 83th</a>
+    <!-- Jerry Feldman -->
+    <li><a href="http://www.blu.org/">Boston Linux and Unix user group</a>
+    <!-- Leandro Rache Sanchez -->
+    <li><a href="http://www.hipertek.net/">Hipertek Ltda.</a>
+    <!-- Jan Kampherbeek -->
+    <li><a href="http://spiderpro.com/">SpiderPro</a>
+    <!-- Porfirio Trincheiras -->
+    <li><a href="http://www.fmh.utl.pt">Faculdade de Motricidade
+    Humana</a> and
+    <a href="http://www.fmv.utl.pt">Faculdade de Medicina Veterinária</a>
+    <!-- info@compamerica.com -->
+    <li><a href="http://www.american-computer.com">American Computer</a>
+    <!-- Bob Radvanovsky -->
+    <li><a href="http://www.unixworks.net">Unixworks</a>
+    <!-- Mats Brante -->
+    <li><a href="http://www.osthyvel.net">Osthyvel.net</a>
+    <!-- Nemeth Tamas -->
+    <li><a href="http://lists.sek.nyme.hu">University of West Hungary</a>
+    <!-- Marc MERLIN -->
+    <li><a href="http://lists.svlug.org/lists/listinfo/">Silicon Valley
+    Linux Users' Group</a>
+    <!-- Bernardo Bernal González -->
+    <li><a href="http://www.fundaciongsr.es">German Sanchez Ruiperez
+    Foundation, Spain</a>
+    <!-- Alejandro G. Sánchez Martínez -->
+    <li><a href="http://www.red-libre.com">www.red-libre.com</a>
+    <!-- Randy Stoeker -->
+    <li><a href="http://comm-org.utoledo.edu">COMM-ORG: The On-Line
+    Conference on Community Organizing</a>
+    <!-- Josenivaldo Benito Junior -->
+    <li>FAI - Faculdades Adamantinenses Integradas
+    <!-- Ravi Starzl -->
+    <li><a href="http://www.oddzz.com">Oddzz</a> and <a
+    href="http://www.casinozz.com">Casinozz</a>.
+    <!-- Don Sizemore -->
+    <li><a href="http://www.ibiblio.org">ibiblio</a>
+    <!-- Marc Bitner -->
+    <li><a href="http://shrplist.umsmed.edu/mailman/listinfo/him-l">University
+    of Mississippi Medical Center HIM Listserve</a>
+    <!-- Eli Caul -->
+    <li><a href="http://www.mirafiori.com">the Fiat Page</a>
+    (automotive), with mailing lists at
+    <a href="http://www.mirafiori.com/lists">this url</a>.
+    <!-- Art Jones -->
+    <li><a href="http://www.meteoritecentral.com/">Meteorite
+    Central</a> via the mailing lists at Pair Networks.
+    <!-- Alstair Hutchinson -->
+    <li><a href="http://www.deviantpc.com">DeviantPC</a>
+    <!-- George D. Holmes -->
+    <li><a href="http://mailman.csce.uark.edu">The Computer Science &
+    Computer Engineering</a> department at the University of Arkansas.
+    <!-- steven -->
+    <li><a href="http://www.shakespeare-monologues.org/">Shakespeare's
+    Monologues</a> with mailing lists at
+    <a
+    href="http://lists.shakespeare-monologues.org/mailman/listinfo/discussion">this url</a>.
+    <!-- Kenneth Irving -->
+    <li><a href="http://www.fq.edu.uy">Universidad de la República,
+    Facultad de Química, Uruguay</a>
+    <!-- Ian McCormack -->
+    <li><a href="http://www.ne4x4.org.uk/">North East 4x4 club</a>
+    <!-- Jörn Nettingsmeier -->
+    <li><a href="http://www.linuxdj.com/audio/lad/">Linux Audio
+    Mailing Lists</a>
+    <!-- Dirk H. Shulz -->
+    <li><a href="http://www.multibyte.de">MultiByte GmbH</a>
+    <!-- Justin Yunke -->
+    <li><a href="http://www.elists.org/">Elists Online</a>
+    <!-- John C. Amodeo -->
+    <li><a href="http://fas.rutgers.edu">FAS - Rutgers, The State
+    University of New Jersey</a>
+    <!-- Lucian Daniel Kafka -->
+    <li><a href="http://www.conexim.com.au">Conexim web hosting Australia</a>
+    <!-- zainul bakri -->
+    <li>National Institute of Health Research and Development, Indonesia.
+    <!-- Chris Olson -->
+    <li><a href="http://astcomm.net/">AST Communications, Inc.</a>
+    <!-- Derek Colley -->
+    <li><a href="http://listserv.sap.com/">SAP</a>
+    <!-- Christian Thamer -->
+    <li><a href="http://www.iwl.com/Support/lists.html">InterWorking Labs</a>
+    <!-- A. Sajjad Zaidi -->
+    <li><a href="http://www.tokyopc.org/">Tokyo PC Users Group</a>
+        with mailing lists <a
+        href="http://www.tokyopc.org/mailman/listinfo/">here</a>.
+    <!-- Dr. David A. Zatz -->
+    <li><a href="http://allpar.com/">Allpar.com (Chrysler enthusiasts)</a>
+    <!-- Donna Hanlon -->
+    <li><a href="http://brainmap.wustl.edu">Van Essen Lab at Washington
+    University School of Medicine</a>
+    <!-- Matt Helsley -->
+    <li><a href="http://linux.ucla.edu">UCLA LUG</a> with mailing
+        lists <a href="http://linux.ucla.edu/mailman/listinfo">here</a>.
+    <!-- Erisian Saint Vinge -->
+    <li><a href="http://www.azone.org/">Azone</a>
+    <!-- Nicolas Cartron -->
+    <li><a href="http://squirrelmail-fr.org">SquirrelMail (French)</a>
+    <!-- Shakaraji Thakor -->
+    <li><a href="http://mail.gnvfc.com/mailman/listinfo">GNFC Ltd</a>
+    <!-- Peter Turner -->
+    <li><a href="http://www.edow.org">Diocese of Washington</a>
+    <!-- Gottfried Hamm -->
+    <li><a href="http://lists.ghks.de/">Gottfried Hamm
+        KommunikationsSysteme</a>
+    <!-- Richard Lippmann -->
+    <li><a href="http://www.zirndorf.de">Cultural events in Zirndorf,
+        Bavaria</a>
+    <!-- Gualter Barbas Baptista -->
+    <li><a href="http://gaia.org.pt">GAIA</a>, with mailing lists at
+        <a href="http://gaia.org.pt/listas/">here</a>.
+    <!-- Ansgar Schmidt -->
+    <li><a href="http://auriga.wearlab.de">Free Mobile Software System</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 00000000..aa56a298
--- /dev/null
+++ b/admin/www/links.h
@@ -0,0 +1,9 @@
+<!-- -*- html -*- -->
+<h3>Overview</h3>
+<li><a href="index.html">Home</a>
+<li><a href="features.html">Features</a>
+<li><a href="otherstuff.html">Logos and Papers</a>
+<li><a href="inthenews.html">Mailman in Use</a>
+<li><a href="prev.html">Previous Releases</a>
+<li><a href="bugs.html">Bugs and Patches</a>
+<li><a href="mirrors.html">Mirrors</a>
diff --git a/admin/www/lists.ht b/admin/www/lists.ht
new file mode 100644
index 00000000..c9e8e563
--- /dev/null
+++ b/admin/www/lists.ht
@@ -0,0 +1,52 @@
+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>
+<p><li><a href="http://mail.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://mail.python.org/pipermail/mailman-users/"><em>archives</em></a>)
+
+<p><li><a href="http://listowner.org/">Listowners</a>
+    is a mailing list with a non-technical focus, specifically for
+    discussions from the perspective of listowners and moderators
+    who do not have "shell access" to the mailing list server
+    where the Mailman software runs. (<a href="http://listowner.org/pipermail/lo/"><em>archives</em></a>)
+
+<p><li><a href="http://mail.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://mail.python.org/pipermail/mailman-announce/"><em>archives</em></a>)
+
+<p><li><a href="http://mail.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://mail.python.org/pipermail/mailman-developers/"><em>archives</em></a>)
+
+    <p>More information about developer resources is available
+    <a href="devs.html">here</a>.
+
+<p><li><a href="http://mail.python.org/mailman/listinfo/mailman-i18n">
+    Mailman Internationalization</a> is the list for discussing the
+    multi-lingual support in Mailman 2.1.  Everyone who is working on
+    translations of Mailman should subscribe to this mailing list.
+    (<a href="http://mail.python.org/pipermail/mailman-i18n/"><em>archives</em></a>)
+
+<p><li><a href="http://mail.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>
diff --git a/admin/www/lists.html b/admin/www/lists.html
new file mode 100644
index 00000000..998d7483
--- /dev/null
+++ b/admin/www/lists.html
@@ -0,0 +1,185 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:23 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman mailing lists
+
+-->
+
+<head>
+<title>Mailman mailing lists</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<b>Mailing lists</b>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Mailman mailing lists</h3>
+
+We have several mailing lists devoted to Mailman, which also provide a 
+nice demonstration of Mailman!
+
+<ul>
+<p><li><a href="http://mail.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://mail.python.org/pipermail/mailman-users/"><em>archives</em></a>)
+
+<p><li><a href="http://listowner.org/">Listowners</a>
+    is a mailing list with a non-technical focus, specifically for
+    discussions from the perspective of listowners and moderators
+    who do not have "shell access" to the mailing list server
+    where the Mailman software runs. (<a href="http://listowner.org/pipermail/lo/"><em>archives</em></a>)
+
+<p><li><a href="http://mail.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://mail.python.org/pipermail/mailman-announce/"><em>archives</em></a>)
+
+<p><li><a href="http://mail.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://mail.python.org/pipermail/mailman-developers/"><em>archives</em></a>)
+
+    <p>More information about developer resources is available
+    <a href="devs.html">here</a>.
+
+<p><li><a href="http://mail.python.org/mailman/listinfo/mailman-i18n">
+    Mailman Internationalization</a> is the list for discussing the
+    multi-lingual support in Mailman 2.1.  Everyone who is working on
+    translations of Mailman should subscribe to this mailing list.
+    (<a href="http://mail.python.org/pipermail/mailman-i18n/"><em>archives</em></a>)
+
+<p><li><a href="http://mail.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><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/mailman.html b/admin/www/mailman.html
new file mode 100644
index 00000000..bc8b1e16
--- /dev/null
+++ b/admin/www/mailman.html
@@ -0,0 +1,146 @@
+<!-- This is a boilerplate for the web pages used in the GNU project.
+     Please change it according to specifications                        -->
+<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
+<HTML>
+<HEAD>
+<TITLE>Mailman - GNU Project - Free Software Foundation (FSF)</TITLE>
+<LINK REV="made" HREF="mailto:webmasters@www.gnu.org">
+</HEAD>
+<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" VLINK="#9900DD">
+<H3>Mailman</H3>
+<!-- When using this boilerplate, remember to replace the "???" in both places above. -->
+
+<!-- when you replace this graphics, make sure you change the link
+     to also point to the correct html page.
+     If you make a new graphics for this page, make sure it has
+     a corresponding entry in /graphics/graphics.html                     -->
+<A HREF="/graphics/dragonlogo.jpg"><IMG SRC="/graphics/dragonlogo.jpg"
+   ALT=" [Delivered by Mailman logo] "
+   WIDTH="247" HEIGHT="93">&nbsp; (jpeg 6k)</A>
+<!-- only english is available currently
+<P>[<A HREF="">French</A>|<A HREF="">Spanish</A>]
+<P> -->
+<HR>
+<P>
+<!-- Replace this list with the page's contents. -->
+<H4>Table of contents</H4>
+<UL>
+  <LI><A HREF="#introduction"
+	 NAME="TOCintroduction">Introduction to Mailman</A>
+  <LI><A HREF="#downloading"
+	 NAME="TOCdownloading">Downloading Mailman</A>
+  <li><a href="#mailinglists"
+	 name="TOCmailinglists">Mailman Discussion Lists</a>
+</UL>
+
+<P>
+<H4><A HREF="#TOCintroduction"
+       NAME="introduction">Introduction to Mailman</A></H4>
+<P>
+Mailman is software to help manage email discussion lists, much like
+Majordomo and SmartList. 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, integrated bounce handling, spam prevention,
+email-based admin commands, direct SMTP delivery (with fast bulk
+mailing), support for virtual domains, and more.
+
+<p>
+Mailman runs on most Un*x-like systems, is compatible with most web
+servers and browsers, and most SMTP servers.  Mailman requires
+<a href="http://www.python.org/">Python version 1.5 or newer</a>.
+Python is a free object-oriented scripting language.  A few files are
+written in C for security purposes.
+
+<p>The manual is still only a set of READMEs provided in the Mailman
+distribution.  For now, more information can be found at
+<a href="http://www.list.org/">www.list.org</a>.
+
+<P>
+<HR>
+<P>
+<H4><A HREF="#TOCdownloading" NAME="downloading">Downloading Mailman</A></H4>
+<P>
+Mailman can be found on
+<A HREF="http://ftp.gnu.org/gnu/mailman/">http://ftp.gnu.org/gnu/mailman/</A>
+or one of <A HREF="/prep/ftp.html">the mirrors</A>.
+<P>
+
+<p>
+<HR>
+<P>
+<H4><a href="#TOCmailinglists" NAME="mailinglists">Mailman Discussion
+Lists</a></h4>
+
+<p>
+There are several mailing lists devoted to Mailman, which also provide
+nice demonstrations 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><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>
+
+<!--
+  * If needed, change the copyright block at the bottom. In general, all pages
+    on the GNU web server should have the section about verbatim copying. Please
+    do NOT remove this without talking with the webmasters first.
+-->
+<HR>
+
+<!-- english only currently
+[<A HREF="">French</A>|<A HREF="">Spanish</A>]<P>
+-->
+Return to <A HREF="/home.html">GNU's home page</A>.
+<P>
+
+Please send FSF &amp; GNU inquiries &amp; questions to 
+
+<A HREF="mailto:gnu@gnu.org"><EM>gnu@gnu.org</EM></A>.
+There are also <A HREF="/home.html#ContactInfo">other ways to
+contact</A> the FSF.
+<P>
+
+Please send comments on these web pages to
+
+<A HREF="mailto:webmasters@gnu.org"><EM>webmasters@gnu.org</EM></A>,
+send other questions to
+<A HREF="mailto:gnu@gnu.org"><EM>gnu@gnu.org</EM></A>.
+<P>
+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.<P>
+Updated:
+<!-- hhmts start -->
+Last modified: Sat Oct 26 13:29:25 EDT 2002
+<!-- hhmts end -->
+<HR>
+</BODY>
+</HTML>
diff --git a/admin/www/mgrs.ht b/admin/www/mgrs.ht
new file mode 100644
index 00000000..d4358062
--- /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://staff.imsa.edu/~ckolar">Chris Kolar</a> has made
+available <a href="http://staff.imsa.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 00000000..37742b1e
--- /dev/null
+++ b/admin/www/mgrs.html
@@ -0,0 +1,159 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:23 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: List Manager Documentation
+
+-->
+
+<head>
+<title>List Manager Documentation</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Documentation
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="docs.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="admins.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="site.html">Site Administrators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="i18n.html">Translators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>List Manager Documentation</h3>
+
+<p><a href="http://staff.imsa.edu/~ckolar">Chris Kolar</a> has made
+available <a href="http://staff.imsa.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/mirrors.ht b/admin/www/mirrors.ht
new file mode 100644
index 00000000..7ca7c37c
--- /dev/null
+++ b/admin/www/mirrors.ht
@@ -0,0 +1,12 @@
+Title: Mailman Web Page Mirrors
+
+<h3>Mailman Web Page Mirrors</h3>
+
+These web pages are mirrored in several locations for your
+convenience.  Here are the current list of mirrors:
+
+<ul>
+<li><a href="http://www.list.org/">www.list.org</a>
+<li><a href="http://www.gnu.org/software/mailman/index.html">GNU</a>
+<li><a href="http://mailman.sf.net/">SourceForge</a>
+</ul>
diff --git a/admin/www/mirrors.html b/admin/www/mirrors.html
new file mode 100644
index 00000000..84c25eda
--- /dev/null
+++ b/admin/www/mirrors.html
@@ -0,0 +1,145 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:23 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Web Page Mirrors
+
+-->
+
+<head>
+<title>Mailman Web Page Mirrors</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Mirrors</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Mailman Web Page Mirrors</h3>
+
+These web pages are mirrored in several locations for your
+convenience.  Here are the current list of mirrors:
+
+<ul>
+<li><a href="http://www.list.org/">www.list.org</a>
+<li><a href="http://www.gnu.org/software/mailman/index.html">GNU</a>
+<li><a href="http://mailman.sf.net/">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/otherstuff.ht b/admin/www/otherstuff.ht
new file mode 100644
index 00000000..b60041f7
--- /dev/null
+++ b/admin/www/otherstuff.ht
@@ -0,0 +1,23 @@
+Title: Mailman Logos and Papers
+
+<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>
+
+<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="http://sourceforge.net/project/showfiles.php?group_id=103"
+>here</a>.
diff --git a/admin/www/otherstuff.html b/admin/www/otherstuff.html
new file mode 100644
index 00000000..47dae557
--- /dev/null
+++ b/admin/www/otherstuff.html
@@ -0,0 +1,156 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Mon Dec 30 23:37:27 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Logos and Papers
+
+-->
+
+<head>
+<title>Mailman Logos and Papers</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Logos and Papers</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<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>
+
+<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="http://sourceforge.net/project/showfiles.php?group_id=103"
+>here</a>.
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/prev.ht b/admin/www/prev.ht
new file mode 100644
index 00000000..a48031be
--- /dev/null
+++ b/admin/www/prev.ht
@@ -0,0 +1,20 @@
+Title: Previous Mailman Releases
+
+<h3>Previous Mailman Releases</h3>
+
+<a href="http://sourceforge.net/project/shownotes.php?release_id=102354"
+>Mailman 2.0.13</a> is the most stable version of the 2.0 release
+branch.  It is in production use at thousands of sites.  It should be
+fairly easy to upgrade from Mailman 2.0.13 to Mailman 2.1 -- see the
+documentation that comes with Mailman 2.1 for details.
+
+<p>Mailman 2.0.13 works with any Python version from 1.5.2 to 2.3
+(still in alpha development as of this writing 26-Dec-2002).  Mailman
+2.1 requires at least Python 2.1.3 and works best with Python 2.2.2.
+If you plan on upgrading Mailman, I first recommend that you upgrade
+to Python 2.2.2, and then upgrade Mailman.
+
+<p>There are tons of <a href="features.html">new features</a> in
+Mailman 2.1, and no new development is being done on the Mailman 2.0.x
+branch.  Only absolutely critical security fixes will be issued for
+Mailman 2.0 -- the last one was issued on 29-Jul-2002.
diff --git a/admin/www/prev.html b/admin/www/prev.html
new file mode 100644
index 00000000..1fa8d465
--- /dev/null
+++ b/admin/www/prev.html
@@ -0,0 +1,153 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:24 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Previous Mailman Releases
+
+-->
+
+<head>
+<title>Previous Mailman Releases</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Previous Releases</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Previous Mailman Releases</h3>
+
+<a href="http://sourceforge.net/project/shownotes.php?release_id=102354"
+>Mailman 2.0.13</a> is the most stable version of the 2.0 release
+branch.  It is in production use at thousands of sites.  It should be
+fairly easy to upgrade from Mailman 2.0.13 to Mailman 2.1 -- see the
+documentation that comes with Mailman 2.1 for details.
+
+<p>Mailman 2.0.13 works with any Python version from 1.5.2 to 2.3
+(still in alpha development as of this writing 26-Dec-2002).  Mailman
+2.1 requires at least Python 2.1.3 and works best with Python 2.2.2.
+If you plan on upgrading Mailman, I first recommend that you upgrade
+to Python 2.2.2, and then upgrade Mailman.
+
+<p>There are tons of <a href="features.html">new features</a> in
+Mailman 2.1, and no new development is being done on the Mailman 2.0.x
+branch.  Only absolutely critical security fixes will be issued for
+Mailman 2.0 -- the last one was issued on 29-Jul-2002.
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/requirements.ht b/admin/www/requirements.ht
new file mode 100644
index 00000000..f193ecea
--- /dev/null
+++ b/admin/www/requirements.ht
@@ -0,0 +1,56 @@
+Title: Mailman Requirements
+Links: download-links.h
+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.sendmail.org/">Sendmail</a>
+    <li><a href="http://www.qmail.org/">Qmail</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>Requirements</h3>
+
+<p>Mailman currently runs only on GNU/Linux and any other Un*x-like
+operating system, such as *BSD, Solaris, etc.  It should work on
+MacOSX but not earlier versions of MacOS.  It probably does not work
+on Windows, although it's possible you could get it running on a
+Cygwin system (please <a
+href="mailto:mailman-developers@python.org">let the developer
+community know</a> if you have success with this!)
+
+<p>Before you can run Mailman, you need to make sure that
+<a href="http://www.python.org/">Python</a> is installed.  Mailman 2.1
+requires at least Python 2.1.3, although Python 2.2.2 is
+recommended. Most GNU/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:
+
+<blockquote>
+<pre>
+% python -V
+Python 2.1.3
+</pre>
+</blockquote>
+
+If your Python executable doesn't understand the <code>-V</code>
+option, it's definitely too old!
+
+<p>You will also need an SMTP server (a.k.a. mail transport agent or
+<em>MTA</em>) for mail delivery and reception.  Mailman should work
+well with any of the most popular Unix mail servers such as
+<a href="http://www.postfix.org/">Postfix</a>,
+<a href="http://www.exim.org/">Exim</a>,
+<a href="http://www.sendmail.org/">Sendmail</a> and
+<a href="http://www.qmail.org/">qmail</a>.
+
+<p>You will also 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.
diff --git a/admin/www/requirements.html b/admin/www/requirements.html
new file mode 100644
index 00000000..1bb74e74
--- /dev/null
+++ b/admin/www/requirements.html
@@ -0,0 +1,196 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:32:32 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Mailman Requirements
+
+-->
+
+<head>
+<title>Mailman Requirements</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Downloading
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="download.html">Downloading</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="version.html">Latest Version</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Requirements</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="install.html">Installing</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+SMTP servers
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.postfix.org/">Postfix</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.exim.org/">Exim</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.sendmail.org/">Sendmail</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.qmail.org/">Qmail</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Other software
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.apache.org/">Apache web server</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.gnu.org/software/gcc/">GNU C compiler</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Requirements</h3>
+
+<p>Mailman currently runs only on GNU/Linux and any other Un*x-like
+operating system, such as *BSD, Solaris, etc.  It should work on
+MacOSX but not earlier versions of MacOS.  It probably does not work
+on Windows, although it's possible you could get it running on a
+Cygwin system (please <a
+href="mailto:mailman-developers@python.org">let the developer
+community know</a> if you have success with this!)
+
+<p>Before you can run Mailman, you need to make sure that
+<a href="http://www.python.org/">Python</a> is installed.  Mailman 2.1
+requires at least Python 2.1.3, although Python 2.2.2 is
+recommended. Most GNU/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:
+
+<blockquote>
+<pre>
+% python -V
+Python 2.1.3
+</pre>
+</blockquote>
+
+If your Python executable doesn't understand the <code>-V</code>
+option, it's definitely too old!
+
+<p>You will also need an SMTP server (a.k.a. mail transport agent or
+<em>MTA</em>) for mail delivery and reception.  Mailman should work
+well with any of the most popular Unix mail servers such as
+<a href="http://www.postfix.org/">Postfix</a>,
+<a href="http://www.exim.org/">Exim</a>,
+<a href="http://www.sendmail.org/">Sendmail</a> and
+<a href="http://www.qmail.org/">qmail</a>.
+
+<p>You will also 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.
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/site.ht b/admin/www/site.ht
new file mode 100644
index 00000000..abb08bd6
--- /dev/null
+++ b/admin/www/site.ht
@@ -0,0 +1,240 @@
+Title: Site Administrator Documentation
+Links: 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>addlang</b>
+<dd>Use this to add language support to a specific list.  The site
+    itself must have the language pack to add already installed.  Note
+    that removing language support from a list requires you to
+    manually <tt>rm</tt> the lists/<em>yourlist</em>/<em>lang</em>
+    subdirectory.
+
+<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>change_pw</b>
+<dd>Use this to change the password for a specific mailing list.
+
+<dt><b>check_db</b>
+<dd>Use this script to check the integrity of a list's
+    <code>config.pck</code> and <code>config.pck.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.  This script can also be used to print out the contents of a
+    pickled message file, which are stored in <code>.pck</code> files.
+
+<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>genaliases</b>
+<dd>Use this script to regenerate the plain text and <em>db</em> alias
+    files for Postfix (if you're using Postfix as you're MTA).
+
+<dt><b>list_admins</b>
+<dd>List all the owners of a mailing list.
+
+<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>mailmanctl</b>
+<dd>The main qrunner control script.  Use this to start, stop, and
+    restart the qrunner.
+
+<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>qrunner</b>
+<dd>Use this to run a single qrunner once (for debugging).
+
+<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>senddigests</b>
+<dd>Sends all accumulated digests.
+
+</dl>
diff --git a/admin/www/site.html b/admin/www/site.html
new file mode 100644
index 00000000..d27461ba
--- /dev/null
+++ b/admin/www/site.html
@@ -0,0 +1,366 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:24 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Site Administrator Documentation
+
+-->
+
+<head>
+<title>Site Administrator Documentation</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Documentation
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="docs.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="admins.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Site Administrators</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="i18n.html">Translators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><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>addlang</b>
+<dd>Use this to add language support to a specific list.  The site
+    itself must have the language pack to add already installed.  Note
+    that removing language support from a list requires you to
+    manually <tt>rm</tt> the lists/<em>yourlist</em>/<em>lang</em>
+    subdirectory.
+
+<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>change_pw</b>
+<dd>Use this to change the password for a specific mailing list.
+
+<dt><b>check_db</b>
+<dd>Use this script to check the integrity of a list's
+    <code>config.pck</code> and <code>config.pck.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.  This script can also be used to print out the contents of a
+    pickled message file, which are stored in <code>.pck</code> files.
+
+<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>genaliases</b>
+<dd>Use this script to regenerate the plain text and <em>db</em> alias
+    files for Postfix (if you're using Postfix as you're MTA).
+
+<dt><b>list_admins</b>
+<dd>List all the owners of a mailing list.
+
+<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>mailmanctl</b>
+<dd>The main qrunner control script.  Use this to start, stop, and
+    restart the qrunner.
+
+<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>qrunner</b>
+<dd>Use this to run a single qrunner once (for debugging).
+
+<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>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/todo.ht b/admin/www/todo.ht
new file mode 100644
index 00000000..c6901ee3
--- /dev/null
+++ b/admin/www/todo.ht
@@ -0,0 +1,190 @@
+Title: The Mailman Wishlist
+
+ <p>
+<h3> The Mailman Wishlist
+</h3>
+ <p>
+<h3> (Last Update: $Date: 2002-12-27 03:36:46 +0000 (Fri, 27 Dec 2002) $)
+</h3>
+Here's the wish list for future versions of Mailman.  Many new
+ features have been added to Mailman 2.1, so what's left will
+ probably end up in a Mailman 3.0.
+ Please also see the Mailman design notes wiki at
+ http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
+<p>
+<h3> Email Handling
+</h3>
+<ul>
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
+
+    <li> For low-traffic sites, a queued message could trigger a qrunner process.  It would work until all mail was delivered, then sleep
+ and exit if no new work arrived.
+
+    <li> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message.
+
+    <li> Separate processing for MIME and plaintext digests.  E.g. you might want to filter images out of plaintext but not MIME
+ digests.
+
+</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
+    <li> Integrate Christopher Kolar's documentation
+</ul>
+<h3> General Web UI
+</h3>
+<ul>
+    <li> NO DEAD ENDS and every web page is reachable.
+    <li> All web UI must be configurable so that it more easily integrates into an existing site's design.  Probably means using
+ a better template language/system like Zope's Presentation
+ Templates, Quixote, or PHP.
+
+    <li> Default UI should add a navigation sidebar to all web pages.
+    <li> Web pages should never mention disabled features.
+    <li> Allow a site admin and list admins to categorize lists, so that they can be better organized on the listinfo and admin overview
+ pages.
+
+</ul>
+<h3> List Administration
+</h3>
+<ul>
+    <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 the admin to disable option settings by users
+    <li> Allow admins to block nomail settings
+    <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> New moderation choice: archive but don't send to list.
+    <li> New moderation choice: annotate and send to author for resubmittal.  Or just be able to annotate the message for
+ multiple moderator scenarios.
+
+    <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> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail
+ posted to the list is always returned unsent.
+
+    <li> Ability to `sideline' some messages in the moderation queue
+    <li> Hook moderation up to a whitelist a la TMDA.  A non-member message gets held in a non-admindb queue, and the sender gets a
+ confirmation message.  When they confirm, we moderate the
+ message as normal, but if they don't we assume it's spam (after
+ some period of time) and discard it.  The admin should be able
+ to see all these super-quarantined messages with the flip of a
+ button.
+
+    <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even
+ if it comes from a non-member.  Treat that non-member as a
+ member for the duration of the thread.  Use In-Reply-To,
+ References and Message-ID to match these up.
+
+    <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message
+ when the approved resend is received.
+
+    <li> Have an option to sort the list of members by real name or email address.
+
+    <li> Test a message for all hold criteria, record them all instead of just the first match, and do a SpamAssassin like scoring to
+ decide whether the message should get held or not.
+
+</ul>
+<h3> List Membership
+</h3>
+<ul>
+    <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> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
+
+    <li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
+ date they last sent a message through the list.  Perhaps also
+ log each message they send through the list.
+
+</ul>
+<h3> Site Administration
+</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> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
+ by addressing it to mailman@site.dom).
+
+</ul>
+<h3> Other Usability Improvments
+</h3>
+<ul>
+    <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.
+
+    <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).
+ Also, limits on mailbacks, infos, etc.
+
+</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 click-thru confirmation
+ to resubscribe.
+
+    <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> 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> Member profiles
+    <li> Allow lists of the same name in two different virtual domains
+    <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> Add more patterns for bounce handling (never ending)
+    <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it).
+
+</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> optional form front-end to public interfaces as a filter to address harvesters.
+
+    <li> In general the whole Pipermail subsystem needs a good rewrite.
+    <li> Write an API between Mailman and the archiver so that message footers can contain the URL to the archived message.
+
+</ul>
+<h3> Code cleanup
+</h3>
+<ul>
+    <li> Turn all remaining string exceptions into class exceptions
+    <li> Unit and system test suite! (ongoing)
+</ul>
diff --git a/admin/www/todo.html b/admin/www/todo.html
new file mode 100644
index 00000000..f681af12
--- /dev/null
+++ b/admin/www/todo.html
@@ -0,0 +1,323 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:25 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: The Mailman Wishlist
+
+-->
+
+<head>
+<title>The Mailman Wishlist</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Overview
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="otherstuff.html">Logos and Papers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="prev.html">Previous Releases</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mirrors.html">Mirrors</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+ <p>
+<h3> The Mailman Wishlist
+</h3>
+ <p>
+<h3> (Last Update: $Date: 2002-12-27 03:36:46 +0000 (Fri, 27 Dec 2002) $)
+</h3>
+Here's the wish list for future versions of Mailman.  Many new
+ features have been added to Mailman 2.1, so what's left will
+ probably end up in a Mailman 3.0.
+ Please also see the Mailman design notes wiki at
+ http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
+<p>
+<h3> Email Handling
+</h3>
+<ul>
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
+
+    <li> For low-traffic sites, a queued message could trigger a qrunner process.  It would work until all mail was delivered, then sleep
+ and exit if no new work arrived.
+
+    <li> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message.
+
+    <li> Separate processing for MIME and plaintext digests.  E.g. you might want to filter images out of plaintext but not MIME
+ digests.
+
+</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
+    <li> Integrate Christopher Kolar's documentation
+</ul>
+<h3> General Web UI
+</h3>
+<ul>
+    <li> NO DEAD ENDS and every web page is reachable.
+    <li> All web UI must be configurable so that it more easily integrates into an existing site's design.  Probably means using
+ a better template language/system like Zope's Presentation
+ Templates, Quixote, or PHP.
+
+    <li> Default UI should add a navigation sidebar to all web pages.
+    <li> Web pages should never mention disabled features.
+    <li> Allow a site admin and list admins to categorize lists, so that they can be better organized on the listinfo and admin overview
+ pages.
+
+</ul>
+<h3> List Administration
+</h3>
+<ul>
+    <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 the admin to disable option settings by users
+    <li> Allow admins to block nomail settings
+    <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> New moderation choice: archive but don't send to list.
+    <li> New moderation choice: annotate and send to author for resubmittal.  Or just be able to annotate the message for
+ multiple moderator scenarios.
+
+    <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> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail
+ posted to the list is always returned unsent.
+
+    <li> Ability to `sideline' some messages in the moderation queue
+    <li> Hook moderation up to a whitelist a la TMDA.  A non-member message gets held in a non-admindb queue, and the sender gets a
+ confirmation message.  When they confirm, we moderate the
+ message as normal, but if they don't we assume it's spam (after
+ some period of time) and discard it.  The admin should be able
+ to see all these super-quarantined messages with the flip of a
+ button.
+
+    <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even
+ if it comes from a non-member.  Treat that non-member as a
+ member for the duration of the thread.  Use In-Reply-To,
+ References and Message-ID to match these up.
+
+    <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message
+ when the approved resend is received.
+
+    <li> Have an option to sort the list of members by real name or email address.
+
+    <li> Test a message for all hold criteria, record them all instead of just the first match, and do a SpamAssassin like scoring to
+ decide whether the message should get held or not.
+
+</ul>
+<h3> List Membership
+</h3>
+<ul>
+    <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> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
+
+    <li> Keep user-centric stats, such as the date the user was subscribed, the date of their last change to their account, the
+ date they last sent a message through the list.  Perhaps also
+ log each message they send through the list.
+
+</ul>
+<h3> Site Administration
+</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> Allow the site admin to send an email message to all the list admins using a mechanism similar to the Urgent: header (possibly
+ by addressing it to mailman@site.dom).
+
+</ul>
+<h3> Other Usability Improvments
+</h3>
+<ul>
+    <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.
+
+    <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).
+ Also, limits on mailbacks, infos, etc.
+
+</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 click-thru confirmation
+ to resubscribe.
+
+    <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> 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> Member profiles
+    <li> Allow lists of the same name in two different virtual domains
+    <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> Add more patterns for bounce handling (never ending)
+    <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it).
+
+</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> optional form front-end to public interfaces as a filter to address harvesters.
+
+    <li> In general the whole Pipermail subsystem needs a good rewrite.
+    <li> Write an API between Mailman and the archiver so that message footers can contain the URL to the archived message.
+
+</ul>
+<h3> Code cleanup
+</h3>
+<ul>
+    <li> Turn all remaining string exceptions into class exceptions
+    <li> Unit and system test suite! (ongoing)
+</ul>
+
+</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 00000000..56267675
--- /dev/null
+++ b/admin/www/users.ht
@@ -0,0 +1,8 @@
+Title: User Documentation
+Links: doco-links.h
+
+<h3>User Documentation</h3>
+
+<p><a href="http://staff.imsa.edu/~ckolar">Chris Kolar</a> has made
+available a <a href="http://staff.imsa.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 00000000..5ce2508d
--- /dev/null
+++ b/admin/www/users.html
@@ -0,0 +1,134 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Thu Dec 26 22:30:24 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: User Documentation
+
+-->
+
+<head>
+<title>User Documentation</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Documentation
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="docs.html">Overview</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Users</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="admins.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="site.html">Site Administrators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="i18n.html">Translators</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>User Documentation</h3>
+
+<p><a href="http://staff.imsa.edu/~ckolar">Chris Kolar</a> has made
+available a <a href="http://staff.imsa.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>
diff --git a/admin/www/version.ht b/admin/www/version.ht
new file mode 100644
index 00000000..1774bf79
--- /dev/null
+++ b/admin/www/version.ht
@@ -0,0 +1,12 @@
+Title: Current Mailman Version
+Links: download-links.h
+
+<h3>Current Mailman Version</h3>
+
+<p>Version
+(<!-VERSION--->2.1<!-VERSION--->,
+released on
+<!-DATE--->30-Dec-2002<!-DATE--->)
+is the latest stable release.  See also information on
+<a href="prev.html">previous version</a> if you're not yet ready to
+upgrade.
diff --git a/admin/www/version.html b/admin/www/version.html
new file mode 100644
index 00000000..17f168a3
--- /dev/null
+++ b/admin/www/version.html
@@ -0,0 +1,135 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
+<!-- Mon Dec 30 23:19:52 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
+<!-- User-specified headers:
+Title: Current Mailman Version
+
+-->
+
+<head>
+<title>Current Mailman Version</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      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="middle" bgcolor="white" class="corner">
+
+<center>
+    <a href="./index.html">
+    <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#eecfa1">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of corner cells -->
+<!-- start of banner -->
+<td width="90%" bgcolor="#eecfa1" class="banner">
+<!-- start of site links table -->
+<table width="100%" border="0"
+CELLSPACING=0 CELLPADDING=0
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#eecfa1">
+<a href="./index.html">Home</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./docs.html">Documentation</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./lists.html">Mailing lists</a>
+    </td>
+</tr><tr>
+    <td bgcolor="#eecfa1">
+<a href="./help.html">Help</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./download.html">Download</a>
+    </td>
+    <td bgcolor="#eecfa1">
+<a href="./devs.html">Developers</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="#eecfa1" class="sidebar">
+<!-- start of sidebar table -->
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+       bgcolor="#ffffff">
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Downloading
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="download.html">Downloading</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<b>Latest Version</b>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="requirements.html">Requirements</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="install.html">Installing</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">&nbsp;
+<tr><td bgcolor="#36648b"><b><font color="#ffffff">
+Email Us
+</font></b></td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+<a href="http://www.python.org/"><img border=0
+                          src="./images/PythonPoweredSmall.png"
+                          ></a>&nbsp;<a href="http://sourceforge.net"><img 
+                          src="http://sourceforge.net/sflogo.php?group_id=103"
+                          width="88" height="31" border="0"
+                          alt="SourceForge Logo"></a>
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&nbsp;
+</td></tr>
+<tr><td bgcolor="#eecfa1">
+&copy; 1998-2002
+Free Software Foundation, Inc.  Verbatim copying and distribution of this
+entire article is permitted in any medium, provided this notice is preserved.
+
+</td></tr>
+</table><!-- end of sidebar table -->
+
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
+<!-- end of sidebar cell -->
+<!-- start of body cell -->
+<td valign="top" width="90%" class="body"><br>
+<h3>Current Mailman Version</h3>
+
+<p>Version
+(<!-VERSION--->2.1<!-VERSION--->,
+released on
+<!-DATE--->30-Dec-2002<!-DATE--->)
+is the latest stable release.  See also information on
+<a href="prev.html">previous version</a> if you're not yet ready to
+upgrade.
+
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>