Search results for "Postorius" - Mailman-users

Re: [Mailman-Developers] Countdown to the 3.1 release

by Barry Warsaw

On Jul 13, 2016, at 12:18 PM, Simon Hanna wrote: >I guess https://gitlab.com/mailman/mailman/issues/219 should be fixed in >the next release. If 3.1 find its way into repositories, we will get >lot's of issue reports for this I suppose. Thanks Simon. I've put this in the 3.1 milestone and will take a look. >Terri was working on this one, it's not critical but nice to have for >usability >https://gitlab.com/mailman/postorius/merge_requests/159 ack. >I have a mr pending for mailmanclient that should be included in the >next release >https://gitlab.com/mailman/mailmanclient/merge_requests/10 I've added a 3.1 milestone to mailmanclient and assigned this one to it. >Postorius has a number of merge requests open. I'm not sure which of >them should be merged before the next release Florian, do you have time in the next few weeks to do some Postorius triaging? >Does your template branch in core need any immediate modifications to >mailmanclient and/or postorius? It shouldn't, at least for API 3.0. All the new template APIs are exposed on v3.1 only, and when using the v3.0 API, they should map the old attribute names to the new mechanisms, so it should all be transparent. Modulo bugs of course. ;) I think it would be nice if mailmanclient and/or Postorius used the v3.1 API to get the full power of the templates branch, but it's probably not critical for the current release. Flo and I did talk about adding a cli that Postorius could call when installing it next to a v3.1 Core, e.g. to install some default templates for a cohabitating Postorius, but on further thought, it would be just as easy to write a bit of Python code to install those templates. Note though that someone would have to write the templates and ship them with Postorius, but they could be done using file: URLs into the Postorius install directory. That would be a fun project for someone to tackle, and I'd be happy to answer any questions that come up. Cheers, -Barry

9 years

Re: Postorius no connection to REST API

by Guillermo Hernandez (Oldno7)

Sorry, it lacked a few lines: On 9/8/21 19:14, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > ####### start of /usr/local/mailman3/apache24.uwsgi.conf > > Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico > Alias /static /usr/local/mailman3/static > ######### > # for hyperkitty > Alias /static/admin /usr/local/mailman3/static/admin > Alias /static/CACHE /usr/local/mailman3/static/CACHE > Alias /static/django_extensions > /usr/local/mailman3/static/django_extensions > Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty > Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty > Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 > Alias /static/rest_framework /usr/local/mailman3/static/rest_framework > # for postorius > Alias /static/postorius /usr/local/mailman3/static/postorius > Alias /static/archives /usr/local/mailman3/static/postorius > ##### > > ###ErrorLog /var/log/httpd/hyperkitty_error.log > ###CustomLog /var/log/httpd/hyperkitty_access.log combined > > <Directory "/usr/local/mailman3/static"> > Require all granted > </Directory> > #### WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> > ######## end of /usr/local/mailman3/apache24.uwsgi.conf

3 years, 11 months

Re: New release candidates for Postorius and Hyperkitty

by Abhilash Raj

+cc: mailman-usersmailman3.org for more visibility. On Sat, Jan 16, 2021, at 2:20 PM, Ruth Ivimey-Cook wrote: > Hi, > > Is there a recommended method for upgrading an existing, running, server > from Python 3.6 to 3.8, especially in such a way as to enable downgrade > if something breaks? It depends on how did you install Mailman. If you installed using virtualenv, you can create another virtualenv and install new versions, that use the same configuration and switch between new and old versions, > > [When I upgraded a server distribution without enough preparation, it > broke mailman3 because I lost python3.6, and getting it working again > needed a lot of work to reinstall it without zapping needed state.] > > Regards > > Ruth > > > On 16/01/2021 20:38, Abhilash Raj wrote: > > Hey Everyone, > > > > Happy new year to everyone! > > > > I am pleased to announce new release candidates for Postorius and Hyperkitty along with new releases for Mailmanclient and Django-mailman3! > > > > These include both new features and bug fixes. Complete change log for each components: > > > > Postorius 1.3.4rc1: https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4rc1 : https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Mailmanclient 3.3.2.: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > Django-mailman3 1.3.5: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > > > Since these are pre-releases, you can install them using: > > > > $ pip install --pre --upgrade postorius hyperkitty > > > > Or you can also specify the exact versions: > > > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > > > Unless there is a release-blocker bug, stable versions for Postorius and Hyperkitty will be released in 2 weeks time. If you can test these releases, we encourage you to report any bugs to us on Gitlab. > > > > If you'd like to help out with translations for some of the new strings in your native language, the documentation is available here[1] on how to do that. > > > > [1]: https://docs.mailman3.org/en/latest/translation.html > > > -- > Software Manager & Engineer > Tel: 01223 414180 > Blog: http://www.ivimey.org/blog > LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/ > > -- thanks, Abhilash Raj (maxking)

4 years, 6 months

duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

Hi I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: client.create_domain(name) Is this a bug? Or did I mess something up? What significance do those SITE_IDs have? What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Thanks! Stanisław

3 years, 4 months

Re: adding imprint / private policy link to postorius

by Thomas Stein

Thanks Abhilash. Will have a look. On 2020-09-03 07:09, Abhilash Raj wrote: > On Tue, Sep 1, 2020, at 11:17 PM, Thomas Stein wrote: >> >> Hello one and all. >> >> Is it possible to add an imprint link to the postorius start page? I >> guess it is, but it would be >> nice if someone could me point to the right direction / documentation. >> Something like they have: >> >> https://lists.openrailwaymap.org/mailman3/postorius/lists/ >> > > There isn't an official way to do that, but you can patch your > installation to update the footer. > > This[1] is the location and file you want to update and you can insert > simple HTML there. If you are using system packages it should be > somewhere in the `/usr/lib/python3/dist-packages` directory and > in `lib/site-packages` if you are using a virtualenv based > installation. > > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… > >> cheers, t. >> _______________________________________________ >> 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/ >>

4 years, 10 months

combine postorius and hyperkitty into one Apache vhost

by Wolfgang Rosenauer

Hi, I'm in the process to set up a new mailman3 site. (Migrating from mailman2) There are RPMs for my distribution which integrate postorius and hyperkitty with uwsgi. The provided samples assume that both are running in different vhosts what I would like to avoid. Since I couldn't find any uwsgi examples for that I'm experimenting heavily but still having issues. I might just miss a simple thing (hopefully). My current apache config: Alias "/mailman/static" "/srv/www/webapps/mailman/postorius/static" ProxyPassMatch ^/mailman/static ! ProxyPass /mailman unix:/run/uwsgi/uwsgi-postorius.sock|uwsgi://localhost-postorius/ Alias "/archives/static" "/srv/www/webapps/mailman/hyperkitty/static" ProxyPassMatch ^/archives/static ! ProxyPass /archives unix:/run/uwsgi/uwsgi-hyperkitty.sock|uwsgi://localhost-hyperkitty/ This currently assumes that postorius just gets a mailman/ prefix and hyperkitty archives/ This setup immediately fails because of the urlpatterns filter in these components. For testing purposes I changed the patterns in urls.py slightly and I could make it work for me. BUT: This cannot be the solution, can it? Isn't there an easier way to allow these components to run under a different document root? Something slightly unrelated but causing issues in some edge cases also is that Django? does not detect the request url properly. For some functionality e.g. when I want to login to Django admin under /archives/admin (even after modifying urls.py) I get a redirect after the form which shows that my initial path was not recognized as /archives/admin but /archive//admin instead. So the last character is replaced with a / Any hints for me? Thanks, Wolfgang

2 years, 6 months

Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi, I'm interesting in Mailman3 deployment with archiving feature completely disabled. I've tried to deploy Core + Postorius using this docker-compose template: https://github.com/maxking/docker-mailman/blob/master/docker-compose-postor… Unfortunately Postorius version came with this template is quite outdated: 1.2.0a1 (as reported in page footer). In Hyperkitty-enabled docker image I see version 1.2.3. I've also checked image maxking/postorius:rolling but it seems irrelevant/broken (container exits with error). Are there newer Postorius docker image I can use? Thanks, Danil Smirnov

6 years, 5 months

Re: postorius only show 50 owner lists

by elalelopez＠gmail.com

Hello, thanks for answering. The DB is postgresql. And it's not a paging problem. The paging buttons are disabled because I am trying to see all the owner's lists. I understand that postorius executes the list_index_authenticated function in postorius / views / list.py The description of the function shows: "" "Index page for authenticated users. Index page for authenticated users is slightly different than un-authenticated ones. Authenticated users will see all their memberships in the index page. This view is not paginated and will show all the lists. "" " Regards.

6 years, 4 months

Re: "Unsubscribe all" failed with large lists

by Alan So

Thanks. We are still using Postorius 1.2.4 and Mailman core 3.2.0. However, there is no such issue. Is this specific to Postorius 1.3.x or a result of using together with Mailman core 3.3.2? Postorius 1.2.4 is probably not using mass-unsubscribe API. We are planning to upgrade Mailman core first to solve another issue and upgrade Postorius a bit later.

4 years, 6 months

Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, You were (of course), absolutely on target, thank you! I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. I have searched on the file system for any such templates and only see the default ones; all zero length files. There are no templates defined for the domain in postorius – but if there were, I’d expect to see that test header all the time. I’m just baffled. Any clues? I’m a relative newbie to mailman3. When I first set it up, I tried the postorius templates for the domain. They didn’t work (had to have been due to the POSTORIUS_TEMPLATE_BASE_URL being wrong. So, I scrapped that and went with templates in the file system. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 3:46 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

5 months, 2 weeks

Mailman-users search results for query "Postorius"