ANNOUNCE: Mailman 3.1.0 final!
Hello Mailpeople!
On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line!
Two years after the original release of Mailman 3.0, this version contains a huge number of improvements across the entire stack. Many bugs have been fixed and new features added in the Core, Postorius (web u/i), and HyperKitty (archiver). Upgrading from Mailman 2.1 should be better too. We are seeing more production sites adopt Mailman 3, and we've been getting great feedback as these have rolled out.
Important: mailman-bundler, our previous recommended way of deploying Mailman 3, has been deprecated. Abhilash Raj is putting the finishing touches on Docker images to deploy everything, and he'll have a further announcement in a week or two.
Feedback is welcome: https://github.com/maxking/docker-mailman
What is GNU Mailman?
GNU Mailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, and more. Mailman 3 is released under the terms of the GNU General Public License, version 3.
The best places to start for all things related to this release:
http://docs.mailman3.org/
http://www.list.org/
https://gitlab.com/mailman
(Note: due to timezone skew, some of the tarballs may not be available on PyPI until tomorrow.)
Happy Mailman Day, -Your friendly neighborhood cabal
An overview of what's new in Mailman 3.1
Feature parity with Mailman 2.1
- You should be able to do just about everything that you could do in Mailman 2.1 *except* for topics and sibling/umbrella lists.
Core
- Added support for Python 3.5 and 3.6
- MySQL is now an officially supported database
- Many improvements with importing Mailman 2.1 lists
- DMARC mitigations have been added, based on, but different than the same feature in Mailman 2.1
- The REST API requires HTTP/1.1
- A new REST API version (3.1) has been added which changes how UUIDs are interpreted, fixing the problem for some JavaScript libraries
- Many new REST resources and methods have been added
- Individual mailing lists can augment the system's header matching rules
mailman create
now creates missing domains by defaultmailman digests
now has--verbose
and--dry-run
optionsmailman shell
now supports readline historymailman members
can filter members based on their subscription roles- A new template system has been added for all messages originating from inside Mailman.
- The Message-ID-Hash header replaces X-Message-ID-Hash
- New placeholders have been added for headers and footers
- Unsubscriptions can now be confirmed and/or moderated
Postorius/HyperKitty
- General U/I and U/X improvements
- Many more features from the Core's have been plumbed through
- We've adopted Django social auth logins and dropped Persona (since it's no longer supported upstream). You can now log in via Facebook, Google, GitHub, and GitLab.
Backward incompatibilities
- Core/REST: Held message resources now have an
original_subject
key that is not RFC 2047 decoded.subject
is now RFC 2047 decoded. - Core/REST: If you've run pre-release versions from git head, and stored welcome and goodbye templates via REST, the template key names have changed backward incompatibility.
On 05/25/2017 04:28 PM, Barry Warsaw wrote:
Hello Mailpeople!
On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line!
And I am happy to report that the Mailman 3 installations at https://mail.python.org/mm3/ and https://lists.mailman3.org/ are now happily running this release.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 05/26/17 17:29, Mark Sapiro wrote:
On 05/25/2017 04:28 PM, Barry Warsaw wrote:
Hello Mailpeople!
On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line!
And I am happy to report that the Mailman 3 installations at https://mail.python.org/mm3/ and https://lists.mailman3.org/ are now happily running this release.
Now if only there were a mailman3 ebuild for Gentoo ...
-- Phil Stracchino Babylon Communications phils@caerllewys.net phil@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
On 27 May 2017 at 01:13, Phil Stracchino phils@caerllewys.net wrote:
On 05/26/17 17:29, Mark Sapiro wrote:
On 05/25/2017 04:28 PM, Barry Warsaw wrote:
Hello Mailpeople!
On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line!
And I am happy to report that the Mailman 3 installations at https://mail.python.org/mm3/ and https://lists.mailman3.org/ are now happily running this release.
Now if only there were a mailman3 ebuild for Gentoo ...
-- Phil Stracchino Babylon Communications phils@caerllewys.net phil@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
It's not you alone crying. There are no ports for FreeBSD too. In fact, I have not been able to find a way to run MM3 on FreeBSD which is as easy as I can do with MM2.1 so, not being knowledgeable with packaging, I am stuck with MM2.1 till kingdom come :)
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."
On 05/27/2017 01:07 AM, Odhiambo Washington wrote:
On 27 May 2017 at 01:13, Phil Stracchino phils@caerllewys.net wrote:
Now if only there were a mailman3 ebuild for Gentoo ...
...
It's not you alone crying. There are no ports for FreeBSD too. In fact, I have not been able to find a way to run MM3 on FreeBSD which is as easy as I can do with MM2.1 so, not being knowledgeable with packaging, I am stuck with MM2.1 till kingdom come :)
We are working on packaging and 2.1 -> 3 migration, and it will come. We should have a Docker container ready soon if that will help.
If anyone is interested in helping with packaging for specific distros, we would love to have your help.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On May 27, 2017, at 08:35 AM, Mark Sapiro wrote:
If anyone is interested in helping with packaging for specific distros, we would love to have your help.
There was some early work on Debian packaging, which was put on hold until 3.1 was released. Now that Stretch's release has also been announced, I think we'll see Debian packages soon.
-Barry
On 05/27/17 11:35, Mark Sapiro wrote:
On 05/27/2017 01:07 AM, Odhiambo Washington wrote:
On 27 May 2017 at 01:13, Phil Stracchino phils@caerllewys.net wrote:
Now if only there were a mailman3 ebuild for Gentoo ...
It's not you alone crying. There are no ports for FreeBSD too. In fact, I have not been able to find a way to run MM3 on FreeBSD which is as easy as I can do with MM2.1 so, not being knowledgeable with packaging, I am stuck with MM2.1 till kingdom come :)
We are working on packaging and 2.1 -> 3 migration, and it will come. We should have a Docker container ready soon if that will help.
If anyone is interested in helping with packaging for specific distros, we would love to have your help.
I was actually giving some thought to putting together a Gentoo ebuild, but I operate only an unofficial overlay. I'm sure an official ebuild would be better.
-- Phil Stracchino Babylon Communications phils@caerllewys.net phil@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
participants (4)
-
Barry Warsaw
-
Mark Sapiro
-
Odhiambo Washington
-
Phil Stracchino