From mark at msapiro.net  Fri Jun  2 21:59:53 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 2 Jun 2017 18:59:53 -0700
Subject: [Mailman-i18n] Mailman 2.1.24 released
Message-ID: <edb090c6-caf4-85dd-da85-7caa2160cbe5@msapiro.net>

I am pleased to announce the release of Mailman 2.1.24.

Python 2.4 is the minimum supported, but Python 2.7 is strongly recommended.

This release has a few new features, a few i18n updates and several bug
fixes. See the attached README.txt 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, please see our web site at one of:

http://www.list.org
http://www.gnu.org/software/mailman
http://mailman.sourceforge.net/
http://mirror.list.org/

Mailman 2.1.24 can be downloaded from

https://launchpad.net/mailman/2.1/
http://ftp.gnu.org/gnu/mailman/    (not yet updated as of this writing)
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.1.24 (02-Jun-2017)

  Security

    - A most likely unexploitable XSS attach that relies on the Mailman web
      server passing a crafted Host: header to the CGI environment has been
      fixed.  Apache for one is not vulnerable.  Thanks to Alqnas Eslam.

  New Features

    - There is a new RCPT_BASE64_HEADER_NAME setting.  If this is set to a
      non-empty string, that string is the name of a header that will be added
      to personalized and VERPed deliveries with value equal to the base64
      encoding of the recipient's email address.  This is intended to enable
      identification of the recipient otherwise redacted from "spam report"
      feedback loop messages.

    - cron/senddigests has a new -e/--exceptlist option to send pending
      digests for all but a named list.  (LP: #1619770)

    - The values for DEFAULT_DIGEST_FOOTER and DEFAULT_MSG_FOOTER have been
      changed to use a standard signature separator for DEFAULT_MSG_FOOTER
      and to remove the unneded line of underscores from DEFAULT_DIGEST_FOOTER.
      (LP: #266269)

  i18n

    - The Polish html templates have been recoded to use html entities
      instead of non-ascii characters.

    - The Basque (Euskara) translation has been updated by Gari Araolaza.

    - The German "details for personalize" page has been updated by
      Christian F Buser.

    - The Japanese translation has been updated by Yasuhito FUTATSUKI.

  Bug fixes and other patches

    - The list-owner at virtual.domain addresses are now added to virtual-mailman
      as they are exposed in 'list created' emails.  (LP: 1694384)

    - The 'list run by' addresses in web page footers are now just the
      list-owner address.  (LP: #1694384)

    - Changed member_verbosity_threshold from a >= test to a strictly > test
      to avoid the issue of moderating every post when the threshold = 1.
      (LP: #1693366)

    - Subject prefixing has been improved to always have a space between
      the prefix and the subject even with non-ascii in the prefix.  This
      will sometimes result in two spaces when the prefix is non-ascii but
      the subject is ascii, but this is the lesser evil.  (LP: #1525954)

    - Treat message and digest headers and footers as empty if they contain
      only whitespace.  (LP: #1673307)

    - Ensured that added message and digest headers and footers always have
      a terminating new-line.  (LP: #1670033)

    - Fixed an uncaught TypeError in the subscribe CGI.  (LP: #1667215)

    - Added recognition for a newly seen mailEnable bounce.

    - Fixed an uncaught NotAMemberError when a member is removed before a
      probe bounce for the member is returned.  (LP: #1664729)

    - Fixed a TypeError thrown in the roster CGI when called with a listname
      containing a % character.  (LP: #1661810)

    - Fixed a NameError issue in bin/add_members with
      DISABLE_COMMAND_LOCALE_CSET = yes.  (LP: #1647450)

    - The CleanseDKIM handler has been removed from OWNER_PIPELINE.  It isn't
      needed there and has adverse DMARC implications for messages to -owner
      of an anonymous list.  (LP: #1645901)

    - Fixed an issue with properly RFC 2047 encoding the display name in the
      From: header for messages with DMARC mitigations.  (LP: #1643210)

    - Fixed an issue causing UnicodeError in sending digests following a
      change of a list's preferred_language.  (LP: #1644356)

    - Enhanced the fix for race conditions in MailList().Load().  (LP: #266464)

    - Fixed a typo in Utils.py that could have resulted in a NameError in
      logging an unlikely occurrence.  (LP: #1637745)

    - Fixed a bug which created incorrect "view more members" links at the
      bottom of the admin Membership List pages.  (LP: #1637061)

    - The 2.1.23 fix for LP: #1604544 only fixed the letter links at the top
      of the Membership List.  The links at the bottom have now been fixed.

    - paths.py now adds dist-packages as well as site-packages to sys.path.
      (LP: #1621172)

    - INIT INFO has been added to the sample init.d script.  (LP: #1620121)

-------------- 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-i18n/attachments/20170602/a87a5506/attachment.sig>

From for-mm-at-python at rplab.ru  Sun Jun 25 05:15:49 2017
From: for-mm-at-python at rplab.ru (Sergey Maslennikov)
Date: Sun, 25 Jun 2017 18:15:49 +0900
Subject: [Mailman-i18n] How can we switch mailman to KOI8-R charset for
 Russian?
Message-ID: <1498382149.2779.30.camel@sn-y510p>

Hi All,

We tried to upgrade Mailman from v. 2.1.9 to v. 2.1.20 (default for
Ubuntu 16.04) and discovered that for Russian language, mailman scripts
tuned the browsers to receive UTF-8 encoded text. How can we turn
mailman back to KOI8-R?

Our problem is that Russian symbols take 2 bytes each in UTF-8. We do
not want to inflate our lists twice. We want to use UTF-8 _only_ for
very mixed (English/Russian/Chinese, for instance) texts/lists, while
for English/Russian texts/lists we want to use one byte per symbol
encodings like KOI8-R or CP1251.

Sergey Maslennikov


From mark at msapiro.net  Sun Jun 25 12:18:47 2017
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 25 Jun 2017 09:18:47 -0700
Subject: [Mailman-i18n] How can we switch mailman to KOI8-R charset for
 Russian?
In-Reply-To: <1498382149.2779.30.camel@sn-y510p>
References: <1498382149.2779.30.camel@sn-y510p>
Message-ID: <09d9db2c-d938-a44a-45e5-0d5a592295ff@msapiro.net>

On 6/25/17 2:15 AM, Sergey Maslennikov wrote:
> 
> We tried to upgrade Mailman from v. 2.1.9 to v. 2.1.20 (default for
> Ubuntu 16.04) and discovered that for Russian language, mailman scripts
> tuned the browsers to receive UTF-8 encoded text. How can we turn
> mailman back to KOI8-R?


There are multiple things going on here.

In Mailman 2.1.19, the character set for Russian (and Romanian) was
changed to UTF-8. This was described in the NEWS for 2.1.19 as follows:

>     - 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.

Independently, Debian (upon which Ubuntu is based) responded to
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398777> with
<https://sources.debian.net/patches/mailman/1:2.1.18-2%2Bdeb8u1/91_utf8.patch/>
which forces all languages to UTF-8 encoding and because it neglects to
do the list attribute string recoding, caused other issues. See
<https://mail.python.org/pipermail/mailman-users/2016-January/080278.html>
and <https://bugs.launchpad.net/mailman/+bug/1462755>.

Probably the least disruptive way for you to reverse this is the following:

1) add this line to mm_cfg.py

LC_DESCRIPTIONS['ru'] = ('Russian', 'koi8-r', 'ltr')

You can't use add_language here because the Debian patch redefines that
to force utf-8.

2) recode messages/ru/LC_MESSAGES/mailman.po with `iconv f=utf-8
t=koi8-r' and run 'msgfmt -o messages/ru/LC_MESSAGES/mailman.mo
messages/ru/LC_MESSAGES/mailman.po' to recompile the message catalog.

3) recode all the templates in templates/ru

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan