Mailman 2.1.15rc1 released
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I am happy to announce the first release candidate for Mailman 2.1.15.
Python 2.4 is the minimum supported, but Python 2.6 is recommended. This release should work with Python 2.7, but has not been tested with that version.
This release includes minor security enhancements, new features and bug fixes. See the Changelog at <https://launchpad.net/mailman/2.1/2.1.15rc1> for more 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, please see:
http://www.list.org http://www.gnu.org/software/mailman
Mailman 2.1.15rc1 can be downloaded from
https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/
It is anticipated that the 2.1.15 final release will be on or about June 13. Bugs found between now and then will be fixed if possible, but I hope that most if not all changes between now and June 13 will be i18n updates. Please send any updates to the templates and/or message catalogs in the 2.1.15rc1 release directly to me no later than June 11.
Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)
iD8DBQFPs0HiVVuXXpU7hpMRAhEfAKDHkpFORnL9a6ka3RRn4WP8m7EsHgCcCKFi C17WrK2wc2irrXn9Gp2ju8I= =5wvM -----END PGP SIGNATURE-----
On Tue, 15 May 2012, Mark Sapiro wrote:
This release includes minor security enhancements, new features and bug fixes. See the Changelog at <https://launchpad.net/mailman/2.1/2.1.15rc1> for more details.
Looking at the Changelog I see ........ 2.1.15rc1 (15-May-2012)
Security
- Strengthened the validation of email addresses.......
Having had many a web form tell me my keyword address was not valid, I thought I'd make sure the developers are aware of the address TMDA (http://tmda.net) can generate and use.
Please make sure the validation routines allow addresses like these. someuser+keyword+mailman.793c93@example.com someuser+sender+81c44a@example.com someuser+dated+1337369972.605ad6@example.com
Thanks.
-- Tim Rice Multitalents tim@multitalents.net
Tim Rice wrote:
Looking at the Changelog I see ........ 2.1.15rc1 (15-May-2012)
Security
- Strengthened the validation of email addresses. ......
Having had many a web form tell me my keyword address was not valid, I thought I'd make sure the developers are aware of the address TMDA (http://tmda.net) can generate and use.
Please make sure the validation routines allow addresses like these. someuser+keyword+mailman.793c93@example.com someuser+sender+81c44a@example.com someuser+dated+1337369972.605ad6@example.com
The above addresses will not be a problem. The only problem would be local parts containing characters other than dot (.) that RFC 5322 defines as 'specials' which, strictly speaking, may appear in quoted local parts, but which are not accepted by Mailman.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
There was an issue in the tarballs I released for Mailman 2.1.15rc1.
They didn't include the updated version information so they installed as version 2.1.14. This should not cause problems other than the version displaying incorrectly. If the tarball was installed as an upgrade over a 2.1.14 installation, the update script would not run to update list attributes, but the lists would be updated when they are later instantiated so this shouldn't be a problem.
The release tarballs at
https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/
have all been replaced with the correct one. There is still an issue with the bzr branch on Launchpad in that the 2.1.15rc1 tag is on revision 1354 instead of 1355, but that will be fixed soon.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Tim Rice