headers
Mark Sapiro | 7 Jun 2008 23:46
Favicon

Mailman 2.1.11rc1 has been released


I am happy to announce the release of the first release candidate for
Mailman 2.1.11.

Mailman 2.1.11 is a cleanup of a few problems found since the release of
Mailman 2.1.10. It fixes the issue of shunted email subscribe requests
and a few minor issues. It updates the contrib/mmdsr script for some
2.1.10 and 2.1.11 log and error messages, and it adds a new cron to cull
and optionally archive old entries in the 'bad' and 'shunt' queues. See
the release notes at
<http://sourceforge.net/project/shownotes.php?group_id=103&release_id=605074>
for details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, including download links, please see:

http://www.list.org
http://mailman.sf.net
http://www.gnu.org/software/mailman

Note that since the 2.1.11rc1 tarball was prepared, a few issues
involving the Dutch, German, Korean, Russian, Spanish and traditional
Chinese translations have been corrected, so if you use any of these
languages, you probably will want to wait for the next candidate or
final release.

--
(Continue reading)

Permalink | Reply | 1 comment |
headers
Barry Warsaw | 17 Jun 2008 19:31

New FAQ


Hi everybody,

I wanted to let you know that Terri Oda has written a nice script to  
turn the old FAQ wizard into FAQ entries on the wiki.  She and others  
have spent some time gardening, tweaking and updating the wiki FAQ and  
it is now ready to take over as our definitive FAQ.  Thanks Terri and  
everyone else who contributed to this effort!

We'll keep the old FAQ wizard around so that existing links will  
continue to work.  I've added a footer indicating that it is obsolete  
and pointing people at the wiki FAQ.  I've also disabled write access  
to the FAQ wizard.

Here's the new FAQ:

http://wiki.list.org/display/DOC/Frequently+Asked+Questions

There's also a link to this on the front page of the wiki:

http://wiki.list.org

Enjoy,
-Barry
Permalink | Reply | 0 comments |
headers
Mark Sapiro | 23 Jun 2008 21:48
Favicon

Mailman 2.1.11rc1 has been released


I am happy to announce the release of the second release candidate for
Mailman 2.1.11.

Mailman 2.1.11 is a cleanup of a few problems found since the release of
Mailman 2.1.10. It fixes the issue of shunted email subscribe requests
and a few minor issues. It updates the contrib/mmdsr script for some
2.1.10 and 2.1.11 log and error messages, and it adds a new cron to cull
and optionally archive old entries in the 'bad' and 'shunt' queues. See
the release notes at
<http://sourceforge.net/project/shownotes.php?group_id=103&release_id=605074>
for details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, including download links, please see:

http://www.list.org
http://mailman.sf.net
http://www.gnu.org/software/mailman

At this point I anticipate releasing 2.1.11 final on June 30.  I am
currently waiting for some updates to the Brazilian Portuguese (pt-BR)
translation.  At this point, I expect that to be the only change from
2.1.11rc2 to 2.1.11 final.

--
Mark Sapiro <mark <at> msapiro.net>        The highway is for gamblers,
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mark Sapiro | 23 Jun 2008 21:58
Favicon

Re: Mailman 2.1.11rc2 has been released


Resending with the correct subject (2.1.11rc2, not 2.1.11rc1). Sorry for
any confusion.

Mark Sapiro wrote:
| I am happy to announce the release of the second release candidate for
| Mailman 2.1.11.
|
| Mailman 2.1.11 is a cleanup of a few problems found since the release of
| Mailman 2.1.10. It fixes the issue of shunted email subscribe requests
| and a few minor issues. It updates the contrib/mmdsr script for some
| 2.1.10 and 2.1.11 log and error messages, and it adds a new cron to cull
| and optionally archive old entries in the 'bad' and 'shunt' queues. See
| the release notes at
|
<http://sourceforge.net/project/shownotes.php?group_id=103&release_id=605074>

|
| for details.
|
| Mailman is free software for managing email mailing lists and
| e-newsletters. Mailman is used for all the python.org and
| SourceForge.net mailing lists, as well as at hundreds of other sites.
|
| For more information, including download links, please see:
|
| http://www.list.org
| http://mailman.sf.net
| http://www.gnu.org/software/mailman
|
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mark Sapiro | 30 Jun 2008 21:15
Favicon

Mailman 2.1.11 final has been released.


I am happy to announce the final release of the Mailman 2.1.11.

Mailman 2.1.11 is a cleanup of a few problems found since the release of
Mailman 2.1.10. It fixes the issue of shunted email subscribe requests
and a few minor issues. It updates the contrib/mmdsr script for some
2.1.10 and 2.1.11 log and error messages, and it adds a new cron to cull
and optionally archive old entries in the 'bad' and 'shunt' queues.

Mailman 2.1.11 has updates to several i18n translations.

A few bounce log messages now have the list name prepended.

There is a new Defaults.py|mm_cfg.py setting
ACCEPTABLE_LISTNAME_CHARACTERS with default value '[-+_.=a-z0-9]'.  This
Python regular expression character class specifies the characters
allowed in list names.  The motivation for this is the fact that
previously, a list named, e.g., xxx&yyy could be created and MTA aliases
generated that would cause the MTA to execute yyy as a command.  There
is a possible security issue  here, but it is not believed to be
exploitable in any meaningful way.

If anyone is concerned about the security issue and not ready to
upgrade, the mailman-2.1.11-listname-patch file contains a patch that
can be applied to Mailman 2.1.9 or 2.1.10 to add this feature.

See the release notes at
<http://sourceforge.net/project/shownotes.php?group_id=103&release_id=605074>
for more details.
(Continue reading)

Permalink | Reply | 7 comments |
headers
Mark Sapiro | 1 Jul 2008 20:04
Favicon

Re: Mailman 2.1.11 final has been released.


The release notes and NEWS file for Mailman 2.1.11 contains the
following innocuous looking item.

~    - Improved bounce loop detection and handling in BounceRunner.py.

This actually first appeared in 2.1.11rc2. It turns out this had an
unintended consequence, but I actually think it is a good thing.

The change involved bounces returned to the site list (mailman list)
-bounces address. There was always code in BounceRunner.py to look at
bounces returned to the site list -bounces address to try to detect if
the bounce was a bounce of a notice to a list owner, and if so, to send
the bounce to the site list instead of processing it. This code never
worked right.

The main problem, is I don't in general know how to tell to what address
the bounced message was originally sent. If I did, there would never be
an unrecognized bounce. So part of the change in 2.1.11 rc2 and final is
to just forward to the site list owner any message that arrives to the
site list -bounces address so the owner can handle the bounce.

The unintended consequence is that bounces of password reminders will
also now go to the site list owner whereas before they were probably
just ignored or processed as unrecognized bounces to the site list.

Most of these bounces will probably be for dead addresses where the user
disabled delivery and forgot about the list and the address died and the
password reminders have been bouncing for a long time.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Barry Warsaw | 1 Jul 2008 20:57

Re: [Mailman-Users] Mailman 2.1.11 final has been released.


On Jul 1, 2008, at 2:40 PM, Hank van Cleef wrote:

> I'm also concerned about this proposed scheme to discontinue montnly
> mailings.  It most definitely needs some mechanism whereby a user can
> reset or re-obtain their password without moderator intervention.  Our
> user base is just plain not password-savvy, and I'm concerned about
> the increase in moderator workload if the recovery method is similar
> to password resetting by root (the Unix method).

Don't worry, going forward we'll have a fairly typical password reset  
feature instead of the monthly reminder.  The other advantage of this  
is that we won't have to keep user passwords in our database  
unencrypted.

-Barry
Permalink | Reply | 0 comments |

Gmane