Search results for "Postorius" - Mailman-users

Postorius extremely slow on some of the mailinglists

by Eric Broens

Hi, Postorius became extremely slow recently on some of our mailinglists, but not on all of them. Postorius even times out when opening some of them (https://<hostname>/postorius/lists/<mailing_list>.<domain>/) and shows the message "Mailman REST API not available. Please start Mailman core." This only happens when I am logged in (as administrator), but not when I am not logged in. It seems to be independent on the number of subscribers on the particular mailing list. Below you'll find an extract from the logs for a case where it timed out, and for a case where the page showed up after a long time. Mainly "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" takes a long time. There is nothing unusual going on regarding database queries, and mails are delivered normally. Any idea why this happens and how it can be solved? [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain> HTTP/1.1" 200 378 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/owner HTTP/1.1" 200 2283 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>@<domain>/config HTTP/1.1" 200 3107 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [05/Feb/2025:19:04:43 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [2025-02-05 19:05:14 +0100] [1612] [CRITICAL] WORKER TIMEOUT (pid:1653) [2025-02-05 19:05:14 +0100] [1653] [INFO] Worker exiting (pid: 1653) [2025-02-05 19:05:15 +0100] [64429] [INFO] Booting worker with pid: 64429 [07/Feb/2025:13:42:14 +0100] "POST /3.1/lists/find HTTP/1.1" 200 18226 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain> HTTP/1.1" 200 414 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/owner HTTP/1.1" 200 2337 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/roster/moderator HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>@<domain>/config HTTP/1.1" 200 3232 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:20 +0100] "GET /3.1/lists/<mailing_list>.<domain>/archivers HTTP/1.1" 200 81 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:46 +0100] "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" 200 520132 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:42:46 +0100] "GET /3.1/lists/<mailing_list>.<domain>/member/<my.email>%40<mydomain> HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:43:15 +0100] "GET /3.1/lists/<mailing_list>@<domain>/requests HTTP/1.1" 200 520132 "-" "GNU Mailman REST client v3.3.1" [07/Feb/2025:13:43:15 +0100] "GET /3.1/lists/<mailing_list>@<domain>/held?count=50&page=1 HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.1" Thanks, Eric

1 year, 4 months

KeyError: 'get_requests_count' after an upgrade

by Guillermo Hernandez (Oldno7)

I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' ... (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please?

5 years, 4 months

Re: What's the difference between (purpose of) reject and ignore

by Mark Sapiro

On 6/23/22 12:37, denis.bitouze(a)univ-littoral.fr wrote: > Hi, > > at a page of the form .../postorius/lists/mylist/held_messages, it is > possible to: > > - Accept > - Reject > - Ignore What is the Postorius version and is it installed from source, pip or as package and if as package, what package? The choices should be Accept, Reject and Discard. There should be no Ignore choice, but I'm guessing you see them in French where the translation of Discard is Ignorer. See https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/…. The difference between Reject and Discard is Reject notifies the sender of the rejection whereas Discard just discards the message without notification. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by IEM Network Operation Center (IOhannes m zmölnig)

thanks again, Mark, for your detailed answer. On 3/15/22 17:21, Mark Sapiro wrote: > See https://gitlab.com/mailman/mailman/-/issues/901 > > You can add something like > ``` > Alternatively, you can confirm by going to the URL > > https://$domain/mailman3/lists/$list_id/confirm/?token=$token > ``` hmm. the list-url (e.g. where you can subscribe to the list) for my instance looks like https://$domain/postorius/lists/$list_id/ (that is: it spells "postorius" rather than "mailman3"). so i guess the URL should be https://$domain/postorius/lists/$list_id/confirm/?token=$token, which unfortunately returns 404. also, my postorius/urls.py does not contain an url-pattern for "confirm", unlike the current one as found on <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> so i guess this was not possible yet with postorius 1.2.4 > to the list:user:action:subscribe template. Note that `$domain` may not > be appropriate here because it is the email domain which may not be the > web domain. > >> also: the confirmation mail says that the subject must be kept intact. >> however, i noticed that the actual "From" address of the confirmation >> mail already contains the token. > > The current template > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l… > doesn't say that. yes. the *current* template. but not the template that came with mailman3 3.2.1 > >> finally: what else is required to approve the confirmation? will the >> sender's email-address be taken into account? (e.g. if they subscribed >> "foo+mylist(a)example.com" but send the confirmation-reply from >> "foo(a)example.com", will that still work? > > > Yes. Only the token is required. > cool thanks. together with the not-yet-expired tokens, i think i can create some ad-hoc web-service that translates URLs to confirmation replies. mfd IOhannes

4 years, 3 months

Re: How can administrator sign people up to a list?

by worik

Sorry about the noise. Found it. It is on the page for the list, a ,menu option at the top of the page. Thanks Worik On 11/02/19 2:28 PM, worik wrote: > On 11/02/19 2:25 PM, Mike wrote: >> Sign into Postorius and go to "Mass Operations" - >> "Mass Subscribe". >> >> >> >> On 2/10/2019 7:13 PM, worik wrote: >>> As a list administrator, how do I add a group of email addresses to a >>> list? > > I cannot see that option. > > When I click on the Postorius logo I get to postorius/lists/?all-lists > > Worik > -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

7 years, 4 months

Re: Separating Lists by Domain

by Mark Sapiro

On 5/1/20 9:59 AM, Sven Seeberg via Mailman-users wrote: > >> Is it possible to have only the lists to show that are part of the >> domain being used to access? This is the setting FILTER_VHOST = True. It causes problems in Postorius and doesn't work well in HyperKitty. See <https://gitlab.com/mailman/postorius/-/issues/394> and <https://gitlab.com/mailman/hyperkitty/-/issues/254>. Both these issues are fixed for the next releases of Postorius and HyperKitty which should be out later this month. > On > top of that another question: is it possible to add user accounts that > can manage lists for one domain but not other domains? We already have the concept of domain owner, but implementation of domain owner permissions is not yet done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Re: Residual signature?

by Mark Sapiro

On 5/28/26 06:57, Paul Tomblin via Mailman-users wrote: > > But anyway, I had no idea those templates were there, so I'll have to file that away in my memory for next time I wonder why lists have footers that don't show up in the UI. Am I right in thinking that a UI configured template will override the ones in that directory tree? That is correct. Creating a template in Postorius will put an entry for that template in the template table in the database with a URI pointing to Postorius and that is where Mailman core will go to find that template. However, it you delete that template from Postorius, that will remove the entry from the template table, and absent that, Mailman core will fall back to default search rules. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 6 days

Re: Incorrect error log message in OutgoingRunner._dispose()

by Mark Sapiro

On 4/26/26 10:42 AM, Craig Leres wrote: > On 4/26/26 06:52, Mark Sapiro wrote: >> >> Did you by chance run import21 as root or another non-mailman user >> resulting in template files unreadable by Mailman? > > Yes and no. I ran it as a user in group mailman; the template files are > owned by the user but are group mailman read/write... Then those templates in Mailman's var/templates/LIST-ID/LC/ should be used for the list for that language as long as they are readable and not overridden by a Postorius template or other URI for the list in the template table in the database. Was there anything in mailman.log prior to your defining a Postorius template indicating why they weren't used? >>> Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server >>> 127.0.0.1 on port 25 >> >> This is a well known issue. See <https://gitlab.com/mailman/mailman/-/ >> work_items/582> and related issues referenced therein. > ... > What really bothers me about the error message is that it's reporting a > SMTP connection failure when what really happened was a HTTP connection > failure. That is all part of the above referenced issues. It is a bug and should be fixed but hasn't been yet. It is caused by the low level socket error upon trying to fetch the template, ultimately being caught by the try/except in outgoing runner's sending of the message. >>> I'm using the default webservice port (8001) so I would not expect >>> anything to ever be listening on 8000. >> >> The default web service port (Postorius and HyperKitty) is 8000. Port >> 8001 is Mailman core's rest api. > > Ah. I never noticed anything telling me the apache config needed to also > listen on 8000. It's also confusing to me to call the rest api port the > "web service port" (Also, I'm not running hyperkitty.) Apache doesn't listen on port 8000. The WSGI server (uWsgi or Gunicorn or ...) listens on port 8000 and Apache listens on ports 80 and 443 as normal and proxies the mailman requests to port 8000. > Ok, I added apache config to handle 127:0.0.1:8000 and that solves the > "SMTP" (HTTP) connection error and cpu bound runner. I don't know what you did, but see <https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…> for how Apache should proxy to port 8000. > I still can't get templates to work but I'll debug further and ask for > help later if I still can't get it to work. Do you have a WSGI server running and listening on port 8000? See <https://docs.mailman3.org/en/latest/install/virtualenv.html#setting-up-a-ws…>. You need this for Postorius as Postorius is a Django project and Django is a WSGI application. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 4 weeks

Re: Multiple domain problem

by Mark Sapiro

On 2/10/23 01:43, Lars Bjørndal wrote: > On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: >> On 2/9/23 13:21, Lars Bjørndal wrote: >>> >>> If I connect to example2.com, the title is example2.com, without the >>> preceding List index. And the body says Page not found. >> >> >> What's in the browser's address bar for that page? > > It's https://example2.com/mailman3/lists/ And when you get the Page not found, is it a browser 404 error or a Postorius error page? > >> What's in Postorius domains view? > > I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). Why are you going to http://localhost:8000/? You should be able to see the domain's view at https://example1.com/mailman3/domains/ or https://example1.com/mailman3/domains/ or by just clicking Domains in Postorius top nav bar. > Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Again you should be able to go to https://example1.com/admin or https://example2.com/admin. If these don't work, you need to add directives in your web server to proxy them to http://localhost:8000/admin -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Re: domain owner role

by Abhilash Raj

> On Sep 1, 2021, at 7:52 AM, Rainer Herbst <rainer.herbst(a)aip.de> wrote: > > Dear all, > > recently, I have added one account to a domain as domain owner. I did expect the new owner to see all lists in that domain in Postorius, but he sees no list at all. > > Is this the way it should be? How can I add administrators able to perform administrative tasks on all lists in Postorius? > Domain owner role isn’t currently very useful in Postorius, they can so far only edit the domain templates. If you want to grant the user ability to manage lists in Postorius, you’d have to grant the user superuser privileges which will allow them to manage all the domains. I was thinking there is an open issue for it, but apparently there isn’t one so I opened a new one. https://gitlab.com/mailman/postorius/-/issues/533 -- thanks, Abhilash Raj (maxking)

4 years, 9 months

Mailman-users search results for query "Postorius"