Search results for "Postorius" - Mailman-users

Re: postorius not displaying mailman logo

by Andrew Hodgson

sekamug--- wrote:Sent: 22 March 2022 09:34 >I successfully installed mailman3 but Postorius doesn't display images on the web interface. I have checked and the files exist at at the location /opt/mailman/web/static/postorius i have checked the logs and they appear as follows: >[pid: 366783|app: 0|req: 43/104] () {34 vars in 687 bytes} [Tue Mar 22 09:36:30 2022] GET /static/postorius/js/script.js => generated 5280 bytes in 43 msecs (HTTP/1.1 404) 6 headers in 197 bytes (1 switches on core 0) >[pid: 366783|app: 0|req: 44/105] () {34 vars in 715 bytes} [Tue Mar 22 09:36:30 2022] GET /static/postorius/img/favicon.ico => generated 5280 bytes in 43 msecs (HTTP/1.1 404) 6 headers in 197 bytes (1 switches on core 1) it seems the browser fails to access the directory where the pictures are stored. I >have checked and mailman is the owner of that directory. >Please advise. The process that hosts the Postorius/Hyperkitty content from Python doesn't serve static pages. In most cases you need to run a reverse proxy which is capable of serving static content as well as to proxy out to the service hosting those Python apps. Hope this helps. Andrew.

2 years, 8 months

Set Postorius interface locale

by Duane Raymond

Hi everyone, Thanks to Brian I'm up and running with my migrated mailman3 lists and am now starting to get into customising the interface (styling and content). I've been trying to figure out how to set/change the Postorius locale - I specifically want to change some text strings on the info page without breaking the i18n mechanisms. I've worked with po and mo files before, so changing and compiling them isn't a problem. The problems I've encountered so far are: 1) Where do I set the local of the Postorius interface? 2) Individual lists have a language setting, but it doesn't seem to reflect what the Postorius locales are as the only english option is "English (USA)" and none of the other English speaking locales and on the file system there is no en-us PO files....so I suspect I'm looking in the wrong place. Am I looking at this all wrong? The documentation doesn't seem to have any info about this and yet the mechanisms seem to be there. Once I learn more I'm quite keen to start working on improving the documentation based on what I learn. Cheers, Duane

3 years, 8 months

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

by ulf.rapphahn＠offis.de

Hello, I have the lasted version of mailman3 in an fresh venv installation and I am testing it for our upcoming migration from v2.1. When I add a new list in the django admin interface this list will never appear in postorius (vice versa it works). The new list is also not in both databases: SELECT * FROM mailman.mailinglist; SELECT * FROM mailmanweb.hyperkitty_mailinglist; (Why two databases are needed with redundant data?) The same when changing for example the description of an existing list in the django admin interface it doesn't change the description of the list in postorius. Vice versa it works. Changes made in postorius are also seen in django. Could please someone help me or explain this behavior? I hope it is a problem with my configuration. Thank you and regards, Ulf

2 weeks, 2 days

no access to Postorius web pages after upgrade

by David Newman

Upgrading to MM3 3.39, Postorius 1.3.10, Hyperkitty, 1.3.8, Django-mailman3 1.3.11, and Mailman-web 0.0.8 in a venv all seemed to go OK. Mailman3 lists work as expected, and admins can log in via Django. However, any attempt to reach lists, domains, users, etc. now returns a 404 Not Found error. All the Postorius stuff worked as expected before the upgrade. In the nginx server logs, any Hyperkitty and Postorius URLs are now appended to /opt/www/roundcubemail, which is this web server's root directory but not the root for Mailman3 (I run Roundcubemail and MM3 on the same server; don't judge me :-). Here is the nginx error, with obfuscation of client and server info: 2023/10/22 10:43:24 [error] 2264140#2264140: *135 "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: No such file or directory), client: 1.2.3.4, server: lists.example.com, request: "GET /postorius/domains/ HTTP/2.0", host: "lists.example.com", referrer: "https://lists.example.com/mailman3/listinfo" And here are the relevant bits of the Nginx config. Again, this worked before the upgrade. server { listen 443 ssl http2; server_name lists.example.com; root /opt/www/roundcubemail; # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff } Also, I'm not sure if it's relevant but after upgrading, the migrate command throws a warning like this: (venv) mailman@mail10:~$ mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks in advance for clues on getting all Postorius/Django links working again. dn

1 year, 1 month

Postorius -owner messages

by ssehi＠nebraska.edu

I manage a number of lists for non-technical users that are considered owners of their own lists. Some of them have expressed that they would like to emulate some other mailing list services' "Quiet" owners for people that need to be able to access the list settings for administrative reconciliation as well as a fallback, but want to leave subscription requests or approval of messages to others that are more involved in the day-to-day management. They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? Thanks, Sam

1 year, 5 months

Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Mark Sapiro

On 9/30/23 15:23, Wikinaut wrote: > After having changed and re-changed "only" the line in /etc/mailman3/mailman-web.py (which looks to be only a "blinder" and the real problem could be a different one) > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' This should not include the mailman3/ path. If http://localhost/mailman3/ gets to Postorius, it should just be 'http://localhost/'. > the web access via Postorius is not working any more and throws "Error 500" > > My logfile /var/log/mailman3/web/mailman-web.log shows now > ...> from django.utils.encoding import force_bytes, force_str, force_text > ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) > > I already run pip install -U postorius to update that (looks okay to me): > > Requirement already satisfied: postorius in /usr/local/lib/python3.9/dist-packages (1.3.8) ... > Requirement already satisfied: django<4.2,>=3.2 in /usr/local/lib/python3.9/dist-packages (from postorius) (4.1.9) ... > dpkg -l | grep django > ii python3-django 2:2.2.28-1~deb11u2 all High-level Python web development framework Something is confused here. Your Django version from dpkg is 2.2.28, bit from your above `pip install`, it is 4.1.9. I'm not sure haw the Debian package installs, but probably in a venv. > ii python3-django-q 1.2.1-1 all Django multiprocessing distributed task queue (Python 3 version) I don't know what the django-q version in the venv is, but Django >=4.0 requires django-q >=1.3.0 If The Debian backage includes Django>=4.0 and django-q<1.3.0, it's a Debian packaging issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 12/14/22 13:40, Jeremy Stanley wrote: > > Once these entries are automatically added by visiting that page, > they're all associated with the one "web host" ("site" in Django) we > have for the server, and now the list filtering functionality in > Postorius breaks and any of the vhosts all display the full set of > mailing lists on the server rather than only those associated with a > particular vhost (note that this seems to only be confusing > Postorius, Hyperkitty has them correctly filtered still). See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and also below. > Okay, so it looks like this is because the mail hosts are all tied > to the one web host. Yes. > We can create additional "sites" in the Django > admin UI and then switch the association of the mail hosts to those > distinct web hosts. But after doing so, the first vhost still seems > to show an unfiltered list of all lists in Postorius (Hyperkitty > continues to be fine), while Postorius on the other vhosts correctly > shows their filtered sets of lists instead. > > I also noticed when mailman-web is starting up, its log claims the > first site is being set as the "default domain," so have to wonder > if that's related to this behavior. Should we create an extra web > host to serve as the "default" so that all our typical vhosts get > the expected list filtering behavior, or am I completely off-base > and there's a much better approach I've missed? I'm not really sure what's going on here. You could try creating a dummy default host to see if that fixes the issue for you. There are subtle differences in the implementation between HyperKitty and Postorius that allow HyperKitty to work better, but it too will exhibit some anomalous behaviors. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: templates

by Christian

In March when I started troubleshooting my lists, you stated: "Also, one other thing you might check. Do these non-working lists have templates defined in postorius, in particular, one for list:member:regular:footer, and if not, are there any in Mailman's var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that Mailman doesn't have permission to find and read?" There are no other templates listed in either Postorius nor in Mailman's var/templates (as I stated, I do not even lave a 'lists' subdirectory under Mailman's var/templates). My subscribers are not receiving message distributions from my lists, even while some of them are listed in the archives. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, May 4, 2023 10:58 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/4/23 10:33, Christian via Mailman-users wrote: > I'm having issues with my lists. For each list I have created a > template [ list:user:action:subscribe ]which has a prospective > subscriber have to consent to list rules before they are subscribed. > This template I created is listed in Postorius for each list. I have > noticed that there are no other templates listed in Postorius. Furthermore, there is no 'lists' > subdirectory under Mailman's var/templates/. When you set a template in Postorius it saves it in the postorius_emailtemplate table in the database and tells Mailman core to get the template from Postorius via a URI to a Postorius API. -- 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ This message sent to csa(a)web-analysts.net

1 year, 6 months

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

8 years, 4 months

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, 3 months

Mailman-users search results for query "Postorius"