From sca at andreasschulze.de  Mon Jul  2 05:34:21 2018
From: sca at andreasschulze.de (A. Schulze)
Date: Mon, 02 Jul 2018 11:34:21 +0200
Subject: [Mailman-Developers] LOCK_SPAMHAUS_LISTED_DBL_SUBSCRIBE should use
 dbl.spamhaus.org
In-Reply-To: <575ec64d-1d07-8044-124b-637d96c89121@msapiro.net>
Message-ID: <20180702113421.Horde.gNU2ZDMQWKdvtH1ntu8OP00@andreasschulze.de>


Mark Sapiro:

> I am pleased to announce the release of Mailman 2.1.27.


Hello,

one new, cool feature is "BLOCK_SPAMHAUS_LISTED_DBL_SUBSCRIBE"
But I'm unsure if it will block any subscription.

see  
https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Utils.py#L1546
There, for a potential subscriber <user at example.org> a DNS query for  
example.com.zen.spamhaus.org is generated.
But, https://www.spamhaus.org/zen/ say "ZEN is the combination of all  
Spamhaus IP-based DNSBLs ..."

I assume, example.org is and will never be listed in zen.spamhaus.org
Shouldn't "example.com.dbl.spamhaus.org" be used?

(Or do I have an wrong/outdated view on zen.spamhaus.org?)

Andreas



From mark at msapiro.net  Mon Jul  2 18:28:53 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 2 Jul 2018 15:28:53 -0700
Subject: [Mailman-Developers] LOCK_SPAMHAUS_LISTED_DBL_SUBSCRIBE should
 use dbl.spamhaus.org
In-Reply-To: <20180702113421.Horde.gNU2ZDMQWKdvtH1ntu8OP00@andreasschulze.de>
References: <20180702113421.Horde.gNU2ZDMQWKdvtH1ntu8OP00@andreasschulze.de>
Message-ID: <0129d804-2be4-2345-53ca-c6519e73531c@msapiro.net>

On 7/2/18 2:34 AM, A. Schulze wrote:
> 
> one new, cool feature is "BLOCK_SPAMHAUS_LISTED_DBL_SUBSCRIBE"
> But I'm unsure if it will block any subscription.
> 
> see
> https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/Utils.py#L1546
> 
> There, for a potential subscriber <user at example.org> a DNS query for
> example.com.zen.spamhaus.org is generated.


You are correct. Thank you very much for the report.

As you note, line 1546 of Utils.py should be

    lookup = '%s.dbl.spamhaus.org' % (domain)

This is now reported at
<https://bugs.launchpad.net/mailman/+bug/1779774> and will be fixed.

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

From mark at msapiro.net  Tue Jul 10 21:03:06 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 10 Jul 2018 18:03:06 -0700
Subject: [Mailman-Developers] Mailman 2.1.18 Security fix release
Message-ID: <49581d63-1175-3802-6433-e5021d0782d2@msapiro.net>

This is a heads up. There is a recently identified minor security issue
in Mailman 2.1.27 and earlier. This is not something that allows
permanent compromise or information leak from your site, but is
something that needs to be fixed. This issue has been given CVE ID
CVE-2018-13796.

I plan to release Mailman 2.1.28 on 24 July, 2018 along with details of
the issue and a patch to apply to earlier releases.

This is just notification of that plan for those that need to plan ahead.

Also, if you are a Mailman translator and you have any updates to your
translation, please submit them in some form prior to 24 July so they
can be incorporated in the release.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20180710/a72bcba1/attachment.sig>

From mark at msapiro.net  Tue Jul 10 23:13:16 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 10 Jul 2018 20:13:16 -0700
Subject: [Mailman-Developers] correction: Mailman 2.1.28 Security fix
 release
In-Reply-To: <49581d63-1175-3802-6433-e5021d0782d2@msapiro.net>
References: <49581d63-1175-3802-6433-e5021d0782d2@msapiro.net>
Message-ID: <106e27ee-73ba-fc83-bb22-4d6f3d34340f@msapiro.net>

Resending with correct subject (2.1.28, not 2.1.18)

On 7/10/18 6:03 PM, Mark Sapiro wrote:
> This is a heads up. There is a recently identified minor security issue
> in Mailman 2.1.27 and earlier. This is not something that allows
> permanent compromise or information leak from your site, but is
> something that needs to be fixed. This issue has been given CVE ID
> CVE-2018-13796.
> 
> I plan to release Mailman 2.1.28 on 24 July, 2018 along with details of
> the issue and a patch to apply to earlier releases.
> 
> This is just notification of that plan for those that need to plan ahead.
> 
> Also, if you are a Mailman translator and you have any updates to your
> translation, please submit them in some form prior to 24 July so they
> can be incorporated in the release.


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20180710/372e19b8/attachment.sig>

From maxking at asynchronous.in  Wed Jul 11 02:50:09 2018
From: maxking at asynchronous.in (Abhilash Raj)
Date: Tue, 10 Jul 2018 23:50:09 -0700
Subject: [Mailman-Developers] Announcing Mailman Suite 3.2 release
Message-ID: <1531291809.1383003.1436888560.7910BC6D@webmail.messagingengine.com>

I am very pleased to announce the release of Mailman Suite 3.2.

This includes Mailman Core 3.2.0, MailmanClient 3.2.0, Postorius 1.2.0, Django-Mailman3 1.2.0, Hyperkitty 1.2.0.

This release includes tons of new features and bug fixes. We had support from tons of new contributors and I, on behalf of the whole Mailman Core team, would like to thank each one of you.

Mailman Core includes support for plugins, more attributes exposed in REST API and improved support for migrating Mailman 2.x lists.  You can now migrate settings and memberships from Mailman 2.x lists to Mailman 3.1. Full change log is available here:

    https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#la-villa-strangiato

Postorius,  The New Mailman Web UI,  now has more settings exposed. The most noteworthy of the features include Python 3.5+ support. Also, you can now set templates for headers, footers and automatic responses inside of Postorius. Full change log is available here:

     https://postorius.readthedocs.io/en/latest/news.html#id1

Hyperkitty, the next-generation mailing-list archiver, has also jumped on the Python 3.5+ wagon and supports all the latest and stable versions of Django.  Importing archives from Mailman 2.x is now even more improved. Full change log is available here:

    https://hyperkitty.readthedocs.io/en/latest/news.html#id1

All the components can be downloaded from https://pypi.org.

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.

The Full documentation for the Suite is available at:

    http://docs.mailman3.org/en/latest/

For more information, please see our web site at one of:

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

--
thanks,
Abhilash Raj (maxking)

From chris at schoeppi.net  Wed Jul 11 07:22:54 2018
From: chris at schoeppi.net (Christian Schoepplein)
Date: Wed, 11 Jul 2018 13:22:54 +0200
Subject: [Mailman-Developers] Problems with the encoding of the list pages
Message-ID: <20180711112254.GA29351@v.cs-x.de>

Hi,

since I've updated my mailman instances to 2.1.27 I have problems with 
the encoding of my list pages. Many of my users are using German Umlauts 
(?, ?, ?, ?, ?, ?, ?) in their listconfiguration, e.g. for the list 
description or the list info texts. Those special characters are broken 
now, while the other special German characters, that are comming from 
the template files of the page, are OK.

It seems that the list templates are encoded in ISO-8859-1 and the 
content, which is unique for every list, is stored an displayed as 
UTF-8.

I don't know if something went wrong via the update process or what else 
caused the issue, but with earlier mailman versions I did no have those 
problems and some of my installations are quite old.

Do you have any idea what I can do to solve this issue? The best IMHO 
would be to convert the whole setup to UTF-8, but as long as the 
template files are stored as ISO-8859-1 or do not have any charset 
stored in the html header of the page, this is difficult.

I have also tried to convert the list settings for every list from UTF-8 
back to ISO-8859-1 with the config_list command and iconv. Maybe I could 
solve the issue this way... What do you think?

Has anything changed in mailman 2.1.27 that caused this encoding issue 
and do others have those problems also?

cheers and thanks for any help,

  Schoepp

-- 
Christian Schoepplein - <chris (at) schoeppi.net> - http://schoeppi.net

From Hagedorn at uni-koeln.de  Wed Jul 11 08:47:57 2018
From: Hagedorn at uni-koeln.de (Sebastian Hagedorn)
Date: Wed, 11 Jul 2018 14:47:57 +0200
Subject: [Mailman-Developers] Problems with the encoding of the list
 pages
In-Reply-To: <20180711112254.GA29351@v.cs-x.de>
References: <20180711112254.GA29351@v.cs-x.de>
Message-ID: <FD1AD9E79DC2FAFA40928AF2@tyrion.rrz.uni-koeln.de>

We're running 2.1.27 with predominantly German lists, and we don't have 
that problem. Could it be related to your web server settings?

--On 11. Juli 2018 um 13:22:54 +0200 Christian Schoepplein 
<chris at schoeppi.net> wrote:

> Has anything changed in mailman 2.1.27 that caused this encoding issue
> and do others have those problems also?
-- 
    .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:.
                 .:.Regionales Rechenzentrum (RRZK).:.
   .:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:.

From mark at msapiro.net  Wed Jul 11 10:02:27 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 11 Jul 2018 07:02:27 -0700
Subject: [Mailman-Developers] Mailman 2.1.18 Security fix release (date
 change)
In-Reply-To: <49581d63-1175-3802-6433-e5021d0782d2@msapiro.net>
References: <49581d63-1175-3802-6433-e5021d0782d2@msapiro.net>
Message-ID: <7a73d4eb-2db6-90b8-fa23-c65a930817a2@msapiro.net>

On 7/10/18 6:03 PM, Mark Sapiro wrote:
> This is a heads up. There is a recently identified minor security issue
> in Mailman 2.1.27 and earlier. This is not something that allows
> permanent compromise or information leak from your site, but is
> something that needs to be fixed. This issue has been given CVE ID
> CVE-2018-13796.
> 
> I plan to release Mailman 2.1.28 on 24 July, 2018 along with details of
> the issue and a patch to apply to earlier releases.
> 
> This is just notification of that plan for those that need to plan ahead.


Due to changed circumstances, I am changing the planned release date
from 24 July to 23 July.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20180711/c5586154/attachment.sig>

From mark at msapiro.net  Wed Jul 11 11:16:38 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 11 Jul 2018 08:16:38 -0700
Subject: [Mailman-Developers] Problems with the encoding of the list
 pages
In-Reply-To: <20180711112254.GA29351@v.cs-x.de>
References: <20180711112254.GA29351@v.cs-x.de>
Message-ID: <3e261c3d-61ac-56ce-53f5-665c2fc0d055@msapiro.net>

On 7/11/18 4:22 AM, Christian Schoepplein wrote:
> 
> Has anything changed in mailman 2.1.27 that caused this encoding issue 
> and do others have those problems also?


I need more information to help with this. What version did you upgrade
from? Is this Mailman installed from source or a package? If a package,
which, and if Debian/Ubuntu, see the entire thread at
<https://bugs.launchpad.net/mailman/+bug/1462755> including all the
posts linked from
<https://bugs.launchpad.net/mailman/+bug/1462755/comments/6>.

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

From barry at python.org  Wed Jul 11 12:56:45 2018
From: barry at python.org (Barry Warsaw)
Date: Wed, 11 Jul 2018 09:56:45 -0700
Subject: [Mailman-Developers] Announcing Mailman Suite 3.2 release
In-Reply-To: <1531291809.1383003.1436888560.7910BC6D@webmail.messagingengine.com>
References: <1531291809.1383003.1436888560.7910BC6D@webmail.messagingengine.com>
Message-ID: <BD7C415F-93C2-44D5-BCFC-AAFA8B8C40C1@python.org>

On Jul 10, 2018, at 23:50, Abhilash Raj <maxking at asynchronous.in> wrote:
> 
> I am very pleased to announce the release of Mailman Suite 3.2.

Congratulations!  This was a release long in the making, and I?m so happy that Abhilash was able to take it over the finish line.  Thanks to all the community members who also helped, and continue to make Mailman 3 a great project.

Cheers,
-Barry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20180711/94354eda/attachment.sig>

From mark at msapiro.net  Wed Jul 11 12:58:53 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 11 Jul 2018 09:58:53 -0700
Subject: [Mailman-Developers] [Mailman-Announce] Announcing Mailman
 Suite 3.2 release
In-Reply-To: <1531291809.1383003.1436888560.7910BC6D@webmail.messagingengine.com>
References: <1531291809.1383003.1436888560.7910BC6D@webmail.messagingengine.com>
Message-ID: <e3921b3b-8779-3ed1-e432-e9bfdab9bc12@msapiro.net>

On 7/10/18 11:50 PM, Abhilash Raj wrote:
> I am very pleased to announce the release of Mailman Suite 3.2.
> 
> This includes Mailman Core 3.2.0, MailmanClient 3.2.0, Postorius 1.2.0, Django-Mailman3 1.2.0, Hyperkitty 1.2.0.


We need to tag these releases in the gitlab branches. Do you want to do
that?

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

From maxking at asynchronous.in  Wed Jul 11 14:22:49 2018
From: maxking at asynchronous.in (Abhilash Raj)
Date: Wed, 11 Jul 2018 11:22:49 -0700
Subject: [Mailman-Developers] [Mailman-Announce] Announcing Mailman
 Suite 3.2 release
In-Reply-To: <e3921b3b-8779-3ed1-e432-e9bfdab9bc12@msapiro.net>
References: <1531291809.1383003.1436888560.7910BC6D@webmail.messagingengine.com>
 <e3921b3b-8779-3ed1-e432-e9bfdab9bc12@msapiro.net>
Message-ID: <1531333369.1785587.1437599624.57E3358D@webmail.messagingengine.com>



On Wed, Jul 11, 2018, at 9:58 AM, Mark Sapiro wrote:
> On 7/10/18 11:50 PM, Abhilash Raj wrote:
> > I am very pleased to announce the release of Mailman Suite 3.2.
> > 
> > This includes Mailman Core 3.2.0, MailmanClient 3.2.0, Postorius 1.2.0, Django-Mailman3 1.2.0, Hyperkitty 1.2.0.
> 
> 
> We need to tag these releases in the gitlab branches. Do you want to do
> that?

I forgot to push tags for Mailman Core and Postorius, which is now done! The rest were tagged last night.

> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> https://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: 
> http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-developers/raj.abhilash1%40gmail.com
> 
> Security Policy: http://wiki.list.org/x/QIA9


-- 
  thanks,
  Abhilash Raj (maxking)

From holger at merlinux.eu  Sat Jul 14 02:02:37 2018
From: holger at merlinux.eu (holger krekel)
Date: Sat, 14 Jul 2018 08:02:37 +0200
Subject: [Mailman-Developers] autocrypt/mailman MOSS proposal declined
Message-ID: <20180714060237.GJ10744@beto>

Dear mailman devs, autocrypters, 

just heart back from Mehan from the Mozilla Mission partners programme
that they declined the autocrypt/mailman proposal. Here is the quote:

"At this stage, the committee is not convinced that your project is 
positioned to advance the Mozilla mission in a significant manner in the                                                                 
near-term. Specifically, it is not clear to the committee if Autocrypt +                                                                 
Mailman 3 is on track to encourage wider adoption or a broader set of use                                                                
cases in the future."

thanks everybody who helped with the application.
Let's see if we can anyway advance the ideas of 
easy-to-use encrypted mailing lists ... 

holger