Search results for "Postorius" - Mailman-users

Re: Moderated unsub requests are not provided by mailman3 service

by Joachim Schrod

Mark Sapiro writes: > On 11/29/24 4:47 PM, Joachim Schrod wrote: > > > System information: mailman3 3.3.3; Postorius (mailman3-web) 1.3.4; > > both on Debian 11 (bullseye). > > > > I know that this is out of date; thus a definitive info "this is fixed > > by now" is quite OK for me. (Debian upgrade is planned as the next > > action after getting Mailman3 to work for that use case.) > > Yes, this is fixed. Thanks for the information that it's fixed in Postorius 1.3.6; that information is a great help, it means that I don't need to spend more time on debugging resolved issues. I tried to gather data if an update to Debian 12 (bookworm) would help. But packages.debian.org is not helpful at all, for me. I know that this is beyond the realm of this mailing list, but perhaps someone here has that information and can supply it: Debian 12 (bookworm) package mailman3-web has the version "0+20200530-2.1". This is supposed to be from some source package mailman-suite that is a salsa project that I don't grok at 1st and 2nd sight. Can anybody please provide me with information what versions of mailman3 core and mailman3-web are in this package; i.e., in Debian 12 (bookworm)? Sorry, but I'm not versed enough to understand the information about Debian packages that my search delivers. Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

1 year, 5 months

Re: Database running VERY hot

by Abhilash Raj

Hi Darren, On 3/8/18 9:43 AM, Darren Smith wrote: > Hello all, > > We had an old installation of Mailman 2.1 across three servers with over > 32,000 mailing lists on them. Due to circumstances beyond my control, we > had to shut them down and quickly set up Mailman 3 on a new server. > > We have Mailman3 set up on a single server this time, as we were having > problems with a 3-server setup and Hyperkitty and archives. Long story > short, it is up and running, and our users are starting to come back. > > However, we do not have very many users hitting Postorius and Hyperkitty > yet, and we are seeing a distressing number of 504 gateway timeouts. > > We noticed that there is a significant number of queries to the API > whenever hitting Postorius's front page to load the mailing lists, and then > on every load. It looks as if it makes a single call to the API to get > information about a single list, and does this 10 times - once for each > list - to render the page. This gets much worse when users set the view to > 200 per page, as they are inclined to do with 32,000 mailing lists... > > What we've done, actually, is to override the front page and point the > users to a different set of static pages where we have all of our lists > categorized and searchable, and when they find the list they are looking > for, we have a link back to postorius. It has taken a lot of the stress off > of the server. > > However, I still see where the database at times can run VERY hot. > > We have set up this server to run with PostgreSQL. When I do a ps aux | > grep postgres, I find a lot of processes that have been spawned to take > care of mailman - a dozen or so. However, one of the threads is taking up > about 85% of the load, another thread about 14%, and little dribbles here > and there from the rest of the threads. > > Here are the questions: > > 1) Has anyone run into problems like these? I would think that maybe this > is an issue having so many mailing lists, but honestly there aren't that > many people using the system yet. It is going to ramp up as the users > realize that we are live again, but we aren't getting that much traffic. I can say that in general, Postorius doesn't really optimize REST API queries and so loading a single page can sometimes make things bad. Currently, the largest installation of Mailman 3 that we know of runs at lists.fedoraproejct.org and the administrators of the list would know how well does our Web UI scale. However, I don't think we have anyone actively working on trying to fix this particular issue. Pull Requests and fixes are welcome :) > > 2) Is there any configuration that I can set, especially with regards to > the database, so that it can be used more efficiently and not throttle > through one or two threads? There isn't any configuration that would change how databases are used in Mailman Core. Django *may* have some, but I don't know about any of them of the top of my head. thanks, Abhilash

8 years, 2 months

Deleting archives

by Henrik Rasmussen

Docker-mailman 0.1: I have deleted some lists that I used for testing, but Hyperkitty seems to preserve the archives in the Available lists. Clicking on a list archive gets me to the archive of that list (with no posts because I haven't posted anything to the list). The URL is https://[WEBSITE]/hyperkitty/list/[LISTNAME](a)[LISTDOMAIN]/<https://[WEBSITE]/hyperkitty/list/%5bLISTNAME%5d(a)%5bLISTDOMAIN%5d/> (with a (a)), but when I click Manage subscription, the URI changes to https://[WEBSITE]/postorius/lists/[LISTNAME].[LIST<https://[WEBSITE]/postorius/lists/%5bLISTNAME%5d.%5bLIST>DOMAIN/ (with a dot instead of (a) which seems normal behavior) and I get a "Not Found The requested URL /postorius/lists/[LISTNAME]DOT[LISTDOMAIN]/ was not found on this server. " error. Of course I can't manage the subscription for a list I have deleted, but shouldn't the archive for a list be deleted along deleting the list. Henrik Rasmussen

8 years, 8 months

Re: Affinity Mailman Is Now Beta

by Mark Sapiro

On 6/18/20 12:44 PM, Brian Carpenter wrote: > Dear Mailman Admins and Users, > > Affinity Mailman is our new admin interface for Mailman 3 and we intend > to use it to replace Postorius. It has been under development for about > 3 months now and it recently reached beta. Just to be clear, Brian has the full support of the GNU Mailman project in his endeavor to create a new web UI for Mailman 3, but "our" above means Brian and EMWD, not the GNU Mailman project. We of the GNU Mailman project are delighted that Brian is working on an alternative web UI, but we have no plan to abandon Postorius and HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/11/21 4:18 AM, Richard Rosner wrote: > Mark Sapiro wrote: >>> You are in a better position to answer that than am I. >> What does sudo netstat -lntp show? > > A lot. But since most of that isn't relevant here: > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8024 0.0.0.0:* LISTEN 14076/python3 > tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 20241/master > tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN 14080/python3 So some python3 process is listening on port 8001 > tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 20241/master > tcp6 0 0 :::80 :::* LISTEN 13882/apache2 > tcp6 0 0 :::465 :::* LISTEN 20241/master > tcp6 0 0 :::25 :::* LISTEN 20241/master > tcp6 0 0 :::443 :::* LISTEN 13882/apache2 > tcp6 0 0 :::587 :::* LISTEN 20241/master > >> What does ps -fwwa|grep rest show? > > root 15055 14843 0 12:58 pts/1 00:00:00 grep rest > > So whatever it's supposed to find, it's not there But whatever is listening on port 8001 is apparently not Mailman's rest server. What does ps -fww 14080 or whatever PID is currently listening on port 8001 show. >>> mailman3-web.service must also run as list. > > I changed that. It didn't like it. OK. Perhaps instead you should have uid: list gid: list in your uwsgi configuration if you don't already. > >>> So, what do you have in your apache config for proxying to uwsgi and >> what's your uwsgi configuration. > > lists-ssl.conf: > <VirtualHost *:443> > ServerAdmin admin(a)domain.de > ServerName lists.domain.de > > Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass "/mailman3" "unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost:8001/" I'm not familiar enough with this form of ProxyPass using sockets to understand what the localhost:8001 does in this context, but uwsgi should not be doing anything with port 8001. In a configuration using TCP, it would listen on port 8000. Port 8001 is where Mailman's REST API server listens. uwsgi should receive connects in your case via the unix socket and then pass them to Django via the application in wsgi.py Also, you may want other paths proxied to uwsgi, namely at least some of hyperkitty, postorius, archives, accounts, admin and user-profile. > </IfModule> ... > I guess with uwsgi config you mean the /etc/mailman3/uwsgi.ini file? > [uwsgi] > # Port on which uwsgi will be listening. > uwsgi-socket = /run/mailman3-web/uwsgi.sock > > #Enable threading for python > enable-threads = true > > # Move to the directory wher the django files are. > chdir = /usr/share/mailman3-web > > # Use the wsgi file provided with the django project. > wsgi-file = wsgi.py > > # Setup default number of processes and threads per process. > master = true > process = 2 > threads = 2 > > # Drop privielges and don't run as root. > uid = www-data > gid = www-data These should be 'list', not 'www-data'. That's your permissions issue on settings.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Installed but mailman reports missing hyperkitty module

by jbernal.web.dev＠gmail.com

I've opted for the Mailman3 package installation on Ubuntu 22 LTS on top of a manually installed Mailman3 core package from the Ubuntu 20 Debian repository. Everything is working great on my installation. However, if I try to enable hyperkitty in /etc/mailman.cfg postorius reports 500 status codes on all pages. /var/log/mailman3/mailman.log reports this error: ModuleNotFoundError: No module named 'mailman3_hyperkitty' Any idea why postorius can't seem to find the installed hyperkitty module? Stack trace: 2023-02-08 12:48:14 [FALCON] [ERROR] GET /3.1/lists/test.listdev.ocdla.org/archivers => Traceback (most recent call last): File "falcon/app.py", line 361, in falcon.app.App.__call__ File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 405, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 354, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 614, in __init__ for archiver in config.archivers: File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 280, in archivers archiver = call_name(class_path) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked ModuleNotFoundError: No module named 'mailman3_hyperkitty'

3 years, 3 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/21/20 9:38 AM, Ruth Ivimey-Cook wrote: > > > Problem is, if I do that (which I did in the beginning), the core rest > service listens on localhost / 127.0.0.1 (it obviously recognises that > as the , and so cannot be connected to by anything. That is why I set it > to 0.0.0.0 to begin with, and what the documentation implies (fairly > strongly) that this parameter is about. What documentation? I do understand what you are saying and I see the issue. I don't understand why it works for this poster <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> but maybe that's specific to Docker containers. > IMO, the hostname parameter needs to be split up into a "what address > should the rest of the world use to address me" and separately "what > address(es) should I listen on". Multiple listen addresses enable > multihomed hosts to get the right connectivity, too. Try something like this and let us know if it works? If so, we can do something like add a config setting for this. > --- a/src/mailman/rest/gunicorn.py > +++ b/src/mailman/rest/gunicorn.py > @@ -53,7 +53,7 @@ def make_gunicorn_server(): > # We load some options from config.webservice, while other extended options > # for gunicorn can be defined in configuration: section. We also load up > # some logging options since gunicorn sets up it's own loggers. > - host = config.webservice.hostname > + host = '0.0.0.0' > port = int(config.webservice.port) > log_path = os.path.join(config.LOG_DIR, config.logging.http['path']) > options = { -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

Mailman 3 install questions: HAYSTACK_CONNECTIONS

by heller＠deepsoft.com

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

1 year, 10 months

Re: Apache Conf

by Mail Person

Ok, progress with tinkering some. Using the below configuration I can manually navigate to lists.example.com/mailman3/postorius/lists/ and all is working fine. If I go to lists.example.com/mailman3 it for some reason redirects to lists.example.com/mailman/postorius/lists/ which generates a 404. Going to lists.example.com also hits a 404. So closer, but not perfect. Any ideas? The current, sort of working config: <VirtualHost *:80> ServerAdmin admin(a)example.com ServerName lists.example.com ServerAlias www.lists.example.com Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> RewriteEngine on RewriteCond %{SERVER_NAME} =lists.example.com [OR] RewriteCond %{SERVER_NAME} =www.lists.example.com RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost>

3 years, 9 months

Guidance Request: Migrating Existing Mailman 3 Installation to Docker-Based Deployment

by Prasanth Nair

Hi all, I am currently running a Mailman 3 setup on a standalone server and planning to migrate it to a Docker-based deployment using the official Docker Mailman images. I would appreciate your guidance on the recommended approach for this migration. *Current (existing) setup:* - Mailman Core: 3.3.5 - Postorius: 1.3.6 - HyperKitty: 1.3.5 - PostgreSQL: 12.22 (Ubuntu) - Host-based installation (non-Docker) - Postfix used as the MTA - Active mailing lists with members and archives - Apache reverse proxy in front *Target (new) setup:* - Docker-based Mailman 3 (mailman-core, mailman-web, PostgreSQL containers) - Based on the official Docker Mailman repository - Postfix as the MTA - Apache reverse proxy in front I would like to migrate the following components safely: - Mailing lists and their configurations - Subscribers and roles - HyperKitty archives - Postorius/web data (users, preferences, etc.) I have a few specific questions: 1. What is the recommended migration approach from a host-based Mailman 3 installation to the Docker-based setup? 2. Is it safe to directly restore the PostgreSQL databases into the Docker environment, or is there a preferred migration method? 3. Are there any version compatibility considerations when migrating from Mailman Core 3.3.5 / Postorius 1.3.6 / HyperKitty 1.3.5 to the versions used in the current Docker images? 4. How to migrate archives? 5. The official Docker Compose file references `postgres:12-alpine`. Is it recommended to stay on PostgreSQL 12 for compatibility, or is it supported to use a newer PostgreSQL version (for example, PostgreSQL 18) with the Docker Mailman setup? 6. Are there any common pitfalls or best practices you would recommend for ensuring a smooth migration? Any guidance or documentation you can provide would be greatly appreciated. Thank you for your time and support. Kind regards, Prasanth Nair

4 weeks

Mailman-users search results for query "Postorius"