Search results for "Postorius" - Mailman-users

Re: mailman3 postorius cannot retrieve template

by Wolfgang Bock

Hello Mark, I reconstruct the configuration problems regarding the creation of templates in mm3: I installaed mailman3 via the debian bullseye package(s). BTW: My experience is to install it step by step, not as mailman3-full, but as mailman-3, mailman3-doc, mailman3-web and python3-django-mailman3. In my case the full installation did not run clean, the step-by-step variant run clean. The debian bullseye variant comes with a nginx conf-file in /etc/mailman3/nginx.conf ... # This nginx config file is part of the mailman3-web package. # # This nginx configuration file is a vhost configuration. ... # Nginx SSL snippet. To enable it, please uncomment and update the server_name and the ... server { listen 443; listen [::]:443; server_name mailman.example.com; server_tokens off; # # ## Strong SSL Security # ## https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html & https://cipherli.st/ ssl on; ssl_certificate /etc/letsencrypt/live/mailman.example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mailman.example.com/privkey.pem; # ... The configuration "ssl on" is outdated as nginx -t comments. The actual configuration should be: /etc/nginx/ /etc/nginx/sites-available/nginx.lists.mydomain.ssl (and /sites-enabled) .... server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name lists.mydomain.com; # for example server_tokens off; ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; ... If you - as proposed in the mailman3 nginx.conf - include in nginx.lists.mydomain.ssl the following: .... upstream mailman3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0; } .... you cannot in include this in another vhost-nginx configuration (for example): /etc/nginx/sites-available/nginx.lists.mydomain_2.ssl as nginx -t says something like "no double entries please". So I put this in another file like /etc/nginx/sites-available/nginx.00.mailman3.upstream (and via symlink in .../enabled/...) and both nginx-domain-files work. The debian bullseye also serves a file mailman-web.py with an entry ... POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' ... As mentioned in a mail before that could not work: 1. letsencrypt doesnt serve an entry match for localhost. That floods your syslog. 2. "localhost" doesnt match with the nginx.conf-proposal. It must be something like /etc/mailman3/mailman-web.py .... POSTORIUS_TEMPLATE_BASE_URL = 'lists.mydomain.com/' .... In this combination the creating of templates on the postorius website works. My conclusion: I ask you to consider these experiences in an update for the mailman3 packages in debian bullseye. It would save time, questions and nerves. Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Dienstag, 2. November 2021 23:44 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: mailman3 postorius cannot retrieve template On 11/2/21 3:28 PM, Wolfgang Bock via Mailman-users wrote: > > I get an db-entry in the mailman3 table template which doesnt lead to > a suitable link: > https://localhost/postorius/api/templates/list/testliste01.mydomain.de/list: > member:regular:footer > > In the next stept it leads to a flood of entries in my syslog because > django is asking for a certificate match for "localhost": > Nov 2 11:47:49 myserver mailman3[175334]: Nov 02 11:47:49 2021 > (175334) Certificate did not match expected hostname: localhost. Certificate: ... > > Letsencrypt cannot deliver this match for "localhost", it is > impossible to configurate letsencrypt to do so. > > The running script must create a postgres INSERT database command > which includes the correct domain-name including the correct path > .../mailman3/api/templates .... and not ... postorius/api/.... > > I dont know, where is the place to correct this. > - in mailman-web.py ?? > ... > ALLOWED_HOSTS ... '*' > or > MAILMAN_REST_API_URL = 'http://localhost:8001' > or > POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' If you normally access Postorius on your site at something like https://www.example.com/postorius, than set that as POSTORIUS_TEMPLATE_BASE_URL -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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

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 weeks, 4 days

Re: Postorius: Show only own lists

by Simon Hanna

On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > Imagine an installation with 500+ mailing lists and almost as many local > admins that are supposed to maintain their own local lists with a few local > members. As site admin, I see all 500+ lists, but I was expecting *local* > admins to see only the lists they maintain. I have set all lists to > "advertised = False", so they are hidden from ordinary view. Is there a way > to show only relevant lists to local admins? Are we talking about Postorius or Hyperkitty? There is no way for users that do not have the django superuser permission, to see unadvertised lists in the Postorius list index. I just doublechecked the source. There is an issue about list filtering/search for the index page.

6 years, 10 months

Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Mark Sapiro writes: > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, That's true from "outside", but there are internal links as well. For example, in Postorius top page, the link to HyperKitty is .../archives. I guess it's a good idea to grep the templates to see which URLS are used. > > Now my question is about what could be adding the /mailman3. Is it possible > > that I installed something out of the ordinary? Besides mod_wsgi as Mark suggests and the uwsgi configuration, the only thing I can think of is an Apache rewrite rule. It's not in the Postorius and HyperKitty templates. Steve

1 year, 11 months

Re: Postorius & multi domain

by Mark Sapiro

On 4/22/20 8:14 AM, Gelpi Andrea wrote: > > I search internet for a while and I discovered that using > FILTER_VHOST = True > seems to solve the problem. > >>From posotrius config page: > > FILTER_VHOST > Filter the list of available lists in Postorius and Hyperkitty > depending on the domain they are being currently served from. Mailman 3 > supports multiple domains in a single installation. > > But it doesn't work. I got err 500 form apache. FILTER_VHOST is currently broken unless each domain has the same value for the web and email domains. See the thread at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> and the issue at <https://gitlab.com/mailman/postorius/-/issues/394>. > Were can I find an explanation or a how to configure the system to have > 2 webserver with different domains working on the some server as it was > with mailman 2? If each domain has the same value for the web and email hosts, FILTER_VHOST will work. Currently though if you have domains like web host = lists.example.com and email host = example.com, FILTER_VHOST is broken. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

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.

5 years, 1 month

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

6 years, 10 months

Re: Timeout in Postorius when trying to approve or reject moderated messages

by Brian Carpenter

On 8/27/20 10:33 AM, Sebastian Hagedorn wrote: > In case it matters, I'm trying to moderate the list using the "root" > account. Discarding works, but when I try to either accept or reject a > message, there is a timeout. Is there an error message displaying in Postorius or do you receive an Apache timeout error? When you say root account, do you mean the Django superuser account? Also have you made sure all of the permissions are owned by the mailman user in /opt/mailman? -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

4 years, 2 months

Different Mail Domain Cause Key Error

by Brian Carpenter

I have a client that requires his list address to be list(a)domain.com. But since he is using domain.com for an external website, he has to access his list via Postorius using list.domain.com. So here is what I did: Django Admin Add Site: list.domain.com Add Mail Domain: domain.com (Site selected is list.domain.com) Postorius Add Domain: Mailhost is domain.com. Web Host is list.domain.com (list.domain.com). I have list.domain.com listed in the allowed hosts in settings_local.py. I even added domain.com there as well. When I try to access Postorius using list.domain.com I get a "An error occurred while processing your request." message and the logs shows the dreaded: ``` 'Internal Server Error: /mailman3/lists/ KeyError at /mailman3/lists/ 'file' ``` Did I miss a step here? Thanks, Brian

4 years, 7 months

Re: FILTER_VHOST fix - was: Postorius & multi domain

by jdanitxu＠gmail.com

Hi, we are writing from the NGO Engineering Without Borders - Spain. After having migrated from mailman2 to mailman3 in a server with Debian 11, our domains are like these: https://listas.isf.es/mailman3/ https://listas.andalucia.isf.es/mailman3/ https://listas.aragon.isf.es/mailman3/ ... I have set FILTER_VHOST = True and restarted postorius (systemctl restart mailman3-web), but when we enter in every URL, we see all the lists. Any hint to search? Thanks a lot in advance! P.S: apart from this conversation, I suggest to include in documentation related to migrations the fact that is important to have 'charset': 'utf8mb4' if MariaDB/MySQL is used, in order not to get migration errors doubt to encodings. We had 75 GB of mbox messages and some of them have had trouble doubt to not setting it before.

2 years, 10 months

Mailman-users search results for query "Postorius"