Search results for "Postorius" - Mailman-users

Re: How to upgrade to 3.10

by Paul Tomblin

On Sat, Mar 7, 2026, at 8:09 PM, Mark Sapiro wrote: > On 3/7/26 17:02, Paul Tomblin via Mailman-users wrote: >> >> Ok, I've done those, and the migrate, compress, collectstatic. Where does base_url get set? > > base_url is an attribute of the domain and can be set in Postorius in > the domains view. I’m not seeing it. -- Paul Tomblin

3 months, 2 weeks

venv and upgrade from python 3.11 to 3.13 because of OS-upgrade

by Andreas Vetter

Hi, I have a venv installation (mailman postorius django-mailman3 hyperkitty mailman-web) with python 3.11 from the Linux distribution. Since distribution EOL nears, I checked python version in next distribution and it is python 3.13. So my guess is, after distro upgrade, this will stop working. How should I upgrade? -- Mit freundlichen Gruessen, Andreas Vetter

3 months, 1 week

Re: Python 3.13 compatibility

by Thomas Krichel

Thomas Krichel writes > What now? Actually it looks I could do pip install -U mailman==3.3.9 postorius django-mailman3 hyperkitty mailman-web To get back to a working system But that still leaves me without 3.3.11 which I apparently need for my import21. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22213th day.

2 months, 3 weeks

Changing default language for lists

by Wessel Kraaij

How can I change the default language for lists (and other defaults)? I changed it in mailman-core but Postorius overrides these core defaults with a patch. I am using the docker version of maxking Wessel

2 months, 1 week

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >It is the intent that Postorius will eventually expose all these >settings. We're not there yet. At present you could possibly do this by >interacting with mailmanclient, although I'm not certain the settings are >exposed there. I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the `delivery_mode` attribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum). Cheers, -Barry

10 years, 1 month

Re: Rejection Reason for refusing a subscription request

by Brian Carpenter

On 3/27/21 6:03 PM, Mark Sapiro wrote: > It's in Postorius since 1.3.3. If in the held message view, you click > the subject of a held message, you get a popup dialog the shows the > message with options to also show headers or the raw message. There is > also a dropdown t=o set the poster's moderation action and a box for a > reject reason if you click the reject button in the dialog. > > Do you not see this? I am referring to "Subscriptions pending approval". I apologize if I did not make that clear. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

Re: Assistance with mailman3

by Abhilash Raj

On Wed, Mar 13, 2019, at 8:47 AM, ayen(a)afilias.info wrote: > Hi all > > I'm pretty new to mailman but been trying to install mailman 3 and been > running into issues, following the documentation at > http://docs.mailman3.org/en/latest/prodsetup.html > installed Python 3.6, nginx, ruby-sass > then with pip installed whoosh mailman-hyperkitty postorius hyperkitty > mailman > > tried to start mailman core, symlinked master and runner -> /usr/bin/ > (otherwise it wouldn't run) > mailman core starts but when I hit the api url I get this in the logs > > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 248, in __call__ > responder, params, resource, req.uri_template = > self._get_responder(req) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 664, in _get_responder > route = self._router_search(path, req=req) > TypeError: find() got an unexpected keyword argument 'req' > Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 > > and on frontend "A server error occurred. Please contact the administrator." Inside your virtualenv, please run: $ pip install -U falcon==1.4.1 This should fix the above error. > > that leads to my gnu not working and throwing keyerrors for postorius. > > I'm using a clean install of ubuntu 18.04 but have also tried to > install on centos 7 with no success. > > Are there any missing dependencies or steps that I've missed any > assistance would be appreciated. > > Andy > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 3 months

An archive/read-only list on a full setup?

by Andreas Schamanek

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

3 years, 2 months

Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 10:25 AM, Mark Sapiro wrote: > I just upgraded from Django 3.2.11 to 3.2.14 on mail.python.org and > lists.mailman3.org. How to upgrade mailman-web to align with Django? I upgraded from Django 3.0.14 to 3.1.14 and then 3.2.14 using these docs: https://docs.djangoproject.com/en/4.0/howto/upgrade-version/ But then this upgrade command returned a complaint that mailman-web 0.0.5 requires Django<3.1: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi and it downgraded Django back to 3.0.14. I did not see anything about this in the Django for Mailman Admins doc, but I may have missed something. https://docs.mailman3.org/en/latest/django-primer.html Thanks. dn

3 years, 11 months

Mailman 3 Core user assistance

by Tony Deshields

I currently have a docker mailman stack that utilizes Django LDAP backend for authentication. I have my users attributes mapped as you see below in my settings.py file. Whenever a user logs into postorius with their 'uid', mailman-core uses their 'uid' as their email address instead of the 'email' attribute. Is there anyway to change this functionality? I would like my users to be able to login with their enterprise uid but be mapped to their email but I feel like there is a disconnect between Django and MM3 core. Any assistance is much appreciated. AUTH_LDAP_USER_ATTR_MAP = { "uid" : "userPrincipalName", "first_name": "givenName", "last_name": "sn", "email" : "mail", }

2 years, 5 months

Mailman-users search results for query "Postorius"