Search results for "Postorius" - Mailman-users

Re: Rejection Reason for refusing a subscription request

by Mark Sapiro

On 3/27/21 2:08 PM, Brian Carpenter wrote: > I was testing out the process of rejecting an incoming subscription > request. Choosing the reject option for a moderated subscription request > does send out a rejection notice but it gives no reason for the > rejection. ... > Is there a place somewhere in Postorius to provide a rejection reasons > for moderated subscription requests? Does Mailman 3 core provide this > via its REST api but it is just not revealed in Postorius yet? It's in Postorius since 1.3.3. If in the held message view, you click the subject of a held message, you get a popup dialog the shows the message with options to also show headers or the raw message. There is also a dropdown t=o set the poster's moderation action and a box for a reject reason if you click the reject button in the dialog. Do you not see this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: Time Zone Problem In Postorius

by Abhilash Raj

On Thu, May 28, 2020, at 2:02 PM, Brian Carpenter wrote: > I have the server TZ set to EST. I have the TZ for Postfix set to EST. > I have the following set in my settings_local.py file: > > TIME_ZONE = 'America/New_York' > USE_TZ = True > > However messages showing up in the pending moderation queue box shows > UTC date. I am seeing this behavior in Affinity as well so I figured it > is either a Mailman core setting or perhaps database? Can anyone shed > light on that? I think that's because we display as-is values in the UI. Core really doesn't need to be aware of the TZ related info IMO, it is the responsibility of UI (Django!) to record the user's/UIs preferred timezone info and use that with the datetime objects. The offending line[1] for held messages is this, which simply formats the datetime to a specific "format" but we need to also format it to localtime using perhaps [2]. There would be similar values for other places where date time objects are presented in the UI. The change is simple enough, if you can open a ticket, it should be simple enough to fix I think. [1]: https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… [2]: https://docs.djangoproject.com/en/3.0/topics/i18n/timezones/#std:templatefi… > Brian > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

Re: Issues installing postorius and hyperkitty

by Mark Sapiro

On 10/23/19 6:43 AM, thushantha.lakmal(a)arm.com wrote: > 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. How is Django 2.2.6 installed? If you are only using Django for Mailman (Postorius and HyperKitty), just do pip3 install Django<2.2 > For hyperkitty (Using pip3 install hyperkitty ) All of the below is saying that the install of hyperkitty is trying to install rcssmin, that in turn requires building '_rcssmin' extension which requires gcc. Do you have some other C compiler not named gcc? If so, you might be able to work around this by creating a symlink to your C compiler from /usr/bin/gcc, but it would be better to install gcc using apt, rpm, or whatever your package manager is. > > 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

Re: modify subscription page by mailinglist?

by Lars Schimmer

On 10/01/2022 14:14, Stephen J. Turnbull wrote: > Lars Schimmer writes: > > > Is it (easy) possible to modify the subscription page individual per > > mailinglist? > > > > If so, since which version? And how? Is there a guide? > > Not sure which page you have in mind, or how substantial the > modifications you propose are. There are several subscription-related > Django templates under postorius/src/postorius/templates/postorius, > which could be customized to using various Mailman variables known to > Postorius/Django. Not sure where they end up in your installation. Ok, for debian thats /usr/lib/python3/dist-packages/postorius/templates/postorius And I think I could fiddle out how it works. But in general, e.g. a custom page per mailinglist for the "list information page" is a bit more work than expected and I will not follow this idea. (e.g. adding a logo per list, ...) Thank you so far. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

4 years, 8 months

Re: Error -- postorius Un-handled exception

by admin＠bclug.ca

Mark wrote: > After working my way through your suggestions with no joy I discovered > to my embarrassment that I hadn't created the "mailman-hyperkitty.cfg" > file. Once created all was well. I'm having the exact same error, but I already have a file at "/etc/mailman3/mailman-hyperkitty.cfg". After `systemctl restart mailman3.service mailman3-web.service` I'm still getting: > ERROR 2024-04-10 10:19:19,739 104735 postorius Un-handled exception: HTTP Error HTTP Error 500: {"title": "500 Internal Server Error"} > File "/opt/mailman/venv/lib/python3.10/site-packages/mailmanclient/restbase/connection.py", line 161, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR 2024-04-10 10:19:19,744 104735 django.request Internal Server Error: /mailman3/lists/new_test.domain.tld/ > ERROR 2024-04-10 10:19:19,744 104735 django.request Internal Server Error: /mailman3/lists/new_test.domain.tld/ > ERROR 2024-04-10 10:19:19,745 104735 django.server "GET /mailman3/lists/new_test.domain.tld/ HTTP/1.0" 500 8667 Anyone have suggestions? (venv) mailman@mail:~$ GNU Mailman 3.3.9 (Tom Sawyer) Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg

2 years, 5 months

Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://www.example.com/postorius/lists/ you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://www.example.com/postorius/lists/?role=owner and if you are a member as well as owner of an unadvertised list, you will see it at https://www.example.com/postorius/lists/?role=member. But (here's the tricky part) if you go to https://www.example.com/postorius/lists/?all-lists, you will not see any unadvertised lists, not even ones you own. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Re: Error while mass operation, no progress display while mass operation is running

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/6/25 04:53, Markus Grandpré wrote: > > Unfortunately, I have not found any error message in the log > > files. > > If you are using uWSGI, a harakiri timeout should be logged in uWSGI's log. I think gunicorn logs to access.log and error.log in the Mailman logs directory. I would think it would log 500 level events, that indicates server trouble. > > Regardless of whether a mass operation process runs without errors or > > continues to run despite an error, I find it hard that Postorius does > > not display the progress of such a mass operation in order to monitor > > the process, as mass operations with more than 1000 members are very > > time-consuming. Perhaps this could be changed in a future version of > > Postorius? > > This is a reasonable request. The best place for such a request is > https://gitlab.com/mailman/postorius/-/issues/new It's reasonable, but for unsubscribe Postorius invokes the mass remove REST API. So to report progress there it would require new code in Mailman and mailmanclient to report progress, or Postorius could use an explicit loop over addresses as mass subscribe does -- which would be noticably slower, I suspect. Periodic heavy use of mass operations is a common use case at universities. It's not uncommon for each term to see thousands of list averaging scores of subscriptions or unsubscriptions, with both number of lists and average roster size spike at academic year transitions when departmental and university-wide lists turn over. We should look at speeding up mass operations. I suspect internally Mailman is looping over individual addresses, probably creating a separate RDBMS transaction for each one. It should be possible to batch these, allowing the RDBMS to optimize its own table locking. Perhaps for the university use case it would make sense to even have Mailman multiplex these transactions across multiple lists being accessed at the same time. Steve

1 year, 7 months

Re: How to upgrade to 3.10

by Mark Sapiro

On 3/8/26 10:25, Paul Tomblin via Mailman-users wrote: > > > On Sat, Mar 7, 2026, at 11:08 PM, Mark Sapiro wrote: >> >> Do you have the latest Postorius from GitLab? > > I missed that step at first, but now I've done it, I see no change. It still says version 1.3.13, and the Edit Domain page still just has Description, Alias Domain, and Web Host. > > When I was installing it, it said it was this commit: > Resolved https://gitlab.com/mailman/postorius to commit 2c0c3aeb905c82ee4d6724897b89def71c02c1ef > which does appear to be the latest. That should be good. It will say 1.3.13 as the version hasn't been updated in GitLab. Is an old page cached somewhere? Have you tried clearing browser cache or a different browser or depending on browser and platform ctrl+reload or shift+reload. Does your /opt/mailman/venv/lib/py<version>/site-packages/postorius/forms/domain_forms.py match <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/forms/doma…>? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 2 weeks

Re: Unwanted E-mail to Maillists Submitted via Postorius Interface

by Matthew Alberti

Well, I actually received what appears to be a SPAM response to my original email post. No joke. If mods want a copy of it, let me know. Matt Alberti ⁣Get BlueMail for Android On Aug 25, 2021, 7:43 PM, at 7:43 PM, matthew(a)alberti.us wrote: >Hi Everyone, > >I’ve seen a recent uptick in SPAM messages making it into mailing >lists. Looking at the raw, it seems that the e-mails are being >submitted thru the Postorius/Hyperkitty “Start a New Thread” interface. >Is there a way to turn that off? We would want people to only be able >to post via e-mail. Part of the problem is that our anti-spam system >RSPAMD trusts the mailman-web IP… so it doesn’t scan things originating >from there.. ☹ > > > >Another uestion: Is there a way to implement captcha, or is there a >recommended gate that can be put in the signup process? Apparently bots >are finding a way thru the signup process, and then sending messages to >the list via the Postorius web interface. There seems to be a Django >plugin for it; but it appears the Mailman code would have to be >adjusted to implement it. > > > >I’m open to any suggestions, including on places to check for >misconfiguration. 😊 > > > > Thanks. > > > >- Matt Alberti > >_______________________________________________ >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

Re: Subscription requires confirmation when list is set as Open

by Mark Sapiro

On 12/18/24 18:22, Joachim Schrod wrote: > Mark Sapiro writes: >> >> It is not the subscription that requires confirmation. It is the user's >> email address. Even though the list's subscribe policy is open, a >> previously unknown email address has to be confirmed. > > I assume that's the verification that one can turn off in Postorious > `Mass Suscription' with the checkbox "Pre Verified". That is correct. > I maintain a mailing list for a private holiday where people don't > subscribe themselves; I subscribe them. I have vetted their email > address beforehand. (The subscribers are mostly not able to handle a > verification email, nor any email-based workflow at all.) Is there a > configuration option for a mailing list that sets "Pre Verified" to > true as a default? This is https://gitlab.com/mailman/postorius/-/issues/563 it was fixed by https://gitlab.com/mailman/postorius/-/merge_requests/930 which was later extended by https://gitlab.com/mailman/postorius/-/merge_requests/945 however these are not available until Postorius 1.3.14 which is not yet released. These add a setting, POSTORIUS_DEFAULTS, which can be used to set these defaults. E.g., setting POSTORIUS_DEFAULTS = {'mass_subscription_pre_verify': True} will set the default for Pre Verified to True. So far, the only defaults that can be set in this manner are mass_subscription_pre_confirm, mass_subscription_pre_approve, mass_subscription_pre_verify and mass_subscription_invite and those not until Postorius 1.3.14, but more may be added. -- 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

Mailman-users search results for query "Postorius"