Search results for "Postorius" - Mailman-users

Re: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 6:11 PM, adam.heathcote(a)utas.edu.au wrote: > > mailman members -R owner your_list(a)your.domain > > Shows myself as an owner as well as the imported owners from the previous list. You originally wrote: "but now when clicking on the list, Postorius shows: An error occurred while processing your request." I'm guessing you are clicking the list in the Postorius `Mailing Lists` view, i.e. something like https://example.com/mailman3/ or https://example.com/mailman3/lists, and you are logged in, and the link is to https://example.com/mailman3/lists/listname.example.com. What if you go to that page without being logged in, or logged in as a different user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Re: Upgrading other python packages than the mailman ones in a venv results in dependency conflicts

by Andreas Vetter

On Montag, 16. Dezember 2024 11:52:25 CET Odhiambo Washington via Mailman- users wrote: > On Mon, Dec 16, 2024 at 1:39 PM Ulf R. <ulf.rapphahn(a)offis.de> wrote: > > > > Hello, > > I know this should be the way to upgrade: > > https://docs.mailman3.org/en/latest/upgrade-guide.html > > I have 3.3.10 installed. > > I saw that some python packages are outdated an tried this which install > > all outdated packages in a row: > > pip list --outdated --format=json | jq '.[].name' | xargs -n1 pip install > > -U > > One outdated package was django and this part happened: > > ------------------------------- > > vDownloading Django-5.1.4-py3-none-any.whl (8.3 MB) > > Installing collected packages: Django > > > > Attempting uninstall: Django > > > > Found existing installation: Django 4.2.16 > > Uninstalling Django-4.2.16: > > > > Successfully uninstalled Django-4.2.16 > > > > ERROR: pip's dependency resolver does not currently take into account all > > the packages that are installed. This behaviour is the source of the > > following dependency conflicts. > > hyperkitty 1.3.12 requires django<5.1,>=4.2, but you have django 5.1.4 > > which is incompatible. > > mailman-web 0.0.9 requires django<4.3,>=4.0, but you have django 5.1.4 > > which is incompatible. > > postorius 1.3.13 requires django<5.1,>=4.2, but you have django 5.1.4 > > which is incompatible. > > django-mailman3 1.3.15 requires django<5.1,>=4.2, but you have django > > 5.1.4 which is incompatible. > > Successfully installed Django-5.1.4 > > ------------------------------- > > > > So I made a roll back. > > > > Is this really the only secure way to update the venv?: > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > > Correct! > > > May be yes and I have to ignore the rest? ;-) > > Yes. Let them pull their own versions of dependencies. OK. So what about --upgrade-strategy eager: pip install -U --upgrade-strategy eager mailman postorius django-mailman3 hyperkitty mailman-web Is that allowed/supported? > -- > Best regards, > Odhiambo WASHINGTON, -- Mit freundlichen Gruessen, Andreas Vetter

1 year, 4 months

Re: More Mailman releases!

by Mark Sapiro

On 10/24/23 6:12 AM, Wikinaut wrote: > After installing the last program to be updated (mailman-web), the archives become unavailable due to (again) some glitches with the urls. > I did not(!) change the /etc/mailman3/ configuration files. > > before upgrade, example.com/mailman3/lists/mylist.mydomain (=> worked) > after upgrade, example.com/postorius/lists/mylist.mydomain failed Did example.com/postorius/lists/mylist.mydomain work before the upgrade? Does example.com/mailman3/lists/mylist.mydomain work after upgrade? > Why and who changed my settings? The latest mailman-web upgrade added entries to urls.py. mailman-web<0.0.8 would recognize only the /mailman3/ and /archives/ urls. mailman-web=0.0.8 still recognizes those and now also recognizes /postorius/ and /hyperkitty/ urls. If /postorius/ and /hyperkitty/ urls are not working for you now, the issue is probably in your web server configuration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Re: User settings triggers error

by Mark Sapiro

On 6/16/20 10:34 AM, Mark Dadgar wrote: > If one of my users (including admin) goes to their user drop-down in the upper-right of Postorius and clicks Mailman Settings, it triggers an error: > > > > Here’s the error log: > > Internal Server Error: /mailman3/postorius/accounts/subscriptions/ > > KeyError at /postorius/accounts/subscriptions/ > 'file' The KeyError is bogus. It is an error that occurs in Django's logging when trying to log the real error. > Request Method: GET > Request URL: https://mail.pdc-racing.net/mailman3/postorius/accounts/subscriptions/ ... > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner > 34. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 115. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py" in _wrapped_view > 21. return view_func(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/user.py" in user_subscriptions > 307. memberships = [m for m in mm_user.subscriptions] Here we're trying to grt all the user's subscriptions. Se we call mailmanclient for that. > File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py" in subscriptions > 62. for address in self.addresses: client is getting all the user's addresses > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __iter__ > 221. for entry in self.rest_data: It got the addresses and is now iterating over them. > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data > 197. response, content = self._connection.call(self._url) Which calls the REST API > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) And gets a 500 from core. > During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: Which we aren't interested in. The next step is to look in core's mailman.log to see what the rest call was and the exception and hopefully traceback the caused the 500 response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Postorius Suggestion: Give owner a view of all users of all owned lists

by Stephen J. Turnbull

Andreas Vetter writes: > A list of all addresses subscribed to all lists owned by the logged > in person. This is starting to take a better form. It's still very specialized, so I'm starting to wonder if trying to add it to Postorius is a great idea. Of course if people are coming in over the network, you don't want to reproduce all the authentication and authorization logic implemented in Django and Postorius. That may as well be done in Django, and if you're doing Django it may as well be Postorius too. But if you're in a single sign-on environment so presence in the network implies strong authentication, you will get more flexibility from local scripts using mailmanclient, or if you're confident in security access to the REST API directly. Just putting that out for your consideration, since implementing what is taking shape here would take quite some time as the folks skilled with Postorius are not so active these days. > Owner is the primary target group for that. But since it should be > a tool for managing subscriptions in a simple way, it might also be > of interest for superusers. For me as a superuser it would make > life easier. [...] > Ah, I see the problem and agree: So, the presentation should have a > sorted and searchable list of addresses and a Button next to each > address, maybe labeled "Subscriptions". Looking at your description above, for superusers that is basically the Users tab, though. Users are identified by primary address, and you'd not see alternate addresses in the list. But presumably your internal users use their @your.org addresses as primary. Can you make clear what could be more streamlined for your use cases as superuser? I give one example below, maybe that's what you're mostly interested in. The caveats about access to User objects still apply for owners, so even if they look the same (which is a good UX idea if owner functionality is a subset of superuser functionality, also they might even be able to share the basic page templates), the implementation is going to be rather different. I suspect you superusers would be quite frustrated if using the "subscribe all these lists" functionality meant you couldn't get at the User object without going to a different page. I do see one weird thing: you can't manipulate subscription itself from the User page as seen by the superuser from that list, only toggle moderation and delivery mode. I guess that's reasonable for a lot of use cases, though. I've never wanted to do a subscribe or unsubscribe from there. I always have a long list of users to subscribe to specific lists, never a list of lists a specific user should belong to, > The presentation given when above "Subscriptions" Button is clicked > should contain the address as kind of Headline. Then a table of > all lists of the logged in owner and next to each mailing list an > indication, if the address is subscribed or not and a Button to > toggle subscription/unsubscription. May be a single Toggle Button > or (maybe better) two buttons, a suscribe and a unsubscribe button, > where one is greyed out. This would not work with the current User page as presented to a superuser, that's true. The current presentation is quite suited to its purpose, with sections for Addresses, Subscriptions, Ownership, and Delete User in that order. But especially for superusers, there are plenty of sites with thousands, even tens of thousands of lists, and even a paged or scrollable presentation would be awful UI, and the potential for a disastrous mistake using "do all" is high. > In addition my owners would like to have a "unsubscribe from all my > lists" button. And a "subscribe to all my lists" button. This might > be visually nicer, when having the two-button approach above. I wonder if your owners really want "subscribe all". "Unsubscribe all" does make sense for separations, of course, and they wouldn't necessarily be terminations. It would be useful in an internal transfer where "delete user" is not a solution. But in my experience specialized channels tend to proliferate but the same people are likely to be running them as run the department-wide lisst. > In our case we would want to (un-)subscribe the address in a "do > it, don't ask anyone" fashion, but maybe this is not a good idea in > general. What do you think? I think we would implement it similarly to the mass subscribe for multiple addresses case, where the list owner can decide how much bureaucracy to require of the subscriber. You'd want to be careful to make sure address verification is done at most once (for your use case, probably not at all). And there would be some things that could be done to arrange that most lists would have sensible defaults. > Yes, I agree, but policy here is to get rid of subdomains, and that > falls on our feet now. Well, once we figure out how to implement domain ownership, it wouldn't be hard to adapt that technology to "departments" that are administratively distinct but share mail and/or web domains. The main problem would be deciding whether and how to nest them. Superuser > domain owner > list owner > moderator is pretty obvious, but how "department owner" would fit in is less so.

1 year, 1 month

Re: broken route to accounts

by Thomas Krichel

Stephen J. Turnbull writes > (Note: I usually copy that file to /etc/mailman3/urls.py in case I > make changes. In particular I usually comment out the ^postorius and > ^hyperkitty routes.) But in your case, I don't know what's in > > > | Using the URLconf defined in <code>mailman_web.urls</code>, > > You have to tell us what's in that file. I only now understand that this file is in fact root@darni:/usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py root@darni ~ # ls -l /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py -rw-rw-r-- 1 mailman mailman 1559 Mar 18 08:25 /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py root@darni ~ # md5sum /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py f382f0bc9cea1277c70226b45cf86def /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py I strongly suspect the file is the original file I got from pipping the package. root@darni ~ # cat /usr/local/mailman/venv/lib/python3.13/site-packages/mailman_web/urls.py | grep -v ^# from django.conf.urls import include from django.contrib import admin from django.urls import path, reverse_lazy from django.views.generic import RedirectView urlpatterns = [ path( '', RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True), ), # Include alternate Postorius and HyperKitty URLs. path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), # Order counts for various links. Put the above first and the following # after so the suggested Apache config still works. path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), path('', include('django_mailman3.urls')), path('accounts/', include('allauth.urls')), path('admin/', admin.site.urls), ] ok, I tested your approach, even though I don't know what the ... I am doing, Copying not mailman@darni:~/venv/lib/python3.13/site-packages/postorius/urls.py but mailman@darni:~/venv/lib/python3.13/site-packages/mailman_web/urls.py following guidance of Mark gleaned from https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and added ROOT_URLCONF='urls' to /etc/mailman3/settings.py I can test. The obvious way is to add a route for acocunts. This can be done as an additional line path('accounts', include('allauth.urls')), There are two cases. If I place that line *after* the line path('accounts/', include('allauth.urls')), then on clicking the sign-in button, I get a redirect to https://lists.repec.info/accountslogin/?next=/mailman3/lists/ which 404s. This may give the experts an addition hint where the problem is coming from. Placing path('accounts', include('allauth.urls')), *before* path('accounts/', include('allauth.urls')), seems to finally work, I can login! On the command line mailman@darni:~$ GET http://localhost:4386/accounts/ works and mailman@darni:~$ GET http://localhost:4386/accounts fails. My problem seems to be that I have to customize the installation, even though I have tried as much as I can not to, because the files as pipped seem not to work for me, for reason none of us seems to understand. Cheers to all! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22210th day.

1 month, 1 week

Re: Removing banned emails

by Mark Sapiro

On 08/02/2018 11:47 AM, Kaleb White wrote: > I am trying to remove a banned email with a special character via the rest api and it's not working. It's also not working via the UI. Any ideas? > http://localhost:8001/3.0/lists/example.com/bans/provisor#41@bankofamerica.… > <Response [404]> You can't do it from Postorius (This should be considered a bug in Postorius or perhaps mailman-client). You can do it via rest if you URL encode the request as http://localhost:8001/3.0/lists/example.com/bans/provisor%2341@bankofameric… The issue is whatever client is making the HTTP request is considering '#41(a)bankofamerica.com' to be a fragment identifier so it issues the request for the resource '3.0/lists/example.com/bans/provisor' and expects to find sub-resource identified by '41(a)bankofamerica.com' in the response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Andrew Bernard

Abilash, This is most helpful. But there seems to be an inconsistency, and it goes to exactly the question I am asking. You refer to mailman suite at the top of the file. But I want to follow your advice to use pip. Then after the pip instructions, you talk about the mailman-suite config file for Django. t's exactyl what I _don't_ want. Where is the Django config area for the pip installed modules? It is this that I find obscure. Andrew On Sat, 8 Jun 2019 at 19:53, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > 4. Finally, you need to create config files in right places: > > - Mailman Core's config lives at `/etc/mailman.cfg > > - Django config lives in the django project, mailman-suite. > > I am not going to dive into actual runtime configuration here. > >

6 years, 11 months

Re: MM3 does not receive gmail-Members!

by Mark London

On 4/24/2023 5:11 PM, mailman-users-request(a)mailman3.org wrote: > The Postorius Domains view will show you the SITE_ID for your domain. > In /etc/mailman3/settings.py you probably have > SITE_ID = 1 > Change that to the value from the Postorius Domains view. > If you have more than one domain, you can set > SITE_ID = 0 > and that should show the domain from the http request. Mark - I encountered the same problem and it wasn't clear from the documentation what to do about it. So I eventually changed the name from example.com using the /admin link. But if I now set SITE_ID = 0, and restart the server, it is not happy and tells me it encountered an error. raise self.model.DoesNotExist(django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. I guess I should just let it be set to 1 and be done with it? - Mark

3 years

Mailman3 stopped working after Upgrade to Ubuntu 21.04

by Thomas Möhle

Hey, I have set up mailman3 with mailman3-web on my mailserver and after upgrading to Ubuntu 21.04 my setup stopped working. I can see repeating log entries of mailman trying to reach something within hyperkitty and getting an error. The same constant repeating cycle of log entries is visible in my log files. I have attached my config files as well as the logfiles for mailman3 and mailman-web. As you can see, I'm not really getting many errors, yet within 5 seconds there are almost 2000 lines of log entries where mailman tries to reach something within hyperkitty over and over and over again. One thing I did to create an error message is start up both services, then edit a test list, that I created, in the web interface. This is the error you can find in the logs then: ERROR 2021-08-07 12:50:26,932 2343625 postorius Un-handled exception: HTTP Error 404: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 71, 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 97, 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 127, in call raise HTTPError(url, response.status_code, urllib.error.HTTPError: HTTP Error 404: WARNING 2021-08-07 12:50:26,938 2343625 django.request Not Found: /mailman3/postorius/lists/test.lists.example.com/ Can anyone here help me debug this? I'm working on this problem for days now and can't seem to find a solution. Thanks so much in advance, Thomas

4 years, 9 months

Mailman-users search results for query "Postorius"