diff options
40 files changed, 3335 insertions, 1477 deletions
diff --git a/admin/www/MMGenerator.py b/admin/www/MMGenerator.py index cd76dbed8..c40690dad 100644 --- a/admin/www/MMGenerator.py +++ b/admin/www/MMGenerator.py @@ -105,8 +105,11 @@ class MMGenerator(Skeleton, Sidebar, Banner): def get_lightshade(self): """Return lightest of 3 color scheme shade.""" - return '#99997c' + # The Mailman logo's foreground is approximately #da7074 + #return '#99997c' + #return '#a39c82' + return '#caa08f' def get_darkshade(self): """Return darkest of 3 color scheme shade.""" - return '#663300' + return '#545454' diff --git a/admin/www/admins.ht b/admin/www/admins.ht index 31eae4f86..06015c11a 100644 --- a/admin/www/admins.ht +++ b/admin/www/admins.ht @@ -26,12 +26,22 @@ usually <code>/home/mailman</code></em>. members, select whether various notification emails are sent, and choose which list to add the members to. +<dt><b>addlang</b> +<dd>Use this to add language support to a specific list. The site + itself must have the language pack to add already installed. Note + that removing language support from a list requires you to + manually <tt>rm</tt> the lists/<em>yourlist</em>/<em>lang</em> + subdirectory. + <dt><b>arch</b> <dd>Use this to rebuild a list's archive. This script can't be used to modify a list's raw mbox file, but once you've edited the mbox file some other way, you can use this script to regenerate the HTML version of the on-line archive. +<dt><b>change_pw</b> +<dd>Use this to change the password for a specific mailing list. + <dt><b>check_db</b> <dd>Use this script to check the integrity of a list's <code>config.db</code> and <code>config.db.last</code> database @@ -80,13 +90,21 @@ web_page_url = 'http://www.mynewsite.com/mailman-relocated/' database file. These files usually contain Python marshaled dictionaries, and can be found in the <code>qfiles</code> directory, the <code>lists/<em>listname</em></code> directory, - etc. + etc. This script can also be used to print out the contents of a + pickled message file, which are stored in <code>.pck</code> files. <dt><b>find_member</b> <dd>Use this script to search all the lists, or some subset of lists, for an address matching a regular expression. command line options let you also search the list managers as well. +<dt><b>genaliases</b> +<dd>Use this script to regenerate the plain text and <em>db</em> alias + files for Postfix (if you're using Postfix as you're MTA). + +<dt><b>list_admins</b> +<dd>List all the owners of a mailing list. + <dt><b>list_lists</b> <dd>List all, or some subset of, the mailing lists in the system. @@ -95,6 +113,10 @@ web_page_url = 'http://www.mynewsite.com/mailman-relocated/' print just the regular or just the digest members, print the case-preserved addresses of the members, etc. +<dt><b>mailmanctl</b> +<dd>The main qrunner control script. Use this to start, stop, and + restart the qrunner. + <dt><b>mmsitepass</b> <dd>Use this script to set the site password, which can be used any where in the system a list or user password can be used. @@ -107,6 +129,9 @@ web_page_url = 'http://www.mynewsite.com/mailman-relocated/' <dt><b>newlist</b> <dd>Use this script to create new mailing lists. +<dt><b>qrunner</b> +<dd>Use this to run a single qrunner once (for debugging). + <dt><b>remove_members</b> <dd>Use this list to remove members from a mailing list. @@ -209,10 +234,6 @@ cron scripts do: <dt><b>nightly_gzip</b> <dd>Regenerates the Pipermail <code>gzip</code>'d flat archive files. -<dt><b>qrunner</b> -<dd>This is the primary cron script for processing messages in - Mailman's queue directory <code>qfiles</code>. - <dt><b>senddigests</b> <dd>Sends all accumulated digests. diff --git a/admin/www/admins.html b/admin/www/admins.html index d83642635..8a61ec912 100644 --- a/admin/www/admins.html +++ b/admin/www/admins.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:35 2001 --> +<!-- Thu Jul 12 00:43:55 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Site Administrator Documentation <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>Site Administrators</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,73 +81,73 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="users.html">Users</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mgrs.html">List Managers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Site Administrators</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="devs.html">Developers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="i18n.html">Internationalization</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="otherdocs.html">Other Documentation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -155,10 +155,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -193,12 +193,22 @@ usually <code>/home/mailman</code></em>. members, select whether various notification emails are sent, and choose which list to add the members to. +<dt><b>addlang</b> +<dd>Use this to add language support to a specific list. The site + itself must have the language pack to add already installed. Note + that removing language support from a list requires you to + manually <tt>rm</tt> the lists/<em>yourlist</em>/<em>lang</em> + subdirectory. + <dt><b>arch</b> <dd>Use this to rebuild a list's archive. This script can't be used to modify a list's raw mbox file, but once you've edited the mbox file some other way, you can use this script to regenerate the HTML version of the on-line archive. +<dt><b>change_pw</b> +<dd>Use this to change the password for a specific mailing list. + <dt><b>check_db</b> <dd>Use this script to check the integrity of a list's <code>config.db</code> and <code>config.db.last</code> database @@ -247,13 +257,21 @@ web_page_url = 'http://www.mynewsite.com/mailman-relocated/' database file. These files usually contain Python marshaled dictionaries, and can be found in the <code>qfiles</code> directory, the <code>lists/<em>listname</em></code> directory, - etc. + etc. This script can also be used to print out the contents of a + pickled message file, which are stored in <code>.pck</code> files. <dt><b>find_member</b> <dd>Use this script to search all the lists, or some subset of lists, for an address matching a regular expression. command line options let you also search the list managers as well. +<dt><b>genaliases</b> +<dd>Use this script to regenerate the plain text and <em>db</em> alias + files for Postfix (if you're using Postfix as you're MTA). + +<dt><b>list_admins</b> +<dd>List all the owners of a mailing list. + <dt><b>list_lists</b> <dd>List all, or some subset of, the mailing lists in the system. @@ -262,6 +280,10 @@ web_page_url = 'http://www.mynewsite.com/mailman-relocated/' print just the regular or just the digest members, print the case-preserved addresses of the members, etc. +<dt><b>mailmanctl</b> +<dd>The main qrunner control script. Use this to start, stop, and + restart the qrunner. + <dt><b>mmsitepass</b> <dd>Use this script to set the site password, which can be used any where in the system a list or user password can be used. @@ -274,6 +296,9 @@ web_page_url = 'http://www.mynewsite.com/mailman-relocated/' <dt><b>newlist</b> <dd>Use this script to create new mailing lists. +<dt><b>qrunner</b> +<dd>Use this to run a single qrunner once (for debugging). + <dt><b>remove_members</b> <dd>Use this list to remove members from a mailing list. @@ -376,10 +401,6 @@ cron scripts do: <dt><b>nightly_gzip</b> <dd>Regenerates the Pipermail <code>gzip</code>'d flat archive files. -<dt><b>qrunner</b> -<dd>This is the primary cron script for processing messages in - Mailman's queue directory <code>qfiles</code>. - <dt><b>senddigests</b> <dd>Sends all accumulated digests. diff --git a/admin/www/bugs.html b/admin/www/bugs.html index 866bdfc46..9be3e2742 100644 --- a/admin/www/bugs.html +++ b/admin/www/bugs.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:35 2001 --> +<!-- Wed Jul 11 23:44:02 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Bugs and Patches <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,64 +81,64 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Bugs and Patches</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Exits </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://sourceforge.net/bugs/?group_id=103">Bug Tracker</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://sourceforge.net/patch/?group_id=103">Patch Manager</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://sourceforge.net/projects/mailman">Mailman Project</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -146,10 +146,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> diff --git a/admin/www/devs.html b/admin/www/devs.html index ad838b936..f1a45f00b 100644 --- a/admin/www/devs.html +++ b/admin/www/devs.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:35 2001 --> +<!-- Wed Jul 11 23:44:02 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Developer Documentation <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>Developers</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,73 +81,73 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="users.html">Users</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mgrs.html">List Managers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="admins.html">Site Administrators</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Developers</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="i18n.html">Internationalization</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="otherdocs.html">Other Documentation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -155,10 +155,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> diff --git a/admin/www/download.ht b/admin/www/download.ht index 0ade845c7..e675d7a0c 100644 --- a/admin/www/download.ht +++ b/admin/www/download.ht @@ -15,31 +15,33 @@ Other-links: <h3>Requirements</h3> -<p>Mailman currently runs only on Unix-y systems, such as GNU/Linux, -Solaris, *BSD, etc. It should work on MacOSX but not earlier versions -of MacOS. It probably does not work on Windows, although it's -possible you could get it running on a Cygwin system (please -<a href="mailto:mailman-developers@python.org">let the developer +<p>Mailman currently runs only on GNU/Linux and any other Un*x-like +operating system, such as *BSD, Solaris, etc. It should work on +MacOSX but not earlier versions of MacOS. It probably does not work +on Windows, although it's possible you could get it running on a +Cygwin system (please <a +href="mailto:mailman-developers@python.org">let the developer community know</a> if you have success with this!) <p> Before you can run Mailman, you need to make sure that -<a href="http://www.python.org/">Python</a> is installed. Mailman -requires at least Python 1.5.2 and is known to work with Python 1.6 -and Python 2.0. 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: +<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.2alpha. Most GNU/Linux systems come with +Python pre-installed, so you just need to make sure you're running an +up-to-date version. You can do this by executing the following at +your shell's command line: <blockquote> <pre> -% python -Python 2.0 (#128, Oct 18 2000, 04:48:44) -[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 -Type "copyright", "credits" or "license" for more information. ->>> ^D +% python -V +Python 2.1 </pre> </blockquote> +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 @@ -65,10 +67,13 @@ gcc 2.8.1 or later is known to work well. <h3>Downloading</h3> <p>Version -(<!-VERSION--->2.1a1<!-VERSION--->, +(<!-VERSION--->2.1a2<!-VERSION--->, released on -<!-DATE--->Mar 4 2001<!-DATE--->) -is the current GNU release. It is available from the following mirror sites: +<!-DATE--->11-Jul-2001<!-DATE--->) +is an alpha release of the next version. It is not recommended that +this version be used in production systems yet. It, and the current +stable version 2.0.5, is available from +the following mirror sites: <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 9b515304d..114a22e48 100644 --- a/admin/www/download.html +++ b/admin/www/download.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:36 2001 --> +<!-- Thu Jul 12 00:00:07 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Downloading Mailman <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,90 +81,90 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Requirements, Download</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> SMTP servers </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.postfix.org/">Postfix</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.exim.org/">Exim</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.qmail.org/">Qmail</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.sendmail.org/">Sendmail</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Other software </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.apache.org/">Apache web server</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.gnu.org/software/gcc/">GNU C compiler</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Mailman downloads </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="ftp://ftp.gnu.org/gnu/mailman/">From GNU</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.list.org/mailman.tar.gz">From List.Org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://sourceforge.net/project/showfiles.php?group_id=103">From SourceForge</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -172,10 +172,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -187,31 +187,33 @@ Email Us <TD VALIGN=TOP WIDTH="90%"><BR> <h3>Requirements</h3> -<p>Mailman currently runs only on Unix-y systems, such as GNU/Linux, -Solaris, *BSD, etc. It should work on MacOSX but not earlier versions -of MacOS. It probably does not work on Windows, although it's -possible you could get it running on a Cygwin system (please -<a href="mailto:mailman-developers@python.org">let the developer +<p>Mailman currently runs only on GNU/Linux and any other Un*x-like +operating system, such as *BSD, Solaris, etc. It should work on +MacOSX but not earlier versions of MacOS. It probably does not work +on Windows, although it's possible you could get it running on a +Cygwin system (please <a +href="mailto:mailman-developers@python.org">let the developer community know</a> if you have success with this!) <p> Before you can run Mailman, you need to make sure that -<a href="http://www.python.org/">Python</a> is installed. Mailman -requires at least Python 1.5.2 and is known to work with Python 1.6 -and Python 2.0. 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: +<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.2alpha. Most GNU/Linux systems come with +Python pre-installed, so you just need to make sure you're running an +up-to-date version. You can do this by executing the following at +your shell's command line: <blockquote> <pre> -% python -Python 2.0 (#128, Oct 18 2000, 04:48:44) -[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 -Type "copyright", "credits" or "license" for more information. ->>> ^D +% python -V +Python 2.1 </pre> </blockquote> +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 @@ -237,10 +239,13 @@ gcc 2.8.1 or later is known to work well. <h3>Downloading</h3> <p>Version -(<!-VERSION--->2.1a1<!-VERSION--->, +(<!-VERSION--->2.1a2<!-VERSION--->, released on -<!-DATE--->Mar 4 2001<!-DATE--->) -is the current GNU release. It is available from the following mirror sites: +<!-DATE--->11-Jul-2001<!-DATE--->) +is an alpha release of the next version. It is not recommended that +this version be used in production systems yet. It, and the current +stable version 2.0.5, is available from +the following mirror sites: <ul> <li><a href="ftp://ftp.gnu.org/gnu/mailman/">From GNU</a> diff --git a/admin/www/faq.ht b/admin/www/faq.ht index 817e515dd..de7fbfdcf 100644 --- a/admin/www/faq.ht +++ b/admin/www/faq.ht @@ -46,7 +46,7 @@ Title: Mailman Frequently Asked Questions you can use add-on tools such as demime or stripmime. More information on these tools can be found at: <p> (Stripmime) <a href="http://www.phred.org/~alex/stripmime.html.">http://www.phred.org/~alex/stripmime.html.</a> - (Demime) <a href="http://scifi.squawk.com/demime.html.">http://scifi.squawk.com/demime.html.</a> +<p> (Demime) <a href="http://scifi.squawk.com/demime.html.">http://scifi.squawk.com/demime.html.</a> <p> <b> Q. What if I get "document contains no data" from the web server, or mail isn't getting delivered, or I see "Premature end of script headers" or "Mailman CGI error!!!" @@ -61,8 +61,8 @@ Title: Mailman Frequently Asked Questions for details. <p> These errors are logged to syslog and they do not show up in the Mailman log files. Problems with the CGI wrapper do get reported - in the Web browser though, and include the expected GID, so that - should help a lot. + in the web browser though (unless STEALTH_MODE is enabled), and + include the expected GID, so that should help a lot. <p> You may want to have syslog running and configured to log the mail.error log class somewhere; on Solaris systems, the line <p> mail.debug /var/log/syslog @@ -73,6 +73,14 @@ Title: Mailman Frequently Asked Questions visit the mailman/listinfo web page, and it's due to a UID or GID mismatch, then you should get an entry at the end of /var/log/syslog identifying the expected and received values. +<p> If you are not getting any log messages in syslog, or in Mailman's + own log files, but messages are still not being delivered, then it + is likely that qrunner is not running (qrunner is the process that + handles all mail in the system). In Mailman 2.0, qrunner was + invoked from cron so make sure your crontab entries for the + `mailman' user have been installed. In Mailman 2.1, qrunner is + started with the bin/mailmanctl script, which can be invoked + manually, or merged with your OS's init scripts. <p> <b> Q. Why do my web pages hang? </b><br> A. CERN Web servers might leave Python processes running, and in some @@ -91,14 +99,17 @@ Title: Mailman Frequently Asked Questions ~mailman/logs/error, and some of the modules write caught errors there, as well, so you should check there at least occasionally to look for bugs in the code and problems in your setup. -<p> One thing that is *not* caught by the standard error hook is syntax - errors, but any of these should have been caught in the - installation phase, which byte-compiles all .py files in the - distribution. There may be syntax errors lurking if you hacked the - code, or in the scripts that are not modules. +<p> One thing that is reported in logs/error is syntax errors, but any + of these should have been caught in the installation phase, which + byte-compiles all .py files in the distribution. There may be + syntax errors lurking if you hacked the code, or in the scripts + that are not modules. <p> You can always use the Python module `compile' or `compileall' to force byte compilation of a file, or just fire up the Python interpreter and try importing the module. +<p> You may want to periodically check the other log files in the logs/ + directory, perhaps occasionally rotating them with something like + the Linux logrotate script. <p> <b> Q. Why doesn't the archive link work? </b><br> A. Have any messages been posted to the list? This is a known buglet; diff --git a/admin/www/faq.html b/admin/www/faq.html index cdaac6a6f..c95709785 100644 --- a/admin/www/faq.html +++ b/admin/www/faq.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Mon Jun 25 17:26:20 2001 --> +<!-- Wed Jul 11 23:45:38 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Mailman Frequently Asked Questions <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>FAQ</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,51 +81,51 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Frequently Asked Questions</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -133,10 +133,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -192,7 +192,7 @@ Email Us you can use add-on tools such as demime or stripmime. More information on these tools can be found at: <p> (Stripmime) <a href="http://www.phred.org/~alex/stripmime.html.">http://www.phred.org/~alex/stripmime.html.</a> - (Demime) <a href="http://scifi.squawk.com/demime.html.">http://scifi.squawk.com/demime.html.</a> +<p> (Demime) <a href="http://scifi.squawk.com/demime.html.">http://scifi.squawk.com/demime.html.</a> <p> <b> Q. What if I get "document contains no data" from the web server, or mail isn't getting delivered, or I see "Premature end of script headers" or "Mailman CGI error!!!" @@ -207,8 +207,8 @@ Email Us for details. <p> These errors are logged to syslog and they do not show up in the Mailman log files. Problems with the CGI wrapper do get reported - in the Web browser though, and include the expected GID, so that - should help a lot. + in the web browser though (unless STEALTH_MODE is enabled), and + include the expected GID, so that should help a lot. <p> You may want to have syslog running and configured to log the mail.error log class somewhere; on Solaris systems, the line <p> mail.debug /var/log/syslog @@ -219,6 +219,14 @@ Email Us visit the mailman/listinfo web page, and it's due to a UID or GID mismatch, then you should get an entry at the end of /var/log/syslog identifying the expected and received values. +<p> If you are not getting any log messages in syslog, or in Mailman's + own log files, but messages are still not being delivered, then it + is likely that qrunner is not running (qrunner is the process that + handles all mail in the system). In Mailman 2.0, qrunner was + invoked from cron so make sure your crontab entries for the + `mailman' user have been installed. In Mailman 2.1, qrunner is + started with the bin/mailmanctl script, which can be invoked + manually, or merged with your OS's init scripts. <p> <b> Q. Why do my web pages hang? </b><br> A. CERN Web servers might leave Python processes running, and in some @@ -237,14 +245,17 @@ Email Us ~mailman/logs/error, and some of the modules write caught errors there, as well, so you should check there at least occasionally to look for bugs in the code and problems in your setup. -<p> One thing that is *not* caught by the standard error hook is syntax - errors, but any of these should have been caught in the - installation phase, which byte-compiles all .py files in the - distribution. There may be syntax errors lurking if you hacked the - code, or in the scripts that are not modules. +<p> One thing that is reported in logs/error is syntax errors, but any + of these should have been caught in the installation phase, which + byte-compiles all .py files in the distribution. There may be + syntax errors lurking if you hacked the code, or in the scripts + that are not modules. <p> You can always use the Python module `compile' or `compileall' to force byte compilation of a file, or just fire up the Python interpreter and try importing the module. +<p> You may want to periodically check the other log files in the logs/ + directory, perhaps occasionally rotating them with something like + the Linux logrotate script. <p> <b> Q. Why doesn't the archive link work? </b><br> A. Have any messages been posted to the list? This is a known buglet; diff --git a/admin/www/features.ht b/admin/www/features.ht index 6496d4c67..71a4d9bcf 100644 --- a/admin/www/features.ht +++ b/admin/www/features.ht @@ -5,6 +5,8 @@ Other-links: <h3>Mailman Features</h3> +This is just a short summary of all the features of Mailman. + <ul> <li>Web based list administration for nearly all tasks, including list configuration, moderation (post approvals), management of user @@ -16,13 +18,21 @@ Other-links: <li>A customizable <em>home page</em> for each mailing list. +<li>Through-the-web list creation and removal (with automatic support + depending on the MTA). + <li>Per-list privacy features, such as closed-subscriptions, private archives, private membership rosters, etc. +<li>Multi-lingual support: list web pages and email notices can be in + any supported language, configurable per-site, per-list, and + per-user. + <li>Configurable (per-list and per-user) delivery mode <ul><li>Regular (immediate) delivery <li>MIME digest - <li>Plain (RFC 934) digests + <li>Plain (<a href="http://www.faqs.org/rfcs/rfc1153.html">RFC + 1153</a>) digests </ul> <li>Integrated bounce detection within an extensible framework. @@ -45,8 +55,10 @@ Other-links: <li>Support for virtual domains. -<li>Runs on most Un*x-like systems, compatible with most web - servers and browsers, and most SMTP servers. Requires Python - 1.5.2 or newer (works with Python 1.6 and 2.0). +<li>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. <li>An extensible mail delivery pipeline. + +<li>High-performance mail delivery, with a scalable architecture. diff --git a/admin/www/features.html b/admin/www/features.html index f951763e0..e41a04fe7 100644 --- a/admin/www/features.html +++ b/admin/www/features.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:36 2001 --> +<!-- Wed Jul 11 23:55:09 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Mailman Features <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,58 +81,58 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Features</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Exits </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.oac.uci.edu/indiv/ehood/mhonarc.html">MHonArc</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -140,10 +140,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -155,6 +155,8 @@ Email Us <TD VALIGN=TOP WIDTH="90%"><BR> <h3>Mailman Features</h3> +This is just a short summary of all the features of Mailman. + <ul> <li>Web based list administration for nearly all tasks, including list configuration, moderation (post approvals), management of user @@ -166,13 +168,21 @@ Email Us <li>A customizable <em>home page</em> for each mailing list. +<li>Through-the-web list creation and removal (with automatic support + depending on the MTA). + <li>Per-list privacy features, such as closed-subscriptions, private archives, private membership rosters, etc. +<li>Multi-lingual support: list web pages and email notices can be in + any supported language, configurable per-site, per-list, and + per-user. + <li>Configurable (per-list and per-user) delivery mode <ul><li>Regular (immediate) delivery <li>MIME digest - <li>Plain (RFC 934) digests + <li>Plain (<a href="http://www.faqs.org/rfcs/rfc1153.html">RFC + 1153</a>) digests </ul> <li>Integrated bounce detection within an extensible framework. @@ -195,12 +205,14 @@ Email Us <li>Support for virtual domains. -<li>Runs on most Un*x-like systems, compatible with most web - servers and browsers, and most SMTP servers. Requires Python - 1.5.2 or newer (works with Python 1.6 and 2.0). +<li>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. <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 --> diff --git a/admin/www/i18n.html b/admin/www/i18n.html index 58c6f89ad..a14a7bd5a 100644 --- a/admin/www/i18n.html +++ b/admin/www/i18n.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:32:53 2001 --> +<!-- Wed Jul 11 23:44:02 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Internationalization <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,73 +81,73 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="users.html">Users</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mgrs.html">List Managers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="admins.html">Site Administrators</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="devs.html">Developers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Internationalization</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="otherdocs.html">Other Documentation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -155,10 +155,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> diff --git a/admin/www/index.ht b/admin/www/index.ht index 979c62e7c..bdfbbb550 100644 --- a/admin/www/index.ht +++ b/admin/www/index.ht @@ -11,22 +11,22 @@ Other-links: <h3>Mailman, the GNU Mailing List Manager</h3> -Mailman is software to help manage electronic mail discussion lists, -much like Majordomo or SmartList. Mailman gives each mailing list a -unique web page and allows users to subscribe, unsubscribe, and change -their account options over the web. Even the list manager can -administer his or her list entirely via the web. Mailman has most of -the features that people want in a mailing list management system, -including built-in archiving, mail-to-news gateways, spam filters, -bounce detection, digest delivery, and so on. See the -<a href="features.html">features page</a> for more detail. +Mailman is software to help manage electronic mail discussion lists. +Mailman gives each mailing list a unique web page and allows users to +subscribe, unsubscribe, and change their account options over the web. +Even the list manager can administer his or her list entirely via the +web. Mailman has most of the features that people want in a mailing +list management system, including built-in archiving, mail-to-news +gateways, spam filters, bounce detection, digest delivery, and so on. +See the <a href="features.html">features page</a> for more detail. <p>Mailman is free software. It is distributed under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>. The canonical Mailman home page is at <a href="http://www.gnu.org/software/mailman/"> -www.gnu.org/software/mailman</a>, with more information -available at <a href="http://www.list.org/">www.list.org</a>. Mailman +www.gnu.org/software/mailman</a>, which is mirrored at +<a href="http://www.list.org/">www.list.org</a> and +<a href="http://sf.net/projects/mailman">SourceForge</a>. Mailman is written in the <a href="http://www.python.org/">Python</a> programming language, with a little bit of C code for security. @@ -38,16 +38,16 @@ StudlyCaps). <h3>Current Version</h3> <p>Version -(<!-VERSION--->2.1a1<!-VERSION--->, +(<!-VERSION--->2.1a2<!-VERSION--->, released on -<!-DATE--->Mar 4 2001<!-DATE--->) +<!-DATE--->11-Jul-2001<!-DATE--->) is the current stable GNU release. <h3>Acknowledgements</h3> <p>Mailman is brought to you by the <em>Mailman Cabal</em>, currently composed of the following core developers: -<a href="http://barry.wooz.org/">Barry Warsaw</a>, Harald +<a href="http://barry.wooz.org/">Barry Warsaw</a>, Thomas Wouters, Harald Meland, Ken Manheimer, Scott Cotton, and John Viega. Mailman was originally written by John Viega. @@ -58,7 +58,7 @@ Timothy O'Malley, Balazs Nagy, Michael Mclay, Greg Stein, Gergely Madarasz, Andrew Kuchling, Jeff Hahn, Paul Hebble, Christopher P. Lindsey, Chris Kolar, J C Lawrence, Jeremy Hylton, Nigel Metheringham, Dan Mick, Jim Tittsler, Ricardo Kustner, Bernhard -Reiter, Thomas Wouters, Jeff Berliner, Ted Cabeen, Michael Yount, Ron +Reiter, Guido van Rossum, Jeff Berliner, Ted Cabeen, Michael Yount, Ron Jarrell, Chris Snell, David Champion, Darrell Fuhriman, Owen Taylor, Fil, Noam Zeilberger, Mark MERLIN, John A. Martin, Erik Forsberg, Tanner Lovelace, Les Niles, Mike Noyes, Tokio Kikuchi, Vizi Szilard, diff --git a/admin/www/index.html b/admin/www/index.html index 413cd1c22..bfbdf925d 100644 --- a/admin/www/index.html +++ b/admin/www/index.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Tue Jul 10 10:28:34 2001 --> +<!-- Wed Jul 11 23:49:54 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Mailman, the GNU Mailing List Manager <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>Home</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,92 +81,92 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Home</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="users.html">Users</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mgrs.html">List Managers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="admins.html">Site Administrators</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="devs.html">Developers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="i18n.html">Internationalization</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="otherdocs.html">Other Documentation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Exits </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.python.org/">Python</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.gnu.org/">GNU/FSF</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://www.list.org/">List.Org mirror</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="http://barry.wooz.org/">Barry Warsaw</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -174,10 +174,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -190,22 +190,22 @@ Email Us <h3>Mailman, the GNU Mailing List Manager</h3> -Mailman is software to help manage electronic mail discussion lists, -much like Majordomo or SmartList. Mailman gives each mailing list a -unique web page and allows users to subscribe, unsubscribe, and change -their account options over the web. Even the list manager can -administer his or her list entirely via the web. Mailman has most of -the features that people want in a mailing list management system, -including built-in archiving, mail-to-news gateways, spam filters, -bounce detection, digest delivery, and so on. See the -<a href="features.html">features page</a> for more detail. +Mailman is software to help manage electronic mail discussion lists. +Mailman gives each mailing list a unique web page and allows users to +subscribe, unsubscribe, and change their account options over the web. +Even the list manager can administer his or her list entirely via the +web. Mailman has most of the features that people want in a mailing +list management system, including built-in archiving, mail-to-news +gateways, spam filters, bounce detection, digest delivery, and so on. +See the <a href="features.html">features page</a> for more detail. <p>Mailman is free software. It is distributed under the <a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>. The canonical Mailman home page is at <a href="http://www.gnu.org/software/mailman/"> -www.gnu.org/software/mailman</a>, with more information -available at <a href="http://www.list.org/">www.list.org</a>. Mailman +www.gnu.org/software/mailman</a>, which is mirrored at +<a href="http://www.list.org/">www.list.org</a> and +<a href="http://sf.net/projects/mailman">SourceForge</a>. Mailman is written in the <a href="http://www.python.org/">Python</a> programming language, with a little bit of C code for security. @@ -217,16 +217,16 @@ StudlyCaps). <h3>Current Version</h3> <p>Version -(<!-VERSION--->2.1a1<!-VERSION--->, +(<!-VERSION--->2.1a2<!-VERSION--->, released on -<!-DATE--->Mar 4 2001<!-DATE--->) +<!-DATE--->11-Jul-2001<!-DATE--->) is the current stable GNU release. <h3>Acknowledgements</h3> <p>Mailman is brought to you by the <em>Mailman Cabal</em>, currently composed of the following core developers: -<a href="http://barry.wooz.org/">Barry Warsaw</a>, Harald +<a href="http://barry.wooz.org/">Barry Warsaw</a>, Thomas Wouters, Harald Meland, Ken Manheimer, Scott Cotton, and John Viega. Mailman was originally written by John Viega. @@ -237,7 +237,7 @@ Timothy O'Malley, Balazs Nagy, Michael Mclay, Greg Stein, Gergely Madarasz, Andrew Kuchling, Jeff Hahn, Paul Hebble, Christopher P. Lindsey, Chris Kolar, J C Lawrence, Jeremy Hylton, Nigel Metheringham, Dan Mick, Jim Tittsler, Ricardo Kustner, Bernhard -Reiter, Thomas Wouters, Jeff Berliner, Ted Cabeen, Michael Yount, Ron +Reiter, Guido van Rossum, Jeff Berliner, Ted Cabeen, Michael Yount, Ron Jarrell, Chris Snell, David Champion, Darrell Fuhriman, Owen Taylor, Fil, Noam Zeilberger, Mark MERLIN, John A. Martin, Erik Forsberg, Tanner Lovelace, Les Niles, Mike Noyes, Tokio Kikuchi, Vizi Szilard, diff --git a/admin/www/install-check.ht b/admin/www/install-check.ht index 571c89897..39af31f67 100644 --- a/admin/www/install-check.ht +++ b/admin/www/install-check.ht @@ -3,9 +3,9 @@ Links: links.h install-links.h <h3>Check your installation</h3> - To check that your installation has all the correct permissions - and group ownerships, you should run the <code>check_perms</code> - script: + After you've run "make install", you can check that your + installation has all the correct permissions and group ownerships + by running the check_perms script: <blockquote> <pre> diff --git a/admin/www/install-check.html b/admin/www/install-check.html index de124a066..a2ff5894b 100644 --- a/admin/www/install-check.html +++ b/admin/www/install-check.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:36 2001 --> +<!-- Thu Jul 12 00:16:33 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Check your installation <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Check your installation</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -179,9 +179,9 @@ Email Us <TD VALIGN=TOP WIDTH="90%"><BR> <h3>Check your installation</h3> - To check that your installation has all the correct permissions - and group ownerships, you should run the <code>check_perms</code> - script: + After you've run "make install", you can check that your + installation has all the correct permissions and group ownerships + by running the check_perms script: <blockquote> <pre> diff --git a/admin/www/install-config.ht b/admin/www/install-config.ht index 16e13a0ff..66e5522f0 100644 --- a/admin/www/install-config.ht +++ b/admin/www/install-config.ht @@ -3,14 +3,13 @@ Links: links.h install-links.h <h3>Running configure</h3> - <em>TAKE SPECIAL NOTE OF THE <code>--with-mail-gid</code> AND - <code>--with-cgi-gid</code> OPTIONS BELOW. YOU WILL PROBABLY NEED - TO USE THESE!</em> + <strong>TAKE SPECIAL NOTE OF THE --with-mail-gid AND --with-cgi-gid + OPTIONS BELOW. YOU WILL PROBABLY NEED TO USE THESE!</strong> - <p>You should <b>not be root</b> while performing the - steps in this section. Do them under your own login, or whatever - account you typically install software as. You do not need to do - these steps as user <code>mailman</code>, but you could. + <p>You should not be root while performing the steps in this + section. Do them under your own login, or whatever account you + typically install software as. You do not need to do these steps + as user <tt>mailman</tt>, but you could. <p>Make sure that you have write permissions to the target installation directory, and permission to create a setgid file in @@ -18,111 +17,103 @@ Links: links.h install-links.h configured to inhibit setgid settings). <p>If you've installed other GNU software, you should be familiar - with the <code>configure</code> script. Usually you can just - cd to the directory you unpacked Mailman into, and run - <code>configure</code> with no arguments: + with the configure script. Usually you can just cd to the + directory you unpacked Mailman into, and run configure with no + arguments: <blockquote> <pre> -% cd mailman-version +% cd mailman-<em>version</em> % ./configure % make install </pre> </blockquote> -If you need to run configure with some options, you can do it like -this: - -<blockquote> -<pre> -% ./configure --with-mail-gid=mail --with-cgi-gid=nobody -</pre> -</blockquote> - -<h3>Configure options</h3> - - The following options allow you to customize your Mailman + <p>The following options allow you to customize your Mailman installation. - <dl> - <dt>--prefix=<em>dir</em> - <dd>Standard GNU configure option which changes the base - directory that Mailman is installed into. By default - <code>$prefix</code> is <code>/home/mailman</code>. This - directory must already exist, and be set up as described in - section 1 above. + <dl> + <p><dt>--prefix=<em>dir</em> + <dd>Standard GNU configure option which changes the base + directory that Mailman is installed into. By default + <em>$prefix</em> is <tt>/usr/local/mailman</tt>. This + directory must already exist, and be set up as described + in section 1 above. + + <p><dt>--exec-prefix=<em>dir</em> + <dd>Standard GNU configure option which lets you specify a + different installation directory for architecture + dependent binaries. - <dt>--exec-prefix=<em>dir</em> - <dd>Standard GNU configure option which lets you specify a - different installation directory for architecture dependent - binaries. + <p><dt>--with-var-prefix=<em>dir</em> + <dd>Store mutable data under <em>dir</em> instead of under + the prefix or exec_prefix. - <dt>--with-var-prefix=<em>dir</em> - <dd>Store mutable data under <em>dir</em> instead of under - <code>$prefix</code> or <code>$exec_prefix</code>. + <p><dt>--with-python=<em>/path/to/python</em> + <dd>Specify an alternative Python interpreter to use for + the wrapper programs. The default is to use the + interpreter found first on your shell's <tt>$PATH</tt>. + Note that when running the scripts from the command line, + the first Python interpreter found on <tt>$PATH</tt> is + always used. - <dt>--with-python=<em>/path/to/python</em> - <dd>Specify an alternative Python interpreter to use for the - wrapper programs. The default is to use the interpreter - found first on your shell's <code>$PATH</code>. Note that - when running the scripts from the command line, the first - Python interpreter found on <code>$PATH</code> is always - used. + <p><dt>--with-username=<em>username-or-uid</em> + <dd>Specify a different username than <tt>mailman</tt> to use + as a default. Use this only if the username + <tt>mailman</tt> is already in use by somebody (e.g. Mark + Ailman's login name). This switch can take an integer + user id or a user name. Be sure your <em>$prefix</em> + directory is owned by this user. - <dt>--with-username=<em>username-or-uid</em> - <dd>Specify a different username than <code>mailman</code> to use as a - default. Use this only if the username <code>mailman</code> - is already in use by somebody (e.g. Mark Ailman's login - name). Can take an integer user id. Be sure your - <code>$prefix</code> directory is owned by this user. + <p><dt>--with-groupname=<em>groupname-or-gid</em> + <dd>Specify a different groupname than <tt>mailman</tt> to use + as a default. Use this only if the groupname + <tt>mailman</tt> is already in use. This switch can take + an integer group id or a group name. Be sure your + <em>$prefix</em> directory is group-owned by this group. - <dt>--with-groupname=<em>groupname-or-gid</em> - <dd>Specify a different groupname than <code>mailman</code> to use as a - default. Use this only if the groupname - <code>mailman</code> is already in use. Can take an integer - group id. Be sure your <code>$prefix</code> directory is - group-owned by this group. + <p><dt>--with-mail-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + mail wrapper. <em>group-or-groups</em> can be a list of one or + more integer group ids or symbolic group names. The first + value in the list that resolves to an existing group is + used. By default, the value is the list <tt>other daemon</tt>. - <dt>--with-mail-gid=<em>group-or-groups</em> - <dd>Specify an alternative group for running scripts via the - mail wrapper. <em>group-or-groups</em> can be a list of one - or more integer group ids or symbolic group names. The - first value in the list that resolves to an existing group - is used. By default, the value is the list <code>other, - daemon</code>. + <p>This is highly system dependent and you must get this + right, because the group id is compiled into the mail + wrapper program for added security. On systems using + sendmail, the sendmail.cf configuration file designates + the group id of sendmail processes using the "DefaultUser" + option. (If commented out, it still may be indicating the + default...) - <p>This is highly system dependent and you must get this - right, because the group id is compiled into the mail - wrapper program for added security. On systems using - sendmail, the <code>sendmail.cf</code> configuration file - designates the group id of sendmail processes using the - <em>DefaultUser</em> option. (If commented out, it still - may be indicating the default...) + <p>Check your MTA's documentation and configuration files to + find the right value for this switch. - <dt>--with-cgi-gid=<em>group-or-groups</em> - <dd>Specify an alternative group for running scripts via the - CGI wrapper. <em>group-or-groups</em> can be a list of one - or more integer group ids or symbolic group names. The - first value in the list that resolves to an existing group - is used. By default, the value is the the list - <code>www, www-data, nobody</code>. + <p><dt>--with-cgi-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + CGI wrapper. <em>group-or-groups</em> can be a list of one or + more integer group ids or symbolic group names. The first + value in the list that resolves to an existing group is + used. By default, the value is the the list <tt>www www-data + nobody</tt>. - <p>The proper value for this is dependent on your web server - configuration. You must get this right, because the group - id is compiled into the CGI wrapper program for added - security, and no Mailman CGI scripts will run if this is - incorrect. + <p>The proper value for this is dependent on your web server + configuration. You must get this right, because the group + id is compiled into the CGI wrapper program for added + security, and no Mailman CGI scripts will run if this is + incorrect. - <p>If you're using Apache, check the values for the <em>Group</em> - option in your <code>httpd.conf</code> file. + <p>If you're using Apache, check the values for the `Group' + option in your httpd.conf file. - <dt>--with-cgi-ext=<em>extension</em> - <dd>Specify an extension for cgi-bin programs. The CGI - wrappers placed in <code>$PREFIX/cgi-bin</code> will have this - extension (some web servers require an extension). - <em>extension</em> must include the dot. + <p><dt>--with-cgi-ext=<em>extension</em> + <dd>Specify an extension for cgi-bin programs. The CGI + wrappers placed in <em>$PREFIX/cgi-bin</em> will have this + extension (some web servers require an extension). + <em>extension</em> must include the dot. - <dt>--with-gcc=no - <dd>Don't use gcc, even if it is found. cc must be found on - your <code>$PATH</code> + <p><dt>--with-gcc=no + <dd>Don't use gcc, even if it is found. `cc' must be found on + your <em>$PATH</em>. </dl> diff --git a/admin/www/install-config.html b/admin/www/install-config.html index c22d8e343..b85fcda63 100644 --- a/admin/www/install-config.html +++ b/admin/www/install-config.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:37 2001 --> +<!-- Thu Jul 12 00:15:30 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Running configure <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Running configure</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -179,14 +179,13 @@ Email Us <TD VALIGN=TOP WIDTH="90%"><BR> <h3>Running configure</h3> - <em>TAKE SPECIAL NOTE OF THE <code>--with-mail-gid</code> AND - <code>--with-cgi-gid</code> OPTIONS BELOW. YOU WILL PROBABLY NEED - TO USE THESE!</em> + <strong>TAKE SPECIAL NOTE OF THE --with-mail-gid AND --with-cgi-gid + OPTIONS BELOW. YOU WILL PROBABLY NEED TO USE THESE!</strong> - <p>You should <b>not be root</b> while performing the - steps in this section. Do them under your own login, or whatever - account you typically install software as. You do not need to do - these steps as user <code>mailman</code>, but you could. + <p>You should not be root while performing the steps in this + section. Do them under your own login, or whatever account you + typically install software as. You do not need to do these steps + as user <tt>mailman</tt>, but you could. <p>Make sure that you have write permissions to the target installation directory, and permission to create a setgid file in @@ -194,113 +193,105 @@ Email Us configured to inhibit setgid settings). <p>If you've installed other GNU software, you should be familiar - with the <code>configure</code> script. Usually you can just - cd to the directory you unpacked Mailman into, and run - <code>configure</code> with no arguments: + with the configure script. Usually you can just cd to the + directory you unpacked Mailman into, and run configure with no + arguments: <blockquote> <pre> -% cd mailman-version +% cd mailman-<em>version</em> % ./configure % make install </pre> </blockquote> -If you need to run configure with some options, you can do it like -this: - -<blockquote> -<pre> -% ./configure --with-mail-gid=mail --with-cgi-gid=nobody -</pre> -</blockquote> - -<h3>Configure options</h3> - - The following options allow you to customize your Mailman + <p>The following options allow you to customize your Mailman installation. - <dl> - <dt>--prefix=<em>dir</em> - <dd>Standard GNU configure option which changes the base - directory that Mailman is installed into. By default - <code>$prefix</code> is <code>/home/mailman</code>. This - directory must already exist, and be set up as described in - section 1 above. + <dl> + <p><dt>--prefix=<em>dir</em> + <dd>Standard GNU configure option which changes the base + directory that Mailman is installed into. By default + <em>$prefix</em> is <tt>/usr/local/mailman</tt>. This + directory must already exist, and be set up as described + in section 1 above. + + <p><dt>--exec-prefix=<em>dir</em> + <dd>Standard GNU configure option which lets you specify a + different installation directory for architecture + dependent binaries. - <dt>--exec-prefix=<em>dir</em> - <dd>Standard GNU configure option which lets you specify a - different installation directory for architecture dependent - binaries. + <p><dt>--with-var-prefix=<em>dir</em> + <dd>Store mutable data under <em>dir</em> instead of under + the prefix or exec_prefix. - <dt>--with-var-prefix=<em>dir</em> - <dd>Store mutable data under <em>dir</em> instead of under - <code>$prefix</code> or <code>$exec_prefix</code>. + <p><dt>--with-python=<em>/path/to/python</em> + <dd>Specify an alternative Python interpreter to use for + the wrapper programs. The default is to use the + interpreter found first on your shell's <tt>$PATH</tt>. + Note that when running the scripts from the command line, + the first Python interpreter found on <tt>$PATH</tt> is + always used. - <dt>--with-python=<em>/path/to/python</em> - <dd>Specify an alternative Python interpreter to use for the - wrapper programs. The default is to use the interpreter - found first on your shell's <code>$PATH</code>. Note that - when running the scripts from the command line, the first - Python interpreter found on <code>$PATH</code> is always - used. + <p><dt>--with-username=<em>username-or-uid</em> + <dd>Specify a different username than <tt>mailman</tt> to use + as a default. Use this only if the username + <tt>mailman</tt> is already in use by somebody (e.g. Mark + Ailman's login name). This switch can take an integer + user id or a user name. Be sure your <em>$prefix</em> + directory is owned by this user. - <dt>--with-username=<em>username-or-uid</em> - <dd>Specify a different username than <code>mailman</code> to use as a - default. Use this only if the username <code>mailman</code> - is already in use by somebody (e.g. Mark Ailman's login - name). Can take an integer user id. Be sure your - <code>$prefix</code> directory is owned by this user. + <p><dt>--with-groupname=<em>groupname-or-gid</em> + <dd>Specify a different groupname than <tt>mailman</tt> to use + as a default. Use this only if the groupname + <tt>mailman</tt> is already in use. This switch can take + an integer group id or a group name. Be sure your + <em>$prefix</em> directory is group-owned by this group. - <dt>--with-groupname=<em>groupname-or-gid</em> - <dd>Specify a different groupname than <code>mailman</code> to use as a - default. Use this only if the groupname - <code>mailman</code> is already in use. Can take an integer - group id. Be sure your <code>$prefix</code> directory is - group-owned by this group. + <p><dt>--with-mail-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + mail wrapper. <em>group-or-groups</em> can be a list of one or + more integer group ids or symbolic group names. The first + value in the list that resolves to an existing group is + used. By default, the value is the list <tt>other daemon</tt>. - <dt>--with-mail-gid=<em>group-or-groups</em> - <dd>Specify an alternative group for running scripts via the - mail wrapper. <em>group-or-groups</em> can be a list of one - or more integer group ids or symbolic group names. The - first value in the list that resolves to an existing group - is used. By default, the value is the list <code>other, - daemon</code>. + <p>This is highly system dependent and you must get this + right, because the group id is compiled into the mail + wrapper program for added security. On systems using + sendmail, the sendmail.cf configuration file designates + the group id of sendmail processes using the "DefaultUser" + option. (If commented out, it still may be indicating the + default...) - <p>This is highly system dependent and you must get this - right, because the group id is compiled into the mail - wrapper program for added security. On systems using - sendmail, the <code>sendmail.cf</code> configuration file - designates the group id of sendmail processes using the - <em>DefaultUser</em> option. (If commented out, it still - may be indicating the default...) + <p>Check your MTA's documentation and configuration files to + find the right value for this switch. - <dt>--with-cgi-gid=<em>group-or-groups</em> - <dd>Specify an alternative group for running scripts via the - CGI wrapper. <em>group-or-groups</em> can be a list of one - or more integer group ids or symbolic group names. The - first value in the list that resolves to an existing group - is used. By default, the value is the the list - <code>www, www-data, nobody</code>. + <p><dt>--with-cgi-gid=<em>group-or-groups</em> + <dd>Specify an alternative group for running scripts via the + CGI wrapper. <em>group-or-groups</em> can be a list of one or + more integer group ids or symbolic group names. The first + value in the list that resolves to an existing group is + used. By default, the value is the the list <tt>www www-data + nobody</tt>. - <p>The proper value for this is dependent on your web server - configuration. You must get this right, because the group - id is compiled into the CGI wrapper program for added - security, and no Mailman CGI scripts will run if this is - incorrect. + <p>The proper value for this is dependent on your web server + configuration. You must get this right, because the group + id is compiled into the CGI wrapper program for added + security, and no Mailman CGI scripts will run if this is + incorrect. - <p>If you're using Apache, check the values for the <em>Group</em> - option in your <code>httpd.conf</code> file. + <p>If you're using Apache, check the values for the `Group' + option in your httpd.conf file. - <dt>--with-cgi-ext=<em>extension</em> - <dd>Specify an extension for cgi-bin programs. The CGI - wrappers placed in <code>$PREFIX/cgi-bin</code> will have this - extension (some web servers require an extension). - <em>extension</em> must include the dot. + <p><dt>--with-cgi-ext=<em>extension</em> + <dd>Specify an extension for cgi-bin programs. The CGI + wrappers placed in <em>$PREFIX/cgi-bin</em> will have this + extension (some web servers require an extension). + <em>extension</em> must include the dot. - <dt>--with-gcc=no - <dd>Don't use gcc, even if it is found. cc must be found on - your <code>$PATH</code> + <p><dt>--with-gcc=no + <dd>Don't use gcc, even if it is found. `cc' must be found on + your <em>$PATH</em>. </dl> </TD><!-- end of body cell --> diff --git a/admin/www/install-custom.ht b/admin/www/install-custom.ht index e3ccb4a06..7205a827c 100644 --- a/admin/www/install-custom.ht +++ b/admin/www/install-custom.ht @@ -12,9 +12,11 @@ Links: links.h install-links.h override them in <code>$prefix/Mailman/mm_cfg.py</code>, <b>NOT IN</b> <code>Defaults.py</code>! See the comments in <code>Defaults.py</code> for details. Once a list is created, - editing many of these variables will have no effect (you need to + editing many of these variables will have no effect At that + point, you'll need to configure your lists through the web admin interface or through - the command line script <code>bin/config_list</code>). + the command line script <code>bin/config_list</code> or + <code>bin/withlist</code>. <p>Specifically check to make sure the variables <em>DEFAULT_HOST_NAME</em> and <em>DEFAULT_URL</em> are @@ -40,4 +42,11 @@ $prefix/bin/mmsitepass your-site-password mailing list administrator passwords are required, giving the mailman site administrator the ability to adjust these things when necessary. + + <p>You may also want to create a password for the site-wide + <em>list creator</em> role (someone other than the site + administrator who as privileges to create and remove lists + through the web). Use the <tt>-c</tt> option to mmsitepass to + set this. + </ul> diff --git a/admin/www/install-custom.html b/admin/www/install-custom.html index 7b18947f8..c3abea3b4 100644 --- a/admin/www/install-custom.html +++ b/admin/www/install-custom.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:37 2001 --> +<!-- Thu Jul 12 00:23:15 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Customize Mailman <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Customize Mailman</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -188,9 +188,11 @@ Email Us override them in <code>$prefix/Mailman/mm_cfg.py</code>, <b>NOT IN</b> <code>Defaults.py</code>! See the comments in <code>Defaults.py</code> for details. Once a list is created, - editing many of these variables will have no effect (you need to + editing many of these variables will have no effect At that + point, you'll need to configure your lists through the web admin interface or through - the command line script <code>bin/config_list</code>). + the command line script <code>bin/config_list</code> or + <code>bin/withlist</code>. <p>Specifically check to make sure the variables <em>DEFAULT_HOST_NAME</em> and <em>DEFAULT_URL</em> are @@ -216,6 +218,13 @@ $prefix/bin/mmsitepass your-site-password mailing list administrator passwords are required, giving the mailman site administrator the ability to adjust these things when necessary. + + <p>You may also want to create a password for the site-wide + <em>list creator</em> role (someone other than the site + administrator who as privileges to create and remove lists + through the web). Use the <tt>-c</tt> option to mmsitepass to + set this. + </ul> </TD><!-- end of body cell --> diff --git a/admin/www/install-faq.html b/admin/www/install-faq.html index fee3ae27f..15d98ff85 100644 --- a/admin/www/install-faq.html +++ b/admin/www/install-faq.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:37 2001 --> +<!-- Wed Jul 11 23:44:04 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Common problems FAQ <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Common problems FAQ</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> diff --git a/admin/www/install-final.ht b/admin/www/install-final.ht index 05fbbf82e..bcdce06be 100644 --- a/admin/www/install-final.ht +++ b/admin/www/install-final.ht @@ -7,8 +7,15 @@ Links: links.h install-links.h everything running you need to hook Mailman up to both your web server and your mail system. - <ul> - <li>If you plan on running your MTA and web server on different + <ul><p><li>If there is a <tt>README.<em>yourMTA</em>></tt> file + that describes your mail + server (MTA), read it now. Some MTAs are more compatible with + Mailman such that you can do automatic creation and removal of + mailing lists, including through-the-web operations. Examples + are Exim and Postfix. Setup instructions for specific MTAs are + contained in these README files. + + <p><li>If you plan on running your MTA and web server on different machines, sharing Mailman installations via NFS, be sure that the clocks on those two machines are synchronized closely. You might take a look at the file @@ -85,15 +92,34 @@ Alias /pipermail/ $varprefix/archives/public/ <p>Now restart your web server. - <p><li><b>IMPERATIVE! IMPORTANT! DO THIS! YOU'LL BE SORRY IF - YOU DON'T!</b> + <p><li>Set up the crontab entries. Mailman runs a number of cron jobs + for its basic functionality. In version of Mailman prior to + 2.1alpha2, setting up your crontab was imperative to getting + Mailman to work. With MM2.1alpha2 though, the qrunner is + started from the <tt>bin/mailmanctl</tt> script (see below) + instead of cron. You still want to set up crontab to run the + ancillary scripts, but it isn't as crucial to getting Mailman + working as it once was. Note that if you're upgrading from a + previous version of Mailman, you'll want to install the new + crontab, but be careful if you're running multiple Mailman + installations on your site! Changing the crontab could mess + with other parallel Mailman installations. + + <p>If your version of crontab supports the -u option, you must be + root to do this next step. Add $prefix/cron/crontab.in as a + crontab entry by executing these commands: + +<blockquote> +<pre> +% cd $prefix/cron +% crontab -u mailman crontab.in +</pre> +</blockquote> - <p>Set up the crontab entries. Mailman runs a number of cron - jobs for its basic functionality. You need to be user - <code>mailman</code> (or whatever you specified as - <code>--with-ownername</code>) to perform this step. Add - <code>$prefix/cron/crontab.in</code> as a crontab entry by - executing these commands: + <p>If you used the <tt>--with-ownername</tt> option, use that + user name instead of mailman for the <tt>-u</tt> argument value. + If your crontab does not support the <tt>-u</tt> option, try these + commands: <blockquote> <pre> @@ -103,9 +129,17 @@ Alias /pipermail/ $varprefix/archives/public/ </pre> </blockquote> - <p><li>Look to see if there is special instructions about hooking your - MTA up to Mailman. If so, there will be a - README.<em>yourMTA</em> file in the Mailman source directory. + <p><li>Start the Mailman qrunner daemon, by executing the following + from the <tt>$prefix</tt> directory: + +<blockquote> +<pre> +% bin/mailmanctl start +</pre> +</blockquote> + + You can use the mailmanctl script as a typical Unix init + script. <strong>BAW: add more here.</strong> <p><li>Add aliases for <code>mailman</code> and <code>mailman-owner</code> to the system's mail alias diff --git a/admin/www/install-final.html b/admin/www/install-final.html index 337381c0d..db59e99de 100644 --- a/admin/www/install-final.html +++ b/admin/www/install-final.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:37 2001 --> +<!-- Thu Jul 12 00:23:15 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Final system setup <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Final system setup</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -183,8 +183,15 @@ Email Us everything running you need to hook Mailman up to both your web server and your mail system. - <ul> - <li>If you plan on running your MTA and web server on different + <ul><p><li>If there is a <tt>README.<em>yourMTA</em>></tt> file + that describes your mail + server (MTA), read it now. Some MTAs are more compatible with + Mailman such that you can do automatic creation and removal of + mailing lists, including through-the-web operations. Examples + are Exim and Postfix. Setup instructions for specific MTAs are + contained in these README files. + + <p><li>If you plan on running your MTA and web server on different machines, sharing Mailman installations via NFS, be sure that the clocks on those two machines are synchronized closely. You might take a look at the file @@ -261,15 +268,34 @@ Alias /pipermail/ $varprefix/archives/public/ <p>Now restart your web server. - <p><li><b>IMPERATIVE! IMPORTANT! DO THIS! YOU'LL BE SORRY IF - YOU DON'T!</b> + <p><li>Set up the crontab entries. Mailman runs a number of cron jobs + for its basic functionality. In version of Mailman prior to + 2.1alpha2, setting up your crontab was imperative to getting + Mailman to work. With MM2.1alpha2 though, the qrunner is + started from the <tt>bin/mailmanctl</tt> script (see below) + instead of cron. You still want to set up crontab to run the + ancillary scripts, but it isn't as crucial to getting Mailman + working as it once was. Note that if you're upgrading from a + previous version of Mailman, you'll want to install the new + crontab, but be careful if you're running multiple Mailman + installations on your site! Changing the crontab could mess + with other parallel Mailman installations. + + <p>If your version of crontab supports the -u option, you must be + root to do this next step. Add $prefix/cron/crontab.in as a + crontab entry by executing these commands: + +<blockquote> +<pre> +% cd $prefix/cron +% crontab -u mailman crontab.in +</pre> +</blockquote> - <p>Set up the crontab entries. Mailman runs a number of cron - jobs for its basic functionality. You need to be user - <code>mailman</code> (or whatever you specified as - <code>--with-ownername</code>) to perform this step. Add - <code>$prefix/cron/crontab.in</code> as a crontab entry by - executing these commands: + <p>If you used the <tt>--with-ownername</tt> option, use that + user name instead of mailman for the <tt>-u</tt> argument value. + If your crontab does not support the <tt>-u</tt> option, try these + commands: <blockquote> <pre> @@ -279,9 +305,17 @@ Alias /pipermail/ $varprefix/archives/public/ </pre> </blockquote> - <p><li>Look to see if there is special instructions about hooking your - MTA up to Mailman. If so, there will be a - README.<em>yourMTA</em> file in the Mailman source directory. + <p><li>Start the Mailman qrunner daemon, by executing the following + from the <tt>$prefix</tt> directory: + +<blockquote> +<pre> +% bin/mailmanctl start +</pre> +</blockquote> + + You can use the mailmanctl script as a typical Unix init + script. <strong>BAW: add more here.</strong> <p><li>Add aliases for <code>mailman</code> and <code>mailman-owner</code> to the system's mail alias diff --git a/admin/www/install-start.ht b/admin/www/install-start.ht index e2ce9d2a5..415f81186 100644 --- a/admin/www/install-start.ht +++ b/admin/www/install-start.ht @@ -12,11 +12,19 @@ information. You first need to prepare your system as outlined in the sections below, and then configure and install the Mailman software. -<p><em>IMPORTANT: Pay special attention to the step below where -you have to set up your crontab entries. If you do not do this, -Mailman will not work.</em> - <p><em>UPGRADING: Upgrading is usually as easy as just installing the new version over the existing installation. However, you should read the notes in the file UPGRADING for important information before you upgrade.</em> + +<p><ol> +<li><a href="install-start.html">Start installing</a> +<li><a href="install-system.html">System setup</a> +<li><a href="install-config.html">Running configure</a> +<li><a href="install-check.html">Check your installation</a> +<li><a href="install-final.html">Final system setup</a> +<li><a href="install-custom.html">Customize Mailman</a> +<li><a href="install-test.html">Create a test list</a> +<li><a href="install-trouble.html">Troubleshooting</a> +<li><a href="install-faq.html">Common problems FAQ</a> +</ol>
\ No newline at end of file diff --git a/admin/www/install-start.html b/admin/www/install-start.html index 56b15987b..5948e55eb 100644 --- a/admin/www/install-start.html +++ b/admin/www/install-start.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:37 2001 --> +<!-- Thu Jul 12 00:01:38 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Start installing Mailman <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>Installation</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Installation</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Start installing</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -188,15 +188,22 @@ information. You first need to prepare your system as outlined in the sections below, and then configure and install the Mailman software. -<p><em>IMPORTANT: Pay special attention to the step below where -you have to set up your crontab entries. If you do not do this, -Mailman will not work.</em> - <p><em>UPGRADING: Upgrading is usually as easy as just installing the new version over the existing installation. However, you should read the notes in the file UPGRADING for important information before you upgrade.</em> +<p><ol> +<li><a href="install-start.html">Start installing</a> +<li><a href="install-system.html">System setup</a> +<li><a href="install-config.html">Running configure</a> +<li><a href="install-check.html">Check your installation</a> +<li><a href="install-final.html">Final system setup</a> +<li><a href="install-custom.html">Customize Mailman</a> +<li><a href="install-test.html">Create a test list</a> +<li><a href="install-trouble.html">Troubleshooting</a> +<li><a href="install-faq.html">Common problems FAQ</a> +</ol> </TD><!-- end of body cell --> </TR><!-- end of sidebar/body row --> </TABLE><!-- end of page table --> diff --git a/admin/www/install-system.ht b/admin/www/install-system.ht index a43f8bca2..426fb4e52 100644 --- a/admin/www/install-system.ht +++ b/admin/www/install-system.ht @@ -11,41 +11,46 @@ Links: links.h install-links.h <ul> - <li>Add a new user called <code>mailman</code>. Typically - this is added to your <code>/etc/passwd</code> file. If - username <code>mailman</code> is already in use, choose - something else unique and see the - <code>--with-ownername</code> flag below. + <li>Add a new user called <tt>mailman</tt>. Typically this is added to + your <tt>/etc/passwd</tt> file. If username <tt>mailman</tt>'is + already in use, choose something else unique and see the + <tt>--with-ownername</tt> flag below. - <p><li>Add a new group called <code>mailman</code>. Typically this - is added to your <code>/etc/group</code> file. The Mailman - files will be installed under the <code>mailman</code> group, - with the <em>set-group-id</em> bit. This is so both the web - based and mail based programs will have the proper write - permissions. If groupname <code>mailman</code> is already in - use, choose something else unique and see the - <code>--with-ownergroup</code> below. + <p><li>Add a new group called <tt>mailman</tt>. Typically this is added to + your <tt>/etc/group</tt> file. The Mailman files will be + installed under the <tt>mailman</tt> group, with the + <em>set-group-id</em> bit. Mailman's security is based on + group-ownership permissions, so it is important to get this step + right. If groupname <tt>mailman</tt> is already in use, choose + something else unique and see the <tt>--with-ownergroup</tt> below. - <p><li>Create an installation directory (called <code>$prefix</code> - in the documentation that follows). All of the Mailman files - will be installed under <code>$prefix</code>. Run - <code>configure --help</code> for ways to split the - installation up based on read-only vs. read/write files. + <p><li>Create an installation directory (called <em>$prefix</em> in the + documentation that follows). All of the Mailman files will be + installed under $prefix. Run <tt>configure --help</tt> for ways + to split the installation up based on read-only vs. read/write + files. - <p>The default directory for installing is - <code>/home/mailman</code>, but some sites do things like - mount <code>/home</code> with the <em>nosuid</em> option. - This will break Mailman, which relies on setgid programs for - its security. If this describes your environment, simply - install Mailman in a location that allows setgid programs. + <p>The default installation directory for Mailman 2.1 is + <tt>/usr/local/mailman</tt>. It used to be + <tt>/home/mailman</tt> for all versions prior to Mailman + 2.1alpha2. You can override the default by using the + <tt>--prefix</tt> option to configure (see below). If you're + upgrading from a version previous to Mailman2.1alpha2, you will + need to use <tt>--prefix</tt> unless you move your mailing lists. - <p>Make sure this directory is set to group <code>mailman</code> - (or whatever you're going to specify as - <code>--with-ownergroup</code>) and has the setgid bit set - (but see the README.BSD file in the source distribution if - you're on a BSD system). You probably also want to guarantee - that this directory is readable and executable by everyone. - For example, these shell commands will accomplish this: + <p>Watch out if your site does something like mount + <tt>/usr/local</tt> with the nosuid option. This will break + Mailman, which relies on set-gid programs for its security. If + this describes your environment, simply install Mailman in a + location that allows setgid programs. + + <p>Make sure the install directory is set to group + <tt>mailman</tt> (or whatever you're going to specify as + <tt>--with-ownergroup</tt>) and has the setgid bit set (but see + <em>README.BSD</em> if you're on a BSD system). You probably + also want to guarantee that this directory is readable and + executable by everyone. For example, these shell commands will + accomplish this: <blockquote> <pre> @@ -56,4 +61,5 @@ Links: links.h install-links.h </blockquote> You are now ready to configure and install the Mailman software. - </ul> + </ul> + diff --git a/admin/www/install-system.html b/admin/www/install-system.html index 7cc97d5fe..79f1b5ddf 100644 --- a/admin/www/install-system.html +++ b/admin/www/install-system.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:37 2001 --> +<!-- Thu Jul 12 00:07:17 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: System setup <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>System setup</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -187,41 +187,46 @@ Email Us <ul> - <li>Add a new user called <code>mailman</code>. Typically - this is added to your <code>/etc/passwd</code> file. If - username <code>mailman</code> is already in use, choose - something else unique and see the - <code>--with-ownername</code> flag below. + <li>Add a new user called <tt>mailman</tt>. Typically this is added to + your <tt>/etc/passwd</tt> file. If username <tt>mailman</tt>'is + already in use, choose something else unique and see the + <tt>--with-ownername</tt> flag below. - <p><li>Add a new group called <code>mailman</code>. Typically this - is added to your <code>/etc/group</code> file. The Mailman - files will be installed under the <code>mailman</code> group, - with the <em>set-group-id</em> bit. This is so both the web - based and mail based programs will have the proper write - permissions. If groupname <code>mailman</code> is already in - use, choose something else unique and see the - <code>--with-ownergroup</code> below. + <p><li>Add a new group called <tt>mailman</tt>. Typically this is added to + your <tt>/etc/group</tt> file. The Mailman files will be + installed under the <tt>mailman</tt> group, with the + <em>set-group-id</em> bit. Mailman's security is based on + group-ownership permissions, so it is important to get this step + right. If groupname <tt>mailman</tt> is already in use, choose + something else unique and see the <tt>--with-ownergroup</tt> below. - <p><li>Create an installation directory (called <code>$prefix</code> - in the documentation that follows). All of the Mailman files - will be installed under <code>$prefix</code>. Run - <code>configure --help</code> for ways to split the - installation up based on read-only vs. read/write files. + <p><li>Create an installation directory (called <em>$prefix</em> in the + documentation that follows). All of the Mailman files will be + installed under $prefix. Run <tt>configure --help</tt> for ways + to split the installation up based on read-only vs. read/write + files. - <p>The default directory for installing is - <code>/home/mailman</code>, but some sites do things like - mount <code>/home</code> with the <em>nosuid</em> option. - This will break Mailman, which relies on setgid programs for - its security. If this describes your environment, simply - install Mailman in a location that allows setgid programs. + <p>The default installation directory for Mailman 2.1 is + <tt>/usr/local/mailman</tt>. It used to be + <tt>/home/mailman</tt> for all versions prior to Mailman + 2.1alpha2. You can override the default by using the + <tt>--prefix</tt> option to configure (see below). If you're + upgrading from a version previous to Mailman2.1alpha2, you will + need to use <tt>--prefix</tt> unless you move your mailing lists. - <p>Make sure this directory is set to group <code>mailman</code> - (or whatever you're going to specify as - <code>--with-ownergroup</code>) and has the setgid bit set - (but see the README.BSD file in the source distribution if - you're on a BSD system). You probably also want to guarantee - that this directory is readable and executable by everyone. - For example, these shell commands will accomplish this: + <p>Watch out if your site does something like mount + <tt>/usr/local</tt> with the nosuid option. This will break + Mailman, which relies on set-gid programs for its security. If + this describes your environment, simply install Mailman in a + location that allows setgid programs. + + <p>Make sure the install directory is set to group + <tt>mailman</tt> (or whatever you're going to specify as + <tt>--with-ownergroup</tt>) and has the setgid bit set (but see + <em>README.BSD</em> if you're on a BSD system). You probably + also want to guarantee that this directory is readable and + executable by everyone. For example, these shell commands will + accomplish this: <blockquote> <pre> @@ -232,7 +237,8 @@ Email Us </blockquote> You are now ready to configure and install the Mailman software. - </ul> + </ul> + </TD><!-- end of body cell --> </TR><!-- end of sidebar/body row --> diff --git a/admin/www/install-test.ht b/admin/www/install-test.ht index 401913714..37884f78c 100644 --- a/admin/www/install-test.ht +++ b/admin/www/install-test.ht @@ -3,21 +3,63 @@ Links: links.h install-links.h <h3>Create a test list</h3> -Create a list named <em>test</em>. To do so, run the program -<code>$prefix/bin/newlist</code>. You will be prompted for the name -of the list, as well as the email address of the person running the -list. Put your own email address as the list administrator's address. - -<p>Running newlist will generate a list of aliases that must be added -to the system. If you are running Sendmail, you may add the lines -output directly to the file <code>/etc/aliases</code>. You may need -to run the command <code>newaliases</code> (all as <b>root</b>). Now -the mailing address for your list as well as its administrative -addresses will be set up. If you are not running Sendmail, consult -your MTA's documentation for information on adding aliases. + To create and test your first list, try the following: -<p>You will receive email instructions on how to visit the list you -just created. Using these instructions, subscribe to the mailing -list. Once you have subscribed (which requires a confirmation step!), -send a message to the list, and see if you get it. If so, then you -have successfully installed Mailman, and set up your first list! + <p><li>First, initialize the site administrator's password by cd'ing to + the install directory (by default <tt>/usr/local/mailman</tt>) + and typing + +<blockquote> +<pre> +% bin/mmsitepass +New site password: [yourpassword] +Again to confirm password: [yourpassword] +Password changed. +</pre> +</blockquote> + + <p><li>Visit the url + +<blockquote> +<pre> +http://my.dom.ain/mailman/create +</pre> +</blockquote> + + <p>Fill out the form as described in the on-screen instructions, + and in the <em>List creator's password</em> field, type the + password you entered above. Type your own email address for the + <em>Initial list owner address</em>, and select <em>Yes</em> to + notify the list administrator. + + <p><li>Hit <em>Create List</em> + + <p><li>Check your email for a message from Mailman informing you that + your new mailing list was created. + + <p><li>NOTE: If you are using an MTA other than Exim or Postfix + (e.g. Sendmail or Qmail), then you'll need to do the extra step + of installing the mailing list aliases manually. Follow the + instructions in an email message that you should have received + (you'll need to know how to do this for your particular MTA, see + the README for your MTA for more information). + + <p><li>Now visit the list's admin page (either by following the link on + the web page or entering the link from the email Mailman just + sent you). Type in the list's password and click on + <em>Let me in...</em> + + <p><li>Click on <em>Membership Management</em> and then on + <em>Mass Subscription</em>. + + <p><li>Enter your email address in the big text field, and click on + <em>Submit Your Changes</em> + + <p><li>Now go to your email and send a message to yourlist@my.dom.ain. + Within a minute or two you should see your message reflected + back to you via Mailman. + + <p>Congratulations! You've just set up and tested your first Mailman + mailing list. If you had any problems along the way, please see + the <a href="install-trouble.html">Troubleshooting</a> section. +</ul> diff --git a/admin/www/install-test.html b/admin/www/install-test.html index cf7c68e0b..20b15b6b1 100644 --- a/admin/www/install-test.html +++ b/admin/www/install-test.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:38 2001 --> +<!-- Thu Jul 12 00:27:31 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Create a test list <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Create a test list</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-trouble.html">Troubleshooting</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -179,24 +179,66 @@ Email Us <TD VALIGN=TOP WIDTH="90%"><BR> <h3>Create a test list</h3> -Create a list named <em>test</em>. To do so, run the program -<code>$prefix/bin/newlist</code>. You will be prompted for the name -of the list, as well as the email address of the person running the -list. Put your own email address as the list administrator's address. - -<p>Running newlist will generate a list of aliases that must be added -to the system. If you are running Sendmail, you may add the lines -output directly to the file <code>/etc/aliases</code>. You may need -to run the command <code>newaliases</code> (all as <b>root</b>). Now -the mailing address for your list as well as its administrative -addresses will be set up. If you are not running Sendmail, consult -your MTA's documentation for information on adding aliases. + To create and test your first list, try the following: -<p>You will receive email instructions on how to visit the list you -just created. Using these instructions, subscribe to the mailing -list. Once you have subscribed (which requires a confirmation step!), -send a message to the list, and see if you get it. If so, then you -have successfully installed Mailman, and set up your first list! + <p><li>First, initialize the site administrator's password by cd'ing to + the install directory (by default <tt>/usr/local/mailman</tt>) + and typing + +<blockquote> +<pre> +% bin/mmsitepass +New site password: [yourpassword] +Again to confirm password: [yourpassword] +Password changed. +</pre> +</blockquote> + + <p><li>Visit the url + +<blockquote> +<pre> +http://my.dom.ain/mailman/create +</pre> +</blockquote> + + <p>Fill out the form as described in the on-screen instructions, + and in the <em>List creator's password</em> field, type the + password you entered above. Type your own email address for the + <em>Initial list owner address</em>, and select <em>Yes</em> to + notify the list administrator. + + <p><li>Hit <em>Create List</em> + + <p><li>Check your email for a message from Mailman informing you that + your new mailing list was created. + + <p><li>NOTE: If you are using an MTA other than Exim or Postfix + (e.g. Sendmail or Qmail), then you'll need to do the extra step + of installing the mailing list aliases manually. Follow the + instructions in an email message that you should have received + (you'll need to know how to do this for your particular MTA, see + the README for your MTA for more information). + + <p><li>Now visit the list's admin page (either by following the link on + the web page or entering the link from the email Mailman just + sent you). Type in the list's password and click on + <em>Let me in...</em> + + <p><li>Click on <em>Membership Management</em> and then on + <em>Mass Subscription</em>. + + <p><li>Enter your email address in the big text field, and click on + <em>Submit Your Changes</em> + + <p><li>Now go to your email and send a message to yourlist@my.dom.ain. + Within a minute or two you should see your message reflected + back to you via Mailman. + + <p>Congratulations! You've just set up and tested your first Mailman + mailing list. If you had any problems along the way, please see + the <a href="install-trouble.html">Troubleshooting</a> section. +</ul> </TD><!-- end of body cell --> </TR><!-- end of sidebar/body row --> diff --git a/admin/www/install-trouble.ht b/admin/www/install-trouble.ht index b5bbfb932..f4665a9bd 100644 --- a/admin/www/install-trouble.ht +++ b/admin/www/install-trouble.ht @@ -4,19 +4,21 @@ Links: links.h install-links.h <h3>Troubleshooting</h3> If you encounter problems with running Mailman, first check the - "Common Problems" section, below. If your problem is not covered - there, check the file <a href="faq.html">FAQ</a> and FAQ.LINUX. - Then check for a log entry from Mailman in your syslog. + <a href="install-faq.html">Common Problems FAQ</a> page. If your + problem is not covered there, check the + <a href="faq.html">FAQ</a>. Then check for a log + entry from Mailman in your syslog and in the + <tt>$prefix/logs/error</tt> file. <p>Where syslog lives on your particular machine may vary. It may - be in <code>/var/log/maillog</code>. It may also be in - <code>/var/log/syslog</code>. On many machines, syslog files live - in <code>/adm/log/</code> instead of <code>/var/log</code>. + be in <tt>/var/log/maillog</tt>. It may also be in + <tt>/var/log/syslog</tt>. On many machines, syslog files live in + <tt>/adm/log/</tt> instead of <tt>/var/log</tt>. <p>If you encounter an error, send an error report to - <a - href="mailto:mailman-users@python.org">mailman-users@python.org</a>. + <a href="mailto:mailman-users@python.org">mailman-users@python.org</a>. Include a description of what you're doing to cause the problem, and the relevant lines from your - syslog. Also include information on your operating system and - version of Python. + syslog. Also include information on your operating system, which + version of Python you're using, and which version of Mailman + you're installing. diff --git a/admin/www/install-trouble.html b/admin/www/install-trouble.html index cc5b5e3dd..d5e348ca4 100644 --- a/admin/www/install-trouble.html +++ b/admin/www/install-trouble.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:38 2001 --> +<!-- Thu Jul 12 00:30:11 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Troubleshooting <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,82 +81,82 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Installing Mailman </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Start installing</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-system.html">System setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-config.html">Running configure</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-check.html">Check your installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-final.html">Final system setup</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-custom.html">Customize Mailman</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-test.html">Create a test list</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Troubleshooting</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-faq.html">Common problems FAQ</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -164,10 +164,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -180,22 +180,24 @@ Email Us <h3>Troubleshooting</h3> If you encounter problems with running Mailman, first check the - "Common Problems" section, below. If your problem is not covered - there, check the file <a href="faq.html">FAQ</a> and FAQ.LINUX. - Then check for a log entry from Mailman in your syslog. + <a href="install-faq.html">Common Problems FAQ</a> page. If your + problem is not covered there, check the + <a href="faq.html">FAQ</a>. Then check for a log + entry from Mailman in your syslog and in the + <tt>$prefix/logs/error</tt> file. <p>Where syslog lives on your particular machine may vary. It may - be in <code>/var/log/maillog</code>. It may also be in - <code>/var/log/syslog</code>. On many machines, syslog files live - in <code>/adm/log/</code> instead of <code>/var/log</code>. + be in <tt>/var/log/maillog</tt>. It may also be in + <tt>/var/log/syslog</tt>. On many machines, syslog files live in + <tt>/adm/log/</tt> instead of <tt>/var/log</tt>. <p>If you encounter an error, send an error report to - <a - href="mailto:mailman-users@python.org">mailman-users@python.org</a>. + <a href="mailto:mailman-users@python.org">mailman-users@python.org</a>. Include a description of what you're doing to cause the problem, and the relevant lines from your - syslog. Also include information on your operating system and - version of Python. + syslog. Also include information on your operating system, which + version of Python you're using, and which version of Mailman + you're installing. </TD><!-- end of body cell --> </TR><!-- end of sidebar/body row --> diff --git a/admin/www/inthenews.ht b/admin/www/inthenews.ht index aeab6adba..717abd07e 100644 --- a/admin/www/inthenews.ht +++ b/admin/www/inthenews.ht @@ -241,5 +241,8 @@ like to be included in this list, please <li><a href="http://www.arachnis.com/">www.arachnis.com</a> <!-- Supreet Sethi --> <li><a href="http://www.sarai.net/">Sarai (New Media Initiative)</a> + <!-- Pankaj Kaushal --> + <li><a href="http://www.gnu-india.org">The Hurd + development/hacking group in India</a> </ul> diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html index 26f4b1df2..291b26ca7 100644 --- a/admin/www/inthenews.html +++ b/admin/www/inthenews.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Fri Jul 6 04:00:28 2001 --> +<!-- Thu Jul 12 00:43:55 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Mailman in Use and in the News <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,51 +81,51 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Mailman in Use</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -133,10 +133,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -387,6 +387,9 @@ like to be included in this list, please <li><a href="http://www.arachnis.com/">www.arachnis.com</a> <!-- Supreet Sethi --> <li><a href="http://www.sarai.net/">Sarai (New Media Initiative)</a> + <!-- Pankaj Kaushal --> + <li><a href="http://www.gnu-india.org">The Hurd + development/hacking group in India</a> </ul> diff --git a/admin/www/lists.ht b/admin/www/lists.ht index de9691c7a..ca5cdae58 100644 --- a/admin/www/lists.ht +++ b/admin/www/lists.ht @@ -28,7 +28,9 @@ nice demonstration of Mailman! (<a href="http://www.python.org/pipermail/mailman-developers/"><em>archives</em></a>) <p>You may also want to find a project on our Mailman - <a href="todo.html">TODO list</a>. + <a href="todo.html">TODO list</a> or on the + <a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage">Mailman + design notes wiki</a>. <p><li><a href="http://www.python.org/mailman/listinfo/mailman-i18n"> Mailman Internationalization</a> is the list for discussing the diff --git a/admin/www/lists.html b/admin/www/lists.html index bdc81b545..404b861f7 100644 --- a/admin/www/lists.html +++ b/admin/www/lists.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:38 2001 --> +<!-- Wed Jul 11 23:47:41 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Mailman mailing lists <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>Discussion Lists</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,51 +81,51 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Discussion Lists</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -133,10 +133,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -174,7 +174,9 @@ nice demonstration of Mailman! (<a href="http://www.python.org/pipermail/mailman-developers/"><em>archives</em></a>) <p>You may also want to find a project on our Mailman - <a href="todo.html">TODO list</a>. + <a href="todo.html">TODO list</a> or on the + <a href="http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage">Mailman + design notes wiki</a>. <p><li><a href="http://www.python.org/mailman/listinfo/mailman-i18n"> Mailman Internationalization</a> is the list for discussing the diff --git a/admin/www/mgrs.html b/admin/www/mgrs.html index d75b5da9d..a1142f66e 100644 --- a/admin/www/mgrs.html +++ b/admin/www/mgrs.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:38 2001 --> +<!-- Wed Jul 11 23:44:06 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: List Manager Documentation <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>List Managers</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,73 +81,73 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="users.html">Users</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>List Managers</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="admins.html">Site Administrators</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="devs.html">Developers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="i18n.html">Internationalization</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="otherdocs.html">Other Documentation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -155,10 +155,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> diff --git a/admin/www/otherdocs.html b/admin/www/otherdocs.html index 6abd12953..319a9a605 100644 --- a/admin/www/otherdocs.html +++ b/admin/www/otherdocs.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:38 2001 --> +<!-- Wed Jul 11 23:44:06 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: Other Documentation <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,73 +81,73 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="users.html">Users</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mgrs.html">List Managers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="admins.html">Site Administrators</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="devs.html">Developers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="i18n.html">Internationalization</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Other Documentation</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -155,10 +155,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> diff --git a/admin/www/todo.ht b/admin/www/todo.ht index abf75cd1b..8ba022ee7 100644 --- a/admin/www/todo.ht +++ b/admin/www/todo.ht @@ -2,16 +2,44 @@ 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 25-Jun-2001), so what's left will probably end up in a Mailman 3.0. <p> + 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 11-Jul-2001), so what's left will probably end up in a + Mailman 3.0. + Please also see the Mailman design notes wiki at + http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage +<p> <h3> Email Handling </h3> <ul> + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. - <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly (optional). + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + </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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -19,101 +47,855 @@ Title: The Mailman Wishlist <li> More on-line documentation and UI help <li> A developer's guide w/ architecture and API information <li> manpages for the scripts in bin and cron - <li> Integrate Christopher Kolar's documentation + <li> Integrate Christopher Kolar's documentation </ul> <h3> General Web UI </h3> <ul> - <li> NO DEAD ENDS - <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using a template language/system like Quixote or PHP. + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a 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 turned-off features. + <li> Web pages should never mention disabled features. </ul> <h3> List Administration </h3> <ul> - <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the message was edited by the moderator). + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + <li> Allow the list-admin to require approvals for unsubs <li> Allow the admin to disable option settings by users <li> Ability to set defaults for the various user settings from the "Membership Management" page. - <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + <li> New moderation choice: archive but don't send to list. <li> New moderation choice: annotate and send to author for resubmittal. <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. - <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). - <li> Add an option to include Reply-To: header in the membership test for a members-only list posting + + <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> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out duplicate deliveries. - <li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever address they want to whichever list, with different options per subscription. + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) - <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + </ul> <h3> Site Administration </h3> <ul> - <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their list. - <li> add_members should have a switch to disable admin notifications + <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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications </ul> <h3> Other Usability Improvments </h3> <ul> - <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and authorization to modify the sub & superlists. Majordomo2 is reported to have some good features in this regard. + <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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). - <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Don't use the first public mailing list as the `originator' of password reminders. + </ul> <h3> Mailcmd interface </h3> <ul> + <li> Here's the wish list for future versions of Mailman. Many new + features have been added to Mailman 2.1 (still in alpha as of this + writing 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + <li> Provide an email interface to all administrative commands - <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control this. Also, adding a confirmation with hit-reply to resubscribe - <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation message. Helps track down subscribe bombs. + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + <li> Investigate Majordomo2's email admin capabilities. - <li> Support the `which' command. + <li> Support the `which' command. </ul> <h3> Portability & architecture </h3> <ul> - <li> Replace cron stuff with our own scheduling mechanism. - <li> Get rid of the one-shot process model altogether in favor of a multithreaded monolithic architecture. - <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a relational database, ZODB, LDAP, etc) + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + <li> Keep a members Real Name with their email address <li> Member profiles - <li> Do a serious and thorough security audit + <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> 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. - <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + </ul> <h3> Bounce handling </h3> <ul> + <li> Here's the wish list for future versions of Mailman. Many new + features have been added to Mailman 2.1 (still in alpha as of this + writing 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + + <li> Keep a members Real Name with their email address + <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. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + <li> Add more patterns for bounce handling (never ending) <li> Occasionally remove stale bounce entries <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). - <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. We may want to do this for explicitly disabled addrs too, but perhaps with a different schedule. - <li> Delete bounce disabled address after some period of retry + + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. + We may want to do this for explicitly disabled addrs too, but + perhaps with a different schedule. + + <li> Delete bounce disabled address after some period of retry </ul> <h3> Pipermail + Archiving mechanism </h3> <ul> + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + + <li> Keep a members Real Name with their email address + <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. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + + <li> Add more patterns for bounce handling (never ending) + <li> Occasionally remove stale bounce entries + <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). + + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. + We may want to do this for explicitly disabled addrs too, but + perhaps with a different schedule. + + <li> Delete bounce disabled address after some period of retry <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> In general the whole Pipermail subsystem needs a good rewrite. </ul> <h3> Code cleanup </h3> <ul> + <li> Here's the wish list for future versions of Mailman. Many new + features have been added to Mailman 2.1 (still in alpha as of this + writing 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + + <li> Keep a members Real Name with their email address + <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. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + + <li> Add more patterns for bounce handling (never ending) + <li> Occasionally remove stale bounce entries + <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). + + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. + We may want to do this for explicitly disabled addrs too, but + perhaps with a different schedule. + + <li> Delete bounce disabled address after some period of retry + <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! </ul> diff --git a/admin/www/todo.html b/admin/www/todo.html index 43d6c0b29..d1266f81c 100644 --- a/admin/www/todo.html +++ b/admin/www/todo.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Mon Jun 25 17:26:20 2001 --> +<!-- Wed Jul 11 23:44:07 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: The Mailman Wishlist <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./users.html">Users</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,51 +81,51 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Wishlist!</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -133,10 +133,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> @@ -148,16 +148,44 @@ Email Us <TD VALIGN=TOP WIDTH="90%"><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 25-Jun-2001), so what's left will probably end up in a Mailman 3.0. <p> + 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 11-Jul-2001), so what's left will probably end up in a + Mailman 3.0. + Please also see the Mailman design notes wiki at + http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage +<p> <h3> Email Handling </h3> <ul> + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. - <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly (optional). + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + </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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -165,103 +193,857 @@ Email Us <li> More on-line documentation and UI help <li> A developer's guide w/ architecture and API information <li> manpages for the scripts in bin and cron - <li> Integrate Christopher Kolar's documentation + <li> Integrate Christopher Kolar's documentation </ul> <h3> General Web UI </h3> <ul> - <li> NO DEAD ENDS - <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using a template language/system like Quixote or PHP. + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a 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 turned-off features. + <li> Web pages should never mention disabled features. </ul> <h3> List Administration </h3> <ul> - <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the message was edited by the moderator). + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + <li> Allow the list-admin to require approvals for unsubs <li> Allow the admin to disable option settings by users <li> Ability to set defaults for the various user settings from the "Membership Management" page. - <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + <li> New moderation choice: archive but don't send to list. <li> New moderation choice: annotate and send to author for resubmittal. <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. - <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). - <li> Add an option to include Reply-To: header in the membership test for a members-only list posting + + <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> Allow the user to be excluded from postings if they're getting them in the to: or cc: headers. Be smarter about filtering out duplicate deliveries. - <li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever address they want to whichever list, with different options per subscription. + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) - <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + </ul> <h3> Site Administration </h3> <ul> - <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their list. - <li> add_members should have a switch to disable admin notifications + <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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications </ul> <h3> Other Usability Improvments </h3> <ul> - <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and authorization to modify the sub & superlists. Majordomo2 is reported to have some good features in this regard. + <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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). - <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Don't use the first public mailing list as the `originator' of password reminders. + </ul> <h3> Mailcmd interface </h3> <ul> + <li> Here's the wish list for future versions of Mailman. Many new + features have been added to Mailman 2.1 (still in alpha as of this + writing 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + <li> Provide an email interface to all administrative commands - <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control this. Also, adding a confirmation with hit-reply to resubscribe - <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation message. Helps track down subscribe bombs. + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + <li> Investigate Majordomo2's email admin capabilities. - <li> Support the `which' command. + <li> Support the `which' command. </ul> <h3> Portability & architecture </h3> <ul> - <li> Replace cron stuff with our own scheduling mechanism. - <li> Get rid of the one-shot process model altogether in favor of a multithreaded monolithic architecture. - <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a relational database, ZODB, LDAP, etc) + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + <li> Keep a members Real Name with their email address <li> Member profiles - <li> Do a serious and thorough security audit + <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> 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. - <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + </ul> <h3> Bounce handling </h3> <ul> + <li> Here's the wish list for future versions of Mailman. Many new + features have been added to Mailman 2.1 (still in alpha as of this + writing 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + + <li> Keep a members Real Name with their email address + <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. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + <li> Add more patterns for bounce handling (never ending) <li> Occasionally remove stale bounce entries <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). - <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. We may want to do this for explicitly disabled addrs too, but perhaps with a different schedule. - <li> Delete bounce disabled address after some period of retry + + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. + We may want to do this for explicitly disabled addrs too, but + perhaps with a different schedule. + + <li> Delete bounce disabled address after some period of retry </ul> <h3> Pipermail + Archiving mechanism </h3> <ul> + <li> 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 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + + <li> Keep a members Real Name with their email address + <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. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + + <li> Add more patterns for bounce handling (never ending) + <li> Occasionally remove stale bounce entries + <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). + + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. + We may want to do this for explicitly disabled addrs too, but + perhaps with a different schedule. + + <li> Delete bounce disabled address after some period of retry <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> In general the whole Pipermail subsystem needs a good rewrite. </ul> <h3> Code cleanup </h3> <ul> + <li> Here's the wish list for future versions of Mailman. Many new + features have been added to Mailman 2.1 (still in alpha as of this + writing 11-Jul-2001), 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> Use VERP or DSN for address tracing, perhaps tied to the monthly password reminders, or VERPing the occasional regular message. + + <li> Re-implement bulk mailer the Right Way: an asynchat/asyncore server to do DNS lookups and remote MTA delivery directly + (optional). + + <li> A detailed feature list + <li> A user's guide + <li> A site-admin's guide + <li> A list-admin's guide + <li> More on-line documentation and UI help + <li> A developer's guide w/ architecture and API information + <li> manpages for the scripts in bin and cron + <li> Integrate Christopher Kolar's documentation + <li> NO DEAD ENDS and every web page is reachable. + <li> All web UI must be configurable so that it more easily integrates into an existing site's design. Probably means using + a template language/system like Zope's Presentation Templates, + Quixote, or PHP. + + <li> Default UI should add a navigation sidebar to all web pages. + <li> Web pages should never mention disabled features. + <li> Allow the moderator to edit posts being held for approval (make it evident, either through a header or other means that the + message was edited by the moderator). + + <li> Allow the list-admin to require approvals for unsubs + <li> Allow the admin to disable option settings by users + <li> Ability to set defaults for the various user settings from the "Membership Management" page. + + <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes + very useful, but could be dangerous!) + + <li> New moderation choice: archive but don't send to list. + <li> New moderation choice: annotate and send to author for resubmittal. + <li> Make it easier for an admin who manages multiple lists to handling pending requests sitting on all those lists. + + <li> Ability to ban specific troublesome users (from posting, subscribing, etc). Posts from banned users would be discarded. + + <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a + secondary channel, like moderators@isc.org). + + <li> 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. + + <li> Allow the user to get BOTH normal and digested delivery (but I still don't understand why someone would want this) + + <li> More flexible digests: index digests (subject and authors only, with URLs to retrieve the article) + + <li> Timed vacations, allowing a user to postpone or discard email for a certain number of days or weeks. + + <li> Allow the site admin to define list styles or themes, and list admins to choose one of the canned styles to apply to their + list. + + <li> add_members should have a switch to disable admin notifications + <li> A better strategy is needed for sub-lists and super-lists, including dealing with the resulting password reminders and + authorization to modify the sub & superlists. Majordomo2 is + reported to have some good features in this regard. + + <li> Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). + + <li> Don't use the first public mailing list as the `originator' of password reminders. + + <li> Provide an email interface to all administrative commands + <li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control + this. Also, adding a confirmation with click-thru confirmation + to resubscribe. + + <li> For email subscribes, keep an audit of where requests are coming from, and send the original request headers in the confirmation + message. Helps track down subscribe bombs. + + <li> Investigate Majordomo2's email admin capabilities. + <li> Support the `which' command. + <li> Use a real transactional database for all information, and allow various bits of information to come from different sources (a + relational database, ZODB, LDAP, etc) + + <li> Keep a members Real Name with their email address + <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. + + <li> Split Mailman into libraries so, e.g. the delivery part could be used by other projects. + + <li> Make a distinction between disabled addresses due to bouncing and a user's explicit disabling of an address + + <li> Add more patterns for bounce handling (never ending) + <li> Occasionally remove stale bounce entries + <li> Send mail to people who are being removed without their knowledge (even though they're likely not to get it). + + <li> Reminders to disabled addresses. The idea is that if an addr is disabled due to bouncing, we should send out periodic reminders. + We may want to do this for explicitly disabled addrs too, but + perhaps with a different schedule. + + <li> Delete bounce disabled address after some period of retry + <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! </ul> </TD><!-- end of body cell --> diff --git a/admin/www/users.html b/admin/www/users.html index 73d789677..de4155589 100644 --- a/admin/www/users.html +++ b/admin/www/users.html @@ -1,6 +1,6 @@ <HTML> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed May 16 22:31:39 2001 --> +<!-- Wed Jul 11 23:44:06 2001 --> <!-- USING HT2HTML 1.1 --> <!-- SEE http://www.wooz.org/barry/software/pyware.html --> <!-- User-specified headers: @@ -21,57 +21,57 @@ Title: User Documentation <!-- start of banner row --> <TR> <!-- start of corner cells --> -<TD WIDTH=150 VALIGN=CENTER BGCOLOR="black"> +<TD WIDTH=150 VALIGN=CENTER BGCOLOR="white"> <center> <a href="./index.html"> <img border=0 src="./images/logo-70.jpg"></a></center> </TD> -<TD WIDTH=15 BGCOLOR="#99997c"> </TD><!--spacer--> +<TD WIDTH=15 BGCOLOR="#caa08f"> </TD><!--spacer--> <!-- end of corner cells --> <!-- start of banner --> -<TD WIDTH="90%" BGCOLOR="#99997c"> +<TD WIDTH="90%" BGCOLOR="#caa08f"> <!-- start of site links table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=0 COLS=3 ROWS=4 BGCOLOR="#ffffff"> <TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./index.html">Home</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <b>Users</b> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.list.org/">List.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./install-start.html">Installation</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./mgrs.html">List Managers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/software/mailman/mailman.html">Mailman at GNU</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./faq.html">FAQ</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./admins.html">Site Administrators</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.python.org/">Python.Org</a> </TD> </TR><TR> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./lists.html">Discussion Lists</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="./devs.html">Developers</a> </TD> - <TD BGCOLOR="#99997c"> + <TD BGCOLOR="#caa08f"> <a href="http://www.gnu.org/">Gnu.Org</a> </TD> </TR> @@ -81,73 +81,73 @@ CELLSPACING=0 CELLPADDING=0 </TR><!-- end of banner row --> <TR><!-- start of sidebar/body row --> <!-- start of sidebar cells --> -<TD WIDTH=150 VALIGN=TOP BGCOLOR="#99997c"> +<TD WIDTH=150 VALIGN=TOP BGCOLOR="#caa08f"> <!-- start of sidebar table --> <TABLE WIDTH="100%" BORDER=0 CELLSPACING=0 CELLPADDING=3 BGCOLOR="#ffffff"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Overview </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="index.html">Home</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="features.html">Features</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="download.html">Requirements, Download</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="install-start.html">Installation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="lists.html">Discussion Lists</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="bugs.html">Bugs and Patches</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="faq.html">Frequently Asked Questions</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="inthenews.html">Mailman in Use</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="todo.html">Wishlist!</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Documentation </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <b>Users</b> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mgrs.html">List Managers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="admins.html">Site Administrators</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="devs.html">Developers</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="i18n.html">Internationalization</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="otherdocs.html">Other Documentation</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> -<TR><TD BGCOLOR="#663300"><B><FONT COLOR="#ffffff"> +<TR><TD BGCOLOR="#caa08f"> +<TR><TD BGCOLOR="#545454"><B><FONT COLOR="#ffffff"> Email Us </FONT></B></TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <A HREF="mailto:mailman-users@python.org">mailman-users@python.org</A> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> <a href="http://www.python.org/"><img border=0 src="./images/PythonPoweredSmall.png" ></a> <a href="http://sourceforge.net"><img @@ -155,10 +155,10 @@ Email Us width="88" height="31" border="0" alt="SourceForge Logo"></a> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> </TD></TR> -<TR><TD BGCOLOR="#99997c"> +<TR><TD BGCOLOR="#caa08f"> © 1998,1999,2000,2001<br>Free Software Foundation, Inc. </TD></TR> </TABLE><!-- end of sidebar table --> |