June 2017 - Mailman-users - lists.mailman3.org

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