summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbwarsaw2002-12-09 13:34:43 +0000
committerbwarsaw2002-12-09 13:34:43 +0000
commit543d3fc785a7f4b487d9247c76eb401da76e7d3f (patch)
treee6cde5a03f536188320975df06874d47fdc922d2
parent64c752f9fc7687f58bed74d4c647c894e744c66b (diff)
downloadmailman-543d3fc785a7f4b487d9247c76eb401da76e7d3f.tar.gz
mailman-543d3fc785a7f4b487d9247c76eb401da76e7d3f.tar.zst
mailman-543d3fc785a7f4b487d9247c76eb401da76e7d3f.zip
Updates
-rw-r--r--admin/www/admins.html268
-rw-r--r--admin/www/bugs.html250
-rw-r--r--admin/www/devs.html268
-rw-r--r--admin/www/download.html6
-rw-r--r--admin/www/faq.html4
-rw-r--r--admin/www/features.html4
-rw-r--r--admin/www/i18n.html4
-rw-r--r--admin/www/index.html6
-rw-r--r--admin/www/install-check.html286
-rw-r--r--admin/www/install-config.html286
-rw-r--r--admin/www/install-custom.html286
-rw-r--r--admin/www/install-faq.html286
-rw-r--r--admin/www/install-final.html286
-rw-r--r--admin/www/install-start.html284
-rw-r--r--admin/www/install-system.html286
-rw-r--r--admin/www/install-test.html286
-rw-r--r--admin/www/install-trouble.html286
-rw-r--r--admin/www/inthenews.html2
-rw-r--r--admin/www/lists.html4
-rw-r--r--admin/www/mgrs.html4
-rw-r--r--admin/www/otherdocs.html4
-rw-r--r--admin/www/todo.ht921
-rw-r--r--admin/www/todo.html923
-rw-r--r--admin/www/users.html4
24 files changed, 1779 insertions, 3465 deletions
diff --git a/admin/www/admins.html b/admin/www/admins.html
index 03bf44d70..062636a5c 100644
--- a/admin/www/admins.html
+++ b/admin/www/admins.html
@@ -1,173 +1,185 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Oct 4 06:45:48 2001 -->
-<!-- USING HT2HTML 1.2 -->
-<!-- SEE http://barry.wooz.org/software/ht2html -->
+<!-- Mon Dec 9 08:32:57 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Site Administrator Documentation
-->
-<HEAD>
-<TITLE>Site Administrator Documentation</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<b>Site Administrators</b>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Documentation
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="users.html">Users</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mgrs.html">List Managers</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mgrs.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Site&nbsp;Administrators</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="devs.html">Developers</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="i18n.html">Internationalization</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="otherdocs.html">Other Documentation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="devs.html">Developers</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="i18n.html">Internationalization</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="otherdocs.html">Other Documentation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Site Administrator Documentation</h3>
By definition, the site administrator has shell access to the Mailman
@@ -406,7 +418,7 @@ cron scripts do:
</dl>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/bugs.html b/admin/www/bugs.html
index 9be3e2742..cf5893b99 100644
--- a/admin/www/bugs.html
+++ b/admin/www/bugs.html
@@ -1,164 +1,176 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Wed Jul 11 23:44:02 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:57 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Bugs and Patches
-->
-<HEAD>
-<TITLE>Bugs and Patches</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Bugs and Patches</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Exits
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://sourceforge.net/bugs/?group_id=103">Bug Tracker</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://sourceforge.net/patch/?group_id=103">Patch Manager</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://sourceforge.net/projects/mailman">Mailman Project</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://sourceforge.net/bugs/?group_id=103">Bug Tracker</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://sourceforge.net/patch/?group_id=103">Patch Manager</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://sourceforge.net/projects/mailman">Mailman Project</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Bugs and Patches</h3>
<p>Mailman is being
@@ -170,7 +182,7 @@ python.org. If you have patches you'd like to submit, the best place
to do that is on the SourceForge
<a href="http://sourceforge.net/patch/?group_id=103">patch manager</a>.
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/devs.html b/admin/www/devs.html
index f1a45f00b..9895289a3 100644
--- a/admin/www/devs.html
+++ b/admin/www/devs.html
@@ -1,173 +1,185 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Wed Jul 11 23:44:02 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:57 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Developer Documentation
-->
-<HEAD>
-<TITLE>Developer Documentation</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Developer 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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<b>Developers</b>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Documentation
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="users.html">Users</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mgrs.html">List Managers</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="admins.html">Site&nbsp;Administrators</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="users.html">Users</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mgrs.html">List Managers</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="admins.html">Site&nbsp;Administrators</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Developers</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="i18n.html">Internationalization</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="otherdocs.html">Other Documentation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="i18n.html">Internationalization</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="otherdocs.html">Other Documentation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Developer Documentation</h3>
If you're the kind of person who loves to hack on the nitty gritty,
@@ -192,7 +204,7 @@ will be plotted in plain sight. Because Wikis are intended to be
collaborative, you're free to contribute to this page in true Wiki
fashion.
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/download.html b/admin/www/download.html
index 7b3b682e4..bdf19896e 100644
--- a/admin/www/download.html
+++ b/admin/www/download.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Tue Nov 19 01:52:44 2002 -->
+<!-- Mon Dec 9 08:32:57 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -246,9 +246,9 @@ gcc 2.8.1 or later is known to work well.
<h3>Downloading</h3>
<p>Version
-(<!-VERSION--->2.1b5<!-VERSION--->,
+(<!-VERSION--->2.1b6<!-VERSION--->,
released on
-<!-DATE--->19-Nov-2002<!-DATE--->)
+<!-DATE--->09-Dec-2002<!-DATE--->)
is a beta release of the next version. While the betas seem to be
working quite well, it is still recommended that you use the
<a href="http://sourceforge.net/project/showfiles.php?group_id=103">latest
diff --git a/admin/www/faq.html b/admin/www/faq.html
index add546c86..9c5c55d60 100644
--- a/admin/www/faq.html
+++ b/admin/www/faq.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Wed Oct 23 09:40:34 2002 -->
+<!-- Mon Dec 9 08:33:00 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -149,7 +149,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->
diff --git a/admin/www/features.html b/admin/www/features.html
index 3fbc301ed..d65034fcf 100644
--- a/admin/www/features.html
+++ b/admin/www/features.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 5 00:30:17 2002 -->
+<!-- Mon Dec 9 08:32:58 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -156,7 +156,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->
diff --git a/admin/www/i18n.html b/admin/www/i18n.html
index e9d765949..2d459d30a 100644
--- a/admin/www/i18n.html
+++ b/admin/www/i18n.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Wed Oct 23 09:40:34 2002 -->
+<!-- Mon Dec 9 08:32:58 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -171,7 +171,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->
diff --git a/admin/www/index.html b/admin/www/index.html
index c1ef6ef31..86b45d4f4 100644
--- a/admin/www/index.html
+++ b/admin/www/index.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Tue Nov 19 01:52:44 2002 -->
+<!-- Mon Dec 9 08:32:58 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -229,9 +229,9 @@ StudlyCaps).
<h3>Current Version</h3>
<p>Version
-(<!-VERSION--->2.1b5<!-VERSION--->,
+(<!-VERSION--->2.1b6<!-VERSION--->,
released on
-<!-DATE--->19-Nov-2002<!-DATE--->)
+<!-DATE--->09-Dec-2002<!-DATE--->)
is the current development release of the next version of Mailman.
This version is stable and is being used in some production
environments, but it may still have some lurking bugs. If you decide
diff --git a/admin/www/install-check.html b/admin/www/install-check.html
index a2ff5894b..4f90fcef3 100644
--- a/admin/www/install-check.html
+++ b/admin/www/install-check.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:16:33 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:58 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Check your installation
-->
-<HEAD>
-<TITLE>Check your installation</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Check your installation</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Check your installation</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Check your installation</h3>
After you've run "make install", you can check that your
@@ -209,7 +221,7 @@ Email Us
<li>Repeat previous step until no more errors are reported!
</ul>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-config.html b/admin/www/install-config.html
index b85fcda63..8357962a8 100644
--- a/admin/www/install-config.html
+++ b/admin/www/install-config.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:15:30 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:58 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Running configure
-->
-<HEAD>
-<TITLE>Running configure</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Running configure</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Running configure</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Running configure</h3>
<strong>TAKE SPECIAL NOTE OF THE --with-mail-gid AND --with-cgi-gid
@@ -294,7 +306,7 @@ Email Us
your <em>$PATH</em>.
</dl>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-custom.html b/admin/www/install-custom.html
index c3abea3b4..84dbdf214 100644
--- a/admin/www/install-custom.html
+++ b/admin/www/install-custom.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:23:15 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:58 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Customize Mailman
-->
-<HEAD>
-<TITLE>Customize Mailman</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Customize 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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Customize Mailman</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Customize Mailman</h3>
You should do these steps using the account you installed Mailman
@@ -227,7 +239,7 @@ $prefix/bin/mmsitepass your-site-password
</ul>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-faq.html b/admin/www/install-faq.html
index 15d98ff85..61080970d 100644
--- a/admin/www/install-faq.html
+++ b/admin/www/install-faq.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Wed Jul 11 23:44:04 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:58 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Common problems FAQ
-->
-<HEAD>
-<TITLE>Common problems FAQ</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Common problems FAQ</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Common problems FAQ</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Common Problems FAQ</h3>
<b>Problem:</b> All Mailman web pages give a <em>404 File not
@@ -307,7 +319,7 @@ Attempt to exec script with invalid gid 51, expected 99
</pre>
</blockquote>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-final.html b/admin/www/install-final.html
index db59e99de..bd95c78f5 100644
--- a/admin/www/install-final.html
+++ b/admin/www/install-final.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:23:15 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:58 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Final system setup
-->
-<HEAD>
-<TITLE>Final system setup</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Final system setup</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Final system setup</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Final system set-up</h3>
Congratulations! You've installed the Mailman software. To get
@@ -345,7 +357,7 @@ mailman-owner: mailman
aliases.
</ul>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-start.html b/admin/www/install-start.html
index 5948e55eb..0ddf92e4a 100644
--- a/admin/www/install-start.html
+++ b/admin/www/install-start.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:01:38 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:59 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Start installing Mailman
-->
-<HEAD>
-<TITLE>Start installing Mailman</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Start 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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<b>Installation</b>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Installation</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
<b>Start installing</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Start installing Mailman</h3>
These are the on-line instructions for installing Mailman from source.
@@ -204,7 +216,7 @@ upgrade.</em>
<li><a href="install-trouble.html">Troubleshooting</a>
<li><a href="install-faq.html">Common problems FAQ</a>
</ol>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-system.html b/admin/www/install-system.html
index 79f1b5ddf..070aade8d 100644
--- a/admin/www/install-system.html
+++ b/admin/www/install-system.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:07:17 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:59 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: System setup
-->
-<HEAD>
-<TITLE>System setup</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>System setup</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>System setup</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>System setup</h3>
<p><em>You will need to be <b>root</b> to perform the steps in this
@@ -240,7 +252,7 @@ Email Us
</ul>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-test.html b/admin/www/install-test.html
index 20b15b6b1..81ef100b0 100644
--- a/admin/www/install-test.html
+++ b/admin/www/install-test.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:27:31 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:59 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Create a test list
-->
-<HEAD>
-<TITLE>Create a test list</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Create a test list</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Create a test list</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-trouble.html">Troubleshooting</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-trouble.html">Troubleshooting</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Create a test list</h3>
To create and test your first list, try the following:
@@ -240,7 +252,7 @@ http://my.dom.ain/mailman/create
the <a href="install-trouble.html">Troubleshooting</a> section.
</ul>
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/install-trouble.html b/admin/www/install-trouble.html
index d5e348ca4..f6b56f82b 100644
--- a/admin/www/install-trouble.html
+++ b/admin/www/install-trouble.html
@@ -1,182 +1,194 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Thu Jul 12 00:30:11 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Dec 9 08:32:59 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
Title: Troubleshooting
-->
-<HEAD>
-<TITLE>Troubleshooting</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
- TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
- LINK="#0000bb" VLINK="#551a8b"
- ALINK="#ff0000">
+<head>
+<title>Troubleshooting</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>
+<table width="100%" border="0" cellspacing="0" cellpadding="0">
<!-- start of banner row -->
-<TR>
+<tr>
<!-- start of corner cells -->
-<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white">
+<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="#caa08f">&nbsp;&nbsp;</TD><!--spacer-->
+ <img border=0 src="./images/logo-70.jpg"></a></center> </td>
+<td width="15" bgcolor="#caa08f">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of corner cells -->
<!-- start of banner -->
-<TD WIDTH="90%" BGCOLOR="#caa08f">
+<td width="90%" bgcolor="#caa08f" class="banner">
<!-- start of site links table -->
-<TABLE WIDTH="100%" BORDER=0
+<table width="100%" border="0"
CELLSPACING=0 CELLPADDING=0
- COLS=3 ROWS=4 BGCOLOR="#ffffff">
-<TR>
- <TD BGCOLOR="#caa08f">
+ bgcolor="#ffffff">
+<tr>
+ <td bgcolor="#caa08f">
<a href="./index.html">Home</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./users.html">Users</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.list.org/">List.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./install-start.html">Installation</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./mgrs.html">List Managers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./faq.html">FAQ</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./admins.html">Site Administrators</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.python.org/">Python.Org</a>
- </TD>
-</TR><TR>
- <TD BGCOLOR="#caa08f">
+ </td>
+</tr><tr>
+ <td bgcolor="#caa08f">
<a href="./lists.html">Discussion Lists</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="./devs.html">Developers</a>
- </TD>
- <TD BGCOLOR="#caa08f">
+ </td>
+ <td bgcolor="#caa08f">
<a href="http://www.gnu.org/">Gnu.Org</a>
- </TD>
-</TR>
-</TABLE><!-- end of site links table -->
+ </td>
+</tr>
+</table><!-- end of site links table -->
-</TD><!-- end of banner -->
-</TR><!-- end of banner row -->
-<TR><!-- start of sidebar/body row -->
+</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="#caa08f">
+<td width="150" valign="top" bgcolor="#caa08f" class="sidebar">
<!-- start of sidebar table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3
- BGCOLOR="#ffffff">
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+<table width="100%" border="0" cellspacing="0" cellpadding="3"
+ bgcolor="#ffffff">
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Overview
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="index.html">Home</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="features.html">Features</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="download.html">Requirements, Download</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="lists.html">Discussion Lists</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="bugs.html">Bugs and Patches</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="faq.html">Frequently Asked Questions</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="inthenews.html">Mailman in Use</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="todo.html">Wishlist!</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="features.html">Features</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="download.html">Requirements, Download</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="lists.html">Discussion Lists</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="bugs.html">Bugs and Patches</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="faq.html">Frequently Asked Questions</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="inthenews.html">Mailman in Use</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="todo.html">Wishlist!</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
+Exits
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://listowners.org">Listowners.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Installing Mailman
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-start.html">Start installing</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-system.html">System setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-config.html">Running configure</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-check.html">Check your installation</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-final.html">Final system setup</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-custom.html">Customize Mailman</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-test.html">Create a test list</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-start.html">Start installing</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-system.html">System setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-config.html">Running configure</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-check.html">Check your installation</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-final.html">Final system setup</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-custom.html">Customize Mailman</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-test.html">Create a test list</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
<b>Troubleshooting</b>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="install-faq.html">Common problems FAQ</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">&nbsp;
-<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff">
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="install-faq.html">Common problems FAQ</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
Email Us
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="mailto:mailman-users@python.org">mailman-users@python.org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
<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="#caa08f">
+</td></tr>
+<tr><td bgcolor="#caa08f">
&nbsp;
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
-</TD></TR>
-</TABLE><!-- end of sidebar table -->
+</td></tr>
+<tr><td bgcolor="#caa08f">
+&copy; 1998-2002<br>Free Software Foundation, Inc.
+</td></tr>
+</table><!-- end of sidebar table -->
-</TD>
-<TD WIDTH=15>&nbsp;&nbsp;</TD><!--spacer-->
+</td>
+<td width="15">&nbsp;&nbsp;</td><!--spacer-->
<!-- end of sidebar cell -->
<!-- start of body cell -->
-<TD VALIGN=TOP WIDTH="90%"><BR>
+<td valign="top" width="90%" class="body"><br>
<h3>Troubleshooting</h3>
If you encounter problems with running Mailman, first check the
@@ -199,7 +211,7 @@ Email Us
version of Python you're using, and which version of Mailman
you're installing.
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html
index 5a5ea963b..0f6e75070 100644
--- a/admin/www/inthenews.html
+++ b/admin/www/inthenews.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Tue Nov 19 01:52:44 2002 -->
+<!-- Mon Dec 9 08:32:59 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
diff --git a/admin/www/lists.html b/admin/www/lists.html
index 89752edf6..b346a862e 100644
--- a/admin/www/lists.html
+++ b/admin/www/lists.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Sun May 5 00:30:17 2002 -->
+<!-- Mon Dec 9 08:32:59 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -149,7 +149,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->
diff --git a/admin/www/mgrs.html b/admin/www/mgrs.html
index 7452ab2b7..7ae4792af 100644
--- a/admin/www/mgrs.html
+++ b/admin/www/mgrs.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Fri Aug 2 11:48:08 2002 -->
+<!-- Mon Dec 9 08:32:59 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -171,7 +171,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->
diff --git a/admin/www/otherdocs.html b/admin/www/otherdocs.html
index 3c66edf83..287ab61cc 100644
--- a/admin/www/otherdocs.html
+++ b/admin/www/otherdocs.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Fri Aug 2 11:48:08 2002 -->
+<!-- Mon Dec 9 08:32:59 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -171,7 +171,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->
diff --git a/admin/www/todo.ht b/admin/www/todo.ht
index 3dd91433e..35f621426 100644
--- a/admin/www/todo.ht
+++ b/admin/www/todo.ht
@@ -1,11 +1,12 @@
Title: The Mailman Wishlist
+ <p>
<h3> The Mailman Wishlist
</h3>
<p>
-<h3> (Last Update: $Date: 2002-11-19 07:11:17 +0000 (Tue, 19 Nov 2002) $)
+<h3> (Last Update: $Date: 2002-12-09 13:34:43 +0000 (Mon, 09 Dec 2002) $)
</h3>
- Here's the wish list for future versions of Mailman. Many new
+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
@@ -14,12 +15,6 @@ Title: The Mailman Wishlist
<h3> Email Handling
</h3>
<ul>
- <li> 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
-
<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
@@ -34,22 +29,6 @@ Title: The Mailman Wishlist
<h3> Documentation
</h3>
<ul>
- <li> 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
-
- <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.
-
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -62,30 +41,6 @@ Title: The Mailman Wishlist
<h3> General Web UI
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
<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
@@ -100,40 +55,6 @@ Title: The Mailman Wishlist
<h3> List Administration
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
<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).
@@ -177,79 +98,6 @@ Title: The Mailman Wishlist
<h3> List Membership
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
<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.
@@ -268,93 +116,6 @@ Title: The Mailman Wishlist
<h3> Site Administration
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
<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.
@@ -365,99 +126,6 @@ Title: The Mailman Wishlist
<h3> Other Usability Improvments
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
<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.
@@ -468,105 +136,6 @@ Title: The Mailman Wishlist
<h3> Mailcmd interface
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
<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
@@ -581,115 +150,6 @@ Title: The Mailman Wishlist
<h3> Portability & architecture
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
<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)
@@ -705,126 +165,6 @@ Title: The Mailman Wishlist
<h3> Bounce handling
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
- <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.
-
<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).
@@ -832,129 +172,6 @@ Title: The Mailman Wishlist
<h3> Pipermail + Archiving mechanism
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
- <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.
-
- <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).
-
<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
@@ -968,138 +185,6 @@ Title: The Mailman Wishlist
<h3> Code cleanup
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
- <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.
-
- <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).
-
- <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.
-
<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
index b2ee939b3..b84604b69 100644
--- a/admin/www/todo.html
+++ b/admin/www/todo.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Tue Nov 19 01:52:44 2002 -->
+<!-- Mon Dec 9 08:33:00 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -158,12 +158,13 @@ Email Us
<!-- 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-11-19 07:11:17 +0000 (Tue, 19 Nov 2002) $)
+<h3> (Last Update: $Date: 2002-12-09 13:34:43 +0000 (Mon, 09 Dec 2002) $)
</h3>
- Here's the wish list for future versions of Mailman. Many new
+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
@@ -172,12 +173,6 @@ Email Us
<h3> Email Handling
</h3>
<ul>
- <li> 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
-
<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
@@ -192,22 +187,6 @@ Email Us
<h3> Documentation
</h3>
<ul>
- <li> 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
-
- <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.
-
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -220,30 +199,6 @@ Email Us
<h3> General Web UI
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
<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
@@ -258,40 +213,6 @@ Email Us
<h3> List Administration
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
<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).
@@ -335,79 +256,6 @@ Email Us
<h3> List Membership
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
<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.
@@ -426,93 +274,6 @@ Email Us
<h3> Site Administration
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
<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.
@@ -523,99 +284,6 @@ Email Us
<h3> Other Usability Improvments
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
<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.
@@ -626,105 +294,6 @@ Email Us
<h3> Mailcmd interface
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
<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
@@ -739,115 +308,6 @@ Email Us
<h3> Portability & architecture
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
<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)
@@ -863,126 +323,6 @@ Email Us
<h3> Bounce handling
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
- <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.
-
<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).
@@ -990,129 +330,6 @@ Email Us
<h3> Pipermail + Archiving mechanism
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
- <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.
-
- <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).
-
<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
@@ -1126,138 +343,6 @@ Email Us
<h3> Code cleanup
</h3>
<ul>
- <li> 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
-
- <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.
-
- <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
- <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.
-
- <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.
-
- <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.
-
- <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).
-
- <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.
-
- <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.
- <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.
-
- <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).
-
- <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.
-
<li> Turn all remaining string exceptions into class exceptions
<li> Unit and system test suite! (ongoing)
</ul>
diff --git a/admin/www/users.html b/admin/www/users.html
index a12d81875..ab1f028a7 100644
--- a/admin/www/users.html
+++ b/admin/www/users.html
@@ -1,7 +1,7 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Fri Aug 2 11:48:08 2002 -->
+<!-- Mon Dec 9 08:33:00 2002 -->
<!-- USING HT2HTML 2.0 -->
<!-- SEE http://ht2html.sf.net -->
<!-- User-specified headers:
@@ -171,7 +171,7 @@ Email Us
&nbsp;
</td></tr>
<tr><td bgcolor="#caa08f">
-&copy; 1998,1999,2000,2001<br>Free Software Foundation, Inc.
+&copy; 1998-2002<br>Free Software Foundation, Inc.
</td></tr>
</table><!-- end of sidebar table -->