Search results for "Postorius" - Mailman-users

Postorius performance with over 1000 pending users

by Nick W

I've got a couple things I need help with: The Symptom and The Problem. The Symptom: Postorius has gotten quite slow to load, taking more than 30s to load the Subscription Requests tab. Having zero pending subscription requests (I'm on v1.2.5), I started investigating unconfirmed subscriptions. I followed the commands from here[1] and got this: mailman shell -l your.list.id util = getUtility(IPendings) print(len(list(util.find(mlist=m,pend_type='subscription')))) 1816 Wow, 1816 pending subscription requests. I can say for certain that my list is not popular so these requests must have been submitted by bots. Let's get there in The Problem. How can I "purge" this list? I'm willing to assume that none of these requests are valid and would reject all unconfirmed user requests. The Problem: How might this activity be happening? Running cat /opt/mailman/core/var/logs/mailman.log | grep POST returns a lot of 202 and 409 responses for `POST /3.1/members`. Could it be that these requests are being submitted through Postorius? I'd assume there would be some sort of honeypot input to prevent abuse. I'll continue investigating and follow up with any insight I can on the cause of The Problem. Thanks, Nick [1]: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>

5 years, 5 months

Can't edit lists anymore: "Something went wrong HTTP Error 404"

by Nils

When I try to edit any list at "postorius/lists/LISTNAME.SUBDOMAIN.DOMAIN.TLD/", I get this error. The lists are displayed correctly at "postorius/lists/". Selecting any of those lists leads to that error. First step of creating a new list is possible but I get the same error right after the creation of the new list. These lines in the mailman.log seem suspicious: Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] Postorius Version 1.3.5 Here are the full logs of this event: mailman3/web/mailman-web.log ERROR 2023-12-29 11:59:30,571 2416033 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get primary_email = set_preferred(request.user, mm_user) File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred mm_user.preferred_address = primary_email.email File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__ super(User, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__ return super(RESTObject, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address response, content = self._connection.call(url, {'email': email}) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ [pid: 2416033|app: 0|req: 9/9] 2003:ca:bf1d:b000:efc2:8dfa:6fd:715f () {72 vars in 1618 bytes} [Fri Dec 29 11:59:30 2023] GET /postorius/lists/testliste.lists.DOMAIN.TLD/ => generated 6285 bytes in 466 msecs (HTTP/1.1 404) 7 headers in 227 bytes (1 switches on core 0) mailman3/mailman.log Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD HTTP/1.1" 200 384 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/owner HTTP/1.1" 200 640 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/moderator HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/config HTTP/1.1" 200 2132 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/archivers HTTP/1.1" 200 61 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/requests?request_type=subscription HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b HTTP/1.1" 200 286 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/addresses/USERNAME(a)DOMAIN.TLD HTTP/1.1" 200 369 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Kind regards

10 months, 3 weeks

Re: Postorius web issues after upgrading mailman 3

by Mark Sapiro

On 10/12/21 8:38 AM, Tibor Molnar wrote: > Hello, > > I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 > I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. > The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated. These are all HyperKitty pages, not Postorius. Did you run all the post-upgrade tasks mentioned at <https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade> after upgrading? Also, it is possible, but not the likely cause of this, that there is an incompatibility between the latest hyperkitty and django-mailman3 in PyPI. See <https://gitlab.com/mailman/django-mailman3/-/issues/48>. You could try ``` pip install -U git+https://gitlab.com/mailman/hyperkitty.git ``` and see if that helps. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: Message-Footer after migrating to Mailman3

by Abhilash Raj

> On Jul 9, 2021, at 9:15 AM, christopher.claus(a)tgcamberg1848.de wrote: > > Mark Sapiro wrote: >>> ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. >>> WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer >>> It appears you created the new template with Postorius, but there is an >> issue for Postorius templates. Possibly your Django setting for >> POSTORIUS_TEMPLATE_BASE_URL needs to be adjusted. >>> Obviously I have a problem with the hostname. I set >>> [code] >>> POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 >>> [/code] >>> where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost >>> [code] >>> wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamberg... >>> [/code] >>> will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? >>> If that works, yes. > > Hi Mark, > > thanks for your reply and excuse my delay. I was very busy in the last weeks but made some tests. Newly created templates with POSTORIUS_TEMPLATE_BASE_URL=http://localhost:8000 did not work. I changed it to my fqdn - at the moment I am able to access the template via this URl (e.G. http://lists.example.de:8000/postorius/api/templates/list/homepage.lists.ex…). > But if I try to send an email I got the following error: You want the URL at which Postorius (postorius) is available from Core (mailman-core container). The default for that in the container images is set to http://mailman-web:8000. Does that not work for you? If you want to verify, you want to exec into the Core’s container (`docker exec -it mailman-core bash`) and see if you can curl the URL from inside there. If you are using the default docker-compose-postorius.yaml then there is a /etc/hosts entry created by docker for the mailman-web container, hence `http://mailman-web:8000` works there (but it won’t work on the host, since docker doesn’t modify the host’s /etc/hosts). There might also be a bug in play here which would cause such connection refused errors when subscribing/unsubscribing when there was a template configured for the list. Is that the case for you or are you seeing always when trying to send the email (which would imply that the Web container simply isn’t reachable from Core). -- thanks, Abhilash Raj (maxking)

3 years, 3 months

Re: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 11:14 AM, Jens Günther wrote: > Just checked again and saw: > > - in the setup it works perfectly in Hyperkitty, that's nice > > - for the first web host I have 2 mail domains registered, so it also > matches (unfortunately) with what you said :-( > > Anyway, I dceleted one of it, still both lists are shown on either web > host, so it's generally not working. I don't know why this didn't work. If there is only one mail host in the domains that has the current web host as its web host, it should work. > If I can do something on this issue, please advise me. Thanks. The issue is that neither Postorius or HyperKitty as a direct way of getting lists by web host as the web host information is not an attribute of the list. We have to see which mail hosts are associated with the current web host and then display only those lists that match one of those mail hosts. The issue with Postorius is if there was more than one mail host associated with the web host, this code https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… could be relatively easily made to work by extending all_lists to include all the mail hosts, but it wasn't clear to me how to fix https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… in the case where there was more than one mail host. If you can suggest a fix, that would help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

error changed after restart (was: KeyError: 'get_requests_count' after an upgrade)

by Guillermo Hernandez (Oldno7)

I restarted de server and the error changed. Now the log shows "KeyError: 'subscription_mode'": ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server Error: /mailman3/mailman3/lists/name_and_domain.of.the.list 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: 'subscription_mode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", line 295, in get member.subscription_mode == File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 124, in __getattr__ self.__class__.__name__, name)) AttributeError: 'Member' object has no attribute 'subscription_mode' *********************** some info about the installed versions via pip list: pip list | grep django django-allauth 0.44.0 django-appconf 1.0.4 django-compressor 2.4 django-extensions 3.1.0 django-gravatar2 1.4.4 django-haystack 3.0 django-mailman3 1.3.5 django-picklefield 3.0.1 django-q 1.3.4 djangorestframework 3.12.2 pip list | grep mailman django-mailman3 1.3.5 mailman 3.3.3 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 pip list | grep postorius postorius 1.3.4 On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > 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? > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 9 months

Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/2/20 8:10 AM, Mohsen Masoudfar wrote: > > This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? You can't upgrade Postorius alone in any configuration because the latest Postorius requires recent Mailman core, mailmanclient and django-mailman3. Depending on how the Debian/Ubuntu package installs these things, it may be possible to upgrade them with pip3, but as I don't know the details of how they are installed in this package, I can't say how to do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Unknown attribute: process_bounces

by Mark Sapiro

On 5/18/21 1:29 AM, xlefloch--- via Mailman-users wrote: > Hello, > > I've upgraded my Mailman installation from those versions: > mailman==3.2.2 > postorius==1.2.4 > mailmanclient==3.2.2 > > To those ones: > mailman==3.3.0 > postorius==1.3.3 > mailmanclient==3.3.2 > > I'm having issues in Postorius in the settings section: Unknown attribute: process_bounces. > When i'm printing the settings list for the concerned list retrieved by the REST API, i'am missing all the parameters related to the management of bounces. In the "mailinglist" table of the Mailman database, i have the columns managing these parameters. > > Anyone have any ideas? Postorius 1.3.3 requires Mailman core >=3.3.1 How did you upgrade?. If this was a package upgrade, your packager has produced an incompatible set of components. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

Postorius not HTML-decoding < to "<" characters

by Ron / BCLUG

Andy Smith wrote on 2024-10-30 20:59: > # Block access to the signup form from Tor exit nodes. > <Location /mailman/accounts/signup> > <RequireAll> > Require all granted > Include /etc/apache2/tor-exit-list.conf > </RequireAll> > </Location> If we look at the above message, there are less-than and greater-than symbols around the Apache keywords in the email as expected. If we look at the archived version of the message, we see a slightly mangled representation: # Block access to the signup form from Tor exit nodes. <Location /mailman/accounts/signup> <RequireAll> Require all granted Include /etc/apache2/tor-exit-list.conf </RequireAll> </Location> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Hopefully I've assigned the blame to Postorius accurately and no formatting nor archiving issues make the issue difficult to understand. Thanks.

2 weeks, 2 days

Re: Postorius admin/user guide

by Odhiambo Washington

On Fri, Nov 8, 2024 at 5:55 PM Florin Pasăre via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hello, > We're trying to update mailman to version 3 from version 2, and I can't > seem to find some non-technical guide for Postorius, something like an > owners manual for all the configurations available in Postorius. > Is there such a thing? > > Thank you, > > Florin > Hi Florin, You cannot "update" Mailman from version 2 to version 3. You will install version 3 and then migrate your lists/archives from version 2 into the version 3 install. That, I think is an "upgrade". The recommended installation method is documented here: https://docs.mailman3.org/en/latest/install/virtualenv.html Once you've completed the installation, you need to create the superuser. The command is: ``` mailman-web createsuperuser ``` The username you create here will be used to log in to Postorius. You can also use the same username/password to login to the Django Admin web UI - https://list-url/admin/ What goes on in Postoirius isn't complex, so do not fear. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 weeks, 3 days

Mailman-users search results for query "Postorius"