- Mailman-users - lists.mailman3.org

Healthchecks and Django
by Philip Colmer Jan. 5, 2022

Jan. 5, 2022

Hello We have a number of Mailman 3 servers running on AWS infrastructure. To help us maintain that, we're using Route 53 Health Checks to alert us when something stops responding. For the MM3 servers, we're probing "/mailman3/lists/". We've observed that when a server gets patched during a maintenance window, it will get rebooted and there is a phase where Django responds to web queries but the underlying MM3 services aren't quite in place yet. As a result, we then get emails from Django telling us about the service not being available. Given the number of AWS health checkers, that can result in quite a few emails ... Is there another URL we could use to check the health of a MM3 server without triggering the emails during service startup? Or, if not, is there a way of stopping Django from sending out the emails? We'd get alerted of a problem via AWS anyway, so I'm not too worried about not receiving the Django emails. Thank you. Philip

2 5

If you delete a list but not the HyperKitty archive
by Philip Colmer Jan. 5, 2022

Jan. 5, 2022

It seems that if you delete a list from the "Delete" option on a list's management page, the corresponding HyperKitty archive does not get deleted. That seems fair enough ... but now I wondering how HyperKitty manages visibility access to the archive when the list was private. HyperKitty certainly *seems* to have some knowledge of who was subscribed to a list as attempting to access a private archive with an account that wasn't subscribed prior to the list being deleted does deny access with "This mailing list is private. You must be subscribed to view the archives." But logging in as the server admin, going to the archive URL and then clicking on "Manage subscription" gives me a "Page not found" error ... which isn't too surprising as the list has been deleted. It suggests, though, that it isn't possible to manage access to the *archive* after the list has been removed. So ... should the archive be deleted when the list is deleted and it is a bug that it isn't? Or is it expected that access to the archive is "frozen" once a list is deleted? Many thanks. Philip

2 2

is there a mailman command/setting to periodically clean archives?
by William Oliver Jan. 4, 2022

Jan. 4, 2022

Thanks to everyone's help, mailman3 is up and running for me on two servers with three lists, and they all work as far as I can see. I'm sending out invitations to users tomorrow. Yayy. Up until today, I had been stuck using a plugin in Joomla, which was not the best solution. I'm tickled pink, and my users will be, too. Now I'm just playing and tinkering a bit. I'd like to delete all my archives that are more than a certain age, e.g. more than a week old. I can easily do that with a cron job, deleting old files in /opt/mailman/mm/var/archives/prototype/testlist(a)example.com/* which is, as far as I can see the only place archive emails live. However... I was wondering if there was some mailman command or config variable that would accomplish this without using cron. billo

3 4

Strange behaviour when SSL (https) is activated
by fr-mm3＠tourde.org Jan. 4, 2022

Jan. 4, 2022

Hi, I do a fresh install of Mailman3 and Mailman3-web on Debian 11 and all seems working fine using non-ssl access. But if I activate SSL on the web server, I'm unable to login. I go to the /admin, prompted for the user/pass, and got a Firefox error page saying "Échec de la connexion sécurisée". Main django account was created with: mailman-web createsuperuser --username XXXX --email xxxx(a)xxxx.xx extract of /var/log/mailman3/web/mailman-web.log : [pid: 103142|app: 0|req: 40/40] 192.168.200.252 () {48 vars in 1039 bytes} [Mon Jan 3 11:26:32 2022] GET /accounts/login/ => generated 9321 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 429 bytes (1 switches on core 0) Mon Jan 3 11:26:40 2022 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 248] during POST /accounts/login/ (192.168.200.252) OSError: write error [pid: 103142|app: 0|req: 41/41] 192.168.200.252 () {54 vars in 1008 bytes} [Mon Jan 3 11:26:40 2022] POST /accounts/login/ => generated 0 bytes in 704 msecs (HTTP/1.1 302) 9 headers in 0 bytes (1 switches on core 1) All is working fine on non-ssl connection. Any hint appreciated ;)

3 5

Held for notification - runner exception: 'ascii' codec can't encode character
by Seth Seeger Jan. 3, 2022

Jan. 3, 2022

Hello all, Happy new year! I have a case where a user (set to be moderated), posts a message. She got the appropriate email back saying she was being held for moderation. However, the moderator did not get the email. I found the following block in mailman.log: Dec 28 19:37:44 2021 (33) Uncaught runner exception: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.8/site-packages/mailman/core/chains.py", line 79, in process link.function(mlist, msg, msgdata) File "/usr/lib/python3.8/site-packages/mailman/chains/hold.py", line 234, in _process text = MIMEText(expand(template, mlist, substitutions), File "/usr/lib/python3.8/email/mime/text.py", line 42, in __init__ self.set_payload(_text, _charset) File "/usr/lib/python3.8/email/message.py", line 315, in set_payload payload = payload.encode(charset.output_charset) UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in position 5: ordinal not in range(128) Dec 28 19:37:44 2021 (33) SHUNTING: 1640720264.0541506+b139f885caa9444586b43093a09991b7c19581e6 There are two owners listed, one of them is also listed as the moderator. "mailman version" says: GNU Mailman 3.3.4 (Tom Sawyer) We are running from Docker. I can send you the pck file offline if that would help. Thank you, Seth

2 4

HyperKitty failure
by horvath.arpad.szfvar＠gmail.com Jan. 2, 2022

Jan. 2, 2022

Hi, I try to connect mailman3 to hyperkitty, but there is no success so far. You can see the details below. How can I solve the problem? As I have several domain name (like lists.xxx.hu, xxx.hu, yyy.hu) on the same server, so I guess localhost won't work. In mailman-hyperkitty.cfg there is a line: base_url: http://lists.xxx.hu/hyperkitty/ /etc/mailman3/mailman-web.py includes "*" in ALLOWED_HOSTS I have an error message in /var/log/mailman3/mailman.log Dec 30 21:41:23 2021 (126976) HyperKitty failure on http://lists.xxx.hu/hyperkitty/api/mailman/archive: (405) Dec 30 21:41:23 2021 (126976) Exception in the HyperKitty archiver: Dec 30 21:41:23 2021 (126976) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError In /var/log/mailman3/web/mailman-web.log WARNING 2021-12-30 20:41:23,816 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive [pid: 127032|app: 0|req: 101/101] 109.230.236.204 () {38 vars in 592 bytes} [Thu Dec 30 20:41:23 2021] GET /hyperkitty/api/mailman/archive?key=lHzJB%2FzfSWUrbPKZ84JNSlLXHVyCDt8T => generated 0 bytes in 1 msecs (HTTP/1.1 405) 6 headers in 189 bytes (1 switches on core 0) WARNING 2021-12-30 20:41:23,854 127032 django.request Method Not Allowed (GET): /hyperkitty/api/mailman/archive On Debian 11, I have these packages ii mailman3 3.3.3-1 all Mailing list management system ii mailman3-full 3.3.3-1 all Full Mailman3 mailing list management suite (metapackage) ii mailman3-web 0+20200530-2 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-10 all Mailman3 plugin to archive emails with HyperKitty Thanks, Arpad

3 8

signup / registration error - permissions and cert chains
by David Newman Jan. 1, 2022

Jan. 1, 2022

I'd like for regular (non-admin) list subscribers to be able to manage their subscription preferences and view list archives. However, when new users attempt to create logins from the Postorius "Sign Up" page, the server returns the error pasted below, and displays a "server error" page to users. If I'm reading the error correctly, this is related to an inability to verify the cert chain. The /etc/mailman3/settings.py file points to the same cert and key files used by Nginx, Postfix, and Dovecot. Since TLS works OK with these other services, it appears the cert and key are valid. (Viewing the cert in a web browser also supports this.) The keyfile has 0400 permissions. I tried changing this to 0640 and making the keyfile owned by root:mailman. Even after restarting mailman3 and mailmanweb the same error occurs. (Permissions in the cert and key directories and above are not blocking access.) The etc/mailman3/settings.py file includes these settings: EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'dnewman(a)networktest.com' EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know' EMAIL_USE_TLS = 'True' EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt' EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key' But this might only be for email, not Postorius/Django. I checked the Mailman Web docs and settings reference but didn't see anything relevant on either page. https://docs.mailman3.org/en/latest/config-web.html https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html What additional configuration is needed to allow regular users to create and manage their own accounts? Thanks. dn ERROR 2021-12-30 16:03:53,787 436935 django.request Internal Server Error: /accounts/signup/ Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper return bound_method(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/decorators/debug.py", line 76, in sensitive_post_parameters_wrapper return view(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 230, in dispatch return super(SignupView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 74, in dispatch response = super(RedirectAuthenticatedUserMixin, self).dispatch( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 204, in dispatch return super(CloseableSignupMixin, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 102, in post response = self.form_valid(form) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/views.py", line 248, in form_valid return complete_signup( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 209, in complete_signup return perform_login( File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 175, in perform_login send_email_confirmation(request, user, signup=signup, email=email) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/utils.py", line 346, in send_email_confirmation email_address.send_confirmation(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 62, in send_confirmation confirmation.send(request, signup=signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/models.py", line 169, in send get_adapter(request).send_confirmation_mail(request, self, signup) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 464, in send_confirmation_mail self.send_mail(email_template, emailconfirmation.email_address.email, ctx) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/adapter.py", line 136, in send_mail msg.send() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/message.py", line 284, in send return self.get_connection(fail_silently).send_messages([self]) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 102, in send_messages new_conn_created = self.open() File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smtp.py", line 67, in open self.connection.starttls(keyfile=self.ssl_keyfile, certfile=self.ssl_certfile) File "/usr/lib/python3.9/smtplib.py", line 772, in starttls context = ssl._create_stdlib_context(certfile=certfile, File "/usr/lib/python3.9/ssl.py", line 787, in _create_unverified_context context.load_cert_chain(certfile, keyfile) PermissionError: [Errno 13] Permission denied

3 6

multiple sites on a mailman3 server question
by William Oliver Dec. 29, 2021

Dec. 29, 2021

So, I have successfully installed mailman3 and it's working great. However, the way it works now, if someone goes to the domain website, he or she will get the mailman page. I'd prefer that it work something like: My www.example.com goes to a home page lists.example.com goes to the mailman3 page mail.example.com goes to a roundcube page I'm using nginx, and this is the first time I've set up an nginx server (I have traditionally done apache), and I'm still figuring out the syntax. My sites-available file is below, for the domain emergenus.com. The behavior I'm getting is that if I go to mail.emergenus.com, it still redirects to mail.emergenus.com/mailman3/lists, but gives a 404 page not found. If I go to lists.emergenus.com, it redirects to lists.emergenus.com/mailman3/lists and gives the nice postorius page, and works fine. So, I'm trying to figure out how to stop that redirect. When I look at my nginx access.log file for mail.emergenus.com, I see: 174.212.104.153 - - [28/Dec/2021:21:03:21 -0500] "GET /mailman3/lists/ HTTP/1.1" 404 188 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36" Aha! says I. My ip address is 203.159.80.234, not 174.212.104.153. Thus, uwsgi (I think) is sneaking in there and taking over regardless of what I'm trying to do. Is there a way to tell mailman to only take over for lists.emergenus.com and not for www.emergenus.com or mail.emergenus.com? Here's my uwsgi.ini (without then env= PYTHONPATH change discussed in another thread: # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log Here's my /etc/nginx/sites-enabled/emergenus.com looks like: server { root /var/www/html2; index index.html index.htm index.nginx-debian.html; server_name emergenus.com, mail.emergenus.com, www.emergenus.com; location /{ try_files $uri $uri/ =404; } ##### added 12/19 listen 443 ssl default_server; listen [::]:443 ssl default_server; ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { root /var/www/html; index index.html index.htm index.nginx-debian.html; server_name lists.emergenus.com; location /{ proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } listen 443 ssl ; listen [::]:443 ssl ; location /static/ { alias /opt/mailman/web/static/; } ########## ssl_certificate /etc/letsencrypt/live/emergenus.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/emergenus.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = mail.emergenus.com) { # return 301 https://$host$request_uri; return 301 https://mail.emergenus.com; } # managed by Certbot if ($host = www.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot if ($host = lists.emergenus.com) { return 301 https://$host$request_uri; } # managed by Certbot listen 80 ; listen [::]:80 ; server_name www.emergenus.com lists.emergenus.com mail.emergenus.com emergenus.com; return 404; # managed by Certbot } Thanks billo

3 6

Question about lists and domains on Mailman 3
by Philip Colmer Dec. 29, 2021

Dec. 29, 2021

I've got a single server hosting multiple domains. I've got Apache working as the proxy in front of MM3. Regardless of whether I go to https://lists.domainA.org/mailman3/lists/ or https://lists.domainB.org/mailman3/lists/, Postorius lists ALL of the lists across both domains. Is there a way of configuring the system so that, if a user goes to "domain A", only the lists for that domain are listed? Thanks. Philip

2 2

slow restart time for mailmanweb
by David Newman Dec. 29, 2021

Dec. 29, 2021

Debian 11.2, Mailman 3.3.5, Python 3.9.2, MariaDB 10.5.12-0+deb11u1 On a Debian system running MariaDB, mailman3 restarts quickly but mailmanweb takes about 90 seconds: root@myhost # time systemctl restart mailmanweb real 1m30.156s user 0m0.013s sys 0m0.000s The daemon.log has a timeout error: Dec 28 12:16:01 myhost systemd[1]: Stopping GNU Mailman Web UI... Dec 28 12:16:03 myhost uwsgi[409333]: [uWSGI] getting INI configuration from /etc/mailman3/uwsgi.ini Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: State 'stop-sigterm' timed out. Killing. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 409333 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418249 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418250 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418252 (sh) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418254 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418258 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418260 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418261 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418262 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418263 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418264 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418265 (mailman-web) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Killing process 418253 (uwsgi) with signal SIGKILL. Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Main process exited, code=killed, status=9/KILL Dec 28 12:17:31 myhost systemd[1]: mailmanweb.service: Failed with result 'timeout'. Dec 28 12:17:31 myhost systemd[1]: Stopped GNU Mailman Web UI. Here is /etc/systemd/system/mailmanweb.service file. [Unit] Description=GNU Mailman Web UI After=syslog.target network.target mariadb.service mailman3.service [Service] Environment="PYTHONPATH=/etc/mailman3/" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini [Install] WantedBy=multi-user.target Starting with Debian 11, the MariaDB service is called mariadb and not mysqld or mysql. I tried substituting mysqld and mysql here and rerunning 'systemctl daemon-reload' each time, but restart times were similar, and also produced the same timeout error. And here is /etc/mailman3/uwsgi.ini: ##### [uwsgi] # Port on which uwsgi will be listening. http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log ##### What's causing the timeout, and what can I do to speed up restarts? Thanks. dn

4 9