Search results for "Postorius" - Mailman-users

Confusing order of checkboxes in Postorius

by Markus Grandpré

Dear list, dear Mailman3 developers, dear Mark Sapiro, in Postorius under "Mass operations / Mass subscribe" we find the order of the checkboxes confusing: 1. Pre confirm 2. Pre approved 3. Pre Verified 4. Invitation We think it would be easier for us and our mailing list administrators to understand the interaction of these settings if they were displayed in the following order: 1. Pre confirm 2. Pre Verified 3. Pre approved 4. Invitation as in our opinion "Pre confirm" and "Pre Verified" belong together more than "Pre confirm" and "Pre approved". Incidentally, a typing error has crept into the term "Pre Verified". It should read "Pre verified". Yours sincerely, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

6 months, 2 weeks

Re: Confirm and Moderate Unsubscribe Requests

by Mark Sapiro

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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

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

by Ulf R.

Thank you (also for Odhiambo) Now remains one question: We have a (internal) Active Directory (AD) Authentication for Mailman3. So everyone who wants to work as an owner nor moderator must be an AD-User. In hyperkitty I am able to assign these list rights directly to AD-Loginnames. With the logic above I have to assign these rights in postorius too by assining the mail address of the users AD-Account? (I see no AD-Data here). Or would it works to assing the mail address of the users AD-Account first an then the allocation will automaticly synced to hyperkitty - maybe using the mail address as key? What would be the best practice for owner/moderator user management? Thank you!

5 months, 1 week

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) > > >

6 years, 1 month

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)

3 years, 2 months

Re: Postorius web issues after upgrading mailman 3

by M4tze

Hi Tibor, I have the same (or a very similar) issue. Have you tried getting jquery-1.11.3.min.js from somewhere on the Internet and move it to <your path here>/static/postorius/libs/jquery/ That fixed it for me. For the docker versions, there is an open issue on this: https://github.com/maxking/docker-mailman/issues/519 Kind regards - M4tze Am 12.10.21 um 17:38 schrieb Tibor Molnar: > Hello, > > I hope someone could help me in relation to this issue. I have experienced some error with my mailman3 deployment (only in postorius web) after went through the upgrading procedure following https://docs.mailman3.org/en/latest/upgrade-3.2.html#upgrading-mailman-3 > I believe this is nothing else then the wrong css/js files gone to the wrong directory or they aren't implemented properly. Basically some part of it works ok and some doesn't. > The following web pages doesn't seem to be implementing the css/js files is Archives, Account, Posting Activity, Log in and Log out web pages. Any help would be appreciated. > > Regards, > Tibor > _______________________________________________ > 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/ >

3 years, 6 months

Re: Editing a Subscriber's Mailman 3 list Settings

by Mark Sapiro

On 7/1/21 11:08 AM, Terry Earley wrote: > Admin users can edit subscriber's Mailman list settings. Once that > subscriber registers as a user, then only he/she can edit. Admin no longer > has permission to change these settings. > [image: editSubscriberByAdmin.gif] The image removed by this list's content filtering was a partial screenshot of a Postorius member options page with the error message "Cannot convert parameters: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings" What Postorius version is this? I am unable to duplicate this either as a site admin or a non-site-admin list owner with Postorius from the head of the gitlab branch (1.3.5b1). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 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/

3 years, 5 months

Re: Members (and moderators) can't view the list of members.

by Mark Sapiro

On 11/7/24 13:34, mrl(a)psfc.mit.edu wrote: > I installed Mailman 3 almost 2 years ago. I only now noticed that members of a mailing list can't view the list of members. Even moderators can't see the list. Only Owners. The error message is "You do not have permissions to visit this page." > > Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] > Postorius Version 1.3.8 This is https://gitlab.com/mailman/postorius/-/issues/369 fixed by https://gitlab.com/mailman/postorius/-/merge_requests/770 in Postorius 1.3.9 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 1 week

Re: Postorius: Show only own lists

by Simon Hanna

On 01/23/2018 12:10 PM, Thor Atle Rustad wrote: > Imagine an installation with 500+ mailing lists and almost as many local > admins that are supposed to maintain their own local lists with a few local > members. As site admin, I see all 500+ lists, but I was expecting *local* > admins to see only the lists they maintain. I have set all lists to > "advertised = False", so they are hidden from ordinary view. Is there a way > to show only relevant lists to local admins? Are we talking about Postorius or Hyperkitty? There is no way for users that do not have the django superuser permission, to see unadvertised lists in the Postorius list index. I just doublechecked the source. There is an issue about list filtering/search for the index page.

7 years, 2 months

Mailman-users search results for query "Postorius"