Updates for 2.1b2

author: bwarsaw 2002-05-05 04:32:04 +0000
committer: bwarsaw 2002-05-05 04:32:04 +0000
commit: 63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a (patch)
tree: 9cbab1df0424850b0b5392cf08a51b4428fdac32
parent: 0932d983da0597cbfdf9eaffe3c272dee75930b7 (diff)
download: mailman-63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a.tar.gz
mailman-63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a.tar.zst
mailman-63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a.zip
13 files changed, 1053 insertions, 1244 deletions
diff --git a/admin/www/download.ht b/admin/www/download.ht
index 7847a440a..276d8dbff 100644
--- a/admin/www/download.ht
+++ b/admin/www/download.ht
@@ -3,8 +3,8 @@ Other-links:
     <h3>SMTP servers</h3>
     <li><a href="http://www.postfix.org/">Postfix</a>
     <li><a href="http://www.exim.org/">Exim</a>
-    <li><a href="http://www.qmail.org/">Qmail</a>
     <li><a href="http://www.sendmail.org/">Sendmail</a>
+    <li><a href="http://www.qmail.org/">Qmail</a>
     <h3>Other software</h3>
     <li><a href="http://www.apache.org/">Apache web server</a>
     <li><a href="http://www.gnu.org/software/gcc/">GNU C compiler</a>
@@ -26,9 +26,8 @@ community know</a> if you have success with this!)
 <p>
 Before you can run Mailman, you need to make sure that
 <a href="http://www.python.org/">Python</a> is installed.  Mailman 2.1
-requires at least Python 2.0 and is known to work with Python versions
-up to and including Python 2.2.  However, it is recommended that you use Python
-2.1.1 or Python 2.2.  Most GNU/Linux systems come with Python
+requires at least Python 2.1, although it is recommended that you use Python
+2.1.3 or Python 2.2.1.  Most GNU/Linux systems come with Python
 pre-installed, so you just need to make sure you're running an
 up-to-date version.  You can do this by executing the following at
 your shell's command line:
@@ -36,7 +35,7 @@ your shell's command line:
 <blockquote>
 <pre>
 % python -V
-Python 2.1.1
+Python 2.1.3
 </pre>
 </blockquote>
 
@@ -44,16 +43,11 @@ If your Python executable doesn't understand the <code>-V</code>
 option, it's probably too old!
 
 <p>You will also need an SMTP server (a.k.a. mail transport agent or
-<em>MTA</em>) for mail delivery and reception.
-<a href="http://www.sendmail.org/">Sendmail</a> is the oldest and most
-widely-used MTA, and comes pre-installed on most Unix systems, however it
-is not the recommended MTA to use with Mailman.  It works, but you may
-get better results from one of the newer MTAs.  Good results are
-reported on the <a href="lists.html">Mailman mailing lists</a> from
-people using <a href="http://www.postfix.org/">Postfix</a>,
-<a href="http://www.exim.org/">Exim</a>, and
-<a href="http://www.qmail.org/">Qmail</a>.  Most Mailman development
-is done with Postfix.
+<em>MTA</em>) for mail delivery and reception.  Mailman should work
+well with <a href="http://www.postfix.org/">Postfix</a>,
+<a href="http://www.exim.org/">Exim</a>,
+<a href="http://www.sendmail.org/">Sendmail</a> and
+<a href="http://www.qmail.org/">qmail</a>.
 
 <p>You will need a web server.
 <a href="http://www.apache.org/">Apache</a> is certainly the most
@@ -68,13 +62,13 @@ gcc 2.8.1 or later is known to work well.
 <h3>Downloading</h3>
 
 <p>Version
-(<!-VERSION--->2.1b1<!-VERSION--->,
+(<!-VERSION--->2.1b2<!-VERSION--->,
 released on
-<!-DATE--->16-Mar-2002<!-DATE--->)
-is an alpha release of the next version.  It is not recommended that
-this version be used in production systems yet.  This alpha release,
-and the current stable version 2.0.9, are available from the following
-mirror sites:
+<!-DATE--->05-May-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 current
+stable version 2.0.10 in your production environments.  Mailman is
+available from the following sources:
 
 <ul>
     <li><a href="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a>
diff --git a/admin/www/download.html b/admin/www/download.html
index 705ac7040..bf7db97ac 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>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Thu Apr  4 00:15:19 2002 -->
+<!-- Sun May  5 00:30:16 2002 -->
 <!-- USING HT2HTML 2.0 -->
 <!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
@@ -9,189 +9,194 @@ Title: Downloading Mailman
 
 -->
 
-<HEAD>
-<TITLE>Downloading Mailman</TITLE>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
-
-<STYLE TYPE="text/css">
-<!--
+<head>
+<title>Downloading Mailman</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
 body { margin: 0px; }
--->
-</STYLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+</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="MIDDLE" 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
-       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">
+</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">
 <b>Requirements, Download</b>
-</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">
+</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">
 SMTP servers
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.postfix.org/">Postfix</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.exim.org/">Exim</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.qmail.org/">Qmail</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.sendmail.org/">Sendmail</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://www.postfix.org/">Postfix</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.exim.org/">Exim</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.sendmail.org/">Sendmail</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.qmail.org/">Qmail</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
 Other software
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.apache.org/">Apache web server</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.gnu.org/software/gcc/">GNU C compiler</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://www.apache.org/">Apache web server</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.gnu.org/software/gcc/">GNU C compiler</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">&nbsp;
+<tr><td bgcolor="#545454"><b><font color="#ffffff">
 Mailman downloads
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="ftp://ftp.gnu.org/gnu/mailman/">From GNU</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.list.org/mailman.tar.gz">From List.Org</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</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="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.list.org/mailman.tar.gz">From List.Org</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</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">
+</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>
+</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>Requirements</h3>
 
 <p>Mailman currently runs only on GNU/Linux and any other Un*x-like
@@ -205,9 +210,8 @@ community know</a> if you have success with this!)
 <p>
 Before you can run Mailman, you need to make sure that
 <a href="http://www.python.org/">Python</a> is installed.  Mailman 2.1
-requires at least Python 2.0 and is known to work with Python versions
-up to and including Python 2.2.  However, it is recommended that you use Python
-2.1.1 or Python 2.2.  Most GNU/Linux systems come with Python
+requires at least Python 2.1, although it is recommended that you use Python
+2.1.3 or Python 2.2.1.  Most GNU/Linux systems come with Python
 pre-installed, so you just need to make sure you're running an
 up-to-date version.  You can do this by executing the following at
 your shell's command line:
@@ -215,7 +219,7 @@ your shell's command line:
 <blockquote>
 <pre>
 % python -V
-Python 2.1.1
+Python 2.1.3
 </pre>
 </blockquote>
 
@@ -223,16 +227,11 @@ If your Python executable doesn't understand the <code>-V</code>
 option, it's probably too old!
 
 <p>You will also need an SMTP server (a.k.a. mail transport agent or
-<em>MTA</em>) for mail delivery and reception.
-<a href="http://www.sendmail.org/">Sendmail</a> is the oldest and most
-widely-used MTA, and comes pre-installed on most Unix systems, however it
-is not the recommended MTA to use with Mailman.  It works, but you may
-get better results from one of the newer MTAs.  Good results are
-reported on the <a href="lists.html">Mailman mailing lists</a> from
-people using <a href="http://www.postfix.org/">Postfix</a>,
-<a href="http://www.exim.org/">Exim</a>, and
-<a href="http://www.qmail.org/">Qmail</a>.  Most Mailman development
-is done with Postfix.
+<em>MTA</em>) for mail delivery and reception.  Mailman should work
+well with <a href="http://www.postfix.org/">Postfix</a>,
+<a href="http://www.exim.org/">Exim</a>,
+<a href="http://www.sendmail.org/">Sendmail</a> and
+<a href="http://www.qmail.org/">qmail</a>.
 
 <p>You will need a web server.
 <a href="http://www.apache.org/">Apache</a> is certainly the most
@@ -247,13 +246,13 @@ gcc 2.8.1 or later is known to work well.
 <h3>Downloading</h3>
 
 <p>Version
-(<!-VERSION--->2.1b1<!-VERSION--->,
+(<!-VERSION--->2.1b2<!-VERSION--->,
 released on
-<!-DATE--->16-Mar-2002<!-DATE--->)
-is an alpha release of the next version.  It is not recommended that
-this version be used in production systems yet.  This alpha release,
-and the current stable version 2.0.9, are available from the following
-mirror sites:
+<!-DATE--->04-May-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 current
+stable version 2.0.10 in your production environments.  Mailman is
+available from the following sources:
 
 <ul>
     <li><a href="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a>
@@ -284,7 +283,7 @@ Note also that some versions of <code>tar</code> don't accept the
 </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/features.ht b/admin/www/features.ht
index 71a4d9bcf..f852524d1 100644
--- a/admin/www/features.ht
+++ b/admin/www/features.ht
@@ -5,7 +5,7 @@ Other-links:
 
 <h3>Mailman Features</h3>
 
-This is just a short summary of all the features of Mailman.
+This is just a short summary of all the features of Mailman 2.1.
 
 <ul>
 <li>Web based list administration for nearly all tasks, including list
@@ -22,7 +22,8 @@ This is just a short summary of all the features of Mailman.
     depending on the MTA).
 
 <li>Per-list privacy features, such as closed-subscriptions, private
-    archives, private membership rosters, etc.
+    archives, private membership rosters, and sender-based posting
+    rules.
 
 <li>Multi-lingual support: list web pages and email notices can be in
     any supported language, configurable per-site, per-list, and
@@ -39,7 +40,7 @@ This is just a short summary of all the features of Mailman.
     Automatic disposition of bouncing addresses (disable,
     unsubscribe).
 
-<li>Integrated spam filters.
+<li>Integrated spam filters and MIME-based content filters.
 
 <li>Automatic web-based Hypermail-style archiving, with hooks for
     external archivers such as
@@ -57,7 +58,7 @@ This is just a short summary of all the features of Mailman.
 
 <li>Runs on GNU/Linux and most Un*x-like systems, compatible with most
     web servers and browsers, and most SMTP servers.  Requires Python
-    2.0 or newer.
+    2.1 or newer.
 
 <li>An extensible mail delivery pipeline.
 
diff --git a/admin/www/features.html b/admin/www/features.html
index e41a04fe7..3fbc301ed 100644
--- a/admin/www/features.html
+++ b/admin/www/features.html
@@ -1,161 +1,173 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Wed Jul 11 23:55:09 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Sun May  5 00:30:17 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
 Title: Mailman Features
 
 -->
 
-<HEAD>
-<TITLE>Mailman Features</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+<head>
+<title>Mailman Features</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      marginwidth="0" marginheight="0"
+      link="#0000bb"  vlink="#551a8b"
+      alink="#ff0000">
 <!-- start of page table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0>
+<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">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="index.html">Home</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
 <b>Features</b>
-</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">
+</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">
 Exits
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</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://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</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">
+</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>
+</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>Mailman Features</h3>
 
-This is just a short summary of all the features of Mailman.
+This is just a short summary of all the features of Mailman 2.1.
 
 <ul>
 <li>Web based list administration for nearly all tasks, including list
@@ -172,7 +184,8 @@ This is just a short summary of all the features of Mailman.
     depending on the MTA).
 
 <li>Per-list privacy features, such as closed-subscriptions, private
-    archives, private membership rosters, etc.
+    archives, private membership rosters, and sender-based posting
+    rules.
 
 <li>Multi-lingual support: list web pages and email notices can be in
     any supported language, configurable per-site, per-list, and
@@ -189,7 +202,7 @@ This is just a short summary of all the features of Mailman.
     Automatic disposition of bouncing addresses (disable,
     unsubscribe).
 
-<li>Integrated spam filters.
+<li>Integrated spam filters and MIME-based content filters.
 
 <li>Automatic web-based Hypermail-style archiving, with hooks for
     external archivers such as
@@ -207,13 +220,13 @@ This is just a short summary of all the features of Mailman.
 
 <li>Runs on GNU/Linux and most Un*x-like systems, compatible with most
     web servers and browsers, and most SMTP servers.  Requires Python
-    2.0 or newer.
+    2.1 or newer.
 
 <li>An extensible mail delivery pipeline.
 
 <li>High-performance mail delivery, with a scalable architecture.
 
-</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/index.ht b/admin/www/index.ht
index 5771879ee..ff7ee06ca 100644
--- a/admin/www/index.ht
+++ b/admin/www/index.ht
@@ -38,9 +38,9 @@ StudlyCaps).
 <h3>Current Version</h3>
 
 <p>Version
-(<!-VERSION--->2.1b1<!-VERSION--->,
+(<!-VERSION--->2.1b2<!-VERSION--->,
 released on
-<!-DATE--->16-Mar-2002<!-DATE--->)
+<!-DATE--->05-May-2002<!-DATE--->)
 is the current development release of the next version of Mailman.
 Although, stable, it
 should <strong>not</strong> be 
diff --git a/admin/www/index.html b/admin/www/index.html
index da3631e90..ab9c75507 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>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Thu Apr  4 00:21:26 2002 -->
+<!-- Sun May  5 00:30:17 2002 -->
 <!-- USING HT2HTML 2.0 -->
 <!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
@@ -9,191 +9,196 @@ Title: Mailman, the GNU Mailing List Manager
 
 -->
 
-<HEAD>
-<TITLE>Mailman, the GNU Mailing List Manager</TITLE>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
-
-<STYLE TYPE="text/css">
-<!--
+<head>
+<title>Mailman, the GNU Mailing List Manager</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
 body { margin: 0px; }
--->
-</STYLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+</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="MIDDLE" 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
-       BGCOLOR="#ffffff">
-<TR>
-    <TD BGCOLOR="#caa08f">
+       bgcolor="#ffffff">
+<tr>
+    <td bgcolor="#caa08f">
 <b>Home</b>
-    </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">
+</font></b></td></tr>
+<tr><td bgcolor="#caa08f">
 <b>Home</b>
-</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">
+</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">
-<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">
+</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">
+<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">
 Exits
-</FONT></B></TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.python.org/">Python</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.gnu.org/">GNU/FSF</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.gnu.org/software/mailman/mailman.html">Mailman&nbsp;at&nbsp;GNU</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://www.list.org/">List.Org&nbsp;mirror</A>
-</TD></TR>
-<TR><TD BGCOLOR="#caa08f">
-<A HREF="http://barry.wooz.org/">Barry Warsaw</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://www.python.org/">Python</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.gnu.org/">GNU/FSF</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.gnu.org/software/mailman/mailman.html">Mailman&nbsp;at&nbsp;GNU</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://www.list.org/">List.Org&nbsp;mirror</a>
+</td></tr>
+<tr><td bgcolor="#caa08f">
+<a href="http://barry.wooz.org/">Barry Warsaw</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">
+</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>
+</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>Mailman, the GNU Mailing List Manager</h3>
 
@@ -224,9 +229,9 @@ StudlyCaps).
 <h3>Current Version</h3>
 
 <p>Version
-(<!-VERSION--->2.1b1<!-VERSION--->,
+(<!-VERSION--->2.1b2<!-VERSION--->,
 released on
-<!-DATE--->16-Mar-2002<!-DATE--->)
+<!-DATE--->04-May-2002<!-DATE--->)
 is the current development release of the next version of Mailman.
 Although, stable, it
 should <strong>not</strong> be 
@@ -268,7 +273,7 @@ you can use to link back to the Mailman website.
 </tr>
 </table>
 
-</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.ht b/admin/www/inthenews.ht
index a80d67857..1b5a32b2f 100644
--- a/admin/www/inthenews.ht
+++ b/admin/www/inthenews.ht
@@ -2,7 +2,11 @@ Title: Mailman in Use and in the News
 
 <h3>Mailman in Use and in the News</h3>
 
-Mailman was featured in a
+Mailman was featured as the Project of the Month in the
+<a href="http://www.linux-mag.com/2002-05/toc.html">May 2002 issue of
+Linux Magazine</a>.
+
+<p>Mailman was featured in a
 <a href="http://www.sunworld.com/swol-03-1999/swol-03-mailtools.html">
 cover story article</a> in the March 1999 issue
 of SunWorld.  The article was written by Cameron Laird and Kathryn
@@ -61,6 +65,9 @@ like to be included in this list, please
     Linux User Group mailing lists</a>
     <!-- Marc Merlin -->
     <li><a href="http://linuxia64.org/">IA-64 Linux Project</a>
+    <!-- Markus Grundmann -->
+    <li><a href="http://www.orsn.org/">ORSN, Open Root Server Network
+    in Europe</a>
     <!-- Jim Hebert -->
     <li><a href="http://www.cosource.com/">Cosource.com</a>
     <li><a href="http://www.vistasource.com/">VistaSource.com</a>
@@ -73,12 +80,8 @@ like to be included in this list, please
     <!-- Bill Hoffman -->
     <li><a href="http://public.kitware.com/">Visualization Tool Kit
     (VTK)</a>
-
-    <!-- J C Lawrence
-      -- <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a>
-      -- currently having h/w problems
-      -->
-
+    <!-- J C Lawrence -->
+    <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a>
     <!-- Michael Dunston -->
     <li><a href="http://www.music.vt.edu">Music and Technology
     Department, Virginia Tech School of the Arts</a>
@@ -361,5 +364,29 @@ like to be included in this list, please
     <!-- Erik J. Heels -->
     <a href="http://www.iserver.com">iServer</a> and
     <a href="http://www.lawlawlaw.com">www.lawlawlaw.com</a>
+    <!-- Peter Verhas -->
+    <a href="http://Scriptbasic.com">Scriptbasic.com</a>
+    <!-- webmaster@itxzone.com -->
+    <a href="http://www.itxzone.com/">ITXZONE: The Indian IT Zone</a>
+    <!-- renn@cy1000.com.tw>
+    <a href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+    >National Central University, Dept. of Civil Engineering, the 83th</a>
+    <!-- Jerry Feldman -->
+    <a href="http://www.blu.org/">Boston Linux and Unix user group</a>
+    <!-- Leandro Rache Sanchez -->
+    <a href="http://www.hipertek.net/">Hipertek Ltda.</a>
+    <!-- Jan Kampherbeek -->
+    <a href="http://spiderpro.com/">SpiderPro</a>
+    <!-- Porfirio Trincheiras -->
+    <a href="http://www.fmh.utl.pt">Faculdade de Motricidade Humana</a>
+    <a href="http://www.fmv.utl.pt">Faculdade de Medicina Veterin�ria</a>
+    <!-- info@compamerica.com -->
+    <a href="http://www.american-computer.com">American Computer</a>
+    <!-- Bob Radvanovsky -->
+    <a href="http://www.unixworks.net">Unixworks</a>
+    <!-- Mats Brante -->
+    <a href="http://www.osthyvel.net">Osthyvel.net</a>
+    <!-- Nemeth Tamas -->
+    <a href="http://lists.sek.nyme.hu">University of West Hungary</a>
 
 </ul>
diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html
index 68e2501f7..66b3c0089 100644
--- a/admin/www/inthenews.html
+++ b/admin/www/inthenews.html
@@ -1,154 +1,170 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Fri Mar 15 21:11:39 2002 -->
-<!-- USING HT2HTML 1.2 -->
-<!-- SEE http://barry.wooz.org/software/ht2html -->
+<!-- Sun May  5 00:30:17 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
 Title: Mailman in Use and in the News
 
 -->
 
-<HEAD>
-<TITLE>Mailman in Use and in the News</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+<head>
+<title>Mailman in Use and in the News</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      marginwidth="0" marginheight="0"
+      link="#0000bb"  vlink="#551a8b"
+      alink="#ff0000">
 <!-- start of page table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0>
+<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">
+</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">
 <b>Mailman in Use</b>
-</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="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">
 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">
+</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>
+</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>Mailman in Use and in the News</h3>
 
-Mailman was featured in a
+Mailman was featured as the Project of the Month in the
+<a href="http://www.linux-mag.com/2002-05/toc.html">May 2002 issue of
+Linux Magazine</a>.
+
+<p>Mailman was featured in a
 <a href="http://www.sunworld.com/swol-03-1999/swol-03-mailtools.html">
 cover story article</a> in the March 1999 issue
 of SunWorld.  The article was written by Cameron Laird and Kathryn
@@ -207,6 +223,9 @@ like to be included in this list, please
     Linux User Group mailing lists</a>
     <!-- Marc Merlin -->
     <li><a href="http://linuxia64.org/">IA-64 Linux Project</a>
+    <!-- Markus Grundmann -->
+    <li><a href="http://www.orsn.org/">ORSN, Open Root Server Network
+    in Europe</a>
     <!-- Jim Hebert -->
     <li><a href="http://www.cosource.com/">Cosource.com</a>
     <li><a href="http://www.vistasource.com/">VistaSource.com</a>
@@ -219,12 +238,8 @@ like to be included in this list, please
     <!-- Bill Hoffman -->
     <li><a href="http://public.kitware.com/">Visualization Tool Kit
     (VTK)</a>
-
-    <!-- J C Lawrence
-      -- <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a>
-      -- currently having h/w problems
-      -->
-
+    <!-- J C Lawrence -->
+    <li><a href="https://www.kanga.nu/lists/listinfo/">Kanga.NU<a>
     <!-- Michael Dunston -->
     <li><a href="http://www.music.vt.edu">Music and Technology
     Department, Virginia Tech School of the Arts</a>
@@ -507,10 +522,34 @@ like to be included in this list, please
     <!-- Erik J. Heels -->
     <a href="http://www.iserver.com">iServer</a> and
     <a href="http://www.lawlawlaw.com">www.lawlawlaw.com</a>
+    <!-- Peter Verhas -->
+    <a href="http://Scriptbasic.com">Scriptbasic.com</a>
+    <!-- webmaster@itxzone.com -->
+    <a href="http://www.itxzone.com/">ITXZONE: The Indian IT Zone</a>
+    <!-- renn@cy1000.com.tw>
+    <a href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+    >National Central University, Dept. of Civil Engineering, the 83th</a>
+    <!-- Jerry Feldman -->
+    <a href="http://www.blu.org/">Boston Linux and Unix user group</a>
+    <!-- Leandro Rache Sanchez -->
+    <a href="http://www.hipertek.net/">Hipertek Ltda.</a>
+    <!-- Jan Kampherbeek -->
+    <a href="http://spiderpro.com/">SpiderPro</a>
+    <!-- Porfirio Trincheiras -->
+    <a href="http://www.fmh.utl.pt">Faculdade de Motricidade Humana</a>
+    <a href="http://www.fmv.utl.pt">Faculdade de Medicina Veterin�ria</a>
+    <!-- info@compamerica.com -->
+    <a href="http://www.american-computer.com">American Computer</a>
+    <!-- Bob Radvanovsky -->
+    <a href="http://www.unixworks.net">Unixworks</a>
+    <!-- Mats Brante -->
+    <a href="http://www.osthyvel.net">Osthyvel.net</a>
+    <!-- Nemeth Tamas -->
+    <a href="http://lists.sek.nyme.hu">University of West Hungary</a>
 
 </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/links.h b/admin/www/links.h
index f1351f0f9..f8c880a85 100644
--- a/admin/www/links.h
+++ b/admin/www/links.h
@@ -9,3 +9,6 @@
 <li><a href="faq.html">Frequently Asked Questions</a>
 <li><a href="inthenews.html">Mailman in Use</a>
 <li><a href="todo.html">Wishlist!</a>
+<h3>Exits</h3>
+<li><a href="http://listowners.org">Listowners.Org</a>
+<!-- add a link to listowners.org/faq -->
diff --git a/admin/www/lists.ht b/admin/www/lists.ht
index 933e47dd3..60855113d 100644
--- a/admin/www/lists.ht
+++ b/admin/www/lists.ht
@@ -6,13 +6,6 @@ We have several mailing lists devoted to Mailman, which also provide a
 nice demonstration of Mailman!
 
 <ul>
-<li><a href="http://www.python.org/mailman/listinfo/mailman-announce">
-    Mailman Announce</a> is a read-only list that you can subscribe to 
-    if you are only interested in release notices and other important
-    news.  Only the core Mailman developers can post messages to this
-    list.
-    (<a href="http://www.python.org/pipermail/mailman-announce/"><em>archives</em></a>)
-
 <p><li><a href="http://www.python.org/mailman/listinfo/mailman-users">
     Mailman Users</a> is the mailing list to subscribe to if you are
     using Mailman at your site, and may have problems or questions
@@ -20,6 +13,19 @@ nice demonstration of Mailman!
     technical discussions off this list.
     (<a href="http://www.python.org/pipermail/mailman-users/"><em>archives</em></a>)
 
+<li><a href="http://listowner.org/">Listowners</a>
+    is a mailing list with a non-technical focus, specifically for
+    discussions from the perspective of listowners and moderators
+    who do not have "shell access" to the mailing list server
+    where the Mailman software runs.
+
+<li><a href="http://www.python.org/mailman/listinfo/mailman-announce">
+    Mailman Announce</a> is a read-only list that you can subscribe to 
+    if you are only interested in release notices and other important
+    news.  Only the core Mailman developers can post messages to this
+    list.
+    (<a href="http://www.python.org/pipermail/mailman-announce/"><em>archives</em></a>)
+
 <p><li><a href="http://www.python.org/mailman/listinfo/mailman-developers">
     Mailman Developers</a> is the mailing list to use if you are
     interested in helping us develop Mailman, discuss future
diff --git a/admin/www/lists.html b/admin/www/lists.html
index c1306d832..89752edf6 100644
--- a/admin/www/lists.html
+++ b/admin/www/lists.html
@@ -1,164 +1,169 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Mon Dec 31 18:19:22 2001 -->
-<!-- USING HT2HTML 1.2 -->
-<!-- SEE http://barry.wooz.org/software/ht2html -->
+<!-- Sun May  5 00:30:17 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
 Title: Mailman mailing lists
 
 -->
 
-<HEAD>
-<TITLE>Mailman mailing lists</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+<head>
+<title>Mailman mailing lists</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      marginwidth="0" marginheight="0"
+      link="#0000bb"  vlink="#551a8b"
+      alink="#ff0000">
 <!-- start of page table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0>
+<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">
 <b>Discussion Lists</b>
-    </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">
+</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">
 <b>Discussion Lists</b>
-</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="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">
 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">
+</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>
+</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>Mailman mailing lists</h3>
 
 We have several mailing lists devoted to Mailman, which also provide a 
 nice demonstration of Mailman!
 
 <ul>
-<li><a href="http://www.python.org/mailman/listinfo/mailman-announce">
-    Mailman Announce</a> is a read-only list that you can subscribe to 
-    if you are only interested in release notices and other important
-    news.  Only the core Mailman developers can post messages to this
-    list.
-    (<a href="http://www.python.org/pipermail/mailman-announce/"><em>archives</em></a>)
-
 <p><li><a href="http://www.python.org/mailman/listinfo/mailman-users">
     Mailman Users</a> is the mailing list to subscribe to if you are
     using Mailman at your site, and may have problems or questions
@@ -166,6 +171,19 @@ nice demonstration of Mailman!
     technical discussions off this list.
     (<a href="http://www.python.org/pipermail/mailman-users/"><em>archives</em></a>)
 
+<li><a href="http://listowner.org/">Listowners</a>
+    is a mailing list with a non-technical focus, specifically for
+    discussions from the perspective of listowners and moderators
+    who do not have "shell access" to the mailing list server
+    where the Mailman software runs.
+
+<li><a href="http://www.python.org/mailman/listinfo/mailman-announce">
+    Mailman Announce</a> is a read-only list that you can subscribe to 
+    if you are only interested in release notices and other important
+    news.  Only the core Mailman developers can post messages to this
+    list.
+    (<a href="http://www.python.org/pipermail/mailman-announce/"><em>archives</em></a>)
+
 <p><li><a href="http://www.python.org/mailman/listinfo/mailman-developers">
     Mailman Developers</a> is the mailing list to use if you are
     interested in helping us develop Mailman, discuss future
@@ -200,7 +218,7 @@ nice demonstration of Mailman!
 Some of the Mailman developers also occasionally hang out on the
 <em>mailman</em> IRC channel at openprojects.net.
 
-</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/todo.ht b/admin/www/todo.ht
index 64bee828a..b8b495623 100644
--- a/admin/www/todo.ht
+++ b/admin/www/todo.ht
@@ -3,9 +3,8 @@ Title: The Mailman Wishlist
 <h3> The Mailman Wishlist
 </h3>
  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ features have been added to Mailman 2.1, so what's left will
+ probably end up in a Mailman 3.0.
  Please also see the Mailman design notes wiki at
  http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
 <p>
@@ -13,31 +12,25 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
 </ul>
 <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 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -51,16 +44,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -71,8 +61,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -81,16 +71,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -101,8 +88,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -110,8 +97,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -120,23 +105,18 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
 </ul>
 <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 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -147,8 +127,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -156,8 +136,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -166,11 +144,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -181,9 +154,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -193,16 +163,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -213,8 +180,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -222,8 +189,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -232,11 +197,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -247,9 +207,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -265,16 +222,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -285,8 +239,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -294,8 +248,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -304,11 +256,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -319,9 +266,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -333,8 +277,7 @@ Title: The Mailman Wishlist
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -344,16 +287,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -364,8 +304,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -373,8 +313,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -383,11 +321,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -398,9 +331,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -412,8 +342,7 @@ Title: The Mailman Wishlist
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -433,16 +362,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -453,8 +379,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -462,8 +388,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -472,11 +396,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -487,9 +406,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -501,8 +417,7 @@ Title: The Mailman Wishlist
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -521,12 +436,7 @@ Title: The Mailman Wishlist
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -538,16 +448,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -558,8 +465,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -567,8 +474,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -577,11 +482,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -592,9 +492,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -606,8 +503,7 @@ Title: The Mailman Wishlist
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -626,12 +522,7 @@ Title: The Mailman Wishlist
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -641,22 +532,18 @@ Title: The Mailman Wishlist
     <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> Delete bounce disabled address after some period of retry
 </ul>
 <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 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -667,8 +554,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -676,8 +563,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -686,11 +571,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -701,9 +581,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -715,8 +592,7 @@ Title: The Mailman Wishlist
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -735,12 +611,7 @@ Title: The Mailman Wishlist
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -750,13 +621,10 @@ Title: The Mailman Wishlist
     <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> Delete bounce disabled address after some period of retry
     <li> Search engine for archives
     <li> Provide downloadable tar.gz's of the html archives
     <li> sort by date should go most-recent to oldest
     <li> allow list owner to edit archive messages
-    <li> archive link should do *something* reasonable before the first message has been posted to the list.
-
     <li> optional form front-end to public interfaces as a filter to address harvesters.
 
     <li> In general the whole Pipermail subsystem needs a good rewrite.
@@ -765,16 +633,13 @@ Title: The Mailman Wishlist
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -785,8 +650,8 @@ Title: The Mailman Wishlist
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -794,8 +659,6 @@ Title: The Mailman Wishlist
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -804,11 +667,6 @@ Title: The Mailman Wishlist
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -819,9 +677,6 @@ Title: The Mailman Wishlist
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -833,8 +688,7 @@ Title: The Mailman Wishlist
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -853,12 +707,7 @@ Title: The Mailman Wishlist
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -868,16 +717,13 @@ Title: The Mailman Wishlist
     <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> Delete bounce disabled address after some period of retry
     <li> Search engine for archives
     <li> Provide downloadable tar.gz's of the html archives
     <li> sort by date should go most-recent to oldest
     <li> allow list owner to edit archive messages
-    <li> archive link should do *something* reasonable before the first message has been posted to the list.
-
     <li> optional form front-end to public interfaces as a filter to address harvesters.
 
     <li> In general the whole Pipermail subsystem needs a good rewrite.
     <li> Turn all remaining string exceptions into class exceptions
-    <li> Unit and system test suite!
+    <li> Unit and system test suite! (ongoing)
 </ul>
diff --git a/admin/www/todo.html b/admin/www/todo.html
index af3518346..94de89cdc 100644
--- a/admin/www/todo.html
+++ b/admin/www/todo.html
@@ -1,157 +1,168 @@
-<HTML>
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
 <!-- THIS PAGE IS AUTOMATICALLY GENERATED.  DO NOT EDIT. -->
-<!-- Fri Mar  8 10:49:56 2002 -->
-<!-- USING HT2HTML 1.2 -->
-<!-- SEE http://barry.wooz.org/software/ht2html -->
+<!-- Sun May  5 00:30:17 2002 -->
+<!-- USING HT2HTML 2.0 -->
+<!-- SEE http://ht2html.sf.net -->
 <!-- User-specified headers:
 Title: The Mailman Wishlist
 
 -->
 
-<HEAD>
-<TITLE>The Mailman Wishlist</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff" TEXT="#000000"
-      TOPMARGIN="0" LEFTMARGIN="0" MARGINWIDTH="0" MARGINHEIGHT="0"
-      LINK="#0000bb"  VLINK="#551a8b"
-      ALINK="#ff0000">
+<head>
+<title>The Mailman Wishlist</title>
+<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+<meta name="generator" content="HT2HTML/2.0">
+<style type="text/css">
+body { margin: 0px; }
+</style>
+</head>
+<body bgcolor="#ffffff" text="#000000"
+      marginwidth="0" marginheight="0"
+      link="#0000bb"  vlink="#551a8b"
+      alink="#ff0000">
 <!-- start of page table -->
-<TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0>
+<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">
+</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">
 <b>Wishlist!</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">
+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">
 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">
+</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>
+</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> The Mailman Wishlist
 </h3>
  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ features have been added to Mailman 2.1, so what's left will
+ probably end up in a Mailman 3.0.
  Please also see the Mailman design notes wiki at
  http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage
 <p>
@@ -159,31 +170,25 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
 </ul>
 <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 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -197,16 +202,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -217,8 +219,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -227,16 +229,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -247,8 +246,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -256,8 +255,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -266,23 +263,18 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
 </ul>
 <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 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -293,8 +285,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -302,8 +294,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -312,11 +302,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -327,9 +312,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -339,16 +321,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -359,8 +338,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -368,8 +347,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -378,11 +355,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -393,9 +365,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -411,16 +380,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -431,8 +397,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -440,8 +406,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -450,11 +414,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -465,9 +424,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -479,8 +435,7 @@ Email Us
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -490,16 +445,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -510,8 +462,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -519,8 +471,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -529,11 +479,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -544,9 +489,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -558,8 +500,7 @@ Email Us
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -579,16 +520,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -599,8 +537,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -608,8 +546,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -618,11 +554,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -633,9 +564,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -647,8 +575,7 @@ Email Us
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -667,12 +594,7 @@ Email Us
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -684,16 +606,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -704,8 +623,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -713,8 +632,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -723,11 +640,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -738,9 +650,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -752,8 +661,7 @@ Email Us
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -772,12 +680,7 @@ Email Us
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -787,22 +690,18 @@ Email Us
     <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> Delete bounce disabled address after some period of retry
 </ul>
 <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 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -813,8 +712,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -822,8 +721,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -832,11 +729,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -847,9 +739,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -861,8 +750,7 @@ Email Us
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -881,12 +769,7 @@ Email Us
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -896,13 +779,10 @@ Email Us
     <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> Delete bounce disabled address after some period of retry
     <li> Search engine for archives
     <li> Provide downloadable tar.gz's of the html archives
     <li> sort by date should go most-recent to oldest
     <li> allow list owner to edit archive messages
-    <li> archive link should do *something* reasonable before the first message has been posted to the list.
-
     <li> optional form front-end to public interfaces as a filter to address harvesters.
 
     <li> In general the whole Pipermail subsystem needs a good rewrite.
@@ -911,16 +791,13 @@ Email Us
 </h3>
 <ul>
     <li>  Here's the wish list for future versions of Mailman.  Many new
- features have been added to Mailman 2.1 (still in alpha as of this
- writing 21-Jan-2002), so what's left will probably end up in a
- Mailman 3.0.
+ 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 bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly
- (optional).
+    <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional).
 
-    <li> allow customizable notices on moderated member helds and discards
     <li> A detailed feature list
     <li> A user's guide
     <li> A site-admin's guide
@@ -931,8 +808,8 @@ Email Us
     <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 template language/system like Zope's Presentation Templates,
- Quixote, or PHP.
+ 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.
@@ -940,8 +817,6 @@ Email Us
  message was edited by the moderator).
 
     <li> Allow the admin to disable option settings by users
-    <li> Ability to set defaults for the various user settings from the "Membership Management" page.
-
     <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes
  very useful, but could be dangerous!)
 
@@ -950,11 +825,6 @@ Email Us
     <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> Add an option to include Reply-To: header in the membership test for a members-only list posting
-
-    <li> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers.  Be smarter about filtering out
- duplicate deliveries.
-
     <li> Have one account per user per site, with multiple email addresses and fallbacks.  Allow them to subscribe whichever
  address they want to whichever list, with different options per
  subscription.
@@ -965,9 +835,6 @@ Email Us
 
     <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks.
 
-    <li> Mailing list invitations; i.e. a middle ground between "mass subscribe" and informally mailing a bunch of folks to tell them
- about the list.
-
     <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.
@@ -979,8 +846,7 @@ Email Us
  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.  Majordomo2 is
- reported to have some good features in this regard.
+ 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.
@@ -999,12 +865,7 @@ Email Us
  relational database, ZODB, LDAP, etc)
 
     <li> Member profiles
-    <li> Do a serious and thorough security audit (ongoing)
     <li> Allow lists of the same name in two different virtual domains
-    <li> More sophisticated attachment handling: strip and discard attachments, post attachments (e.g. via WebDAV) and rewrite to
- include URLs, etc.  Should be admin configurable based on MIME
- type.  Check out Bill Bumgarner's work on this.
-
     <li> Should 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.
@@ -1014,21 +875,18 @@ Email Us
     <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> Delete bounce disabled address after some period of retry
     <li> Search engine for archives
     <li> Provide downloadable tar.gz's of the html archives
     <li> sort by date should go most-recent to oldest
     <li> allow list owner to edit archive messages
-    <li> archive link should do *something* reasonable before the first message has been posted to the list.
-
     <li> optional form front-end to public interfaces as a filter to address harvesters.
 
     <li> In general the whole Pipermail subsystem needs a good rewrite.
     <li> Turn all remaining string exceptions into class exceptions
-    <li> Unit and system test suite!
+    <li> Unit and system test suite! (ongoing)
 </ul>
 
-</TD><!-- end of body cell -->
-</TR><!-- end of sidebar/body row -->
-</TABLE><!-- end of page table -->
-</BODY></HTML>
+</td><!-- end of body cell -->
+</tr><!-- end of sidebar/body row -->
+</table><!-- end of page table -->
+</body></html>
author	bwarsaw	2002-05-05 04:32:04 +0000
committer	bwarsaw	2002-05-05 04:32:04 +0000
commit	63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a (patch)
tree	9cbab1df0424850b0b5392cf08a51b4428fdac32
parent	0932d983da0597cbfdf9eaffe3c272dee75930b7 (diff)
download	mailman-63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a.tar.gz mailman-63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a.tar.zst mailman-63b85c6fe3b9a6844ffcca548f7ed8c05c0cea8a.zip