Search results for "Postorius" - Mailman-users

Broken web interface Ubuntu 20.04

by Simon Brown

Hello, Whilst I wasn't looking something has broken the web interface to mailman on our list server. On the list index page I get the Postorius header, but no list index, instead a Page not found error. Curiously the Postorius header is also broken, the links point to https://host/mailman/(postorius/lists|hyperkitty) not https://host/mailman3/(postorius/lists|hyperkitty) like it should I've poked around and I can't find any useful errors and I don't know exactly when this happened, but I think it was this week. Mailman itself is running happily underneath. Any suggestions as to what might have gone wrong? Simon P.S. Hopefully I've got the right list this time. -- Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown(a)eiscat.se

5 years, 1 month

Issues installing postorius and hyperkitty

by thushantha.lakmal＠arm.com

Hi All. Im trying to install the mailmain suite with the postorius and hyperkitty . Mailman installation completed successfully but for postorius and hyperkitty Im getting the following errors .. Please can someone help me .. For postorius (Using pip3 install postorius ) ERROR: django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have django 2.2.6 which is incompatible. For hyperkitty (Using pip3 install hyperkitty ) de41118f448bcb3b8df405c5228e1 Stored in directory: /root/.cache/pip/wheels/79/50/a5/9410f4b2e62e35c285de46ffa88c2562403cb576e1e7859d68 Building wheel for rcssmin (setup.py) ... error ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-491rzr5s --python-tag cp36 cwd: /tmp/pip-install-563o314q/rcssmin/ Complete output (12 lines): running bdist_wheel running build running build_py creating build creating build/lib.linux-x86_64-3.6 copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 running build_ext building '_rcssmin' extension creating build/temp.linux-x86_64-3.6 gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o unable to execute 'gcc': No such file or directory error: command 'gcc' failed with exit status 1 ---------------------------------------- ERROR: Failed building wheel for rcssmin Running setup.py clean for rcssmin Successfully built robot-detection django-haystack Failed to build rcssmin Installing collected packages: rjsmin, django-appconf, rcssmin, django-compressor, robot-detection, django-haystack, djangorestframework, decorator, networkx, django-extensions, wcwidth, blessed, arrow, django-picklefield, django-q, hyperkitty Running setup.py install for rcssmin ... error ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile cwd: /tmp/pip-install-563o314q/rcssmin/ Complete output (12 lines): running install running build running build_py creating build creating build/lib.linux-x86_64-3.6 copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 running build_ext building '_rcssmin' extension creating build/temp.linux-x86_64-3.6 gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o unable to execute 'gcc': No such file or directory error: command 'gcc' failed with exit status 1 ---------------------------------------- ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile Check the logs for full command output.

7 years

Confusing order of checkboxes in Postorius

by Markus Grandpré

Dear list, dear Mailman3 developers, dear Mark Sapiro, in Postorius under "Mass operations / Mass subscribe" we find the order of the checkboxes confusing: 1. Pre confirm 2. Pre approved 3. Pre Verified 4. Invitation We think it would be easier for us and our mailing list administrators to understand the interaction of these settings if they were displayed in the following order: 1. Pre confirm 2. Pre Verified 3. Pre approved 4. Invitation as in our opinion "Pre confirm" and "Pre Verified" belong together more than "Pre confirm" and "Pre approved". Incidentally, a typing error has crept into the term "Pre Verified". It should read "Pre verified". Yours sincerely, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

2 years, 1 month

Re: Confirm and Moderate Unsubscribe Requests

by Mark Sapiro

On 10/21/20 12:14 PM, Brian Carpenter wrote: > > > Well I can't dictate that to my list owners and there is no confirm > token sent with the moderation notice. Why include this option in > Postorius when it can't be properly handled? Postorius is still a work in progress. The unsubscription policies are in core and are exposed in Postorius. Certainly the ability to moderate an unsubscription should be in Postorius, but it isn't yet. We are an all volunteer project and there aren't that many of us, and perhaps I'm overreacting, but the tone of some of your recent posts seems a bit demanding. -- 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: Postorius web issues after upgrading mailman 3

by M4tze

Hi Tibor, I have the same (or a very similar) issue. Have you tried getting jquery-1.11.3.min.js from somewhere on the Internet and move it to <your path here>/static/postorius/libs/jquery/ That fixed it for me. For the docker versions, there is an open issue on this: https://github.com/maxking/docker-mailman/issues/519 Kind regards - M4tze Am 12.10.21 um 17:38 schrieb Tibor Molnar: > 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. > > Regards, > Tibor > _______________________________________________ > 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/ >

5 years, 1 month

Re: Changes in Django admin interface are not syncing to postorius gui /database

by Ulf R.

Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

2 years

Re: Editing a Subscriber's Mailman 3 list Settings

by Mark Sapiro

On 7/1/21 11:08 AM, Terry Earley wrote: > Admin users can edit subscriber's Mailman list settings. Once that > subscriber registers as a user, then only he/she can edit. Admin no longer > has permission to change these settings. > [image: editSubscriberByAdmin.gif] The image removed by this list's content filtering was a partial screenshot of a Postorius member options page with the error message "Cannot convert parameters: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings" What Postorius version is this? I am unable to duplicate this either as a site admin or a non-site-admin list owner with Postorius from the head of the gitlab branch (1.3.5b1). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 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

2 years, 10 months

Re: Django logins for new subscribers

by Alex McLean

On 12 January 2018 at 19:19, Abhilash Raj <maxking(a)asynchronous.in> wrote: > Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well. Ok thanks. From my perspective this is confusing behaviour though, especially for people new to the concept of mailing lists. There are three things to understand in the suite - mailman, postorius and hyperkitty. It seems that hyperkitty is trying hard to be a web forum and actually does a really good job (one reason why we're switching), but postorious links to it as an archive rather than a full interface to the discussion. The default welcome email didn't contain any web links to postorius or hyperkitty. I realise I can change such texts and will spend some time on this. I'd be interested to hear advice from others who have done this sort of thing. > So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins. Yes true. > It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a `get_or_create()` on each one of them (simplest of all approaches, you can ofcourse better ways to do the same). Ok, I'll look into this. Thanks for the https nudge also by the way, it is on my todo! cheers alex

8 years, 10 months

Re: Members (and moderators) can't view the list of members.

by Mark Sapiro

On 11/7/24 13:34, mrl(a)psfc.mit.edu wrote: > I installed Mailman 3 almost 2 years ago. I only now noticed that members of a mailing list can't view the list of members. Even moderators can't see the list. Only Owners. The error message is "You do not have permissions to visit this page." > > Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] > Postorius Version 1.3.8 This is https://gitlab.com/mailman/postorius/-/issues/369 fixed by https://gitlab.com/mailman/postorius/-/merge_requests/770 in Postorius 1.3.9 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Mailman-users search results for query "Postorius"