Search results for "Postorius" - Mailman-users

Re: Hyperkitty 403 Forbidden Error

by Abhilash Raj

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? Do you have anything else in the logs? There should be something in the Mailman Core or web logs should have something. [1]: https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman_hyperkitt… -- thanks, Abhilash Raj (maxking)

6 years, 1 month

Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by Shawn Heisey

On 10/28/2021 5:28 PM, Abhilash Raj wrote: > The instructions are basically in the issue description, pending move to a documentation page: > > https://github.com/maxking/docker-mailman/issues/293 > > If you are upgrading the latest 0.4.x release from 0.3.x, you also want to look at > > https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release Awesome! Thank you for that info! I just upgraded from 0.4.1 (which was the tag I used for the initial install) to 0.4.2 and it all looks good. The lists are still there in the output of this command on the host: docker exec -u mailman mailman-core mailman lists After the upgrade, I sent a test message to one of the mailing lists that looks like it worked perfectly. I assumed that it would be necessary to update the tags in the docker-compose.yaml file, and I did so. Should that be added to the instructions? One thing that was very non-obvious is how to get the containers to start at boot time. A command like this, issued three times with the actual ID values for the containers, took care of it for me: docker update --restart=unless-stopped 0576df221c0b If it is possible to have the docker-compose.yaml file set that flag when it creates the containers, I think that would be a good idea. I did notice that the postorius and mysql docker-compose configs do set the database container (but not the mailman containers) to restart always ... but my limited experience with docker tells me that unless-stopped is a better option. > If you can send a PR for the config you set up for Apache in Github, or just an issue, I can include it in the docs :-) I created an issue and included a sanitized copy of my virtualhost config. Thanks, Shawn

3 years, 10 months

Re: mailman 3.x upgrade and downgrade

by Mark Sapiro

On 7/12/22 6:12 AM, skooperit(a)gmail.com wrote: > Hi all, > > I have a few contradictory questions. > > 1. How to upgrade the 3.x version? > > 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1? > > 3. If so, what would be the best way to do that? > > > My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: > > django-mailman3 1.3.5 > mailman 3.3.2 > mailman-hyperkitty 1.1.0 > mailman-web 0.0.3 > mailmanclient 3.3.2 > postorius 1.3.3 > > We have ~200 lists with more than a decade of history. So you have installed Mailman 3, apparently following https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a caveat. Current released versions of HyperKitty (I don't see your version above) don't work with mistune >= 2.0.0. This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet released. If your installed mistune is not 2.0.0rc1, you can work around this with this patch ``` --- a/hyperkitty/lib/renderer.py +++ b/hyperkitty/lib/renderer.py @@ -4,7 +4,7 @@ from django.conf import settings import mistune from mistune.plugins.extra import plugin_url -from mistune.scanner import escape_html, escape_url +from mistune.util import escape_html, escape_url class MyRenderer(mistune.HTMLRenderer): ``` Or you can downgrade mistune with ``` pip install mistune==2.0.0rc1 ``` in your virtualenv. To answer your questions, to migrate your lists, you use `mailman import21` and to migrate archives, `mailman-web hyperkitty_import`. Give these commands with the `--help` option for more info. Downgrading lists from Mailman 3 to Mailman 2.1 is not currently possible. There is no inverse to `mailman import21`. You can export a HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Florian Fuchs

On Sat, Dec 03, 2016 at 17:25:24PM -0800, Terri Oda wrote: >On 2016-12-03 12:22 PM, Florian Fuchs wrote: >>I did some manual integration testing today >>(core+mailmanclient+postorius) which looked fine so far. I didn't get >>to test HyperKitty and the bundler though, so any help testing those >>would be very much appreciated. I will have some more time tomorrow. > >I tried to do some testing based on these wiki instructions last weekend >https://wiki.list.org/HyperKitty/DevelopmentSetupGuide > >and hit a "[Errno 61] Connection refused" issue when attempting to log >in to Postorius. I suspect it might be an issue with the mac, since >googling for the error (it's a django one) seems to find a lot of >people on macs with problems, but I didn't manage to narrow it down >more than that to make a useful bug report. Do you have a traceback somewhere? If you're logging in for the first time, it *might* have to do with allauth trying to verify your email address by sending you an confirmation email (which probably fails if you don't have smtp set up on your mac). If that's the case, we should probably try to catch this condition and display a useful error message instead of just letting it break. Cheers Florian >I did set up a new linux install on another machine to work on next, >though, so I may have something else to say on that front tomorrow. > > Terri > > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers(a)python.org >https://mail.python.org/mailman/listinfo/mailman-developers >Mailman FAQ: http://wiki.list.org/x/AgA3 >Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ >Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/f%40florianfuchs… > >Security Policy: http://wiki.list.org/x/QIA9

8 years, 9 months

use_https not being honored?

by Stephen J. Turnbull

sean.p.kiernan--- via Mailman-users writes: > Using Mailman core 3.3.5, and Mailman API 3.1, I have use_https: > yes set in my mailman.cfg so that I can use https for calls to the > API, Despite the name, that's not what use_https does. It means to use "https" when formatting its URL, and AFAICS that's all it does. In particular it does not configure gunicorn (which provides the REST server) to use HTTPS as far as I can tell. > however even in mailman.log, it still says it is using http: > > [2022-06-01 09:35:54 -0500] [959009] [INFO] Starting gunicorn 20.1.0 > [2022-06-01 09:35:54 -0500] [959009] [INFO] Listening at: http://hostname:8001 (959009) > > GET and POST requests work fine if I use http, but fail when trying > to use https. You need to set some or all of the settings here where gunicorn can find them. https://docs.gunicorn.org/en/stable/settings.html#ssl I believe this can be done either in the gunicorn.cfg file or in the [webservice] section of mailman.cfg. This is separate configuration information from any configuration of server credentials you provide for Postorius or HyperKitty. > I've only recently started using Mailman so if there are additional > logs or system information I need to help with this? I'm pretty sure what I wrote above diagnoses the issue correctly, but for the future "didn't work" doesn't tell us enough. You should always provide the exact error message, exactly as presented. If you get a traceback of function calls, you should provide that whole thing as well. You may redact "sensitive" information (which includes personal names, usernames, passwords, and the like, but for some folks also things like IP addresses and domain names). However, try to ensure that there's a one-to-one relation between redacted items and the substitutes. Steve

3 years, 3 months

Re: Not able to start mailman server

by Mark Sapiro

On 8/5/21 12:53 AM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to setup postorius using this website - > > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/docs/W... That documentation is out of date. Start at https://docs.mailman3.org/en/latest/ > I am trying to create a mailling list and it web interface for the users in my group > > The command 'pip install -e ./'(python3) runs successfully but still i am not able to start the server Is the result the same as in your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, i.e., /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > my mailman info shows - > > GNU Mailman 3.3.5b1 (Tom Sawyer) > Python 3.9.5 (default, May 4 2021, 03:36:27) > [Clang 12.0.0 (clang-1200.0.32.29)] > config file: /Users/.../Documents/mailman/var/etc/mailman.cfg > db url: sqlite:////Users/.../Documents/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass We recommend following this guide https://docs.mailman3.org/en/latest/install/virtualenv.html What is the content of the /Users/.../Documents/mailman/var/etc/mailman.cfg file? The 'pip install -e ./' command should have created a bin/ directory containing both `mailman` and `master` executable files and this `mailman` command is the one you should be running. It appears the `mailman` command you are running is '/usr/local/opt/python(a)3.9/bin/mailman'. If that is in fact a symlink to a different bin/mailman file, there should also be a symlink from '/usr/local/opt/python(a)3.9/bin/master' to the existing bin/master or you should adjust your path. What do `which -a mailman` and `which -a master` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Abhilash Raj

On Sun, Mar 10, 2019, at 9:00 AM, Torge Riedel wrote: > Am 10.03.19 um 16:44 schrieb Mark Sapiro: > > On 3/10/19 8:18 AM, Torge Riedel wrote: > >> I deleted the existing "example.com" and added a new one > >> "lists.mydomain.de". > >> > >> Now the admin (django) interface always gives "An error occurred while > >> processing your request". After one of the first navigation clicks I saw > >> a message that "site with id 1 is missing". > > > > In your Django settings your have > > > > SITE_ID = 1 > > > > which pointed to the example.com domain you deleted. > > > > You need to override this in settings_local.py. Probably > > > > SITE_ID = 2 > > > > but if that doesn't work, try '0' > > > Ah, thank you Mark. That makes a kind of sense. I changed the database > directly to fix it. And renamed example.com to lists.mydomain.de. Now > the error is gone. > > I'm wondering why the initial database set up of postorius (?) adds > "example.com". Is there a way to directly add my domain instead? > Somewhere in settings_local.py? Django does that and there doesn't seem to be a way to override that to something else during initial migration. Or nothing I have found yet. Only way is to edit "example.com" to something you'd like or add another domain entry and change SITE_ID to point o that. > _______________________________________________ > 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)

6 years, 6 months

Re: Internal Server Error: /mailman3/postorius/lists/.../held_messages - humanize: where to put?

by Stephen J. Turnbull

Flo via Mailman-users writes: > In /usr/share/mailman3-web/settings.py there is: > > INSTALLED_APPS = ( > ... > 'django.contrib.humanize', > ... > ) Right, that's why Python is looking for it. Since it's not being found, I guess there's a version skew between Mailman and django.contrib. The first thing to do is to make sure all your packages are up to date. Check if the django package (or maybe django-contrib if it's a separate package) is pinned to a particular old version, and consider unpinning and upgrading it. If they are up to date, and you're skilled with Debian, you may consider adding more recent package sources (testing or experimental) and install Django from those sources. If that's not appealing I would strongly discourage trying to add the humanize package from Django upstream. That is a real can of worms. If you wish to continue using the Debian packages, you will need to get help from the Debian maintainers. I wouldn't be surprised if they already are planning to do something about this issue. The alternative would be to uninstall the Debian package and install the most recent Mailman packages from PyPI in a Python virtual environment /opt. This probably requires installing the Debian python3-venv package. This is not terribly difficult, the instructions at docs.mailman3.org/en/latest are good, and you're welcome to ask for help on this list. We recommend this because you will get better support that way. > And POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8001' > I think this has also something to do with it. That has nothing to do with it, they are quite unrelated. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

2 weeks, 4 days

Re: Unable to update templates

by Mark Sapiro

On 5/28/25 19:40, Mark wrote: > > I have jumped the gun on thinking that the template as a file was > working. It's not. It's the same story: the initial file template is > good, but it's for sure getting cached somewhere, and an updated file is > ignored. The same as when the template was being drawn from the database. Are you just updating the file /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt with nothing in Postorius and either no entry at all in the mailman.template table with name = 'list:user:notice:welcome' context = 'testlist.example.com' or if there is such an entry, with uri = 'file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use…' If so, editing the file /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt should work. > Restarting mailman3 and mailmanweb didn't help, neither did rebooting > the server. > > Looking at Gunicorn status, I see a failing connection to 127.0.0.1 > which is the error message I was getting when adding a new subscriber - > with the custom Welcome template in the database (which is why I moved > it to file). > > 127.0.0.1 and locahost are in the ALLOWED_HOSTS and CSRF_TRUSTED_ORIGINS > of the settings.py file > > I'm at a loss with this caching problem. Any other clues happily received. If as I say above, there is no entry in the mailman.template table for the name and context or if there is an entry with uri = 'file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use…', then gunicorn and mailman-web are not involved at all - mailman core will get the template from the file directly. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 2/25/21 9:38 AM, dancab(a)caltech.edu wrote: > Mark, > > Is it only this list that has an issue? > > Yes, this is the only list that is having the issue. > > Can you visit other pages for this list? > > Yes, I'm able to view the members list, list settings, templates, etc. > > I've restarted the service and tried to access the held messages for the list once again. Here's what is in the mailman log. > > > ERROR 2021-02-25 17:28:14,197 393 postorius Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 706, in urlopen > chunked=chunked, > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 445, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailmanve/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 440, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib64/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib64/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib64/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response This is from Django's log. What's in Mailman core's mailman.log? Since everything else is accessing the REST API with no problem, I think core must be stuck on something and timing out. Is there a time delay between trying to get the held messages view and the "Mailman REST API not available. Please start Mailman core." response? Also is there a non-zero count in the badge on the Held messages tab? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Mailman-users search results for query "Postorius"