Search results for "Postorius" - Mailman-users

nextcloud as auth provider for postorius

by Stephen J. Turnbull

mailman3--- via Mailman-users writes: > 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. I don't know of a howto for Mailman and socialauth. The socialauth I've configured has been for corporate environments, so there was a ground source of truth for IDs that happened to also provide the ground source of truth for email addresses. So everything just worked and there was no debugging to do. :-( First, you need to understand that there's no automatic connection between your socialauth identity and your Mailman identity, and that your email address is not your Mailman identity, although it is linked to your Mailman identity.[1] Now, the traditional identity in email is an email address, and the authentication procedure is to make the user prove they can read the mailbox. That is still necessary, so email addresses are still very closely bound to the identity (Mailman User object). Then there are these questions: 1. Does Nextcloud provide an email address as identifying information? 2. Is it the right address (ie, one of the ones linked to your Postorius login)? 3. Is that address verified in Postorius? If none of those questions help you figure out the problem, you'll need to explain exactly what data Nextcloud is providing to Django socialauth, and how Django socialauth is supposed to connect that to a Postorius/Mailman User object. Steve Footnotes: [1] The identities in Mailman are quite complex. From Mailman's point of view, the identity is in a User object in Mailman core's database. That User is *not* exposed to world, instead, a separate application (Postorius in your case, and for most sites) provides a proxy object that automatically synchronizes with the core User object. Besides the proxy object, Postorius also provides authentication services. Those services are delegated to Django, which handles both traditional password authentication as well as "socialauth". Then the socialauth plugin receives some kind of identifier (not an identity!) from the identity provider.

2 years, 3 months

Re: More Mailman releases!

by Eggert Ehmke

The upgrade worked flawless, and my system works as expected, but even after restarting apache in the footer line is displayed: Postorius Dokumentation • GNU Mailman • Postorius Version 1.3.9b1 In the venv: $ pip list | grep postorius postorius 1.3.10 Is this a leftover? Am Samstag, 21. Oktober 2023, 20:35:23 CEST schrieb Abhilash Raj: > Hello Everyone, > > I am pleased to announce several new releases for GNU Mailman project. > Thanks to all the contributors for making these releases possible! > > 1. Postorius 1.3.10 [1] > 2. Hyperkitty 1.3.8 [2] > 3. Django-mailman3 1.3.10 [3] > 4. Mailman-web 0.0.7 [4] > > All the releases are published to PyPI and you can find links to all the > PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 > [2]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 > [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst > Do note that for Postorius, I released 1.3.9, but I forgot to update > dependency metadata to require `django-mailman3>=1.3.10` (which is > required for the new bootstrap 5 upgrade across packages) and so I also > released Postorius 1.3.10 just after. > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > If you find any issues, you can report them at the respective bug > tracker for the projects. The links to issue trackers are available > at https://docs.mailman3.org/en/latest/. > > Finally, similar to Mailman Core, note that PyPI doesn't accept > signatures anymore so each packages' release page now has the tarball > uploaded to them along with the signature: > > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 > Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 > Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 > > -- > thanks, > Abhilash Raj (maxking)

2 years, 4 months

Re: Ann: Postorius 1.3.6 is now out

by Guillermo Hernandez (Oldno7)

On 29/9/21 5:27, Abhilash Raj wrote: > Hey Everyone, > > I just tagged and released Postorius 1.3.6. This release includes both bug fixes and > new features. Just to confirm that I've done a complete upgrade from last version without any problem. From the info page: Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Documentación de Postorius <https://postorius.readthedocs.org> • GNU Mailman <http://list.org> • Versión de Postorius 1.3.6 > > 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 > > Do note that this release requires Mailman Core 3.3.5, so you need to upgrade > Core before upgrading Postorius. > > The release tarball is available on PyPI as usual: > > https://pypi.org/project/postorius/1.3.6/#files > > Please also ensure to run the post-install commands as per the upgrade documentation: > > https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade > > Thanks to all the folks who helped with this release! > > Abhilash > >> Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). >> On Sep 19, 2021, at 8:48 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> Hey Everyone, >> >> I am pleased to announce that Postorius 1.3.6b1 is now out. This is the first pre-release for 1.3.6, which is slated to release next week soon after Mailman Core 3.3.5 release. >> >> This release requires Mailman Core 3.3.5 release, so if you are trying out this release, please also upgrade Mailman Core to 3.3.5rc1 (which was just released today). >> >> This release includes several new features and bug fixes. A full list of changes is available here[1]. >> >> With this release, we have also improved on the localization of the interface, if you want to help out before the release of the stable 1.3.6, please see the instructions for translators here[2]. We use Weblate for translations, so if you are familiar with that, you can directly head over there[3]. >> >> Since this is a pre-release version, you can install this using pip via: >> >> $ pip install --upgrade --pre postorius django-mailman3 mailmanclient >> >> Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). >> >> A release tarball is available on PyPI: >> >> https://pypi.org/project/postorius/1.3.6b1/#files >> >> Finally, thanks to all the folks who helped with this release in any capacity and made it possible. >> >> [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 >> [2]: https://docs.mailman3.org/en/latest/translation.html >> [3]: https://hosted.weblate.org/projects/gnu-mailman/postorius/ >> [4]: https://docs.mailman3.org/en/latest/upgrade-3.2.html#virtualenv-install >> >> >> thanks, >> Abhilash > -- > thanks, > Abhilash Raj (maxking) > > > > _______________________________________________ > 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/ --

4 years, 5 months

Re: Can't subscribe on new site/domain

by Flo

On 10/10/25 17:46, Mark Sapiro wrote: > On 10/10/25 1:37 AM, Flo via Mailman-users wrote: >> >> The difference I am talking about is that lists.example1.com/ >> postorius/ lists shows only its mailing lists while >> lists.example2.com/postorius/ lists shows all mailing lists on the >> server (ie. also mailing lists of example1.com) > > What is your Postorius version? Whether Postorius displays all lists or > only those matching the current host is controlled by the FILTER_VHOST > setting. There was an issue with this prior to Postorius 1.3.3. See > https://gitlab.com/mailman/postorius/-/issues/394 > Postorius Version 1.3.13, /usr/share/mailman3-web/settings.py: FILTER_VHOST = True , however, this is set for the whole server and not for single domains/sites, right? In my case mail_host is the same as web_host so I shouldn't be touched by that problem anyway. Flo

5 months

nextcloud as auth provider for postorius

by mailman3＠huckley.de

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

2 years, 3 months

Re: Mailman, etc. upgrade woes and persistent bugs

by Brian Carpenter

On 2/13/21 3:03 AM, Stephen J. Turnbull wrote: > How different is this from Mailman 2? (Just "not really different" is > fine, I'll be looking at your specific desiderata for more details > later, including potential GSoC tasks.) It seems to me it's basically > the same, except maybe for some Web 2.0 features like sorting on > fields. (I'm not deprecating those features: obviously sorting would > have helped Allan a lot, for example. It's just that Mailman 2 is > very much a Web 1.0, maybe even Web 0.9, application.) Am I missing > something big? I actually took at lot of ideas from the MM 2 Membership List page simply due to the fact that Postorius' was not helpful in inspiring anything. The one thing that I did do is take MM2's approach and modernized it. So here are more tasks a List Owner can do that MM2 could never offer (and Postorius doesn't even come close): -- Sort Members by Delivery mode (regular vs digest). (MM2 has no sorting abilities at all except by alphabet, Postorius doesn't even have that) -- Reveal which Members are registered with the UI (MM2, everyone was registered, in Postorius nothing is revealed about registration) -- Show in one List Member Management panel List Members, Non-Members, Moderators, and Owners (MM2 and Postorius requires this data to be seen via multiple pages) -- View Member's List Subscriptions to other Mailing Lists on the server and, if that List Owner is List Owner of those other lists, can even access the List Owner board (Affinity terminology) for those other Lists. -- Ban a member -- Promote a member to List Owner and/or Moderator -- Add a new List Member, List Owner, Moderator, and Non-Member from a Single List Member Membership panel. (Again both Postorius and MM2 requires multiple pages. Postorius is an improvement in this regard over MM2. The funny thing with Postorius is you can add a single Non-member, Moderator, and List Owner, but you cannot add a single List Member except through *Bulk* adding.) Features are not the only thing about a modern UI, UX design plays a MAJOR role in the modern UI. Postorius should have at least matched MM2 in features in regards to something as important as Member management but instead it took a step back into the dark ages. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

Login confusion

by Stephen J. Turnbull

Markus Grandpré writes: > We've encountered an issue with Postorius after migrating from > Mailman 2.1. It appears that Postorius is treating email addresses > with differing capitalization as distinct user accounts. For > example, <markus.grandpre(a)uni-konstanz.de> and > <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate > identities. That's not true on the systems I've worked with most recently -- those will be recognized as duplicate addresses, both at list import time and at login on Postorius. Those are versions Mailman 3.3.9 and 3.3.11, with corresponding Postorius. As far as I can tell the last case- sensitivity bugs were fixed as of Mailman 3.2.1 (released 2019-02-22). Postorius does not appear to have had any case sensitivity bugs (not surprising since Postorius just passes them through to Mailman). I guess it's possible that this is a Debianism, or there was a temporary regression around 3.3.8. > Is there a known configuration option or method within Postorius > (or Mailman 3 itself) to normalize or unify account identification, > effectively treating email addresses as case-insensitive for > account matching? There is no such configuration option because Mailman has treated email addresses as case insensitive for quite a while. All I can recommend is an upgrade. Steve

1 year, 1 month

Postorius install - missing python modules

by Marco F

Hello, On AlmaLinux 8.7, after Configuring Mailman and Setting up my database (postgres), and hooking up my mailserver (Exim), the instructions proceed to Set up Postorius: https://docs.mailman3.org/projects/postorius/en/latest/setup.html I've tried `pip install postorius`, as well as the latest version, cloning and `pip install -e .`. I've tried with multiple python versions, all with the results: ModuleNotFoundError. Here's highlights of one example: ``` dnf update -y dnf upgrade -y dnf install -y python39 alternatives --config python3 » python3 -V Python 3.9.13 pip3 install postorius git clone https://gitlab.com/mailman/postorius.git cd postorius pip3 install -e . cd example_project ~/postorius/example_project (master)» » python3 manage.py migrate ... ModuleNotFoundError: No module named 'debug_toolbar' » pip3 install debug_toolbar ERROR: Could not find a version that satisfies the requirement debug_toolbar (from versions: none) ERROR: No matching distribution found for debug_toolbar » pip3 install django-debug-toolbar ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel' » pip3 install requests_panel ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel' » pip3 install django-requests-panel ... » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_panel.panel' # I tried a bunch of different modules, none resolved the error, finally tried this & it did: » cd $( dirname $( locate requests_panel/panels.py ) ) && cp -pv panels.py panel.py » python3 manage.py migrate ... ModuleNotFoundError: No module named 'requests_wrapper' » pip3 install requests_wrapper ... » python3 manage.py migrate ... ImportError: cannot import name '_total_seconds' from 'requests_wrapper' (/usr/local/lib/python3.9/site-packages/requests_wrapper/__init__.py) ```

2 years, 10 months

Re: Core, Hyperkitty and Postorius releases

by Abhilash Raj

On Thu, May 13, 2021, at 7:18 AM, Torge Riedel wrote: > Am 03.02.21 um 02:59 schrieb Abhilash Raj: > > Mailman Core 3.3.3:https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs… > > Postorius 1.3.4https://docs.mailman3.org/projects/postorius/en/latest/news.html > > Hyperkitty 1.3.4 :https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Dear MM3 releasers, > > after successful update to latest versions I realized that Mailman Core > change log links are stable (I requested this some time ago and it was > changed - thanks for that), but Postorius and Hyperkitty change logs do > not have stable header ids. > > Can this be changed too? > > It makes it easier for me (and hopefully for others) when communicating > changes to the users. At the moment they see the upcoming changes for > Postorius first, which always introduces confusion for some of them. > The stable headers are sometimes missed when creating a new NEWS section. There isn't an automation that I've found to add a new section in the news.rst file yet which will do that for me. So I just forget sometimes :-) Adding headers is a trivial thing though. If you find one missing on any project please feel free to submit a MR to fix that. It can be done after the release has been made too. See this[1] that Mark just made to fix it for Postorius. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/636/diffs -- thanks, Abhilash Raj (maxking)

4 years, 9 months

Re: Mass subscribe gives HTTP Error 500 when using custom template

by Mark Sapiro

On 1/28/20 6:15 AM, Jeffrey D wrote: > Hi, > > I have some issues with the Mass Subscribe option on Mailman 3.2.1. When using a custom "The notice sent to a member when they are subscribed to the mailing list." template, Postorius will throw an exception after pushing the "Subscribe Users" button on Mass Subscribe. ... > requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /postorius/api/templates/list/<MAILINGLIST>/list:user:notice:welcome (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f0b5ce8d8d0>: Failed to establish a new connection: [Errno 111] Connection refused')) > > Postorius/Mailman is running on port 8001, only Postorius still connecting on port 8000. What is your setting in settings(_local).py for POSTORIUS_TEMPLATE_BASE_URL? It looks like you have the default POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' It should be the base URL for connecting to Postorius. I.e., if you normally connect to Postorius via https://www.example.com/postorius, it should be https://www.example.com You say Postorius/Mailman is running on port 8001. Mailman core's rest server should be listening on port 8001, but your web server can't proxy to Postorius on that port. Normally, the wsgi server that supports wsgi access to Django (Postorius and HyperKitty) listens on port 8000, at least if it is gunicorn or uwsgi proxied from your web server, or if it's Apache and mod_wsgi, proxying is not involved. Again, it looks like you may be using Apache and mod_wsgi in which case you could have POSTORIUS_TEMPLATE_BASE_URL set to something like https://www.example.com or even http://localhost or http://localhost:80, but not port 8000 if no wsgi server is listening there. Also, the URL is now in the database entry for this template in the postorius_emailtemplate table, so even after you fix POSTORIUS_TEMPLATE_BASE_URL, you'll probably have to delete and recreate the template in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Mailman-users search results for query "Postorius"