summaryrefslogtreecommitdiff
path: root/admin
diff options
context:
space:
mode:
authorbwarsaw2002-01-28 05:05:33 +0000
committerbwarsaw2002-01-28 05:05:33 +0000
commit1795b50fb3fe9be91dd9650961914fd2843c5db2 (patch)
treef100665e9de0657ea95bbd8fbae66d6927da3b70 /admin
parent8ee905cbb8564fc8ced6759e729945248c64b54c (diff)
downloadmailman-1795b50fb3fe9be91dd9650961914fd2843c5db2.tar.gz
mailman-1795b50fb3fe9be91dd9650961914fd2843c5db2.tar.zst
mailman-1795b50fb3fe9be91dd9650961914fd2843c5db2.zip
A bunch of updates
Diffstat (limited to 'admin')
-rw-r--r--admin/www/inthenews.ht89
-rw-r--r--admin/www/inthenews.html91
-rw-r--r--admin/www/todo.ht146
-rw-r--r--admin/www/todo.html152
4 files changed, 232 insertions, 246 deletions
diff --git a/admin/www/inthenews.ht b/admin/www/inthenews.ht
index e91852fec..c29269cf3 100644
--- a/admin/www/inthenews.ht
+++ b/admin/www/inthenews.ht
@@ -43,9 +43,14 @@ like to be included in this list, please
<!-- Roger Pena -->
<li><a href="http://www.redhat.com/">RedHat, Inc.</a>
<li><a href="http://lists.samba.org/">Samba</a>
+ <!-- Chris Howells -->
+ <li><a href="http://mail.kde.org/mailman/listinfo">KDE Project</a>
+ <li><a href="http://www.pair.com/pair/pairlist/">Pair List</a>
<!-- Barry Warsaw -->
<li><a href="http://www.python.org/sigs/">Python.Org</a>
+ <li><a href="http://lists.zope.org/">Zope.org</a>
+ <li><a href="http://www.zope.com/">Zope.com</a> (<em>Yay!</em>)
<!-- Owen Taylor -->
<li><a href="http://mail.gnome.org/">GNOME.Org</a>
<!-- Nigel Metheringham -->
@@ -62,6 +67,9 @@ like to be included in this list, please
(private lists only, currently)
<!-- Bill Bradford -->
<li><a href="http://www.sunhelp.org/mailman/listinfo/">SunHelp.Org</a>
+ <li><a href="http://www.sunmanagers.org/mailman/listinfo">Sun Managers</a>
+ <li><a href="http://www.linuxmanagers.org/mailman/listinfo">Linux
+ Managers</a>
<!-- Bill Hoffman -->
<li><a href="http://public.kitware.com/">Visualization Tool Kit
(VTK)</a>
@@ -82,6 +90,23 @@ like to be included in this list, please
<!-- Jeff Berliner -->
<li><a href="http://endeavor.med.nyu.edu/mailman/listinfo">New York
University School of Medicine</a>
+ <!-- Marco Obaid -->
+ <li><a href="http://lists.MUW.Edu/">Mississippi University for Women</a>
+ <!-- Carel Braam -->
+ <li><a href="http://pegasus.tue.nl">Eindhoven University of Technology</a>
+ <!-- Prof. Marcelo Maia Sobral -->
+ <li>University of vale do Itajai, Sao Jose, Brasil
+ <!-- Conal Garrity -->
+ <li><a href="http://www.kvsc.org/">KVSC Radio, St. Cloud State
+ University, MN</a>
+ <!-- Babak Mostaghassi -->
+ <li><a href="http://ill.iut.ac.ir/">Linux Lab of Isfahan
+ University Of Technology</a>
+ <!-- Aly S.P Dharshi -->
+ <li>University of Lethbridge Organization of Residence Students
+ <!-- Courtney V. Bearse -->
+ <li><a href="http://linux.uky.edu/mailman/listinfo/">University of
+ Kentucky</a>
<!-- Chuq von Rospach's alter ego -->
<li><a href="http://www.hockeyfanz.com/">HockeyFanz.com</a>
@@ -165,14 +190,10 @@ like to be included in this list, please
<!-- Krzysztof Wychowalek -->
<li><a href="http://www.most.org.pl">MOST - Polish provider for
Environmental Movement</a>
- <!-- Marco Obaid -->
- <li><a href="http://lists.MUW.Edu/">Mississippi University for Women</a>
<!-- Ken Kyler -->
<li><a href="http://www.elists.org/">eLists.org</a>
<!-- kellan -->
<li><a href="http://lists.indymedia.org/">IndyMedia</a>
- <!-- Carel Braam -->
- <li><a href="http://pegasus.tue.nl">Eindhoven University of Technology</a>
<!-- Yasha Harari -->
<li><a href="http://mail.anywhereyougo.com/">mail.anywhereyougo.com</a>
<!-- Gary Coulbourne -->
@@ -259,8 +280,6 @@ like to be included in this list, please
Contestado-UnC Curitibanos/SC/Brasil</a>
<!-- Quique -->
<li><a href="http://sindominio.net">sindominio.net</a>
- <!-- Prof. Marcelo Maia Sobral -->
- <li>University of vale do Itajai, Sao Jose, Brasil
<!-- Damir Horvat -->
<li><a href="http://www.voljatel.si">VOLJATEL telekomunikacije d.d.</a>
<!-- Rod (Gentle) Ellis -->
@@ -277,5 +296,63 @@ like to be included in this list, please
<!-- Jim Reisert -->
<li><a href="http://lists.contesting.com/mailman/listinfo"
>Contesting.com</a>, Amateur ("Ham") Radio lists.
+ <!-- Stephen McKeown -->
+ <li><a href="http://www.jmbarrie.net">http://www.jmbarrie.net</a>
+ <!-- Dennis Du Bois -->
+ <li><a href="http://freelance-seattle.net/">Freelance-Seattle.net</a>
+ <!-- Charles Tucker -->
+ <li><a href="http://www.riverbend.com/">Riverbend Church</a>
+ <!-- Ben Dyer -->
+ <li><a href="http://lists.evolt.org/">Evolt.org</a>
+ <!-- munindo -->
+ <li><a href="http://mail2.factsoft.de/mailman/listinfo/national"
+ >http://mail2.factsoft.de/mailman/listinfo/national</a>
+ <!-- Ignacio Valdez -->
+ <li><a href="http://www.linuxmednews.com">Linux Medical News</a>
+ <!-- Dean Strik -->
+ <li><a href="http://lists.stack.nl/">stack.nl</a>
+ <!-- Jim Goltz -->
+ <li>NFR Security
+ <!-- Stephan Richter -->
+ <li><a href="http://iuveno-net.de/">iuveno-net.de</a>
+ <!-- Johnny Fuerst -->
+ <li><a href="http://mailman.cathat.net/">cathat.net</a>
+ <!-- gulli -->
+ <li><a href="http://www.heise.de/bin/newsletter/listinfo/newsticker"
+ >heise-newsletter</a>, the biggest news-website for
+ it-professionals in Germany.
+ <!-- Alden Gillespy -->
+ <li><a href="http://www.thetestpattern.com/">Test Pattern Radio</a>
+ <!-- Roberto Mogliotti -->
+ <li><a href="http://lists.atlink.it/">ATLink SRL</a>
+ <!-- Daniel Buchmann -->
+ <li><a href="http://www.bibsys.com/english.html">BIBSYS (Library
+ Automation System, Norway)</a>
+ <!-- Tim Lyons -->
+ <li><a href="http://www.digitalvoodoo.org">www.digitalvoodoo.org</a>
+ <!-- Michael Neil Felzien -->
+ <li><a href="http://www.pied.com/">Process Integrated Engineering
+ Design (PIED)</a>
+ <!-- mark roberts -->
+ <li>BBSRC (Bioscience and Biotechnical Scientific Research Council)
+ <!-- Joshua Erdman -->
+ <li><a href="http://www.ernestallen.com">Ernest & Allen</a>
+ <!-- Hank Roth -->
+ <li><a href="http://pnews.org/">pnews.org</a>
+ <!-- Rene Lange -->
+ <li><a href="http://www.tlug.de">Linux Users Group, Germany</a>
+ <!-- switzerland -->
+ <li><a href="http://lists.indymedia.org">indymedia</a>
+ <!-- Keith Patton -->
+ <li><a href="http://www.ethicalmedia.com">Ethical Media Ltd</a>
+ <!-- Leandro Rache Sanchez -->
+ <li><a href="http://www.hipertek.net">Hipertek Ltda</a>, Bogota,
+ Columbia</a>
+ <!-- Yann Forget -->
+ <li><a href="http://mail.ynternet.net/mailman/listinfo"
+ >ynternet.org</a>
+ <!-- Renn -->
+ <li><a href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+ >National Central University, Dept. of Civil Engineering, the 83th</a>
</ul>
diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html
index 60de4a47c..1f6ae1dd8 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 Jan 18 12:02:30 2002 -->
+<!-- Mon Jan 28 00:04:57 2002 -->
<!-- USING HT2HTML 1.2 -->
<!-- SEE http://barry.wooz.org/software/ht2html -->
<!-- User-specified headers:
@@ -189,9 +189,14 @@ like to be included in this list, please
<!-- Roger Pena -->
<li><a href="http://www.redhat.com/">RedHat, Inc.</a>
<li><a href="http://lists.samba.org/">Samba</a>
+ <!-- Chris Howells -->
+ <li><a href="http://mail.kde.org/mailman/listinfo">KDE Project</a>
+ <li><a href="http://www.pair.com/pair/pairlist/">Pair List</a>
<!-- Barry Warsaw -->
<li><a href="http://www.python.org/sigs/">Python.Org</a>
+ <li><a href="http://lists.zope.org/">Zope.org</a>
+ <li><a href="http://www.zope.com/">Zope.com</a> (<em>Yay!</em>)
<!-- Owen Taylor -->
<li><a href="http://mail.gnome.org/">GNOME.Org</a>
<!-- Nigel Metheringham -->
@@ -208,6 +213,9 @@ like to be included in this list, please
(private lists only, currently)
<!-- Bill Bradford -->
<li><a href="http://www.sunhelp.org/mailman/listinfo/">SunHelp.Org</a>
+ <li><a href="http://www.sunmanagers.org/mailman/listinfo">Sun Managers</a>
+ <li><a href="http://www.linuxmanagers.org/mailman/listinfo">Linux
+ Managers</a>
<!-- Bill Hoffman -->
<li><a href="http://public.kitware.com/">Visualization Tool Kit
(VTK)</a>
@@ -228,6 +236,23 @@ like to be included in this list, please
<!-- Jeff Berliner -->
<li><a href="http://endeavor.med.nyu.edu/mailman/listinfo">New York
University School of Medicine</a>
+ <!-- Marco Obaid -->
+ <li><a href="http://lists.MUW.Edu/">Mississippi University for Women</a>
+ <!-- Carel Braam -->
+ <li><a href="http://pegasus.tue.nl">Eindhoven University of Technology</a>
+ <!-- Prof. Marcelo Maia Sobral -->
+ <li>University of vale do Itajai, Sao Jose, Brasil
+ <!-- Conal Garrity -->
+ <li><a href="http://www.kvsc.org/">KVSC Radio, St. Cloud State
+ University, MN</a>
+ <!-- Babak Mostaghassi -->
+ <li><a href="http://ill.iut.ac.ir/">Linux Lab of Isfahan
+ University Of Technology</a>
+ <!-- Aly S.P Dharshi -->
+ <li>University of Lethbridge Organization of Residence Students
+ <!-- Courtney V. Bearse -->
+ <li><a href="http://linux.uky.edu/mailman/listinfo/">University of
+ Kentucky</a>
<!-- Chuq von Rospach's alter ego -->
<li><a href="http://www.hockeyfanz.com/">HockeyFanz.com</a>
@@ -311,14 +336,10 @@ like to be included in this list, please
<!-- Krzysztof Wychowalek -->
<li><a href="http://www.most.org.pl">MOST - Polish provider for
Environmental Movement</a>
- <!-- Marco Obaid -->
- <li><a href="http://lists.MUW.Edu/">Mississippi University for Women</a>
<!-- Ken Kyler -->
<li><a href="http://www.elists.org/">eLists.org</a>
<!-- kellan -->
<li><a href="http://lists.indymedia.org/">IndyMedia</a>
- <!-- Carel Braam -->
- <li><a href="http://pegasus.tue.nl">Eindhoven University of Technology</a>
<!-- Yasha Harari -->
<li><a href="http://mail.anywhereyougo.com/">mail.anywhereyougo.com</a>
<!-- Gary Coulbourne -->
@@ -405,8 +426,6 @@ like to be included in this list, please
Contestado-UnC Curitibanos/SC/Brasil</a>
<!-- Quique -->
<li><a href="http://sindominio.net">sindominio.net</a>
- <!-- Prof. Marcelo Maia Sobral -->
- <li>University of vale do Itajai, Sao Jose, Brasil
<!-- Damir Horvat -->
<li><a href="http://www.voljatel.si">VOLJATEL telekomunikacije d.d.</a>
<!-- Rod (Gentle) Ellis -->
@@ -423,6 +442,64 @@ like to be included in this list, please
<!-- Jim Reisert -->
<li><a href="http://lists.contesting.com/mailman/listinfo"
>Contesting.com</a>, Amateur ("Ham") Radio lists.
+ <!-- Stephen McKeown -->
+ <li><a href="http://www.jmbarrie.net">http://www.jmbarrie.net</a>
+ <!-- Dennis Du Bois -->
+ <li><a href="http://freelance-seattle.net/">Freelance-Seattle.net</a>
+ <!-- Charles Tucker -->
+ <li><a href="http://www.riverbend.com/">Riverbend Church</a>
+ <!-- Ben Dyer -->
+ <li><a href="http://lists.evolt.org/">Evolt.org</a>
+ <!-- munindo -->
+ <li><a href="http://mail2.factsoft.de/mailman/listinfo/national"
+ >http://mail2.factsoft.de/mailman/listinfo/national</a>
+ <!-- Ignacio Valdez -->
+ <li><a href="http://www.linuxmednews.com">Linux Medical News</a>
+ <!-- Dean Strik -->
+ <li><a href="http://lists.stack.nl/">stack.nl</a>
+ <!-- Jim Goltz -->
+ <li>NFR Security
+ <!-- Stephan Richter -->
+ <li><a href="http://iuveno-net.de/">iuveno-net.de</a>
+ <!-- Johnny Fuerst -->
+ <li><a href="http://mailman.cathat.net/">cathat.net</a>
+ <!-- gulli -->
+ <li><a href="http://www.heise.de/bin/newsletter/listinfo/newsticker"
+ >heise-newsletter</a>, the biggest news-website for
+ it-professionals in Germany.
+ <!-- Alden Gillespy -->
+ <li><a href="http://www.thetestpattern.com/">Test Pattern Radio</a>
+ <!-- Roberto Mogliotti -->
+ <li><a href="http://lists.atlink.it/">ATLink SRL</a>
+ <!-- Daniel Buchmann -->
+ <li><a href="http://www.bibsys.com/english.html">BIBSYS (Library
+ Automation System, Norway)</a>
+ <!-- Tim Lyons -->
+ <li><a href="http://www.digitalvoodoo.org">www.digitalvoodoo.org</a>
+ <!-- Michael Neil Felzien -->
+ <li><a href="http://www.pied.com/">Process Integrated Engineering
+ Design (PIED)</a>
+ <!-- mark roberts -->
+ <li>BBSRC (Bioscience and Biotechnical Scientific Research Council)
+ <!-- Joshua Erdman -->
+ <li><a href="http://www.ernestallen.com">Ernest & Allen</a>
+ <!-- Hank Roth -->
+ <li><a href="http://pnews.org/">pnews.org</a>
+ <!-- Rene Lange -->
+ <li><a href="http://www.tlug.de">Linux Users Group, Germany</a>
+ <!-- switzerland -->
+ <li><a href="http://lists.indymedia.org">indymedia</a>
+ <!-- Keith Patton -->
+ <li><a href="http://www.ethicalmedia.com">Ethical Media Ltd</a>
+ <!-- Leandro Rache Sanchez -->
+ <li><a href="http://www.hipertek.net">Hipertek Ltda</a>, Bogota,
+ Columbia</a>
+ <!-- Yann Forget -->
+ <li><a href="http://mail.ynternet.net/mailman/listinfo"
+ >ynternet.org</a>
+ <!-- Renn -->
+ <li><a href="http://csrfree.csrsr.ncu.edu.tw/mailman/listinfo/ncuce83/"
+ >National Central University, Dept. of Civil Engineering, the 83th</a>
</ul>
diff --git a/admin/www/todo.ht b/admin/www/todo.ht
index 60d4e0702..10bcd12ba 100644
--- a/admin/www/todo.ht
+++ b/admin/www/todo.ht
@@ -4,7 +4,7 @@ Title: 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 11-Jul-2001), so what's left will probably end up in a
+ writing 21-Jan-2002), 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
@@ -14,32 +14,30 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
</ul>
<h3> Documentation
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
- writing 11-Jul-2001), so what's left will probably end up in a
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -54,16 +52,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -85,16 +82,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -113,7 +109,6 @@ Title: The Mailman Wishlist
<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.
@@ -122,10 +117,6 @@ Title: The Mailman Wishlist
<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).
@@ -137,16 +128,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -165,7 +155,6 @@ Title: The Mailman Wishlist
<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.
@@ -174,10 +163,6 @@ Title: The Mailman Wishlist
<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).
@@ -202,16 +187,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -230,7 +214,6 @@ Title: The Mailman Wishlist
<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.
@@ -239,10 +222,6 @@ Title: The Mailman Wishlist
<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).
@@ -270,16 +249,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -298,7 +276,6 @@ Title: The Mailman Wishlist
<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.
@@ -307,10 +284,6 @@ Title: The Mailman Wishlist
<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).
@@ -337,8 +310,7 @@ Title: The Mailman Wishlist
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.
+ Also, limits on mailbacks, infos, etc.
</ul>
<h3> Mailcmd interface
@@ -346,16 +318,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -374,7 +345,6 @@ Title: The Mailman Wishlist
<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.
@@ -383,10 +353,6 @@ Title: The Mailman Wishlist
<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).
@@ -413,8 +379,7 @@ Title: The Mailman Wishlist
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -432,16 +397,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -460,7 +424,6 @@ Title: The Mailman Wishlist
<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.
@@ -469,10 +432,6 @@ Title: The Mailman Wishlist
<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).
@@ -499,8 +458,7 @@ Title: The Mailman Wishlist
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -534,16 +492,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -562,7 +519,6 @@ Title: The Mailman Wishlist
<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.
@@ -571,10 +527,6 @@ Title: The Mailman Wishlist
<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).
@@ -601,8 +553,7 @@ Title: The Mailman Wishlist
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -630,16 +581,9 @@ Title: The Mailman Wishlist
<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
</ul>
<h3> Pipermail + Archiving mechanism
@@ -647,16 +591,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -675,7 +618,6 @@ Title: The Mailman Wishlist
<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.
@@ -684,10 +626,6 @@ Title: The Mailman Wishlist
<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).
@@ -714,8 +652,7 @@ Title: The Mailman Wishlist
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -743,16 +680,9 @@ Title: The Mailman Wishlist
<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
@@ -769,16 +699,15 @@ Title: The Mailman Wishlist
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -797,7 +726,6 @@ Title: The Mailman Wishlist
<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.
@@ -806,10 +734,6 @@ Title: The Mailman Wishlist
<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).
@@ -836,8 +760,7 @@ Title: The Mailman Wishlist
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -865,16 +788,9 @@ Title: The Mailman Wishlist
<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
diff --git a/admin/www/todo.html b/admin/www/todo.html
index a4618933a..9890215f0 100644
--- a/admin/www/todo.html
+++ b/admin/www/todo.html
@@ -1,8 +1,8 @@
<HTML>
<!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. -->
-<!-- Fri Jul 20 13:03:56 2001 -->
-<!-- USING HT2HTML 1.1 -->
-<!-- SEE http://www.wooz.org/barry/software/pyware.html -->
+<!-- Mon Jan 28 00:04:57 2002 -->
+<!-- USING HT2HTML 1.2 -->
+<!-- SEE http://barry.wooz.org/software/ht2html -->
<!-- User-specified headers:
Title: The Mailman Wishlist
@@ -150,7 +150,7 @@ Email Us
</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 11-Jul-2001), so what's left will probably end up in a
+ writing 21-Jan-2002), 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
@@ -160,32 +160,30 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
</ul>
<h3> Documentation
</h3>
<ul>
<li> Here's the wish list for future versions of Mailman. Many new
features have been added to Mailman 2.1 (still in alpha as of this
- writing 11-Jul-2001), so what's left will probably end up in a
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -200,16 +198,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -231,16 +228,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -259,7 +255,6 @@ Email Us
<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.
@@ -268,10 +263,6 @@ Email Us
<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).
@@ -283,16 +274,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -311,7 +301,6 @@ Email Us
<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.
@@ -320,10 +309,6 @@ Email Us
<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).
@@ -348,16 +333,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -376,7 +360,6 @@ Email Us
<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.
@@ -385,10 +368,6 @@ Email Us
<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).
@@ -416,16 +395,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -444,7 +422,6 @@ Email Us
<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.
@@ -453,10 +430,6 @@ Email Us
<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).
@@ -483,8 +456,7 @@ Email Us
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.
+ Also, limits on mailbacks, infos, etc.
</ul>
<h3> Mailcmd interface
@@ -492,16 +464,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -520,7 +491,6 @@ Email Us
<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.
@@ -529,10 +499,6 @@ Email Us
<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).
@@ -559,8 +525,7 @@ Email Us
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -578,16 +543,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -606,7 +570,6 @@ Email Us
<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.
@@ -615,10 +578,6 @@ Email Us
<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).
@@ -645,8 +604,7 @@ Email Us
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -680,16 +638,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -708,7 +665,6 @@ Email Us
<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.
@@ -717,10 +673,6 @@ Email Us
<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).
@@ -747,8 +699,7 @@ Email Us
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -776,16 +727,9 @@ Email Us
<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
</ul>
<h3> Pipermail + Archiving mechanism
@@ -793,16 +737,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -821,7 +764,6 @@ Email Us
<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.
@@ -830,10 +772,6 @@ Email Us
<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).
@@ -860,8 +798,7 @@ Email Us
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -889,16 +826,9 @@ Email Us
<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
@@ -915,16 +845,15 @@ Email Us
<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
+ writing 21-Jan-2002), 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> allow customizable notices on moderated member helds and discards
<li> A detailed feature list
<li> A user's guide
<li> A site-admin's guide
@@ -943,7 +872,6 @@ Email Us
<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.
@@ -952,10 +880,6 @@ Email Us
<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).
@@ -982,8 +906,7 @@ Email Us
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.
+ Also, limits on mailbacks, infos, etc.
<li> Provide an email interface to all administrative commands
<li> Allow email unsubs from matching address to unsubscribe, possibly adding an "allow open unsubscribes" option to control
@@ -1011,16 +934,9 @@ Email Us
<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
generated by cgit v1.3 (git 2.53.0) at 2026-05-14 20:14:56 +0000