Search results for "Postorius" - Mailman-users

Re: Where is postorius.wsgi?

by Timm Stamer

Hi Peter, I use https://gitlab.com/mailman/mailman-suite as WSGI backend for httpd # git clone https://gitlab.com/mailman/mailman-suite.git You have to customize settings.py of mailman-suite before you can start using it. Regards Timm Am Donnerstag, den 25.01.2018, 14:27 +0100 schrieb Peter Münster: > Hi, > > I try to install Postorius, but I don't find the file postorius.wsgi. > Where should I get it please? > > This is, what I've done so far: > - git clone https://gitlab.com/mailman/postorius.git > - cd postorius > - python3 setup.py install > - cd example_project > - virtualenv venv > - . venv/bin/activate > - pip3 install -r requirements.txt > - in venv/lib/python3.6/site-packages/django_mailman3/lib/mailman.py: > replace "urllib2" by "urllib.error" > - python3 manage.py migrate > - python3 manage.py createsuperuser > - python3 manage.py compilemessages > - python3 manage.py collectstatic > > Now I try to follow > https://postorius.readthedocs.io/en/latest/deployment.html#apache-wit > h-mod-wsgi > but I don't find postorius.wsgi ... > > TIA for any help. Kind regards,

7 years, 9 months

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

by Mark Sapiro

On 11/9/24 05:32, ulf.rapphahn(a)offis.de wrote: > 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). Because the mailing lists in the Django admin interface are HyperKitty Lists, not Mailman lists. When you create a list in Postorius or Mailman core, this is a Mailman list. A corresponding HyperKitty list will also be created if hyperkitty is one of the active archivers for the list so you see it in Django. When you create a list in Django, it is only a HyperKitty list and will be visible in HyperKitty, but no Mailman list is created so the list is not in Mailman/Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 3 weeks

Re: nextcloud as auth provider for postorius

by Falk Hackenberger

Hi Jerred, the setting are: INSTALLED_APPS = ( ... 'allauth.socialaccount.providers.nextcloud', ) SOCIALACCOUNT_PROVIDERS = { ... 'nextcloud': { 'SERVER': 'https://website/cloud/index.php', 'EMAIL_AUTHENTICATION': True, }, } the OAuth 2.0-Clients settings in nextcloud are: Name mailman redirection-URI https://website/mailman3/postorius/lists/ Client-Identitifier: XXX Secret **** no errors in the log file. any hints to debug this? thanks Falk Am 01.12.23 um 21:25 schrieb Jered Floyd: > Hi Falk, > > Social logins are mediated by django-allauth. > > Have you configured this properly in your settings.py? (See https://docs.allauth.org/en/latest/socialaccount/providers/nextcloud.html) > > Are there any errors in your mailman logs? > > Regards, > --Jered > > ----- On Dec 1, 2023, at 7:08 AM, mailman3--- via Mailman-users mailman-users(a)mailman3.org wrote: > >> 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 >> _______________________________________________ >> 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… >> >> This message sent to jered(a)convivian.com -- Ochsenweberstr. 43a 22419 Hamburg +49 176 48183883

1 year, 11 months

Re: no access to Postorius web pages after upgrade

by Mark Sapiro

On 10/22/23 10:53, David Newman wrote: > 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" Here you are trying to get https://lists.example.com/postorius/domains/, but (see below) > 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; > } Above you have defined proxying for the paths beginning with /mailman3/, /archives/, /mailman/ and others, but not /postorius/ or /hyperkitty/. Note that /mailman/ will get to Django, but probably won't work unless you have something like ``` path('mailman3/', include('postorius.urls')), ``` or possibly ``` re_path('mailman3?/', include('postorius.urls')), ``` in your urls.py (default mailman_web/urls.py) > 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. This is an issue with MariaDB and MySQL. It can result in more processing because of the lack of an index or possibly a database operation succeeding that should fail because of the unsupported constraint, but these shouldn't affect operation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Error -- postorius Un-handled exception

by Mark

Hi All, I've just installed MM3 on a fresh Debian 12 using the Virtualenv method. (venv)...$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] Postorius Version 1.3.10 After creating a couple of lists, the lists are shown in the table on the "Mailing lists" webpage as they should, but clicking on any of the listnames returns an error page: Something went wrong HTTP Error 500: {"title": "500 Internal Server Error"} And the Mailman log is a mystery to me, and no error is reported in the Nginx log ... # tail -f /opt/mailman/web/logs/mailmanweb.log ERROR 2024-01-24 05:41:46,327 51799 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/postorius/views/list.py", line 359, in get and 'hyperkitty' in archivers # noqa: W504 ^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen _collections_abc>", line 780, in __contains__ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ return self._get(key) ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 88, in _get return self.rest_data[key] ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data response, content = self._connection.call(self._url) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/ ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server Error: /postorius/lists/testing.example.com/ Could anyone steer me in the right direction for fixing this? Thanks, Mark

1 year, 9 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I am pleased to announce new stable releases for Mailman Core, Postorius, > Hyperkitty. > > These include both new features and bug fixes. Complete change log for > each components: > > Mailman Core 3.3.3: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > Postorius 1.3.4 > https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4 : > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Minimum supported Python version is 3.6. > > You can install them using: > > $ pip install --upgrade postorius hyperkitty mailman > I don't know if this is necessary, but I used to do it with another update method documented by Mark. After running the upgrade script (from that method) I would run these too: /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 /opt/mailman/mm/bin/django-admin compress /opt/mailman/mm/bin/django-admin compilemessages /opt/mailman/mm/bin/django-admin migrate Now I did run them and got an error and I wonder if I should be worried: (venv) [mailman3@gw ~]$ /opt/mailman/mm/bin/django-admin compress CommandError: *An error occurred during rendering /opt/mailman/mm/venv/lib/python3.7/site-packages/django_allauth-0.42.0-py3.7.egg/allauth/templates/account/password_reset.html: /bin/sh: sass: Permission denied* Compressing... (venv) [mailman3@gw ~]$ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 5 months

Re: Unable to update templates

by Mark Sapiro

On 5/28/25 01:14, Mark wrote: > > Then I created a template using Postorius and updated the uri in > mailman.templates to: > > file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… - and that works. Which says get the template from the file system at that location and don't ask for it from Postorius at all. This would be the default action if there were no entry for this template in the mailman.template table at all. I.e. you now have a template in Postorius, but it is not used. > It's looking promising. Now I just need to modify my script that > periodically copies the data from the > "mailmanweb.postorius_emailtemplate" table to a file and updates the uri. > > Why it won't handle the templates in the database I don't know. But at > least I can get a work-around solution in place now. If you want to continue to use the template at /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt just delete the template from Postorius and update that file directly. If Postorius template updates don't work because of web server caching or whatever, just don't use them and use templates in the /opt/mailman/mm/var/templates/ hierarchy instead. You can create sitewide templates at /opt/mailman/mm/var/templates/site/en/*, domain specific templates in /opt/mailman/mm/var/templates/domains/en/* and list specific templates in /opt/mailman/mm/var/templates/lists/<list-id>/en/ without any entries in the mailman.template table. Note that sitewide templates can be the most useful and can't be created in Postorius anyway. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months

Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Abhilash, Thank you for the explanation, I've created a report: https://github.com/maxking/docker-mailman/issues/307 Danil сб, 16 февр. 2019 г. в 18:40, Abhilash Raj <maxking(a)asynchronous.in>: > On Sat, Feb 16, 2019, at 4:50 AM, Danil Smirnov wrote: > > 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? > > No, but if you could report the failure and error that you, maybe the > Maintainer can help > fix that issue you have? > > P.S. I maintain those images. The Postorius image is kind of neglected > since there are > fewer people using it, but I'd be happy to fix any error that you see. > > Package ugprades are merely a version number bump in Dockerfile :) > > -- > thanks, > Abhilash Raj (maxking) >

6 years, 8 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

Thanks Mark, On 20/06/2020 03:53, Mark Sapiro wrote: On 6/19/20 4:34 PM, Ruth Ivimey-Cook wrote: I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. What are your Django settings for MAILMAN_REST_API_URL, MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with the [webservice] settings for hostname, port, use_https, admin_user and admin_pass in mailman.cfg in core and is the port open to the outside on the core machine? greyarea-post is the mailman-core and exim server. greyarea-web1 is the postorius and hyperkitty server. On greyarea-web1, in django-settings.py, MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = XXXX and both the above-named hosts are also included in ALLOWED_HOSTS along with localhost. On greyarea-post, in mailman.cfg: [webservice] admin_pass: XXXXX admin_user: restadmin api_version: 3.1 hostname: 0.0.0.0 port: 8870 use_https: no The password and username are as on web1. Do you see REST requests from the Postorius machine in core's mailman.log and access.log? Yes, there are lots of requests of the form: [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" I made a new list using the core CLI, and as a result of navigating directly to the list archive page I get to see: [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" ... but in neither case do I get a complete screen on the browser or 'follow-up' requests. I don't have a file access.log on the greyarea-post. On the greyarea-web1 I have mailmansuite.log with the last few lines: File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba se.py", line 74, in rest_data response, content = self._connection.call(self._url) File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co nnection.py", line 124, in call 'Could not connect to Mailman API: ', repr(e)) mailmanclient.restbase.connection.MailmanConnectionError: ('Could not connect to Mailman API: ', 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection object at 0x7f5416db8518>: Failed to establish a new connection: [Errno 111] Connection refused\',))",),)') ERROR 2020-06-03 01:02:06,115 29002 django.request Service Unavailable: /postorius/lists/ the uwsgi-error_*.log contains many lines of the form: api: url is [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= 1 api: url is [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= 1 My reason for thinking, in my original post, that the wrong host address is being used is that the ConnectionError above contains 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as the listen address on the core web service and does not appear in the config for postorius. I hope this helps, Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: [4]http://www.ivimey.org/blog LinkedIn: [5]http://uk.linkedin.com/in/ruthivimeycook/ References 1. http://greyarea-post:8870/ 2. http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 3. http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page=1 4. http://www.ivimey.org/blog 5. http://uk.linkedin.com/in/ruthivimeycook/

5 years, 4 months

Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 9:39 PM, Abhilash Raj wrote: > > On Wed, Oct 21, 2020, at 3:35 PM, Brian Carpenter wrote: >> On 10/21/20 5:39 PM, Mark Sapiro wrote: >>> On 10/21/20 12:14 PM, Brian Carpenter wrote: >>>> Well I can't dictate that to my list owners and there is no confirm >>>> token sent with the moderation notice. Why include this option in >>>> Postorius when it can't be properly handled? >>> Postorius is still a work in progress. The unsubscription policies are >>> in core and are exposed in Postorius. Certainly the ability to moderate >>> an unsubscription should be in Postorius, but it isn't yet. We are an >>> all volunteer project and there aren't that many of us, and perhaps I'm >>> overreacting, but the tone of some of your recent posts seems a bit >>> demanding. >> I apologize. I didn't think I was coming across demanding but I am >> somewhat exasperated at some of these issues. I have a list owner who is >> now going to get a moderated request notice everyday that he can't do >> anything about it. >> >> But my question still remains: why is this option in Postorius when it >> can't be handled properly? Surely the option can be easily removed, right? > I added the option in my drive to expose every possible Mailinglist settings via Postorius and missed the fact that we weren't actually able to moderate those requests. > > Yes, this option can be hidden if it doesn't work until the next stable release. I hid one of the list settings in Postorius exactly because it didn't work, but this one slipped. Thank you. I will go ahead and remove the option within Affinity. >> Is the ability to list (via the pending moderation notices tab) and >> handle (as in the List owner can decide a moderation response) an >> unsubscribe moderation request there in Mailman core so that I can >> properly address it via Affinity? > Unfortunately no, there is a bug report open for it though and I have some done some analysis on root cause[1]. The bug turned out to be a more than a trivial one and I haven't been able to get to it yet. > > [1]: https://gitlab.com/mailman/mailman/-/issues/768 > > This is good information to have at least so I appreciate letting me know. I probably need to spend more time looking through the outstanding issues for Mailman core and Postorius before launching a nuclear strike of epic and catastrophic proportions upon Mark. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

Mailman-users search results for query "Postorius"