[Mailman-Developers] Mailman 2.1.19 release
I am very pleased to announce the release Mailman 2.1.19 final. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. There are also bug fixes. See the attached README for more details. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. This is the final release of Mailman 2.1.19, but if I receive additional i18n updates, I will release those later. There have been a few changes since the first candidate release, some of which were in the second and third candidates. - There have been updates to the Romanian, Russian, Polish, Japanese and Interlingua translations. - Mailman's character set for both Romanian and Russian has been changed to utf-8 and Mailman's version updater has been augmented to try to find strings in the old character set in list configurations and convert them. - The admindb held message display has been improved to not break multi-byte characters and not abandon conversion to the list's character set on an invalid character. - There was a new subscribe_auto_approval feature in the first release candidate and this is augmented to accept the @listname syntax. - Organization: headers are now removed from posts to anonymous lists. - The display of real names on the list roster added in the first release candidate has been made conditional on a new ROSTER_DISPLAY_REALNAME mm_cfg.py switch that defaults to No due to privacy concerns. Information on these and other changes in this release are in the attached README and in the NEWS file in the release tarball. 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 http://mailman.sourceforge.net/ Mailman 2.1.19 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan 2.2 Branch Backports (released in conjunction with 2.1.19) The following New Features and Bug Fixes have been in an unofficial, never to be released Mailman 2.2 branch for several years. Until now, they were never implemented on the official 2.1 branch because of their i18n impacts. Given that there have been a number of i18n impacting changes due to DMARC mitigations in the last few releases, it has been decided to backport these as well. All of these changes have been running in production on several lists for years without problems other than untranslated strings, so they should be reasonably bug free. New Features - There is a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. (LP: #266609) - Confirmed member change of address is logged in the 'subscribe' log, and if admin_notify_mchanges is true, a notice is sent to the list owner using a new adminaddrchgack.txt template. - Added an 'automate' option to bin/newlist to send the notice to the admin without the prompt. - The processing of Topics regular expressions has changed. Previously the Topics regexp was compiled in verbose mode but not documented as such which caused some confusion. Also, the documentation indicated that topic keywords could be entered one per line, but these entries were not handled properly. Topics regexps are now compiled in non-verbose mode and multi-line entries are 'ored'. Existing Topics regexps will be converted when the list is updated so they will continue to work. - Added real name display to the web roster. (LP: #266754) Bug fixes and other patches - Changed the response to an invalid confirmation to be more generic. Not all confirmations are subscription requests. - Changed the default nonmember_rejection_notice to be more user friendly. (LP: #418728) - Added If you are a list member qualification to some messages from the options login page. (LP: #266442) - Changed the 'Approve' wording in the admindbdetails.html template to 'Accept/Approve' for better agreement with the button labels. - Added '(by thread)' to the previous and next message links in the
Re: [Mailman-Developers] Mailman 2.1.19 release
Yesterday I released Mailman 2.1.19rc2 as noted below. Today I have released Mailman 2.1.19rc3 which can be downloaded from the same places as noted below for 2.1.19rc2. The reason for the quick replacement is I have augmented Mailman's versions.py to fix the encoding for strings in list attributes for existing Romanian and Russian language lists which should ease the pain of the utf-8 transition for these lists. See the attached README and yesterday's announcement copied below for more details. On 02/06/2015 09:05 PM, Mark Sapiro wrote: I am pleased to announce the second release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features since 2.1.18-1, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. There are also bug fixes. See the attached README for more details. The differences between this and the first 2.1.19 candidate are the following. The subscribe_auto_approval feature in the first candidate has been augmented to accept @listname to auto approve members of another list. (LP: #1417093) Organization: headers are unconditionally removed from posts to anonymous lists and a bug involving ANONYMOUS_LIST_KEEP_HEADERS has been fixed. (LP: #1419132) The admindb interface display of a held message body has been fixed to not stop in the middle of a multi-byte character and not fail to convert to the display character set message bodies with invalid characters. (LP: #1415406) Additionally, and the main reason for this second candidate, Mailman's character set for both Romanian and Russian has been changed to utf-8. (LP: #1418735) and (LP: #1418448). This may be disruptive in that following this change, some archive pages and some list attributes for lists whose preferred_language is one of those two languages may not display correctly. Archives can be fixed by running 'bin/arch --wipe' for the affected lists, but list attributes will probably have to be fixed manually. I hope the benefits of this change will outweigh the pain, and I encourage anyone with Romanian or Russian Language lists to try this release and report your experience. It may be possible to fix at least some list attributes programmatically as part of the version update process. I plan to release the final 2.1.19 release at the end of February, and it would be good to have as many i18n updates as possible by then. 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 http://mailman.sourceforge.net/ Mailman 2.1.19rc2 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan 2.2 Branch Backports (released in conjunction with 2.1.19) The following New Features and Bug Fixes have been in an unofficial, never to be released Mailman 2.2 branch for several years. Until now, they were never implemented on the official 2.1 branch because of their i18n impacts. Given that there have been a number of i18n impacting changes due to DMARC mitigations in the last few releases, it has been decided to backport these as well. All of these changes have been running in production on several lists for years without problems other than untranslated strings, so they should be reasonably bug free. New Features - There is a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. (LP: #266609) - Confirmed member change of address is logged in the 'subscribe' log, and if admin_notify_mchanges is true, a notice is sent to the list owner using a new adminaddrchgack.txt template. - Added an 'automate' option to bin/newlist to send the notice to the admin without the prompt. - The processing of Topics regular expressions has changed. Previously the Topics regexp was compiled in verbose mode but not documented as such which caused some confusion. Also, the documentation indicated that topic keywords could be
[Mailman-Developers] Mailman 2.1.19 release
I am pleased to announce the second release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features since 2.1.18-1, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. There are also bug fixes. See the attached README for more details. The differences between this and the first 2.1.19 candidate are the following. The subscribe_auto_approval feature in the first candidate has been augmented to accept @listname to auto approve members of another list. (LP: #1417093) Organization: headers are unconditionally removed from posts to anonymous lists and a bug involving ANONYMOUS_LIST_KEEP_HEADERS has been fixed. (LP: #1419132) The admindb interface display of a held message body has been fixed to not stop in the middle of a multi-byte character and not fail to convert to the display character set message bodies with invalid characters. (LP: #1415406) Additionally, and the main reason for this second candidate, Mailman's character set for both Romanian and Russian has been changed to utf-8. (LP: #1418735) and (LP: #1418448). This may be disruptive in that following this change, some archive pages and some list attributes for lists whose preferred_language is one of those two languages may not display correctly. Archives can be fixed by running 'bin/arch --wipe' for the affected lists, but list attributes will probably have to be fixed manually. I hope the benefits of this change will outweigh the pain, and I encourage anyone with Romanian or Russian Language lists to try this release and report your experience. It may be possible to fix at least some list attributes programmatically as part of the version update process. I plan to release the final 2.1.19 release at the end of February, and it would be good to have as many i18n updates as possible by then. 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 http://mailman.sourceforge.net/ Mailman 2.1.19rc2 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan 2.2 Branch Backports (released in conjunction with 2.1.19) The following New Features and Bug Fixes have been in an unofficial, never to be released Mailman 2.2 branch for several years. Until now, they were never implemented on the official 2.1 branch because of their i18n impacts. Given that there have been a number of i18n impacting changes due to DMARC mitigations in the last few releases, it has been decided to backport these as well. All of these changes have been running in production on several lists for years without problems other than untranslated strings, so they should be reasonably bug free. New Features - There is a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. (LP: #266609) - Confirmed member change of address is logged in the 'subscribe' log, and if admin_notify_mchanges is true, a notice is sent to the list owner using a new adminaddrchgack.txt template. - Added an 'automate' option to bin/newlist to send the notice to the admin without the prompt. - The processing of Topics regular expressions has changed. Previously the Topics regexp was compiled in verbose mode but not documented as such which caused some confusion. Also, the documentation indicated that topic keywords could be entered one per line, but these entries were not handled properly. Topics regexps are now compiled in non-verbose mode and multi-line entries are 'ored'. Existing Topics regexps will be converted when the list is updated so they will continue to work. - Added real name display to the web roster. (LP: #266754) Bug fixes and other patches - Changed the response to an invalid confirmation to be more generic. Not all confirmations are subscription requests. - Changed the default nonmember_rejection_notice to be more user friendly. (LP: #418728) - Added If you
[Mailman-Developers] Mailman 2.1.19 release
I am pleased to announce the first release candidate for Mailman 2.1.19. Python 2.4 is the minimum supported, but Python 2.7 is recommended. This release has several new features, some newly implemented and some backported from the now truly defunct 2.2 branch - there is nothing left in that branch that isn't in this release. There are also bug fixes. See the attached README for more details. Associated with those changes are many things that have i18n impacts including new and modified strings in the message catalog, a new adminaddrchgack.txt template and a minor change to the admindbdetails.html template. I strongly encourage anyone with an interest in translations of Mailman to get this release and help with updating the translations. I plan to release the final 2.1.19 release at the end of February, and it would be good to have as many i18n updates as possible by then. 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 http://mailman.sourceforge.net/ Mailman 2.1.19rc1 can be downloaded from https://launchpad.net/mailman/2.1/ http://ftp.gnu.org/gnu/mailman/ https://sourceforge.net/projects/mailman/ -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan 2.2 Branch Backports (released in conjunction with 2.1.19rc1) The following New Features and Bug Fixes have been in an unofficial, never to be released Mailman 2.2 branch for several years. Until now, they were never implemented on the official 2.1 branch because of their i18n impacts. Given that there have been a number of i18n impacting changes due to DMARC mitigations in the last few releases, it has been decided to backport these as well. All of these changes have been running in production on several lists for years without problems other than untranslated strings, so they should be reasonably bug free. New Features - There is a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. (LP: #266609) - Confirmed member change of address is logged in the 'subscribe' log, and if admin_notify_mchanges is true, a notice is sent to the list owner using a new adminaddrchgack.txt template. - Added an 'automate' option to bin/newlist to send the notice to the admin without the prompt. - The processing of Topics regular expressions has changed. Previously the Topics regexp was compiled in verbose mode but not documented as such which caused some confusion. Also, the documentation indicated that topic keywords could be entered one per line, but these entries were not handled properly. Topics regexps are now compiled in non-verbose mode and multi-line entries are 'ored'. Existing Topics regexps will be converted when the list is updated so they will continue to work. - Added real name display to the web roster. (LP: #266754) Bug fixes and other patches - Changed the response to an invalid confirmation to be more generic. Not all confirmations are subscription requests. - Changed the default nonmember_rejection_notice to be more user friendly. (LP: #418728) - Added If you are a list member qualification to some messages from the options login page. (LP: #266442) - Changed the 'Approve' wording in the admindbdetails.html template to 'Accept/Approve' for better agreement with the button labels. - Added '(by thread)' to the previous and next message links in the archive to emphasize that even if you got to the message from a subject, date or author index, previous and next are still by thread. 2.1.19rc1 (29-Jan-2015) New Features - There is a new list attribute dmarc_wrapped_message_text and a DEFAULT_DMARC_WRAPPED_MESSAGE_TEXT setting to set the default for new lists. This text is added to a message which is wrapped because of dmarc_moderation_action in a separate text/plain part that precedes the message/rfc822 part containing the original message. It can be used to provide an explanation of why the message was wrapped or similar info. - There is a new list attribute equivalent_domains and a DEFAULT_EQUIVALENT_DOMAINS setting to set the default for new lists which in turn defaults to the empty string. This provides a way to specify one or more groups of domains, e.g., mac.com, me.com, icloud.com, which are considered equivalent for validating list membership for posting and moderation purposes. - There is a new WEB_HEAD_ADD setting to specify text to be added