Search results for "Postorius" - Mailman-users

Find all mailing lists a user is subscribed to

by Rodolfo Pilas

Hi, I administer a Mailman 3 server with more than 50 mailing lists. All subscribers belong to the same organization. Occasionally I need to answer questions such as: “Which mailing lists is user(a)example.com subscribed to?” At the moment I iterate over every mailing list, list its members, and grep for the email address. It works, but it is inefficient. Is there a supported way (CLI, REST API, or Postorius) to retrieve all the mailing lists a particular email address is subscribed to, without having to inspect every list individually? Rodolfo Pilas

3 months, 4 weeks

Re: New attack in progress

by Jeremy Stanley

On 2026-08-04 21:24:25 -0700 (-0700), Mark Sapiro wrote: [...] > However it precludes accessing Mailman from a non-javascript > enabled browser. Not entirely, it only forces certain clients to calculate and return hashes, mainly based on user agent strings. For example, I have Anubis in front of all my Postorius/Hyperkitty sites and have no problem accessing them with console-based browsers like lynx. In fact, it's the Javascript in Hyperkitty that makes it so I can't browse list archives that way, Anubis isn't stopping me at all. -- Jeremy Stanley

3 months

Re: Restrict the visible mailing lists to the current domain? – SOLVED

by Mark Sapiro

On 9/20/26 10:43, H.-Dirk Schmitt wrote: > Am Sonntag, dem 20.09.2026 um 09:01 -0700 schrieb Mark Sapiro: >> Set `FILTER_VHOST = True` in your `settings` file. >> > > Thanks – this setting fixed my problem. > IMHO it is undocumented in https://docs.mailman3.org/en/latest/ It is documented, albeit somewhat obscurely. See https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

Re: list archives bleeding across domains.

by Mark Sapiro

On 10/15/26 4:12 PM, Hugh Esco wrote: > > I get it that one domain's news list is supposed to be public, but does > it have to be listed on the page for each domain? Can't it be listed > for anonymous users ONLY IF they browse to its domain? > > My settings_local.py includes: > > FILTER_VHOST = True This should work. How is your web server accessing Postorius? Is it passing the hostname? I.e., `proxy_set_header Host $host;` for nginx or `ProxyPreserveHost On` for Apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 4 days

Re: Broken web interface Ubuntu 20.04

by Mark Sapiro

On 9/30/21 2:30 PM, tim(a)thecutts.org wrote: > > When I look at the mailman-web-logs, the urls that postorious puts into the page don't honour the POSTORIOUS_TEMPLATE_BASE_URL variable in the mailman-web.py file any more. I'm not saying there isn't an issue in Postorius, but I don't think it has anything to do with POSTORIUS_TEMPLATE_BASE_URL which is only used for templates and has nothing to do with the rendering of the list pages and shouldn't contain anything beyond the host and port in any case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: [Mailman-Users] MM3 startup issues

by Brian Carpenter

On 1/7/20 2:16 AM, hansen(a)rc.org wrote: > Beats me, Mark. Brian, do you know? Yes sir. Here are the three startup scripts that you will need to know. I should have included that in the communication I sent you and I apologize for that: systemctl start/stop/restart/status mailman (this is for Mailman core) systemctl start/stop/restart/status qcluster (this is for Django) systemctl start/stop/restart/status gunicorn (this is for web access to postorius/hyperkitty) -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

6 years, 10 months

Re: Can disabled users enable themself?

by Flo

On 7/5/26 3:06 AM, Mark Sapiro wrote: > The notice the user is sent is built from the list.user.notice.warning > template, you may want to create a custom version in Postorius. The Now I did this. However, the subject is still English. Can this be changed as well? Interestingly the final unsubscribe message has a German subject but no body. Can I change that in Postorious? > Regarding > > Afterwards mailman should check every 60d if this continues. > > You may also want to set Bounce disabled warnings interval to a value > less than 60 days. > Good idea, I'll change it to 30d/10 Thank you for your help, Flo.

4 months

Re: Hyperkitty 403 Forbidden Error

by Abhilash Raj

On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: > On 07/08/2019 17:04, Abhilash Raj wrote: > > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: > >> On 06/08/2019 09:48, Phil Thompson wrote: > >> > On 06/08/2019 03:38, Abhilash Raj wrote: > >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: > >> >>> I'm in the process of setting up mailman3. The only problem I seem to > >> >>> be > >> >>> having is getting Hyperkitty to archive messages. Rather than the > >> >>> authorisation problems people have previously asked about on the > >> >>> list, I > >> >>> am getting a 403 error... > >> >>> > >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: > >> >>> <html><title>Forbidden</title><body> > >> >>> <h1>Access is forbidden</h1></body></html> (403) > >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on > >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: > >> >>> <html><title>Forbidden</title><body> > >> >>> <h1>Access is forbidden</h1></body></html> (403) > >> >>> > >> >>> Any suggestions would be appreciated. > >> >> > >> >> How did you install Hyperkitty? > >> > > >> > On Ubuntu... > >> > > >> > apt-get install mailman3-full > >> > > >> >> You probably need to the set the API key correctly in both Core and > >> >> Hyperkitty. > >> >> > >> >> Have you looked at documentation here[1]? > >> >> > >> >> [1]: > >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… > >> >> > >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in > >> >> quotes, single or double, doesn't matter) in your settings.py for Web > >> >> (Django) should be same as the `api_key : value` (without quotes here > >> >> in hyperkitty.cfg config file). > >> > > >> > That's all correct. I'm familiar with the authorisation issues that > >> > other people have had. > >> > > >> > The only thing I'm doing differently (as far as I am aware) is that > >> > I'm using a URL prefixed with /mailman3 which is stripped off in my > >> > nginx configuration... > >> > > >> > # mailman3. > >> > location /mailman3/ { > >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; > >> > include uwsgi_params; > >> > uwsgi_param SERVER_ADDR $server_addr; > >> > uwsgi_modifier1 30; > >> > uwsgi_param SCRIPT_NAME /mailman3; > >> > } > >> > > >> > location /mailman3/static { > >> > alias /var/lib/mailman3/web/static; > >> > } > >> > > >> > location /mailman3/static/favicon.ico { > >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; > >> > } > >> > > >> > ...but I don't see this affecting the mailman to Hyperkitty > >> > communication. Posting to lists and the Postorius and Hyperkitty > >> > frontends seem to work fine. > >> > >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my > >> public IP address). However I now get a 400 Bad Request error. > >> > >> I have traced this to the archive() function in > >> hyperkitty/views/mailman.py which is expect a POST but is actually > >> getting a GET, specifically... > >> > >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' > >> > >> ...which seems to be a fairly fundamental problem. > >> > >> Again, any suggestions would be welcome. > > > > It should be sending POST request to archive emails[1]. How did you > > grab the above request? Was it from logs? > > Yes, I added DEBUG=True in mailman-web.py and captured the HTML from > mailman.log. DEBUG=True doesn't print anything more useful around the 400 error response? > > > Do you have anything else in the logs? There should be something in > > the Mailman Core or web logs should have something. > > There's nothing useful in the core log. > > There are 3 preceding entries in the web log... > > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... > GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... > > There is one item in the spool directory. > > These were all (apparently) successful. It seems odd that the last two > entries were identical. The only other thing that I can think of is, ALLOWED_HOSTS. What settings do you have in your ALLOWED_HOSTS in settings.py for Django? You need to have 'localhost' or whatever is the value of the "Host" in the "base_url" in your hyperkitty.cfg file in Mailman Core. I am not sure what is the default value in Ubuntu system. If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS and see if the problem goes away, this will bypass the Host header check. -- thanks, Abhilash Raj (maxking)

7 years, 3 months

Re: Installing mailman 3

by Mark Sapiro

On 07/25/2017 01:21 PM, Rafael Mora wrote: > Regarding this: > > # To be added to Django's settings.py > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = <username> > EMAIL_HOST_PASSWORD = <password> > > > > What should I use for username and password? > Should I keep the localhost on the host param? If you want Django (i.e. Postorius, Hyperkitty and Django admin/auth/etc.) to deliver via localhost, you don't need EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. Those are only for authentication to some other host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

django-mailman3 update causing errors

by Darren Smith

Hello, In attempting to update our mailman3/postorius/hyperkitty installation, I have run into an error after upgrading the django-mailman3 project. Our webui is being run through supervisord. The command being run is this: /<path>/mailman3/conda/envs/mailman3_ext/bin/waitress-serve --listen=localhost:8787 webui.wsgi:application The error I'm getting is pretty long, but most of it appears to be usage instructions. Here are what I believe to be the pertinent parts: Error: Bad module 'webui.wsgi' Usage: waitress-serve [OPTS] MODULE:OBJECT <lots and lots of usage instructions> There was an exception (ImportError) importing your module. It had these arguments: 1. No module named error Any thoughts on why updating django-mailman3 would cause this? Thanks! -Darren

8 years, 6 months

Mailman-users search results for query "Postorius"