Search results for "Postorius" - Mailman-users

nextcloud as auth provider for postorius

by mailman3＠huckley.de

Hello, have anybody successful setup nextcloud auth provider for postorius? I have done configured the OAuth 2.0-Client in nextcloud/index.php/settings/admin/security. I have add the nexcloud as social application in mailman3/admin/socialaccount/socialapp/. If i try to login via nexcloud, postorius redirect me to the nextcloud, where i successful login, and redirected to postorius But i'm not logged in postorius. what I'm missing? Have anybody a howto? Thanks Falk

5 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 3:03 AM, Stephen J. Turnbull wrote: > How different is this from Mailman 2? (Just "not really different" is > fine, I'll be looking at your specific desiderata for more details > later, including potential GSoC tasks.) It seems to me it's basically > the same, except maybe for some Web 2.0 features like sorting on > fields. (I'm not deprecating those features: obviously sorting would > have helped Allan a lot, for example. It's just that Mailman 2 is > very much a Web 1.0, maybe even Web 0.9, application.) Am I missing > something big? I actually took at lot of ideas from the MM 2 Membership List page simply due to the fact that Postorius' was not helpful in inspiring anything. The one thing that I did do is take MM2's approach and modernized it. So here are more tasks a List Owner can do that MM2 could never offer (and Postorius doesn't even come close): -- Sort Members by Delivery mode (regular vs digest). (MM2 has no sorting abilities at all except by alphabet, Postorius doesn't even have that) -- Reveal which Members are registered with the UI (MM2, everyone was registered, in Postorius nothing is revealed about registration) -- Show in one List Member Management panel List Members, Non-Members, Moderators, and Owners (MM2 and Postorius requires this data to be seen via multiple pages) -- View Member's List Subscriptions to other Mailing Lists on the server and, if that List Owner is List Owner of those other lists, can even access the List Owner board (Affinity terminology) for those other Lists. -- Ban a member -- Promote a member to List Owner and/or Moderator -- Add a new List Member, List Owner, Moderator, and Non-Member from a Single List Member Membership panel. (Again both Postorius and MM2 requires multiple pages. Postorius is an improvement in this regard over MM2. The funny thing with Postorius is you can add a single Non-member, Moderator, and List Owner, but you cannot add a single List Member except through *Bulk* adding.) Features are not the only thing about a modern UI, UX design plays a MAJOR role in the modern UI. Postorius should have at least matched MM2 in features in regards to something as important as Member management but instead it took a step back into the dark ages. -- Brian Carpenter Harmonylists.com Emwd.com

3 years, 2 months

Postorius install - missing python modules

by Marco F

Hello, On AlmaLinux 8.7, after Configuring Mailman and Setting up my database (postgres), and hooking up my mailserver (Exim), the instructions proceed to Set up Postorius: https://docs.mailman3.org/projects/postorius/en/latest/setup.html I've tried `pip install postorius`, as well as the latest version, cloning and `pip install -e .`. I've tried with multiple python versions, all with the results: ModuleNotFoundError. Here's highlights of one example: ``` dnf update -y dnf upgrade -y dnf install -y python39 alternatives --config python3 » python3 -V Python 3.9.13 pip3 install postorius git clone https://gitlab.com/mailman/postorius.git cd postorius pip3 install -e . cd example_project ~/postorius/example_project (master)» » python3 manage.py migrate ... ModuleNotFoundError: No module named 'debug_toolbar' » pip3 install debug_toolbar ERROR: Could not find a version that satisfies the requirement debug_toolbar (from versions: none) ERROR: No matching distribution found for debug_toolbar » pip3 install django-debug-toolbar ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel' » pip3 install requests_panel ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel' » pip3 install django-requests-panel ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel.panel' # I tried a bunch of different modules, none resolved the error, finally tried this & it did: » cd $( dirname $( locate requests_panel/panels.py ) ) && cp -pv panels.py panel.py » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_wrapper' » pip3 install requests_wrapper ... » python3 manage.py migrate ... ImportError: cannot import name '_total_seconds' from 'requests_wrapper' (/usr/local/lib/python3.9/site-packages/requests_wrapper/__init__.py) ```

1 year

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Thu, May 13, 2021, at 7:18 AM, Torge Riedel wrote: > Am 03.02.21 um 02:59 schrieb Abhilash Raj: > > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Dear MM3 releasers, > > after successful update to latest versions I realized that Mailman Core > change log links are stable (I requested this some time ago and it was > changed - thanks for that), but Postorius and Hyperkitty change logs do > not have stable header ids. > > Can this be changed too? > > It makes it easier for me (and hopefully for others) when communicating > changes to the users. At the moment they see the upcoming changes for > Postorius first, which always introduces confusion for some of them. > The stable headers are sometimes missed when creating a new NEWS section. There isn't an automation that I've found to add a new section in the news.rst file yet which will do that for me. So I just forget sometimes :-) Adding headers is a trivial thing though. If you find one missing on any project please feel free to submit a MR to fix that. It can be done after the release has been made too. See this[1] that Mark just made to fix it for Postorius. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/636/diffs -- thanks, Abhilash Raj (maxking)

2 years, 11 months

Re: Mass subscribe gives HTTP Error 500 when using custom template

by Mark Sapiro

On 1/28/20 6:15 AM, Jeffrey D wrote: > Hi, > > I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. ... > requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) > > Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. What is your setting in settings(_local).py for POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' It should be the base URL for connecting to Postorius. I.e., if you normally connect to Postorius via https://www.example.com/postorius, it should be https://www.example.com You say Postorius/Mailman is running on port 8001. Mailman core's rest server should be listening on port 8001, but your web server can't proxy to Postorius on that port. Normally, the wsgi server that supports wsgi access to Django (Postorius and HyperKitty) listens on port 8000, at least if it is gunicorn or uwsgi proxied from your web server, or if it's Apache and mod_wsgi, proxying is not involved. Again, it looks like you may be using Apache and mod_wsgi in which case you could have POSTORIUS_TEMPLATE_BASE_URL set to something like https://www.example.com or even http://localhost or http://localhost:80, but not port 8000 if no wsgi server is listening there. Also, the URL is now in the database entry for this template in the postorius_emailtemplate table, so even after you fix POSTORIUS_TEMPLATE_BASE_URL, you'll probably have to delete and recreate the template in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: per domain SITE_ID views?

by Mark Sapiro

On 12/28/21 1:14 PM, David Newman wrote: > Using FILTER_VHOST, I have two domains set up and working with MM3, > Postorius and Hyperkitty. However, because SITE_ID in settings.py points > to one of the domains, that domain name always appears on Postorius and > Hyperkitty pages. ... > How to get the correct domain to appear on that domain's Postorius and > Hyperkitty pages? I don't think the domain is actually displayed on Postorius pages. If I'm wrong, on what Postorius view do you see it? As far as HyperKitty is concerned, please file an issue for this at https://gitlab.com/mailman/hyperkitty/-/issues/new -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

Re: FILTER_VHOST fix - was: Postorius & multi domain

by Gelpi Andrea

Il 23/04/20 01:08, Mark Sapiro ha scritto: > On 4/22/20 11:52 AM, Mark Sapiro wrote: >> >> I'm currently working on a better fix. I'll post here on my progress. > > > I've got a tentative fix at > <https://gitlab.com/mailman/postorius/-/merge_requests/500/>. You can > see the changes there to the file src/postorius/views/list.py. > > This fix is limited in that it should enable FILTER_VHOST work in an > environment where there are domains with web host different from mail > host, but if there are multiple domains with the same web host but > differing mail hosts, going to that domain's Postorius lists view will > show all domains as if FILTER_VHOST is False. > > I.e. consider the following set of domains: > > mail host web host > example.com lists.example.com > example.net example.net > example.org lists.example.org > example.edu lists.example.org > > With the fix installed and FILTER_VHOST = True > > https://lists.example.com/postorius/lists/ will show only the > example.com lists > > https://example.net/postorius/lists/ will show only the example.net lists > > but https://lists.example.org/postorius/lists/ will show all lists, not > just the example.org and example.edu lists. > I saw the change in the file. As I'm not a programmer How can I test your fix? My system was installed via Debian 10 stable repository. I upgrade with testing repository postorius, django and mailmanclinet Postorius V 1.3.2 Django V. 2.2.12 Django filters V 2.1.0 Djanog mailman V 1.3.2 mailmanclient V 3.3.0 Thnak You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

4 years

Re: Customise Postorius templates?

by Abhilash Raj

> On Feb 7, 2022, at 4:35 AM, Duane Raymond <duane(a)fairsay.com> wrote: > > On Mon, 7 Feb 2022 at 00:56, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >>> On Feb 1, 2022, at 11:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> On 2/1/22 09:47, Duane Raymond wrote: >>>> Hi, >>>> I'm looking to do some radical customisation of the Postorius (and >> Hyperkitty) templates over the next 6 ish months and was wondering if there >> is a 'best practice' way to do this that will survive updates to MM3. I've >> searched around and not found much and also tested copying >>>> >> venv/lib/python3.7/site-packages/postorius/templates/postorius/lists/summary.html >>>> to >>>> var/templates/lists/summary.html >>>> As suggested in some posts - but it didn't seem to pick up the >> customisation - only customisations in the venv path worked - and they get >> overwritten on update. > > >> The best way to do this would be utilize Django’s template loader. See >> here[1] for the documentation on how you can do this. You want to put the >> path where you are putting the templates under `DIRS` option of the >> `TEMPLATES` section. >> >> Do make sure that you are keeping the directory structure correct so that >> Django can discover them. Like, Hyperkitty’s base.html should be in >> `/custom/path/hyperkitty/base.html`, where `/custom/path` is what you’ve >> setup in DIRS setting above. >> > I hadn’t tried it when I sent email, but when I tried it locally on Postorius, it seems to work for me. > This looks promising! I've not got it working yet, but this is what I've > tried: > > 1. Created folder 'custom' in the mm root (in my case: /opt/mailman/mm/) > 2. Copied the files and folders from postorius/templates/postorius/* and > hyperkitty/templates/hyperkitty/* to the custom/ folder (not the > full postorius/templates/postorius/ match, just evening in the > second postorius/ dirrectory) Note that you want to copy from “src/postorius/templates” directory to your "/opt/mailman/mm/custom” directory. It is important that you retain the “postorius” and “hyperkitty” directories. Here is what I have in my settings.py: - 'DIRS': [], + 'DIRS': ['/Users/maxking/Documents/mm3/postorius/example_project/templates’], And here is the structure of the templates directory you are seeing above: $ tree /Users/maxking/Documents/mm3/postorius/example_project/templates /Users/maxking/Documents/mm3/postorius/example_project/templates └── postorius └── lists └── summary.html Note that I am only overriding the Summary page here. > 3. Recursive update of permissions of the custom/ folder and files to be > mailman > 4. Updated /opt/mailman/mm/settings.py by changing "'DIRS': []" > to "'DIRS': [BASE_DIR, '/custom/']" in the "TEMPLATES =" section Note that you don’t want [“BASE_DIR”, “/custom/“] here, the comma is the wrong value here. The docs I mentioned have a “/“. Although, it is possible that even “/“ since that needs BASE_DIR to be a Path datatype and not string. Easiest thing with least surprise would be to use the full path, atleast to ensure that template discovery works as expected. > 5. Edited the original AND copied postorius/lists/summary.html to have a > small change in the footer of each so I know what version it is serving Since I was running a dev server, it doesn’t need restart, but simply restarting gunicorn should should do it. You don’t need to restart anything else. > 6. Restarted: gunicorn qcluster mailman nginx and cleared browser cache > 7. Reloaded the 'info' page of a few lists to see which version ti was > serving > > Variants: I've also changed the DIRS value to the hard-coded path: > /opt/mailman/mm/custom > > Result: it is still serving the default/original Postorius template vs the > custom one. > > Any suggestions for things I should do to make it use the /custom/ folder > instead? Any recompiling or other actions beyond just restarting? (I > probably don't need to restart qcluster and maybe not even mailman core for > this to take effect but I do it just in case!) Hope that helps. -- thanks, Abhilash Raj (maxking)

2 years, 2 months

CVE-2021-40347: New security release for Postorius

by Abhilash Raj

Everyone, A security vulnerability was reported against Postorius recently which allows any logged-in user to unsubscribe any other member on any other list on same Mailman installation using a specially crafted POST request due to a missing ownership check. This has been assigned CVE-2021-40347. This affects all past versions of Postorius including 1.0.0. Thanks to Kunal Mehta for the security report and a quick patch to fix the vulnerability. I am also attaching a minimal patch that fixes it along with this email, without tests and NEWS so that it applies to older versions of Postorius easily (I have tested the included patch with 1.3.3, 1.3.2 git tags). Upgrading to 1.3.5 release is highly recommended and it mostly includes the fix for this vulnerability (and a small compatibility fix for django-mailman3 1.3.6) so it shouldn’t introduce any other bugs. You can upgrade to this release by running: $ pip install postorius==1.3.5 A full change log is available here[1] as usual and can be downloaded from PyPI[2]. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-5 [2]: https://pypi.org/project/postorius/1.3.5/ Since there aren't many changes, this release requires 3.5+ like 1.3.4. Although, note that the next release will drop support for 3.5 and will support 3.6 only. For those of you who use container images, I am working on 0.3.12 of container images right now, so look out for that announcement. For those of you using the rolling releases, you can already upgrade to the latest version of the rolling release as it has the fix. -- thanks, Abhilash Raj (maxking)

2 years, 8 months

Re: mailman3 postorius cannot retrieve template at ... (<no authorization>)

by Mark Sapiro

On 10/29/21 3:41 AM, Wolfgang Bock via Mailman-users wrote: > > the question is: postgres - mailman3web-postorius_emailtemplate table vs > mailman3 - templates table > > I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, Core > Python 3.9.2 postgres12 nginx on debian bullseye. > > I created a template via postorius -> lists -> (testliste01) -> templates > -> new template -> [list:member:regular:footer] and > [list:member:digest:footer] > > They are shown in the postgres database mailman3 table templates: > id name context uri username password > 14 list:member:digest:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:digest:footer > 15 list:member:regular:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer > > First there where no templates in the /var/lib/mailman3/templates folder, > which was empty after installation. This is expected. That is one place where you can put custom templates. > Later I created in /var/lib/mailman3/templates theses folders and the files > /list/testliste01.mydomain.de/list:member:digest:footer + > list:member:regular:footer owned by list:list 644 > > A testmail went through but instead of the default footer no footer was > shown. By default Mailman searches for templates first in the var/templates directory and then in the templates directory in the Mailman installation. The details are described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…. However, the default search is only applied if there is matching entry for the template name and context in the `templates` table in the database or if the uri in the entry is a `mailman://` uri. When you create a template in Postorius, that uri becomes something like `https://example.com/mailman3/api/templates/list/<list_id>/<template_name>` which basically says get the template from Postorius, and the template if any in var/templates is ignored. > In the sys.log I found the following error message: > Oct 29 11:28:04 myserver mailman3[33015]: Message: `Cannot retrieve template > at > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer (<no authorization>)` So Mailman is trying to get the Postorius template. What is in the web server logs for this retrieval? > How can I solve this problem? What kind of authorisation is meant? list? > restadmin? > > I read in > https://docs.mailman3.org/en/latest/config-core.html#configure-templates > ... list specific templates invar/templates/lists/LIST-ID/LC/ ... > I guess the LC means Language Code. But in the database table templates no > LC subdirectory is mentioned (in my case must be de). If you delete the Postorius template, The entry in the templates table will be removed and the search will revert to var/templates, etc. > And I read (dont know where) .... The templates created in Postorius are > created in the postorius_emailtemplate table in Mailman`s database and > referenced via URLs like > `https://example.com/mailman3/api/templates/list/<list-id>/<template-name>`. > I.e., they are not stored in the file system. ... > > That`s true. I found in postgres database mailman3web in the table > mailman3web postorius_emailtemplate my > > id name data language created_at modified_at > context identifier > 15 list:member:digest:footer postorius footer digest 1x linefeed > 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list > testliste01.mydomain.de > 16 list:member:regular:footer postorius footer non-digest 1x > linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list > testliste01.mydomain.de > > But my question is how to integrate this into the mailman3-system. The > language isn`t set either. It is integrated. The language isn`t set because you are getting the template from Postorius and Postorius knows the language. On 10/31/21 4:13 AM, Wolfgang Bock via Mailman-users wrote: > regarding my mail before, here an additional information. > > I can show the templates with following command (anonymized): > https://active_domain.de/postorius/api/templates/list/testliste01.active_do… As it should be. > The complete syslog > (edited and reformatted by me) ``` > --- Logging error --- > Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get > contents = protocols.get(actual_uri, **auth) > File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get > response.raise_for_status() > File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status > raise HTTPError(http_error_msg, response=self) > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost/postorius/api/templates/list/testliste01.active_domain.de/… > During handling of the above exception, another exception occurred: > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/__init__.py", line 430, in format > return self._format(record) > File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format > return self._fmt % record.__dict__ > KeyError: `t` > During handling of the above exception, another exception occurred: ``` Your template is malformed. You have $ strings that are not defined as Mailman substitution variables. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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

Mailman-users search results for query "Postorius"