- Mailman-users - lists.mailman3.org

Mailman 3 Container Images v0.1
by Abhilash Raj June 26, 2017

June 26, 2017

Hi Everyone, I have been working on containerizing Mailman 3 so that it becomes easier to test and try Mailman 3. There are two images in total: * maxking/mailman-core : This consists of Mailman Core and includes the plugin to enable the Hyperkitty Archiver. * maxking/mailman-web : This consists of a full Django installation and run the Mailman's Web UI components. It has Mailman Client, Postorius & Hyperkitty. The images are built from the Dockerfiles hosted on Github[3] in case you want to look at it. You can find most of the documentation about these images at https://asynchronous.in/docker-mailman/. The version of the internal components included in each image is available here[7]. The images are versioned and the process is documented[4], please have a look before you use them. Also, the images are signed and I encourage you to verify them before using. The process of how-to verify is also documented. Docker Compose is a tool written in Python makes is very easy to deploy connected-images and take the pain out of writing long long commands for spinning of containers. There is a sample `docker-compose.yml` file in the Github repository mentioned above which is kind-of tested to be able to spin off these images in vanilla condition (without any customization/configuration). You can report issues, comments or concerns in the Github repo[6]. [1]: https://hub.docker.com/r/maxking/mailman-core/ [2]: https://hub.docker.com/r/maxking/mailman-web/ [3]: https://github.com/maxking/docker-mailman [4]: https://asynchronous.in/docker-mailman/#release [5]: http://semver.org/ [6]: https://github.com/maxking/docker-mailman/issues [7]: https://github.com/maxking/docker-mailman/wiki -- thanks, Abhilash Raj

1 0

API Question: map list -> UI URL?
by tlhackque＠yahoo.com June 24, 2017

June 24, 2017

Using the REST API, how do I get from a list / list configuration to the URL of the management GUI? I've looked through the data returned by the API and even the SQL schemas; I don't see the path. Am I missing something, or do I need to log an issue for this? I'm not particularly interested in the subscriber pages, but it ought to be possible to get there too... Thanks.

1 0

Topics? First bug...
by tlhackque June 21, 2017

June 21, 2017

Hi, I'd like to deploy a new project on Mailman 3, which I prototyped on 2.1). Unfortunately, it's organized as one mailing list with ~ 120 topics. (The project follows another source, and it's much easier to spin up (or down) a new topic than to instantiate & manage a new list.) I see that the latest Mailman 3 release (Congrats!) doesn't support topics yet. Where is that on your todo list? First bug: Looking at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/. If I set "results per page" to a large number & switch months, results per page reverts to the default (10). It should stick with whatever I select... It also would be nice to have an account preference for this, so it doesn't have to be set on each visit.

2 2

Re: Http/Https
by Abhilash Raj June 15, 2017

June 15, 2017

Excerpts from Simon HANNA's message of June 14, 2017 1:06 pm: > You are supposed to force https in the webserver, serving postorius and hyperkitty. Especially in postorius almost all pages contain sensitive information. > > On June 14, 2017 10:05:59 PM GMT+02:00, Bill <bill3(a)uniserve.com> wrote: >>Hi folks, >> >>We're setting up Mailman 3.1 and so far installation has been good and >>we're now in the testing phase. >> >>We've run into a snag with the account signup function on Postorius. >> >>When Postorius sends an email to the user to confirm their address, it >>displays a link using the https protocol. This doesn't work. But, if we >> >>manually change the protocol to http it will work, confirm the address >>and take us back to Postorius. >> >>Is this a known bug or have we committed a configuration error? I agree to Simon's suggestion that you should use HTTPS for all communications for Postorius. However, if you really want to, it is possible to change the behavior using a configuration parameter in django-allauth which is what controls the user signup and email verification. ACCOUNT_DEFAULT_HTTP_PROTOCOL (=”http”) If you set the above to "http" in your django's settings.py, it should then generate urls with http. [1]: https://django-allauth.readthedocs.io/en/latest/configuration.html Message-ID: <draft-878tktptc9.fsf(a)gmail.com> Date: Thu, 15 Jun 2017 01:07:18 -0700 X-Notmuch-Emacs-Draft: True -- thanks, Abhilash Raj

1 0

Http/Https
by Bill June 14, 2017

June 14, 2017

Hi folks, We're setting up Mailman 3.1 and so far installation has been good and we're now in the testing phase. We've run into a snag with the account signup function on Postorius. When Postorius sends an email to the user to confirm their address, it displays a link using the https protocol. This doesn't work. But, if we manually change the protocol to http it will work, confirm the address and take us back to Postorius. Is this a known bug or have we committed a configuration error? All assistance appreciated. Bill -- Sent using Icedove on Debian GNU/Linux.

2 1

Re: "Private archives" aren't private
by Simon Liebold June 6, 2017

June 6, 2017

Am 06.06.2017 um 22:25 schrieb Abhilash Raj: > Excerpts from Simon Liebold via Mailman-users's message of June 6, > 2017 1:20 pm: >> >> AttributeError: type object 'BaseCommand' has no attribute >> 'option_list' > > It was reported recently on the bug tracker, you can track the > progress here[1]. > > > [1]: https://gitlab.com/mailman/hyperkitty/issues/135#note_31529582 Thanks Abhilash for the pointer. Simon

1 0

(Email|Thread) matching query does not exist ?
by Simon Liebold June 6, 2017

June 6, 2017

I am seeing these errors: mailman-suite_project$ python manage.py qcluster 19:27:52 [Q] INFO Q Cluster-11541 starting. 19:27:52 [Q] INFO Process-1:1 ready for work at 11546 19:27:52 [Q] INFO Process-1:2 ready for work at 11547 19:27:52 [Q] INFO Process-1 guarding cluster at 11545 19:27:52 [Q] INFO Process-1:4 pushing tasks at 11549 19:27:52 [Q] INFO Q Cluster-11541 running. 19:27:52 [Q] INFO Process-1:3 monitoring at 11548 19:27:52 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 19:27:52 [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] 19:27:52 [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] 19:27:52 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. 19:27:52 [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. 19:27:52 [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. Should I need to worry? I recently deleted some test emails from the archive. Don't know if this has anything to do with it. Simon

1 0

"Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all'
by Simon Liebold May 30, 2017

May 30, 2017

Is deleting threads from the archive (via Hyperkitty) currently supported? I am getting the error indicated above if I click on "Delete this thread". Is there another way to delete whole threads or individual posts? Simon

3 7

Editing "automatic responses" tab i Postorius does not work
by David Krantz May 26, 2017

May 26, 2017

Hi, I am trying to change e.g. the value of "notify admin on membership changes" through postorius. This is not possible as I have no URLs for the various templates (all templates are using defaults stored on the server). Is this something that can be circumvented or fixed? I can of course change admin_notify_mchanges in the "mailman withlist" interface, but this is less than ideal. best regards // David

2 4

ANNOUNCE: Mailman 3.1.0 final!
by Barry Warsaw May 26, 2017

May 26, 2017

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.

2 1