Re: [Mailman-Developers] ANNOUNCE: Mailman 3.1.0 final!

2017-05-26 Thread Mark Sapiro 
On 05/26/2017 02:38 PM, Fabian A. Santiago wrote:
> 
> I see in the docker readme that it still hasn't been determined how to use 
> postfix with mm3. Is this in fact the case? Does anyone know how?


The comment in the  README.md
only refers to the Mailman instance in the docker container
communicating with Postfix outside the docker container for purposes of
running 'postalias' and 'postmap' commands. This has actually been
addressed even in the docker container by allowing Postfix 'regex'
tables to replace the default 'hash' tables.

There has never been an issue running Mailman 3 with Postfix in general.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] ANNOUNCE: Mailman 3.1.0 final!

2017-05-26 Thread Fabian A. Santiago 
On May 25, 2017 7:28:00 PM EDT, 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!
>
>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 default
>* `mailman digests` now has `--verbose` and `--dry-run` options
>* `mailman shell` now supports readline history
>* `mailman 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.

I see in the docker readme that it still hasn't been determined how to use 
postfix with mm3. Is this in fact the case? Does anyone know how?


-- 
Thanks.
Fabian S.

OpenPGP:

3c3fa072accb7ac5db0f723455502b0eeb9070fc
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Developers] ANNOUNCE: Mailman 3.1.0 final!

2017-05-26 Thread Mark Sapiro 
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
 and  are now
happily running this release.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Developers] ANNOUNCE: Mailman 3.1.0 final!

2017-05-25 Thread Barry Warsaw 
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 default
* `mailman digests` now has `--verbose` and `--dry-run` options
* `mailman shell` now supports readline history
* `mailman 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.


pgp3i5M1JIjBs.pgp
Description: OpenPGP digital signature
___
Mailman-Developers mailing list
Mailman-Developers@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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9