Search results for "Postorius" - Mailman-users

Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 07:52, Jeremy Stanley wrote: > > 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). I don't think it does. There are a couple of migrations at django/contrib/sites/migrations, but these are only the initial creation of the model and an update to make the domain field unique. Why do you think it creates sites in this way. > 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. Mailman core doesn't associate domains with Django sites. Mailman core knows nothing about a web UI. The association between Mailman core domains and Django sites is via Postorius. It doesn't exist in Mailman core. When Postorius sees a new domain from core, it assigns it a web_host based on the current web host accessing Postorius. > 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? No. The only association is if Postorius is creating the domain in core, vs something else creating it via the REST API, Postorius will assign it a web_host in it's own Domain model, and that web host must be an existing Django site, which is only created via Django. > 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? Yes, A new site has to be created in Django. Even Postorius doesn't do that. > 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. No. You create the sites via Django, but not 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. Neither Mailman nor Django. It's Postorius which maintains the relationship between Django sites which it calls web_hosts and domains. > 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. Step 2. $ django_admin shell ``` >>> from django.contrib.sites.models import Site >>> new_site = Site(id=5, domain='5.example.com', name='display_name') >>> new_site.save() ``` Of course the values are up to you and you can omit the id= to have Django assign the first available.. Once you've done step 2, you need to create a domain in Postorius. Look at the code behind Postorius add new domain. Or you can create the domain in core via REST, but you then have to modify it in Postorius to associate the correct site. -- 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: adding imprint / private policy link to postorius

by Thomas Stein

Thanks Abhilash. Will have a look. On 2020-09-03 07:09, Abhilash Raj wrote: > On Tue, Sep 1, 2020, at 11:17 PM, Thomas Stein wrote: >> >> Hello one and all. >> >> Is it possible to add an imprint link to the postorius start page? I >> guess it is, but it would be >> nice if someone could me point to the right direction / documentation. >> Something like they have: >> >> https://lists.openrailwaymap.org/mailman3/postorius/lists/ >> > > There isn't an official way to do that, but you can patch your > installation to update the footer. > > This[1] is the location and file you want to update and you can insert > simple HTML there. If you are using system packages it should be > somewhere in the `/usr/lib/python3/dist-packages` directory and > in `lib/site-packages` if you are using a virtualenv based > installation. > > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/templates/… > >> cheers, t. >> _______________________________________________ >> 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/ >>

6 years, 2 months

duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

Hi I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: client.create_domain(name) Is this a bug? Or did I mess something up? What significance do those SITE_IDs have? What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Thanks! Stanisław

4 years, 7 months

Re: Django 5.2 LTS and mailman 3

by dlb-ml＠anl.gov

Let me expand on this, in that I am failing to get django 5.2 and mailman 3 components to work together in a python3.12 venv. Specifically, despite PIP looking like it understands that the requirements indicate that the allowable range for it's dependency on django is <5.3, pip uninstalls 5.2 and puts in 5.0.14 """ $ pip install git+https://gitlab.com/mailman/postorius@master Collecting git+https://gitlab.com/mailman/postorius@master Cloning https://gitlab.com/mailman/postorius (to revision master) to /tmp/pip-req-build-pq79umwc Running command git clone --filter=blob:none --quiet https://gitlab.com/mailman/postorius /tmp/pip-req-build-pq79umwc warning: redirecting to https://gitlab.com/mailman/postorius.git/ Resolved https://gitlab.com/mailman/postorius to commit 0eef9e5b1e36f9e630fe807d407e6ddcfd8e2bf6 Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Requirement already satisfied: django-mailman3>=1.3.13 in ./lib64/python3.12/site-packages (from postorius==1.3.13) (1.3.15) Requirement already satisfied: django<5.3,>=4.2 in ./lib64/python3.12/site-packages (from postorius==1.3.13) (5.2.11) Requirement already satisfied: mailmanclient>=3.3.3 in ./lib64/python3.12/site-packages (from postorius==1.3.13) (3.3.5) ... Collecting django<5.3,>=4.2 (from postorius==1.3.13) Downloading Django-5.0.14-py3-none-any.whl.metadata (4.1 kB) ... Downloading Django-5.0.14-py3-none-any.whl (8.2 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.2/8.2 MB 34.7 MB/s 0:00:00 Installing collected packages: django Attempting uninstall: django Found existing installation: Django 5.2.11 Uninstalling Django-5.2.11: Successfully uninstalled Django-5.2.11 Successfully installed django-5.0.14 """ Am I doing something wrong?

7 months, 4 weeks

Mailman3 without Hyperkitty in docker

by Danil Smirnov

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? Thanks, Danil Smirnov

7 years, 8 months

Re: postorius only show 50 owner lists

by elalelopez＠gmail.com

Hello, thanks for answering. The DB is postgresql. And it's not a paging problem. The paging buttons are disabled because I am trying to see all the owner's lists. I understand that postorius executes the list_index_authenticated function in postorius / views / list.py The description of the function shows: "" "Index page for authenticated users. Index page for authenticated users is slightly different than un-authenticated ones. Authenticated users will see all their memberships in the index page. This view is not paginated and will show all the lists. "" " Regards.

7 years, 8 months

Re: "Unsubscribe all" failed with large lists

by Alan So

Thanks. We are still using Postorius 1.2.4 and Mailman core 3.2.0. However, there is no such issue. Is this specific to Postorius 1.3.x or a result of using together with Mailman core 3.3.2? Postorius 1.2.4 is probably not using mass-unsubscribe API. We are planning to upgrade Mailman core first to solve another issue and upgrade Postorius a bit later.

5 years, 9 months

Re: Time Zone Issue in Postorius

by David Newman

On 2/4/22 10:29 AM, Mark Sapiro wrote: >> My Postorius account time zone is set to "US/Pacific". > > > The appropriate setting for Django is always `TIME_ZONE = 'UTC'`because > the time passed from Mailman core is a naive datetime.datetime object > and is actually UTC. Could use clarification on this. Are you referring to the settings.py file, or something else? Asking because my settings.py currently has: # Django time zones USE_TZ = True TIME_ZONE = 'America/Los_Angeles' and list timestamps appear to work OK both in Hyperkitty and as received by members' mail clients. This is with postorius 1.3.6 and Django 3.0.14. Is this setting incorrect? Thanks dn

4 years, 9 months

Re: Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface

by Mark Sapiro

On 9/30/23 10:53, Wikinaut wrote: > I use mailman3 since a while, for some of my lists I have been using > > - list:member:digest:footer.txt > - list:member:regular:footer.txt > > When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! Postorius templates are handled differently from file system templates. When you set a template in Postorius, that template becomes available in Postorius' API and an entry for the template in the template table in the database is created with a URI pointing to the template in Postorius' API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for info about template URIs. The fact that Postorius doesn't show the file system template as the initial value when creating a template in Postorius is https://gitlab.com/mailman/postorius/-/issues/366 > When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. They are not created as files - see above. The fact that they aren't working is probably because your Django setting for POSTORIUS_TEMPLATE_BASE_URL is not correct. This should be set to the scheme and host part of the URL you use to access Postorius, e.g., https://lists.mailman3.org for this list's installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

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

by Mark Sapiro

On 11/9/24 12:24, Ron / BCLUG wrote: > > Hopefully I've assigned the blame to Postorius accurately and no > formatting nor archiving issues make the issue difficult to understand. This is a HyperKitty issue. Postorius has nothing to do with archiving. 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. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Mailman-users search results for query "Postorius"