Search results for "Postorius" - Mailman-users

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, 8 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, 7 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

1 year, 2 months

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.

11 months

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

8 months, 1 week

Re: When mass subscribing using format John Doe <john.doe@example.com>, "Members" show some with real name, others without.

by Mark Sapiro

On 10/30/19 2:08 AM, Henrik Rasmussen wrote: > > It seems (I’m not certain about this) that the one’s without real name is the one’s already having an account and thus registred in Django (admin/auth/user/), while the ones subscribed with full name associated is the ones not having an account already. That's probably correct, but not the exact reason. > However, as soon as the member (the one with the account) went to Account and changed his real name, the name was immediately associated with the subscription in Members -> Subscribers. > > I expect this to be by design, but why isn’t the name associated with the subscription when mass subscribing in the first place, taken from the account? To understand, you need a bit of background. The basic engine that manages lists, subscriptions, users, etc. is Mailman core. Core does not provide any web UI. It only provides a REST API for use by other components. It is possible to run Mailman core only without any web UI, but management would need to be done directly via the REST API and/or `mailman shell` which is not particularly convenient. Because Mailman would not be too useful without a web management UI and a web based archiver, we provide Postorius and HyperKitty for these functions. These are only one possibility. One could build an entirely different web UI or other application to communicate with core via its REST API, but few if any have done so. Postorius and HyperKitty are Django projects and run under Django. The account that you see (Postorius top right) is a Django account. Core knows nothing about this. Core knows about users and addresses in its own database which is entirely separate from Django's accounts. These user/address records in core is where the user's display_name is kept. So when a user/address is added to a list, if core already knows that user/address, it just links that to the list and doesn't update the display_name, but if it doesn't know the user/address, it creates it and uses the supplies display name. It appears there is a mechanism within Postorius to detect a change in the name associated with a Django user and update core, but this is separate from subscribing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: Postorius endless loading on Sign in / Register then "Internal Server Error"

by Mark Sapiro

On 6/9/20 12:16 PM, Jacob Bargery wrote: > Pre-cursor, I am in a new position to learn on the go and new to Linux but have been tasked with setting up a List Serv and they wanted Mailman 3 with Postorius and HyperKitty. Running on Ubuntu 20.04 LTS using Postfix and MySQL. I can open up the initial pages. With no Lists created yet. I can open up Register, Login, and Forgot Password but when I submit anything it spins the loading icon for a long time then reads" > > "Internal Server Error > The server encountered an internal error or misconfiguration and was unable to complete your request. Apache/2.4.41 (Ubuntu) Server at groups.smccme.edu Port 80" ... > This is a traceback I could find from another attempt: > > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call > raise MailmanConnectionError('Could not connect to Mailman API') > mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API What are your Django settings for MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' Those match the defaults defined in mailman/config/schema.cfg [webservice] # The hostname at which admin web service resources are exposed. hostname: localhost # The port at which the admin web service resources are exposed. port: 8001 # Whether or not requests to the web service are secured through SSL. use_https: no # The administrative username. admin_user: restadmin # The administrative password. admin_pass: restpass If all that seems to match, what happens if you try telnet localhost 8001 If that doesn't work, but telnet 127.0.0.1 8001 works, there is some issue with `localhost` involving /etc/resolv.conf or /etc/hosts, most likely an ipv6 definition like ::1 localhost in the latter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

Re: Hiding an ML from a site

by Mark Sapiro

On February 6, 2024 7:45:14 AM PST, Odhiambo Washington <odhiambo(a)gmail.com> wrote: > >I had this set to True in settings_local.py, but False in settings.py. >So it seems to not make a difference in my setup. In a standard setup, anything set in settings_local.py overrides any corresponding setting in settings.py. That said, FILTER_VHOSTS is not perfect. It only works for Postorius if the separate web hosts also have different mail hosts. See lines 1051 et seq at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…> -- 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

after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

I did upgrade one of my mailman3 server after Abhilasj announcement: "I am pleased to announce several new releases for GNU Mailman project. 1. Mailman Core 3.3.6 1 <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…> 2. Postorius 1.3.7 2 <https://docs.mailman3.org/projects/postorius/en/latest/news.html#section-2> 3. Hyperkitty 1.3.6 [3] 4. Mailmanclient 3.3.4 [4] 5. Django-mailman3 1.3.8 [5]" I did it via pip and all seems to be working, but when I try to discard or accept any message via postorius it shows a Forbidden 403 error CSRF verification failed. In my settings.py I have commented out these variables: # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' I've been messing with them whith no results. It's like it lacked some value in some template... Can someone, please, point me in the right direction? Thanks in advance -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

4 years

Re: Postorius & multi domain

by Mark Sapiro

On 4/22/20 11:37 AM, Gelpi Andrea wrote: > > I'm not a python programmer so I ask you if it'd be long to implement a > workaround like this. > > If the web server is a.example.com and the email domain is example.com > > It'd be possible to drop the "a" and send the email domain only in the > query? > > It's a workaround. Can you help me in this? I'm currently working on a better fix. I'll post here on my progress. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

Mailman-users search results for query "Postorius"