Search results for "Postorius" - Mailman-users

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

To comment my own text, as my typo let it look rude. I meant: I solved it by myself, just by thinking about it for a while again. Stefan Am Mo., 25. Okt. 2021 um 18:06 Uhr schrieb Stefan Bauer <cubewerk(a)gmail.com >: > So i fixed it by myself, just think about it again. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > Note the trailing slash at the end. > After removing it, the webinterface is up again. > But i have no idea, why this is NOW a problem and was not in the past. > Maybe something has changed in the way, apache is handling this now. > > Anyway, problem solved for me. > > Am Mo., 25. Okt. 2021 um 10:45 Uhr schrieb Stefan Bauer < > cubewerk(a)gmail.com>: > >> Dear Users, >> >> I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the >> web-interface via >> >> https://my.mailinglistserver.local/mailman3/postorius/lists/ >> >> I receive >> >> Not Found: /mailman//postorius/lists/ >> [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} >> [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 >> bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core >> 1) >> >> Where does the wrong path come from (mailman vs. mailman3) >> >> After enabling Debug, i see in the browser the following: >> >> >> Page not found (404) >> Request Method: GET >> Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ >> >> Using the URLconf defined in urls, Django tried these URL patterns, in >> this order: >> >> ^$ >> ^postorius/ >> ^hyperkitty/ >> ^user-profile/delete$ [name='mm_user_account_delete'] >> ^user-profile/$ [name='mm_user_profile'] >> ^accounts/ >> ^admin/ >> >> The current path, /postorius/lists/, didn't match any of these. >> >> You're seeing this error because you have DEBUG = True in your Django >> settings file. Change that to False, and Django will display a standard 404 >> page. >> >> My apache configuration is very simply: >> >> # more /etc/apache2/conf-enabled/mailman3.conf >> Alias /mailman3/favicon.ico >> /var/lib/mailman3/web/static/postorius/img/favicon.ico >> Alias /mailman3/static /var/lib/mailman3/web/static >> >> <Directory "/var/lib/mailman3/web/static"> >> Require all granted >> </Directory> >> >> <IfModule mod_proxy_uwsgi.c> >> ProxyPass /mailman3/favicon.ico ! >> ProxyPass /mailman3/static ! >> ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ >> </IfModule> >> >> I dont see where the path gets traversed in the wrong way. Any help is >> greatly appreciated. >> >> thank you. >> >> Stefan >> >

3 years, 7 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

5 months, 4 weeks

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

6 years, 10 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

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

4 years, 11 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.

3 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

2 years, 1 month

Re: combine postorius and hyperkitty into one Apache vhost

by Mark Sapiro

On 12/29/22 12:58, Eggert Ehmke via Mailman-users wrote: > So you prefer Gunicorn over uWSGI? When I have a working installation that > uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason > for this, and while I am open for alternate solutions, ... No, don't change. If uWSGI is working for you, it's fine. I prefer Gunicorn and recommend it for new installations because it's already installed as a dependency of Mailman core, at least if the web UI is on the same machine as Mailman core, and because I think its configuration is simpler than uWSGI. uWSGI does have an advantage in that it can be configured to start qcluster eliminating the need to do that separately. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

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

3 years, 10 months

Re: add custom styles to postorius list creation menu

by mhazan＠mandint.org

Le 2022-05-03 09:44, mhazan(a)mandint.org a écrit : > Le 2022-05-02 17:32, Mark Sapiro a écrit : >> On 5/2/22 06:39, Michael Hazan wrote: >>> Hello, >>> >>> When creating a list via postorius, i can see 3 style appear >>> (announce, discussion, private). Is it possible to either create a >>> new style and add it to that list or modify one of those style ? >> >> >> See this thread >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… >> >> > > Thanks i will look into setting up that plugin, hopefully an easier > way to do that can make it's way to the default install. working on that plugin, i have found where to inserts the various setting, however it's not clear what types and possibles value are excepted for each ? ie "advertised" is bool True/false, but what about "default_member_action" ? i've tried hold 'hold' "hold" all throw error when trying to apply the style. i cannot find the types in the documentation and all the other non bool settings. >>> Also, coming from mailman2, you could directly set the members post >>> moderation action when subscribing, now you can only do it via the >>> user menu, is there a way to automate this in mm3 ? >> >> >> I don't understand what you mean here. In MM 2.1 a member had only one >> setting - moderated yes or no and if moderated there was a list >> setting for the moderation action. There was also a list setting for >> whether new members were moderated by default. How were you setting >> the new member's moderation when subscribing? >> >> You are correct that when subscribing a new member, the member gets >> the default action for members and different action has to be set in a >> separate operation. I don't think this is significantly different from >> MM 2.1. Also, can you describe what you mean by "automate this". > > in MM2.1, if you set the list to moderated and default action to hold > posting, you can set a some member to be un-moderated (mod bit off) to > automatically allow their posting. In the web interface of MM2.1 there > is a checkbox with moderated bit on/off on the member list itself, in > the postorius interface for MM3 you have to open each members settings > page to access that. For automation, as list owner, upon registering a > member (via mass subscription) the possibility to change that ? also > the me too/dupe setting for example. > > Thanks > _______________________________________________ > 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, 1 month

Mailman-users search results for query "Postorius"