Search results for "Postorius" - Mailman-users

Re: How to remove Held Unsubscriptions

by Mark Sapiro

On 9/9/24 12:14, lowell(a)fas.harvard.edu wrote: > Hello, everyone. > > I'm having the same issue. We're Postorius Version 1.3.4.1. Which is three and a half years old. > I have no idea of how to use a shell or REST API. I update things via the web. If you can't upgrade to Postorius >= 1.3.5, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… which describes the `mailman shell` interaction required to do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

Re: Postorius not HTML-decoding < to "<" characters

by Jeremy Stanley

On 2024-11-09 13:05:16 -0800 (-0800), Mark Sapiro wrote: [...] > Also, it depends on the archive rendering mode and only occurs if the mode > is Markdown text rather than Plain text. It is really `mistune`, > <https://mistune.lepture.com/en/latest/index.html>, which is doing the > markdown rendering and which `escapes` HTML tags. [...] On a related note, the MD rendering here seems to misinterpret sig separators as markup. Like this... -- Jeremy Stanley

1 year, 7 months

Postorius Suggestion: Give owner a view of all users of all owned lists

by Andreas Vetter

Hi, it would be real great if owners that own several lists, but are not superusers, can see all users of all *their* lists and manage them. A down-"selected" version of the superusers view. Use case is an organisation (here are the superusers) with sub-organisations (here are the owners, e.g finance, research, production) having lists for the very sub-org itself and its sub-sub-orgs (e.g. research-all, research-solar, research-wind, research-battery). Would that be possible? -- Mit freundlichen Gruessen, Andreas Vetter

1 year, 3 months

Re: Disabling the version disclosure.

by Mark Sapiro

On March 25, 2025 5:18:13 PM GMT+07:00, ninad--- via Mailman-users <mailman-users(a)mailman3.org> wrote: > >Please let me know if there are any settings that I can set. I don't want to change any html code for the same. There are no settings for this. To remove the version from Postorius footers you would need to edit postorius/templates/postorius/base.html and for Hyperkitty, hyperkitty/templates/hyperkitty/base.html For Mailman core, where are you seeing the version exposed? -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 2 months

Re: New subscribed (by invitation) user: no password received in invitation/welcome e-mail. Postorius sign up / password reset broken

by Stephen J. Turnbull

Marco Emilio Poleggi via Mailman-users writes: > Yeah, indeed, it was a stupid configuration error. Those are always annoying. I'm really happy that it was that easy, and that things are working well for you now. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months, 3 weeks

Re: Postorius permissions granularity

by Liam Reilly

The issue is we don't want first line support staff to have superuser permissions, just the ability to assist end user list owners by being able to administer all lists. So something that is lower level than full superuser would be ideal. I'm considering a cron job that adds a web account as Owner to all lists but this feels like a bit of a bodge.

6 months, 1 week

How to upgrade to 3.10

by Paul Tomblin

I installed 3.9 with pip last week, but i want to upgrade to 3.10. But pip install -U mailman postorius django-mailman3 hyperkitty mailman-web doesn't upgrade it. Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) Collecting mailman Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) ... a bunch of these ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) ...a bunch more... -- Paul Tomblin

3 months, 3 weeks

Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 1 month

Re: Mass un/subscribe optimization?

by Mark Sapiro

On 2/28/22 12:12, Bryan Loniewski wrote: > Hi -- > > We've noticed slowness in mass un/subscribing users; looking through the issue(s) log we see both #419 [1] and #627 [2] open and related. From the cmd line we get better performance, but with the subscriber size on many of our Faculty/Staff/Students ad-hoc lists (think 1k-15K subscribed addresses) and with our number of lists (2600) and unique owners utilizing these actions it would be helpful to optimize the mass actions. We wanted to get some thoughts and guidance on what needs to be optimized/redesigned/fixed? Or is there already something in the works, but needs more time? We may be able to provide resources to encourage and/or assist with any development and/or testing... > > We run a split core/web setup with Apache,mod_wsgi and MySQL backend (AWS hosted). > > [1] - https://gitlab.com/mailman/mailman/-/issues/419 > [2] - https://gitlab.com/mailman/mailman/-/issues/627 Regarding mass removal and #627, that should be fixed as of Postorius 1.3.5. What is your Postorius version. If you want to work on providing a REST endpoint for mass subscribe and supporting it in mailmanclient and Postorius, that would be great. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Jeremy Stanley

On 2023-01-30 12:08:10 -0800 (-0800), Mark Sapiro wrote: [...] > Domains can be created via Postorius or via the Mailman Core REST API that > postorius uses or implicitly by the `mailman create` command when creating a > list in a new domain. However, none of this can create a new site. You can > do this through the Django admin site at sites/site/add/. > > See https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ for methods you > can use to do this programmatically. Thanks, I'm still doing my best to wrap my brain around how Django uses database migrations to create sites (seems like a very strange use of a migration, I'm only accustomed to seeing them applied for database schema updates). Once I work out how to script site creation, I'm still not completely finding the explanations I need for how to map them to domains in Mailman though. The Mailman documentation about domains says "Domains are how Mailman interacts with email host names and web host names" but doesn't actually go on to say (that I can find anywhere) how it actually associates them. I can see in the API docs that a POST to the domains endpoint will create a new domain with a specific mail_host FQDN, but there's some association somewhere of that to a web host (Django site), right? How is that set or manipulated through the API? Or is that something which has to be set directly in Django's data structures instead? To recap, on creation of a mailing list server I want to populate it automatically with multiple lists on different domains and have dynamic SITE_ID=0 domain guessing performed so that the correct site name and list filtering is performed depending on which domain name is used in a URL the client requests. I believe I need to have the automation perform the following steps: 1. Instantiate the Mailman installation and run initial migrations with SITE_ID=1 in order to avoid the problem mentioned in the docs about not using SITE_ID=0 until the tables have been populated, then switch the settings.py to use SITE_ID=0 once done. 2. Create the individual sites I need in Django (Mailman web hosts) by creating and applying database migrations. 3. Create the individual domains I need in Mailman (Mailman mail hosts) through its REST API. 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond to what web hosts. As I said, I'm still trying to understand how to make step 2 happen (Django has a steep learning curve for me), but beyond that I'm unsure how to do step 4 at all. I can do all of this through the WebUI of course, and have confirmed that it works as expected when I do, I'm just trying to work out the automation so that our other sysadmins don't have to perform these steps by hand the next time we need to rebuild the server. Thanks again for all the help so far, and for any additional insight anyone may have into how I can correct my mental model of all this. -- Jeremy Stanley

3 years, 4 months

Mailman-users search results for query "Postorius"