diff options
| author | bwarsaw | 2002-09-28 16:49:44 +0000 |
|---|---|---|
| committer | bwarsaw | 2002-09-28 16:49:44 +0000 |
| commit | a03d9917c5e801af6933345a9cbb807b0a4e4b8e (patch) | |
| tree | ced3b31774e186ac8f7056808857acc58e7d1982 /admin | |
| parent | 67799b36a59d16dc44b8757d49ac25da04d073f4 (diff) | |
| download | mailman-a03d9917c5e801af6933345a9cbb807b0a4e4b8e.tar.gz mailman-a03d9917c5e801af6933345a9cbb807b0a4e4b8e.tar.zst mailman-a03d9917c5e801af6933345a9cbb807b0a4e4b8e.zip | |
The usual assortment of updates
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/www/i18n.ht | 8 | ||||
| -rw-r--r-- | admin/www/i18n.html | 10 | ||||
| -rw-r--r-- | admin/www/index.ht | 9 | ||||
| -rw-r--r-- | admin/www/index.html | 11 | ||||
| -rw-r--r-- | admin/www/inthenews.ht | 2 | ||||
| -rw-r--r-- | admin/www/inthenews.html | 4 | ||||
| -rw-r--r-- | admin/www/todo.ht | 129 | ||||
| -rw-r--r-- | admin/www/todo.html | 131 |
8 files changed, 220 insertions, 84 deletions
diff --git a/admin/www/i18n.ht b/admin/www/i18n.ht index 9bb9cfe90..c18379020 100644 --- a/admin/www/i18n.ht +++ b/admin/www/i18n.ht @@ -149,8 +149,14 @@ internationalized versions of Mailman. Mailman list</a> for discussion of the Russian translation. <p><dt><b>Spanish</b></dt> - <dd><a href="jcrey@uma.es">Juan Carlos Rey Anaya</a> heads + <dd><a href="mailto:jcrey@uma.es">Juan Carlos Rey Anaya</a> heads up the Spanish translations. + <p><dt><b>Swedish</b></dt> + <dd><a href="mailto:information@arvika.se">Eva Österlind</a> + heads up the Swedish translation effort, with help from our + Norwegian champion + <a href="mailto:Daniel.Buchmann@bibsys.no">Daniel Buchmann</a>. + </dl> diff --git a/admin/www/i18n.html b/admin/www/i18n.html index fcdd66db4..8f30cd27e 100644 --- a/admin/www/i18n.html +++ b/admin/www/i18n.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Wed Aug 7 08:34:26 2002 --> +<!-- Sat Sep 28 12:49:12 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -328,9 +328,15 @@ internationalized versions of Mailman. Mailman list</a> for discussion of the Russian translation. <p><dt><b>Spanish</b></dt> - <dd><a href="jcrey@uma.es">Juan Carlos Rey Anaya</a> heads + <dd><a href="mailto:jcrey@uma.es">Juan Carlos Rey Anaya</a> heads up the Spanish translations. + <p><dt><b>Swedish</b></dt> + <dd><a href="mailto:information@arvika.se">Eva Österlind</a> + heads up the Swedish translation effort, with help from our + Norwegian champion + <a href="mailto:Daniel.Buchmann@bibsys.no">Daniel Buchmann</a>. + </dl> diff --git a/admin/www/index.ht b/admin/www/index.ht index e1500c6a3..0e2811ace 100644 --- a/admin/www/index.ht +++ b/admin/www/index.ht @@ -42,9 +42,12 @@ StudlyCaps). released on <!-DATE--->10-Aug-2002<!-DATE--->) is the current development release of the next version of Mailman. -Although, stable, it -should <strong>not</strong> be -used in production environments. Instead, please use +This version is stable and is being used in some production +environments, but it may still have some lurking bugs. If you decide +to use it, it's best to follow the developer's mailing list and cvs +updates for important fixes. + +<p>You may choose instead to use <a href="http://sourceforge.net/project/showfiles.php?group_id=103" >the latest stable release</a>. diff --git a/admin/www/index.html b/admin/www/index.html index 04be01944..650f8ca1e 100644 --- a/admin/www/index.html +++ b/admin/www/index.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Sat Aug 10 00:09:12 2002 --> +<!-- Sat Sep 28 12:49:13 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -233,9 +233,12 @@ StudlyCaps). released on <!-DATE--->10-Aug-2002<!-DATE--->) is the current development release of the next version of Mailman. -Although, stable, it -should <strong>not</strong> be -used in production environments. Instead, please use +This version is stable and is being used in some production +environments, but it may still have some lurking bugs. If you decide +to use it, it's best to follow the developer's mailing list and cvs +updates for important fixes. + +<p>You may choose instead to use <a href="http://sourceforge.net/project/showfiles.php?group_id=103" >the latest stable release</a>. diff --git a/admin/www/inthenews.ht b/admin/www/inthenews.ht index 41cd75057..a39266d3c 100644 --- a/admin/www/inthenews.ht +++ b/admin/www/inthenews.ht @@ -455,5 +455,7 @@ Mailman or Mailman technology to run their mailing lists. Mailing Lists</a> <!-- Dirk H. Shulz --> <li><a href="http://www.multibyte.de">MultiByte GmbH</a> + <!-- Justin Yunke --> + <li><a href="http://www.elists.org/">Elists Online</a> </ul> diff --git a/admin/www/inthenews.html b/admin/www/inthenews.html index 2035acf0c..524a1e412 100644 --- a/admin/www/inthenews.html +++ b/admin/www/inthenews.html @@ -1,7 +1,7 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Sat Aug 10 00:09:13 2002 --> +<!-- Sat Sep 28 12:49:13 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -613,6 +613,8 @@ Mailman or Mailman technology to run their mailing lists. Mailing Lists</a> <!-- Dirk H. Shulz --> <li><a href="http://www.multibyte.de">MultiByte GmbH</a> + <!-- Justin Yunke --> + <li><a href="http://www.elists.org/">Elists Online</a> </ul> diff --git a/admin/www/todo.ht b/admin/www/todo.ht index b5e91fdf9..b180f6c4c 100644 --- a/admin/www/todo.ht +++ b/admin/www/todo.ht @@ -22,9 +22,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. </ul> <h3> Documentation @@ -41,9 +39,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -68,9 +64,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -102,9 +96,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -125,6 +117,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -146,6 +139,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + </ul> <h3> List Membership </h3> @@ -161,9 +162,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -184,6 +183,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -205,6 +205,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -234,9 +242,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -257,6 +263,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -278,6 +285,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -313,9 +328,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -336,6 +349,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -357,6 +371,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have one account per user per site, with multiple email addresses and fallbacks. Allow them to subscribe whichever address they want to whichever list, with different options per subscription. @@ -398,9 +420,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -421,6 +441,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -442,6 +463,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -493,9 +522,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -516,6 +543,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -537,6 +565,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -599,9 +635,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -622,6 +656,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -643,6 +678,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -708,9 +751,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -731,6 +772,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -752,6 +794,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -824,9 +874,7 @@ Title: The Mailman Wishlist <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -847,6 +895,7 @@ Title: The Mailman Wishlist message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -868,6 +917,14 @@ Title: The Mailman Wishlist to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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 e6b4728a5..65f4a659d 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. --> -<!-- Fri Aug 2 11:48:08 2002 --> +<!-- Sat Sep 28 12:49:13 2002 --> <!-- USING HT2HTML 2.0 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -180,9 +180,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. </ul> <h3> Documentation @@ -199,9 +197,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -226,9 +222,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -260,9 +254,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -283,6 +275,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -304,6 +297,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + </ul> <h3> List Membership </h3> @@ -319,9 +320,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -342,6 +341,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -363,6 +363,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -392,9 +400,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -415,6 +421,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -436,6 +443,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -471,9 +486,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -494,6 +507,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -515,6 +529,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -556,9 +578,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -579,6 +599,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -600,6 +621,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -651,9 +680,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -674,6 +701,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -695,6 +723,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -757,9 +793,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -780,6 +814,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -801,6 +836,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -866,9 +909,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -889,6 +930,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -910,6 +952,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. @@ -982,9 +1032,7 @@ Email Us <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> Strip any addresses of members who have nodupe turned on, from the Cc headers of the list copy of a message. <li> A detailed feature list <li> A user's guide @@ -1005,6 +1053,7 @@ Email Us message was edited by the moderator). <li> Allow the admin to disable option settings by users + <li> Allow admins to block nomail settings <li> Allow admins to control and set individual headers, adding, removing, or overriding those in the original message (sometimes very useful, but could be dangerous!) @@ -1026,6 +1075,14 @@ Email Us to see all these super-quarantined messages with the flip of a button. + <li> Add a moderation option to pass through any message which is a reply to a message previously distributed through the list, even + if it comes from a non-member. Treat that non-member as a + member for the duration of the thread. Use In-Reply-To, + References and Message-ID to match these up. + + <li> When a held message is forwarded (for admin editing and approved resend) there should be a way to auto-discard the held message + when the approved resend is received. + <li> Have 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. |