[Mailman-Announce] Mailman 2.1.19 release
Mark Sapiro
mark at msapiro.net
Sat Feb 7 22:40:42 CET 2015
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 <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
-------------- next part --------------
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
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.19rc3 (07-Feb-2015)
New Features
- The subscribe_auto_approval feature backported from the 2.2 branch and
described above has been enhanced to accept entries of the form
@listname to auto approve members of another list. (LP: #1417093)
- 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 to the
<HEAD> section of Mailman's internally generated web pages. This doesn't
apply to pages built from templates, but in those cases, custom templates
can be created. (LP: #1409396)
- There is a new DEFAULT_SUBSCRIBE_OR_INVITE setting. Set this to Yes
to make the default selection on the admin Mass Subscriptions page
Invite rather than Subscribe. (LP: #1404511)
- There is a new list attribute in the Bounce processing section.
bounce_notify_owner_on_bounce_increment if set to Yes will cause
Mailman to notify the list owner on every bounce that increments a
list member's score but doesn't result in a probe or disable. There
is a new configuration setting setting
DEFAULT_BOUNCE_NOTIFY_OWNER_ON_BOUNCE_INCREMENT to set the default
for new lists. This in turn defaults to No. (LP: #1382150)
Changed behavior
- Mailman's log files, request.pck files and heldmsg-* files are no
longer created world readable to protect against access by untrusted
local users. Note that permissions on existing log files won't be
changed so if you are concerned about this and don't rotate logs or
have a logrotate process that creates new log files instead of letting
Mailman create them, you will need to address that. (LP: #1327404)
Other changes
- The Python Powered logo image has been replaced in the misc/ directory
in the source distribution. Depending on how you've installed these
images, you may need to copy PythonPowered.png from the misc/ directory
in the source or from the $prefix/icons/ installed directory to another
location for your web server. (LP: #1408575)
i18n
- Mailman's character set for Romanian has been changed from iso-8859-2
to utf-8 and the templates and messages recoded. This change will
require running 'bin/arch --wipe' on any existing Romanian language
lists in order to recode the list's archives, and will require recoding
any edited templates in lists/LISTNAME/ro/*, templates/DOMAIN/ro/* and
templates/site/ro/*. It may also require recoding any existing
iso-8859-2 text in list attributes. (LP: #1418735)
- Mailman's character set for Russian has been changed from koi8-r to
utf-8 and the templates and messages recoded. This change will
require running 'bin/arch --wipe' on any existing Russian language
lists in order to recode the list's archives, and will require recoding
any edited templates in lists/LISTNAME/ru/*, templates/DOMAIN/ru/* and
templates/site/ru/*. It may also require recoding any existing koi8-r
text in list attributes. (LP: #1418448)
- Mailman's versions.py has been augmented to help with the above two
character set changes. The first time a list with preferred_language
of Romanian or Russian is accessed or upon upgrade to this release,
any list attributes which have string values such as description, info,
welcome_msg, etc. that appear to be in the old character set will be
converted to utf-8. This is done recursively for the values (but not
the keys) of dictionary attributes and the elements of list and tuple
attributes.
- The Russian message catalog has been updated by Danil Smirnov.
- The Romanian message catalog has been updated. (LP: #1415489)
- The Russian templates have been updated by Danil Smirnov. (LP: #1403462)
- The Japanese translation has been updated by SATOH Fumiyasu.
(LP: #1402989)
- A minor change in the French translation of a listinfo subscribe form
message has been made. (LP: #1331194)
Bug fixes and other patches
- Organization: headers are now unconditionally removed from posts to
anonymous lists. Regexps in ANONYMOUS_LIST_KEEP_HEADERS weren't kept
if the regexp included the trailing ':'. This is fixed too.
(LP: #1419132)
- The admindb interface has been fixed so the the detail message body
display doesn't lose part of a multi-byte character, and characters which
are invalid in the message's charset are replaced rather than the whole
body not being converted to the display charset. (LP: #1415406)
- Fixed a bug in bin/rmlist that would throw an exception or just fail to
remove held message files for a list with regexp special characters in
its name. (LP:#1414864)
- When applying DMARC mitigations, CookHeaders now adds the original From:
to Cc: rather than Reply-To: in some cases to make MUA 'reply' and
'reply all' more consistent with the non-DMARC cases. (LP: #1407098)
- The Subject: of the list welcome message wasn't always in the user's
preferred language. Fixed. (LP: #1400988)
- Accept email command in Subject: prefixed with Re: or similar with no
intervening space. (LP: #1400200)
- Fixed a UnicodeDecodeError that could occur in the web admin interface
if 'text' valued attributes have unicode values. (LP: #1397170)
- We now catch the NotAMemberError exception thrown if an authenticated
unsubscribe is submitted from the user options page for a nonmember.
(LP: #1390653)
- Fixed an archiving bug that would cause messages with 'Subject: Re:'
only to be indexed in the archives without a link to the message.
(LP: #1388614)
- The vette log entry for a message discarded by a handler now includes
the list name and the name of the handler. (LP: #558096)
- The options CGI now rejects all but HTTP GET and POST requests.
(LP: #1372199)
- A list's poster password will now be accepted on an Urgent: header.
(LP: #1371678)
- Fixed a bug which caused a setting of 2 for REMOVE_DKIM_HEADERS to be
ignored. (LP: #1363278)
- Renamed messages/sr/readme.sr to README.sr. (LP: #1360616)
- Moved the dmarc_moderation_action checks from the Moderate handler to
the SpamDetect handler so that the Reject and Discard actions will be
done before the message might be held by header_filter_rules, and the
Wrap Message and Munge From actions will be done on messages held by
header_filter_rules if the message is approved. (LP: #1334450)
- <label> tags have been added around most check boxes and radio buttons
and their text labels in the admin and admindb web GUI so they can be
(de)selected by clicking the text. (LP: #266391)
- If checking DNS for dmarc_moderation_action and DNS lookup is not
available, log it. (LP: #1324541)
- Handle missing From: header addresses for DMARC mitigation actions.
(LP: #1318025)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-announce/attachments/20150207/82d628bb/attachment.sig>
More information about the Mailman-announce
mailing list