Search results for "Postorius" - Mailman-users

Another set of new releases

by Abhilash Raj

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11. All the releases are available on PyPI, as usual! -- Thanks Abhilash Raj

6 years, 5 months

Approve an email

by Lars Bjørndal

Hi, list! I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and postorius-1.3.6-2.fc36.noarch installed. with the command sudo -u mailman mailman3 create <listname> I was able to create a list. I'm not able to find out how to setup and configure the postorius package. There's no mailman-web command. Hyperkitty will not installed du to a dependency conflict, but I dont need archiving for the list. Here comes my quesitons: - What's the easiest way to approve an email sent to the list? - How can I configure the list to accept messages also from non members? - How can I setup postorius to work on Fedora? I have django-admin, but I'm not sure where to go. Thanks in advance, Lars

3 years, 5 months

Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 5:40 PM, Brian Carpenter wrote: > Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. Abhilash (@maxking) is one person and he has a $DayJob. We're all doing the best we can. > I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. This is not a Docker issue per se. It is a consequence of upgrading Mailman core to 3.3.1+ and processing many old, stale, previously unprocessed bounces. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. > > I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: > > ### > The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: > > [webservice] > configuration: /path/to/gunicorn.cfg > > and then in the gunicorn.cfg you can add > > [gunicorn] > timeout = 90 > graceful_timeout = 30 > ### > > I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. > > After restarting docker-mailman, I can't access Postorius due to the following error: > > ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Is Mailman core running? If not, whats in core's mailman.log as to why not? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 1:37 PM, Ruth Ivimey-Cook wrote: > Thanks Mark, Ignore bracketed numbers below ([1], [2], etc.) They come from conversion of the HTML only post to plain text. > On 20/06/2020 03:53, Mark Sapiro wrote: > > What are your Django settings for MAILMAN_REST_API_URL, > MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with > the [webservice] settings for hostname, port, use_https, admin_user and > admin_pass in mailman.cfg in core and is the port open to the outside on > the core machine? > > greyarea-post is the mailman-core and exim server. > > greyarea-web1 is the postorius and hyperkitty server. > > On greyarea-web1, in django-settings.py, > > MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = XXXX > > and both the above-named hosts are also included in ALLOWED_HOSTS along > with localhost. > > On greyarea-post, in mailman.cfg: > > [webservice] > admin_pass: XXXXX > admin_user: restadmin > api_version: 3.1 > hostname: 0.0.0.0 > port: 8870 > use_https: no > > The password and username are as on web1. That all looks good. > Do you see REST requests from the Postorius machine in core's > mailman.log and access.log? > > Yes, there are lots of requests of the form: > > [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 > HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" > > I made a new list using the core CLI, and as a result of navigating > directly to the list archive page I get to see: > > [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk > HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" > > ... but in neither case do I get a complete screen on the browser or > 'follow-up' requests. > > I don't have a file access.log on the greyarea-post. Yes, that's actually a gunicorn log so would only be on greyarea-web1, but the mailman.log tells us the requests are getting to the core REST API, so we don't need that info. > On the greyarea-web1 I have mailmansuite.log with the last few lines: > > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba > se.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co > nnection.py", line 124, in call > 'Could not connect to Mailman API: ', repr(e)) > mailmanclient.restbase.connection.MailmanConnectionError: ('Could > not connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > ERROR 2020-06-03 01:02:06,115 29002 django.request Service > Unavailable: /postorius/lists/ OK. This is telling us that mailmanclient (the REST API Python bindings that Postorius uses to access core) is having trouble establishing a connestion to the core REST server, but it clearly gets there some of the time based on the mailman.log entries. > the uwsgi-error_*.log contains many lines of the form: > > api: url is > [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > api: url is > [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > > My reason for thinking, in my original post, that the wrong host > address is being used is that the ConnectionError above contains > 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as > the listen address on the core web service and does not appear in the > config for postorius. The ConnectionError above comes from requests.request (docs at <https://requests.readthedocs.io/en/master/>). Client only provides a URL in the call to request and the URL is the baseurl + the path and the baseurl is MAILMAN_REST_API_URL which you have as http://greyarea-post:8870. Entries above have http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? I suspect a DNS lookup issue. How does greyarea-web1 resolve greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS rather than relying on /etc/resolv.conf and/or /etc/hosts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Re: Editing "automatic responses" tab i Postorius does not work

by David Krantz

But this one is already exposed. But I cannot change it anyway as the tab requires URIs for the different templates to allow saving. I do not use those URIs as I have configured the defaults as I like them. I tried once and it failed so I decided to set the defaults instead. cheers. // David On Sun, May 21, 2017 at 3:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/21/17 5:22 AM, David Krantz wrote: >> >> I am trying to change e.g. the value of "notify admin on membership >> changes" through postorius. > > > There are still many settings not yet exposed in Postorius. We are > painfully aware of this and will probably be working on some of this at > the PyCon sprints starting tomorrow. > > Until we get more of these addressed, you will need to use tools like > "mailman withlist" to set these things. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

9 years, 1 month

[Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 00:21, Mark Sapiro ha scritto: > On 2/28/21 10:17 AM, blackout69 wrote: > It looks to me like a race condition of some kind or possibly an > incompletely deleted thread. Have you deleted any threads? I have not deleted threads > I'm curious as to how you happen to be going to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> > as opposed to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. > I know that ULS and similar ones are in HyperKitty's urls.py, but I > don't see them exposed on any pages. > > Anyway, when you say "from that moment the maiilan3 has stopped > working." (sic) exactly what stopped working. Did core stop delivering > messages? Did Postorius stop working. If so, this all may be related to > some underlying database issue or something like that that was fixed by > the restarts. I don't see how this HyperKitty error could affect > Postorius or Mailman core. When I say that it stops working, I mean that all members of the lists no longer receive messages. Postorius and Hyperkitty continue to work blackout69

5 years, 3 months

Re: Can login at /admin, but cannot login at the account/login page.

by Abhilash Raj

> On Aug 14, 2021, at 9:34 PM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > I'm sorry, I'm in a "second vaccination" fog at the moment (mending > but concentration lasts only about 10 minutes), so I'll answer what I > know offhand since Abhilash is busy and Mark is probably offline for > vacation by now. Perhaps later somebody can give a fuller answer. > > pabsta(a)gmail.com writes: > >> In comparison to the walkthrough, I did two changes; First, I used >> different port numbers , as it would otherwise conflict with other >> services on the server. > > Thank you for the very precise description. It's very helpful. > >> Second, I disabled the social accounts authentification mechanisms. > > This should not be a problem since you disabled only the providers (I > think the socialauth base module is required even if you don't use it.) > >> I am still running on sqllite, as I am still testing things (one >> task at a time). > > This should be no problem. > >> Using my "superuser" credentials, I can log to the admin section in >> a fraction of a second. > > If you mean the django admin page https://localhost:800something/admin, > that doesn't involve any part of Mailman at all. > >> However, if logout and attempt to login from the postorius website, >> I get a « 502 bad gateway » error after roughly 30 seconds. The >> logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech >> free" error message > > I would guess this is also just a connection drop because it doesn't > receive the expected response within timeout. > >> and the nginx error logs just show a connection drop: >> >> 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: >> [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" > a > > >> 1- If I attempt to login with improper credentials, the services >> respond normally, and I get the expected red box with "invalid >> credentials" message on the postorius page. It is only when proper >> credentials are given that the connection fails. > > The only thing I can think of is that having sucessfully logged in, > Postorius can't find Mailman core to populate your user page. That > would explain why an invalid login (which is entirely within Postorius > and Django) proceeds as expected, but a valid login would fail so > spectacularly. This would be my guess too, although, it will show MailmanApiError in logs. Do note that that gunicorn logs don’t have all the logs from exceptions raised in Postorius, for that, you want to file the location of the ‘postorius’ or ‘root’ logger in your settings.py (I couldn’t find that, it seems like you skipped those). So, I’d expect some error or something in the logs if this isn’t the actual case. -- thanks, Abhilash Raj (maxking)

4 years, 10 months

Re: Managing users in postorius

by Mark Sapiro

On 9/25/24 11:08, Lieuallen, Thomas Otis wrote: > I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? In the Django admin web UI under Email addresses, you can add an address and associate it with an existing user. > Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? It should list both member and nonmember rolls. If you scroll down past Subscriptions to Ownerships, it lists owner and moderator rolls. > I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. In the Django admin UI, you can edit the user associated with an email address under Email addresses -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Re: Deactivate list without deleting it?

by Stephen J. Turnbull

Colin Watson writes: > I possibly should have explained our situation in a little more > detail. Well, I was pretty clear on your requirements, it turns out. I don't, and I believe I'm in agreement with the rest of the team here, need to know why you want something (at least not at this "let's see if we can hash out the requirements and the design a bit" stage). After all, even if we end up WONTFIXing it, it's open source and we're happy to talk about how you might do something even if we won't do it for you! > Postorius wouldn't come into it in our case That's an interesting detail. Thing is, at present Postorius *is* the "control panel" for the whole suite (all the best bands are run by their bassists, you know), so we would bring it up if you left it out. However, if you don't want to use Postorius, I think the mailman-client functionality will make it strightforward to implement your UI within Launchpad, and it now includes a nicer CLI so if you prefer to implement core and Hyperkitty functionality before the Launchpad side, mailman-client will allow you to test core features at that stage. > I'd been thinking more of a new enum in HyperKitty for the visibility > state, since it does seem like quite an archiver-specific thing. Well, there is an enum in core for it already. I'm not sure how that works currently (specifically, how you go about telling Hyperkitty if that changes). Keeping that in sync is an issue (at least for us), since Postorius can query it, IIRC. For the rest, I have nothing to add to what Barry already wrote. Steve

8 years, 5 months

Re: Postorius: Search field in lists overview

by Mark Sapiro

On 1/14/25 23:36, Andreas Vetter wrote: > Hi, > is there a way to search lists in Postorius' Lists overview > https://lists.example.com/mailman3/lists/?all-lists > > Well, one can change "results on page" to 200 and then use the search function > of the browser, but that is some more clicks. No, there is no search function for this. If you know the name you are looking for, e.g., list(a)example.com, you can just go to https://lists.example.com/mailman3/lists/list@example.com/ but if you are looking for lists matching a pattern, there is no Postorius function for that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Mailman-users search results for query "Postorius"