Search results for "Postorius" - Mailman-users

postorius ssl-certificates for virtual hosts

by Wolfgang Bock

Hello, On my server are several virtual hosts running with different lists per host. The appropriate webaddress is in general: https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. My domains: [domain-1] starts with a b* [domain-2] starts with a s* [domain-3] starts with a t* If I use the webadress https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… and I do a click on the https-symbol in the address line of my browser I get the secury-information " every thing is ok" and the certificate-information is about the wildcard-certificate I just created for the right domain. Different result is for the webadress https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. In this case I get an information like "you are using a wrong certificate" clicking on the https-symbol references tot he certificate of [domain-1] I set in my apache2 configuration a symbolic link to apache.conf in the /etc/mailman3/directory and made this active. What did I wrong?? If I set use_https to yes in mailman.cfg I get on the website for all lists: postorius: Something went wrong Mailman REST API not available. Please start Mailman core. In the logs I found … mailman.log Nov 14 23:04:25 2019 (28584) command runner started. Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=0&page=1 HTTP/1.1" 200 90 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.0/lists?advertised=true&count=10&page=1 HTTP/1.1" 200 606 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "GET /3.1/domains HTTP/1.1" 200 1438 Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - code 400, message Bad HTTP/0.9 request type ('\x16\x03\x01\x02\x00\x01\x00\x01ü\x03\x03\x00³m\x98¶\x02¨\\Å^\x11£ì{\x94«§*\x 9cÅýÎk\x9f¡ã\x89s/õë') Nov 14 23:20:41 2019 (28590) 127.0.0.1 - - "........ü...³m.¶.¨\Å^.£ì{.«§*.ÅýÎk.¡ã.s/õë .Ô$M...b¥øDR.Ï...G¹PpÖ.'W°û-Óìü¶.>......À,À0..Ì©Ì¨ÌªÀ+À/..À$À(.kÀ#À'.gÀ" 400 mailman-web.log ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call response, content = Http().request(url, method, data_str, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request conn.connect() File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, in connect self.sock = self._context.wrap_socket(sock, server_hostname=self.host) File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket session=session File "/usr/lib/python3.7/ssl.py", line 853, in _create self.do_handshake() File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake self._sslobj.do_handshake() ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1056) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 706, in list_index choosable_domains = _get_choosable_domains(request) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 560, in _get_choosable_domains return [(d.mail_host, d.mail_host) for d in domains] File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 560, in <listcomp> return [(d.mail_host, d.mail_host) for d in domains] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 121, in __getattr__ return self._get(name) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 87, in _get return self.rest_data.get(key) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 76, in rest_data response, content = self._connection.call(self._url) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API [pid: 1405|app: 0|req: 963/963] 2a02:8108:483f:b9c0:94f1:d2bb:9642:b6d0 () {62 vars in 1310 bytes} 22:20:41 2019] GET /mailman3/postorius/lists/ => generated 3901 bytes in 89 msecs (HTTP/1.1 503) 5 headers in 180 bytes (1 switches on core 0)

6 years, 11 months

Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >> >> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >This is not relevant. Does it need resetting back to http://localhost:8000? >> However emails are still coming through with the wrong URL. >I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. Thanks. Andrew.

6 years

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

by Sebastian Hagedorn

Am 27.08.20 um 17:07 schrieb Sebastian Hagedorn: > Am 27.08.20 um 16:41 schrieb 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? > Neither. The browser times out. > ... and when I realized that, I tried a different browser, where it works. Sorry for the noise. FWIW, Firefox isn't working (at least right now), Safari is.

6 years, 2 months

Re: customized welcome message

by Nils

On 12/7/23 18:17, Mark Sapiro wrote: > These messages are sent with `Content-Type: text/plain`. Any html > included in a template will be rendered as plain text. I.e., you can't > include html in templates. I didn't try to include html. It completely ignored the template I've created and sent the html source of the parent domain. Which seems totally random to me. > I see no URI setting in Postorius Settings > Automatic Responses. What > Postorius version is this? Any local mods? It's Postorius Version 1.2.4 installed through the mailman3-web package for ubuntu focal (https://packages.ubuntu.com/focal/mailman3-web) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screenshot_20231207_214025.png Replaced multipart/alternative part with first alternative.

2 years, 11 months

Re: Broken web interface Ubuntu 20.04

by matt＠efs.org

Hi Simon I'm running mm3 on ubuntu 20.04 as well. I don't recall if I saw exactly what you're seeing but it sounds similar. I found that after bootup, mailmain3 would be running fine, but similar to you, I'd get a postorius header but no lists shown on the web UI. I had to restart mailman3-web and it would come up. I assumed it was a startup timing issue and something it needed just wasn't up yet. I don't run production mailing lists so I added a restart post-boot to my startup scripts and this seems to have gone away. Try and restart the service? Matt Sep 30, 2021 06:07:20 Simon Brown <simon.brown(a)eiscat.se>: > Hello, > > Whilst I wasn't looking something has broken the web interface to mailman on > our list server. On the list index page I get the Postorius header, but no > list index, instead a Page not found error. Curiously the Postorius header is > also broken, the links point to > https://host/mailman/(postorius/lists|hyperkitty) not > https://host/mailman3/(postorius/lists|hyperkitty) like it should > > I've poked around and I can't find any useful errors and I don't know exactly > when this happened, but I think it was this week. Mailman itself is running > happily underneath. > > Any suggestions as to what might have gone wrong? > > Simon > > P.S. Hopefully I've got the right list this time. > -- > Simon Brown > System Engineer EISCAT Scientific Association > P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown(a)eiscat.se

5 years, 1 month

Re: Finding a user to delete them

by Stephen J. Turnbull

Quanah Gibson-Mount writes: > But really, the documentation needs to be updated further to point > out the the Django ADMIN INTERFACE as the best way to do user > management, and not the python shell. The Django admin interface is something that most sites are not going to want to expose in addition to Postorius, and Postorius is needed for the users. If you have access to the host (another thing that most sites are not going to want to expose to list owners, who are most relevant to user management), you want to use the Mailman shell, not the Python shell (I assume Mailman shell is what you meant, but other readers may not). The bundled administrative interface *is* Postorius. The Mailman shell is basically a quick hack (sorry Abhilash; if you want to call it a masterwork and say the speed of development is testimony to your skills, I won't deny it ;-) to give more convenient access to internals to experienced Mailman hackers. More administrative features is something we plan to work on, but the Mailman project will focus on Postorius for the forseeable future. For alternatives to Postorius and the Mailman shell, Brian Carpenter (follow Allan's subthread) is working on a new management UI (using PHP), and I believe there's a working node.js API "out there somewhere". Please be very considerate of Brian's time; he and EMWD constitute a bulwark of the Mailman ecosystem and will be even busier with the UI project. But do pass on your suggestions to him as well as to us, he's indicated he's open to that. Steve

6 years, 7 months

Postorius permissions granularity

by Stephen J. Turnbull

Liam Reilly writes: > Is there a way to have more granular permissions in Postorius than > either User or Superuser? Not without additional code. It couldn't be a plugin. It would have to be a fork of the main Postorius code at first (ie, you would be responsible for patching it and merging our public releases, there would not be regular releases). I doubt it would be merged in a near- future release, at least I wouldn't be confident enough to do that myself without beta testing on a branch. I don't think it would be hard to implement a "restricted superuser" role. The annoying part would be figuring out where to apply it, as the "authenticated user", "moderator", and "superuser" roles are implemented via Python "decorators" applied to the functions implementing the various features. And the changes would likely need to be pervasive in page templates, forms, and functional code. > The user permissions that are configurable under /admin/auth/user/ > do not seem to have any effect. As far as I know the only bit that has big effects is "superuser", and there's a "staff" bit that has some effect on the superuser IIRC. Everything else is implemented in Postorius. > We have a helpdesk team that would benefit from being able to > access all list pages in the same way as a Superuser, but without > the ability to accidentally delete the mail domain for example. I almost started on this two years ago, but that customer wanted it for individual lists rather than a helpdesk team, and realized that all the relevant owners would be satisfied with promoting moderators to owner. So it didn't happen. Footnotes: [1] There are several consultants who would be capable of maintenance in the consultant list on the wiki, and more than one who would be able to design and implement the code if you're in a we-want-it-enough- to-pay hurry. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

11 months

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/

5 years

Re: Mailman3 without Hyperkitty in docker

by Danil Smirnov

Hi Abhilash, ср, 27 февр. 2019 г. в 22:21, Abhilash Raj <maxking(a)asynchronous.in>: > So, what errors are you looking at in uwsgi*.log? > There are tons of errors like this: Unknown command: 'qcluster' Type 'manage.py help' for usage. [uwsgi-daemons] respawning "./manage.py qcluster" (uid: 100 gid: 101) Unknown command: 'qcluster' Type 'manage.py help' for usage. [uwsgi-daemons] throttling "./manage.py qcluster" for 26 seconds Do you see any successful requests in mailman core's mailman.log? > Nope, just 'runner started.' entries. Danil > > > With my best regards, > Danil > > > пт, 22 февр. 2019 г. в 09:12, Danil Smirnov <danil(a)smirnov.la>: > > Hi Abhilash, > > Thank you for the quick resolution, but I'm still unable t start the > container: > https://github.com/maxking/docker-mailman/issues/309 > > DB migrations are failing. > > Danil > > вс, 17 февр. 2019 г. в 12:21, Danil Smirnov <danil(a)smirnov.la>: > > 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) > > > -- > thanks, > Abhilash Raj (maxking) > > >

7 years, 8 months

Re: Customise Postorius templates?

by Abhilash Raj

> 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 var/templates directory has a specific structure and is only for custom list specific, domain specific and sitewide templates used for notifications from Mailman core. It has nothing to do with Postorius or HyperKitty templates. > > >> Is there a 'best' way for this? I'd also like to eventually share them with the community and maybe add them to the repo if people want that....but for now I'll start with my own experiments. (and if there is documentation I have missed for this, let me know!) > > > I don't know about a `best` way, but the way I do this is to keep all local mods as patches to the base and apply those patches as part of the upgrade process. 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. One important point to note here is that we can’t promise to not break your custom template in future, because the values passed in the template’s context is not a public or stable API. So, it is technically possible for us to remove/change the variables that are being passed. In practice, I can’t remember when was the last time I removed a variable, so this would work better than patching since you are doing “radical customisation”, which Mark isn’t. [1]: https://docs.djangoproject.com/en/4.0/howto/overriding-templates/ -- thanks, Abhilash Raj (maxking)

4 years, 9 months

Mailman-users search results for query "Postorius"