Search results for "Postorius" - Mailman-users

Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Abhilash Raj

Hi All, I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. The full set of changelog can be found in the documentation[1][2]. The most notable feature that I can think of is non-member management in Postorius. New releases are available on PyPI[3][4]. Thanks to all the contributors who made this release possible! :) [1]: https://postorius.readthedocs.io/en/latest/news.html#id2 [2]: https://mailmanclient.readthedocs.io/en/latest/src/mailmanclient/docs/NEWS.… [3]: https://pypi.org/project/mailmanclient/ [4]: https://pypi.org/project/postorius/ -- thanks, Abhilash Raj (maxking)

7 years, 7 months

Re: Why is this Postorius API public?

by Mark Sapiro

On 3/10/22 12:49, Stanisław Findeisen via Mailman-users wrote: > Hello > > I've just noticed that Postorius API is publicly accessible from the outside to an unauthenticated user, for example: > > https://HOST/postorius/api/templates/list/LISTNAME.VHOST/list:member:regula… > > Is this what is expected? Or a misconfiguration? How to fix this? It is expected. That API only serves Postorius configured email templates. Do you think that is sensitive information? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Re: Can't subscribe on new site/domain

by Mark Sapiro

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

11 months

Re: per domain SITE_ID views?

by David Newman

On 12/28/21 1:30 PM, Mark Sapiro wrote: > On 12/28/21 1:14 PM, David Newman wrote: >> 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. > ... >> How to get the correct domain to appear on that domain's Postorius and >> Hyperkitty pages? > > > I don't think the domain is actually displayed on Postorius pages. You are almost certainly correct. I saw dom1.tld on a login page, but hadn't realized that login page comes from Hyperkitty and not Postorious. > If > I'm wrong, on what Postorius view do you see it? As far as HyperKitty is > concerned, please file an issue for this at > https://gitlab.com/mailman/hyperkitty/-/issues/new Opened an issue here: https://gitlab.com/mailman/hyperkitty/-/issues/404 dn

4 years, 8 months

Re: New release candidates for Postorius and Hyperkitty

by Abhilash Raj

Hello Again, Turned out, there was an issue with a vendored JS library in Hyperkitty 1.3.4rc1. Also, someone requested another release of Core for a couple of bugfixes that have landed in master since the last release in November. I have just released Hyperkitty 1.3.4rc2 and Maiman Core 3.3.3rc1. Complete change logs are available here: Hyperkitty: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Core: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… New stable version of Core will be out alongside the other releases previously announced. Abhilash On behalf of GNU Mailman Team On Sat, Jan 16, 2021, at 12:38 PM, Abhilash Raj wrote: > Hey Everyone, > > Happy new year to everyone! > > I am pleased to announce new release candidates for Postorius and > Hyperkitty along with new releases for Mailmanclient and > Django-mailman3! > > These include both new features and bug fixes. Complete change log for > each components: > > Postorius 1.3.4rc1: > https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4rc1 : > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > Mailmanclient 3.3.2.: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > Django-mailman3 1.3.5: > https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > These releases require Mailman Core 3.3.2 and Python 3.6+. > > Since these are pre-releases, you can install them using: > > $ pip install --pre --upgrade postorius hyperkitty > > Or you can also specify the exact versions: > > $ pip install --upgrade 'postorius==1.3.4rc1' 'hyperkitty==1.3.4rc1' > > Unless there is a release-blocker bug, stable versions for Postorius > and Hyperkitty will be released in 2 weeks time. If you can test these > releases, we encourage you to report any bugs to us on Gitlab. > > If you'd like to help out with translations for some of the new strings > in your native language, the documentation is available here[1] on how > to do that. > > [1]: https://docs.mailman3.org/en/latest/translation.html > > -- > thanks, > Abhilash Raj (maxking) > On behalf of GNU Mailman Team -- thanks, Abhilash Raj (maxking)

5 years, 7 months

Re: Django logins for new subscribers

by Alex McLean

> That's because neither are required to > actually run Mailman. They are part of the 'mailman suite' that I installed, as an integrated whole. I subscribed everyone via postorius, I'd have thought it would make sense and presumably be straightforward for postorius to create django accounts for them at that point. I can also set the welcome message via postorius. Again I think it would make sense to be able to tag the postorius URL at that point as a default (perhaps using a text box rather than URL via third party website). > So I guess it's better to have the default not send anything, > since the other way round would mean sending dead links. Not if you're subscribing people via Postorius in the first place. > Currently the core component of Mailman doesn't have a way > to know under which url Postorius is reachable... Perhaps the web interface url could be passed in from the web interface? Cheers alex

8 years, 7 months

Re: mailman_web/urls.py changes in Postorius 1.3.10

by Mark Sapiro

On 12/5/23 09:52, Lieuallen, Thomas Otis wrote: > The latest release of Postorius includes these lines in mailman_web/urls.py: > > > # Include alternate Postorius and HyperKitty URLs. > > path('postorius/', include('postorius.urls')), > > path('hyperkitty/', include('hyperkitty.urls')), > > > It appears that these paths override the originals (/mailman3 & /archive). They were intended as optional additions, but it appears they do function as overrides for some purposes. > I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. This is apparently a side effect of this change that wasn't considered in making the change. The change was made because some docs and/or example projects used the /postorius and /hyperkitty URLs and some used the /mailman3 and /archives URLs. This was an attempt to make either set work. > If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). > > Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. > > One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? It was intended to just add the /postorius and /hyperkitty URLs as alternates. I had assumed the links on various pages would reflect the URL used to access the page, but this is apparently wrong. I could change the order of the path lines in the distributed urls.py, but at this point it just may cause more confusion. However, since the sample config at https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… shows only the /mailman3 and /archives URLs, I will change the order. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Re: Postorius 1.1.2 security release

by Marvin Gülker

Am 29. December 2017 um 20:57 Uhr +0100 schrieb Marvin Gülker <m-guelker(a)phoenixmail.de>: > I see the below error when I try to upgrade postorius. Given the > statement above, I assume it's a problem with Django then -- I've got no > Python experience after all. So, what's the correct way to upgrade > postorius if just using `$ pip install --upgrade' doesn't work? Nevermind, reading pip's help fixed the problem. The correct command is: $ pip install --upgrade --upgrade-strategy only-if-needed postorius Interestingly, it worked without the --upgrade-strategy switch for Mailman Core. Dear, I'm going to be happy when Mailman 3 makes it into Debian stable's repos... Greetings Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

8 years, 8 months

Re: Approve an email

by Mark Sapiro

On 12/26/22 12:08, Lars Bjørndal wrote: > Hi, list! > > I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and > postorius-1.3.6-2.fc36.noarch installed. with the command > > sudo -u mailman mailman3 create <listname> > > I was able to create a list. > > I'm not able to find out how to setup and configure the postorius > package. There's no mailman-web command. See <https://docs.mailman3.org/projects/postorius/en/latest/>. I don't know how you invoke the Django management command in the postorius-1.3.6-2.fc36.noarch package. It could be manage.py or django-admin or something else. > Hyperkitty will not installed du to a dependency conflict, but I dont > need archiving for the list. > > Here comes my quesitons: > > - What's the easiest way to approve an email sent to the list? Approving held messages via email requires Mailman core >= 3.3.5. See <https://gitlab.com/mailman/mailman/-/issues/169> Thus, the easiest way is via Postorius. > - How can I configure the list to accept messages also from non members? Set the list's default_nonmember_action to Action.defer. This can be done via Postorius, mailman shell or the REST API. > - How can I setup postorius to work on Fedora? I have django-admin, but > I'm not sure where to go. See the Postorius docs at https://docs.mailman3.org/projects/postorius/en/latest/setup.html#installat… to get started. (replace `python manage.py` with `django-admin`) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

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)

7 years, 6 months

Mailman-users search results for query "Postorius"