Search results for "Postorius" - Mailman-users

Re: nextcloud as auth provider for postorius

by 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

2 years, 4 months

Re: Ann: Postorius 1.3.6 is now out

by Mark Dadgar

On Sep 29, 2021, at 9:28 AM, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > On Wed, Sep 29, 2021 at 6:28 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> Hey Everyone, >> >> I just tagged and released Postorius 1.3.6. This release includes both bug >> fixes and >> new features. >> >> Some of the notable features include >> - Ability to list and handle un-subscription requests to the list >> - Option to choose delivery mode and delivery_status directly when >> subscribing to a list >> - Addition of a user management interface, which allows updating a users >> password, >> manually verifying their email addresses, update user’s Display Name >> etc. >> - Expose a number of Bounce processing related options in List’s settings >> >> A full list of changes is available here >> >> >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 >> >> You can install this release using pip >> >> $ pip install postorius django-mailman3 mailmanclient —upgrade >> > > root@svr:/usr/local/mailman # pip install postorius django-mailman3 > mailmanclient —upgrade > ERROR: Invalid requirement: '—upgrade' > > Why do you think I got this? I had this issue too. I think some mail clients are turning a double-dash into an emdash. It should be: --upgrade - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 6 months

Postorius 1.1.2 security release

by Abhilash Raj

Hi Everyone, I am pleased to announce that Postorius 1.1.2 is released and is up on PyPI[1]. This release fixes a security bug that sets the password of a user in Core to their display name. It is recommended that you upgrade to this version. Postorius (Django) and Mailman Core both have different notion of "user" and "password". When a user account in created in Postorius, it creates a user in Core using the REST API. This bug, causes the password of user created in Core to be set to their display name instead. However, as of now, there are no use cases of the user password in Core and it is present only for historical reasons. So, while this bug is a serious one, it wouldn't result in any real-world exploit. Along with the bug-fix, this release includes a new command that resets *all* user passwords in Core to a random value. Again, there are no use cases of these passwords so resetting *all* of them isn't going to cause any inconvenience to users. This command should be run after the upgrade: $ cd mailman-suite/mailman-suite_project/ $ python manage.py reset_passwords Python 2.7 is the only supported Python version for this release. All versions of Django <=1.11 is supported. For more information about GNU Mailman and Postorius, please see our website: http://list.org The source code is available on Gitlab: https://gitlab.com/mailman/ [1]: https://pypi.org/project/postorius -- thanks, Abhilash Raj

8 years, 3 months

per domain SITE_ID views?

by David Newman

Using FILTER_VHOST, I have two domains set up and working with MM3, Postorius and Hyperkitty. However, because SITE_ID in settings.py points to one of the domains, that domain name always appears on Postorius and Hyperkitty pages. The FAQ says there's a way to edit the SITE_ID used by a domain: https://docs.mailman3.org/en/latest/faq.html#id2 But I think that's just for which SITE_ID is associated with each domain, and not what's displayed. I already have 'dom1.tld' and 'dom2.tld' set as the display names for each site (under Postorius/Domains/Edit or admin/Sites/Site). The issue is that Postorius and Hyperkitty show 'dom1.tld' for all pages, even those in dom2.tld. Presumably this is because of the SITE_ID value in settings.py. How to get the correct domain to appear on that domain's Postorius and Hyperkitty pages? Thanks. dn

4 years, 3 months

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

by Mark Sapiro

On 11/9/24 06:52, Odhiambo Washington via Mailman-users wrote: > > I looked at Django Admin and Postorius and I see all my MLs in both. What you see in Django admin is in the HYPERKITTY section and corresponds to hyperkitty_* tables in the mailmanweb database. > What I am sure about is that I did NOT create my MLs using Django admin UI. > I either created them using the CLI or Postorius. > Having said that, I did run two tests: > 1. Create a ML in Postorius and check whether it appears in Django admin - > The list was visible in Django Admin Because the list you created had the hyperkitty archiver enabled. > 2. Create a ML in Django admin and check whether it appears in Postorius - > The list was NOT visible in Postrorius Because it's only in HyperKitty. > 3. Create a ML in CLI and check if it appears in both Django admin and > Postorius - List is visible in Postorius, but not in Django admin Becayse this list did not have the hyperkitty archiver enabled. > ``` > MariaDB [mailmansuite]> select list_name, list_id from mailinglist where > list_name like 'ulf%'; > +-----------+-------------------------------+ > | list_name | list_id | > +-----------+-------------------------------+ > | ulftest2 | ulftest2.lists.kictanet.or.ke | > | ulftest3 | ulftest3.lists.kictanet.or.ke | > +-----------+-------------------------------+ > ``` These are only Mailman lists. > The list that I created using Django admin is NOT listed here! Because it's only in HyperKitty. > ``` > MariaDB [mailmansuite]> select list_id, name from hyperkitty_mailinglist > where list_id like 'ulf%'; > +-------------------------------+-------------------------------+ > | list_id | name | > +-------------------------------+-------------------------------+ > | ulftest1(a)lists.kictanet.or.ke | ulftest1(a)lists.kictanet.or.ke | > | ulftest2.lists.kictanet.or.ke | ulftest2(a)lists.kictanet.or.ke | > +-------------------------------+-------------------------------+ > ``` > The list I created using Django admin and the one I created using > Postorius are both listed, but the one I created from CLI is not listed. Because for some reason, the CLI created list does not create the HyperKitty archive until there is a post or until the `new_lists_from_mailman` job runs even though hyperkitty is enabled. > So there must be some logic behind this. However, I don't know what it is. The bottom line is you can have lists in HyperKitty that are not in Mailman and vice versa. The only thing you can't do is create a list in HyperKitty via the HyperKitty web UI, but you can use hyperkitty_import to import a mbox for a list which is not in Mailman and will be only in HyperKitty. Also, while you can create a list in Mailman that isn't in HyperKitty, if the list has hyperkitty enabled it will be created in HyperKitty when the `new_lists_from_mailman` job runs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Re: Moderation action "None" is misleading

by Markus Grandpré

Dear Mr Sapiro, dear Mr Turnbull, thank you very much for your reply. For clarification I like to change: > What versions of Mailman and Postorius are you using? * mailman3, v3.3.8-2~deb12u2 * mailman3-web, v0+20200530-2.1 * python3-django-mailman3, v1.3.9-1 * python3-django-postorius, v1.3.8-3 * python3-mailman-hyperkitty, v1.2.1-1 * python3-mailmanclient, v3.3.5-1 with Debian GNU/Linux 12 (bookworm). So the newest changes: > This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in > Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ > merge_requests/811 are not yet available on our system. Hopefully we won't have to wait too long with Debian as there is already a lot of confusion among some of our many list administrators as we only started using Mailman3 for production a few days ago. Best Markus Am 04.02.25 um 19:25 schrieb Mark Sapiro: > On 2/4/25 02:51, Markus Grandpré wrote: >> Dear List, >> >> I find the use of the term 'None' (or 'Kein' in the German >> translation; see attachments) in the 'Moderation action' column of the >> member list misleading, as the term suggests that no moderation action >> is applied to the respective member. >> >> However, this is not necessarily the case. If you check a member’s >> "Administration options / Moderation" setting, a moderation action, >> such as "Moderation" or "List default", may be in effect. > > This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in > Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/ > merge_requests/811 > > See the UI changes at https://docs.mailman3.org/projects/postorius/en/ > latest/news.html#news-1-3-9 > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 2 months

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.

4 years, 1 month

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

5 years, 1 month

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

2 years, 6 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

1 year, 5 months

Mailman-users search results for query "Postorius"