Search results for "Postorius" - Mailman-users

Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, You were (of course), absolutely on target, thank you! I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. I have searched on the file system for any such templates and only see the default ones; all zero length files. There are no templates defined for the domain in postorius – but if there were, I’d expect to see that test header all the time. I’m just baffled. Any clues? I’m a relative newbie to mailman3. When I first set it up, I tried the postorius templates for the domain. They didn’t work (had to have been due to the POSTORIUS_TEMPLATE_BASE_URL being wrong. So, I scrapped that and went with templates in the file system. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 3:46 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

7 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

3 years, 7 months

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

2 years, 6 months

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

10 months

Re: "Unsubscribe all" failed with large lists

by Alan So

Alan So wrote: > 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. Just figure out that our production environment with Mailman core 3.2.0 do reply with the API call /3.1/lists/listname.domain/roster/member even for long lists though it takes long time to complete. However, Mailman core 3.3.2 simply give empty reply with long lists after around a minute.

4 years, 7 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

1 year, 11 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > Hey Everyone, > > I am pleased to announce new stable releases for Mailman Core, Postorius, > Hyperkitty. > > These include both new features and bug fixes. Complete change log for > each components: > > Mailman Core 3.3.3: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > Postorius 1.3.4 > https://docs.mailman3.org/projects/postorius/en/latest/news.html > Hyperkitty 1.3.4 : > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html > > Minimum supported Python version is 3.6. > > You can install them using: > > $ pip install --upgrade postorius hyperkitty mailman > > We have also recently been working on making the installation > instructions[1] to be > more detailed and added a new FAQ[2] section for administrators where I > hope > to capture common questions from mailman-users list. > > Feedback or Merge Requests to improve these docs are welcome. You can > either > send an email or open an issue on Gitlab (easier to track) here[3]. > > [1]: https://docs.mailman3.org/en/latest/install/virtualenv.html Hi Abhilash, What's the reason behind the exclusion of MySQL & Apache instructions in the installation instructions? :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 4 months

Re: Where is postorius.wsgi?

by Timm Stamer

Hi Peter, I use https://gitlab.com/mailman/mailman-suite as WSGI backend for httpd # git clone https://gitlab.com/mailman/mailman-suite.git You have to customize settings.py of mailman-suite before you can start using it. Regards Timm Am Donnerstag, den 25.01.2018, 14:27 +0100 schrieb Peter Münster: > Hi, > > I try to install Postorius, but I don't find the file postorius.wsgi. > Where should I get it please? > > This is, what I've done so far: > - git clone https://gitlab.com/mailman/postorius.git > - cd postorius > - python3 setup.py install > - cd example_project > - virtualenv venv > - . venv/bin/activate > - pip3 install -r requirements.txt > - in venv/lib/python3.6/site-packages/django_mailman3/lib/mailman.py: > replace "urllib2" by "urllib.error" > - python3 manage.py migrate > - python3 manage.py createsuperuser > - python3 manage.py compilemessages > - python3 manage.py collectstatic > > Now I try to follow > https://postorius.readthedocs.io/en/latest/deployment.html#apache-wit > h-mod-wsgi > but I don't find postorius.wsgi ... > > TIA for any help. Kind regards,

7 years, 7 months

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

by Mark Sapiro

On 11/9/24 05:32, ulf.rapphahn(a)offis.de wrote: > 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). Because the mailing lists in the Django admin interface are HyperKitty Lists, not Mailman lists. When you create a list in Postorius or Mailman core, this is a Mailman list. A corresponding HyperKitty list will also be created if hyperkitty is one of the active archivers for the list so you see it in Django. When you create a list in Django, it is only a HyperKitty list and will be visible in HyperKitty, but no Mailman list is created so the list is not in Mailman/Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months

Re: nextcloud as auth provider for postorius

by Falk Hackenberger

Hi Jerred, the setting are: INSTALLED_APPS = ( ... 'allauth.socialaccount.providers.nextcloud', ) SOCIALACCOUNT_PROVIDERS = { ... 'nextcloud': { 'SERVER': 'https://website/cloud/index.php', 'EMAIL_AUTHENTICATION': True, }, } the OAuth 2.0-Clients settings in nextcloud are: Name mailman redirection-URI https://website/mailman3/postorius/lists/ Client-Identitifier: XXX Secret **** no errors in the log file. any hints to debug this? thanks Falk Am 01.12.23 um 21:25 schrieb 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 -- Ochsenweberstr. 43a 22419 Hamburg +49 176 48183883

1 year, 9 months

Mailman-users search results for query "Postorius"