diff options
| -rw-r--r-- | admin/www/download.ht | 2 | ||||
| -rw-r--r-- | admin/www/download.html | 4 | ||||
| -rw-r--r-- | admin/www/i18n.ht | 25 | ||||
| -rw-r--r-- | admin/www/i18n.html | 27 | ||||
| -rw-r--r-- | admin/www/todo.ht | 111 | ||||
| -rw-r--r-- | admin/www/todo.html | 113 |
6 files changed, 253 insertions, 29 deletions
diff --git a/admin/www/download.ht b/admin/www/download.ht index c78f943b6..78266a9cd 100644 --- a/admin/www/download.ht +++ b/admin/www/download.ht @@ -67,7 +67,7 @@ released on <!-DATE--->05-May-2002<!-DATE--->) is a beta release of the next version. While the betas seem to be working quite well, it is still recommended that you use the current -stable version 2.0.11 in your production environments. Mailman is +stable version 2.0.12 in your production environments. Mailman is available from the following sources: <ul> diff --git a/admin/www/download.html b/admin/www/download.html index 7b4119b9e..72e05b6b4 100644 --- a/admin/www/download.html +++ b/admin/www/download.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Mon May 20 13:44:44 2002 --> +<!-- Tue Jul 2 19:12:37 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -251,7 +251,7 @@ released on <!-DATE--->05-May-2002<!-DATE--->) is a beta release of the next version. While the betas seem to be working quite well, it is still recommended that you use the current -stable version 2.0.11 in your production environments. Mailman is +stable version 2.0.12 in your production environments. Mailman is available from the following sources: <ul> diff --git a/admin/www/i18n.ht b/admin/www/i18n.ht index 91883c77f..0e680768b 100644 --- a/admin/www/i18n.ht +++ b/admin/www/i18n.ht @@ -5,24 +5,25 @@ Links: links.h doco-links.h Mailman 2.1 is fully internationalized. This means you can add translations of all the email and web templates so that your users can -interact with your mailing lists in their native language. Language -choices are handled as follows: +interact with your mailing lists in their native language. +Internationalization is handled as follows: <ul> <li>Each Mailman installation has a server default language. Mailman ships with US English as the server default. - <li>The site administrator can install new language packs as - donated by volunteer translators. If you'd like to volunteer to - help with translations, or would like to download language packs - for installation at your site, please contact the - <a href="mailto:mailman-i18n@python.org">mailman-i18n@python.org</a> - mailing list. + <li>Mailman comes with many supported languages, and if your + language is on that list, it will just work. + + <li>Once Mailman 2.1 is officially released, we plan to make + available <em>language packs</em> which include updated language + support, or new languages. - <li>Once a language pack has been installed, the site - administrator can make those additional languages available to - individual lists, and can change the server default language to - one of these languages. + <li>If you'd like to volunteer to help with translations, or have + questions about the support for your language of choice, + please contact the <a + href="mailto:mailman-i18n@python.org">mailman-i18n@python.org</a> + mailing list. <li>Individual list owners can choose which languages they'd like their mailing list to support from the suite of site-enabled diff --git a/admin/www/i18n.html b/admin/www/i18n.html index fba5c0718..24e4f21f7 100644 --- a/admin/www/i18n.html +++ b/admin/www/i18n.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Mon May 20 13:44:44 2002 --> +<!-- Tue Jul 2 19:12:37 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -184,24 +184,25 @@ Email Us Mailman 2.1 is fully internationalized. This means you can add translations of all the email and web templates so that your users can -interact with your mailing lists in their native language. Language -choices are handled as follows: +interact with your mailing lists in their native language. +Internationalization is handled as follows: <ul> <li>Each Mailman installation has a server default language. Mailman ships with US English as the server default. - <li>The site administrator can install new language packs as - donated by volunteer translators. If you'd like to volunteer to - help with translations, or would like to download language packs - for installation at your site, please contact the - <a href="mailto:mailman-i18n@python.org">mailman-i18n@python.org</a> - mailing list. + <li>Mailman comes with many supported languages, and if your + language is on that list, it will just work. + + <li>Once Mailman 2.1 is officially released, we plan to make + available <em>language packs</em> which include updated language + support, or new languages. - <li>Once a language pack has been installed, the site - administrator can make those additional languages available to - individual lists, and can change the server default language to - one of these languages. + <li>If you'd like to volunteer to help with translations, or have + questions about the support for your language of choice, + please contact the <a + href="mailto:mailman-i18n@python.org">mailman-i18n@python.org</a> + mailing list. <li>Individual list owners can choose which languages they'd like their mailing list to support from the suite of site-enabled diff --git a/admin/www/todo.ht b/admin/www/todo.ht index b8b495623..9a1dabb06 100644 --- a/admin/www/todo.ht +++ b/admin/www/todo.ht @@ -19,6 +19,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + </ul> <h3> Documentation </h3> @@ -31,6 +38,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -51,6 +65,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -78,6 +99,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -105,6 +133,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + </ul> <h3> List Membership </h3> @@ -117,6 +148,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -144,6 +182,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -170,6 +211,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -197,6 +245,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -229,6 +280,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -256,6 +314,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -294,6 +355,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -321,6 +389,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -369,6 +440,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -396,6 +474,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -455,6 +536,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -482,6 +570,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever address they want to whichever list, with different options per subscription. @@ -544,6 +635,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -571,6 +669,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -640,6 +741,13 @@ Title: The Mailman Wishlist <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -667,6 +775,9 @@ Title: The Mailman Wishlist <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. diff --git a/admin/www/todo.html b/admin/www/todo.html index 94de89cdc..1d5b526c5 100644 --- a/admin/www/todo.html +++ b/admin/www/todo.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Sun May 5 00:30:17 2002 --> +<!-- Tue Jul 2 19:12:37 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -177,6 +177,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + </ul> <h3> Documentation </h3> @@ -189,6 +196,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -209,6 +223,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -236,6 +257,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -263,6 +291,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + </ul> <h3> List Membership </h3> @@ -275,6 +306,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -302,6 +340,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -328,6 +369,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -355,6 +403,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -387,6 +438,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -414,6 +472,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -452,6 +513,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -479,6 +547,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -527,6 +598,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -554,6 +632,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -613,6 +694,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -640,6 +728,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -702,6 +793,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -729,6 +827,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. @@ -798,6 +899,13 @@ Email Us <li> Re-implement the bulk mailer to do DNS lookups and remote MTA delivery directly (optional). + <li> For low-traffic sites, a queued message could trigger a qrunner process. It would work until all mail was delivered, then sleep + and exit if no new work arrived. + + <li> We could get rid of the wrappers by doing a file delivery at the aliases, then having qrunner use UnixMailbox to deliver each + message. There would have to be some locking between the MTA + and Mailman. + <li> A detailed feature list <li> A user's guide <li> A site-admin's guide @@ -825,6 +933,9 @@ Email Us <li> Better integration with moderated newsgroups (and allow some addresses to bypass even that moderation and be delivered to a secondary channel, like moderators@isc.org). + <li> Allow a list to be marked `disabled' so things like the replybot still works, and the archives are still available, but mail + posted to the list is always returned unsent. + <li> 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. |