December 2021 - Mailman-users - lists.mailman3.org

Postorius fails to show list because of a large message being held
by Gilles Filippini 22 Dec '21

22 Dec '21

Hi, Recently a member of one of our private lists sent a message with a picture attached. Because of the large message size (23MB) it was put into the moderation queue. But since then postorius fails to open the list's page with this error: Something went wrong Mailman REST API not available. Please start Mailman core. The database logs show that it processed a request related to the held message just before failing: LOG: statement: SELECT message.id AS message_id_1, message.message_id AS message_message_id, message.message_id_hash AS message_message_id_hash, message.path AS message_path FROM message WHERE message.message_id = '<CAEcCghAdp+20jiG19jNGX06xhJ-iYvZGyyV8b-toW7LqCSv5JQ(a)mail.gmail.com>' LIMIT 1 Mailman Core logs: [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 How should I proceed to unblock the situation? Thanks, _g.

4 7

apache2 security for mailman3 admin
by Lars Schimmer 22 Dec '21

22 Dec '21

Hi, I know it is not the perfect place to ask, but if onyone has a good idea, example, I would be happy. I do run mailman3 with apache ProxyPass in front. I did set: <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> as given as example to set it up. Now I want to limit the mailman3/admin area to a defined IP range. Anyone has a working example to limit only the /admin area to a IP range in Apache2, but everything else as it is now? Thank you, MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 1

list footer web customization procedure
by Philippe B 20 Dec '21

20 Dec '21

I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. Could someone share the instructions for doing that? Thanks.

4 21

restricting public lists per virtual domain
by David Newman 17 Dec '21

17 Dec '21

Can lists set to be viewable on the index page be limited to the virtual domain they are a part of? Let's say I have two virtual domains: lists.dom1.tld lists.dom2.tld Currently, if any list in either domain is set to be viewable on the index page, it's viewable in both domains, not just the one it's a part of. How to restrict access on a per-domain basis? I searched the archives and found something about disabling archives per domain [1], but that's a different question. This seems like a standard problem and may have been asked a different way before, and I may have missed it. Thanks in advance for config clues. dn [1] https://lists.mailman3.org/archives/search?mlist=mailman-users%40mailman3.o…

3 3

Strange problem in user lists
by Gelpi Andrea 16 Dec '21

16 Dec '21

Hi, I have a strange problem in one list. when I add a memebr I use the form "Name Surname" <email(a)domain.tld> I cant' understand why, but I have two members with the wrong name. "A B" <C(a)dom.tld> "D E" <F(a)dom.tld> My problem is that A and B must be associated with F(a)dom.tld and vice-versa. I tried to delete the user member and recreate it, but it has always the wrong name. Is it possible to correct those errors? How? Thanks in advance -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

2 1

File in /var/lib/mailman3/queue/bounces/
by Andreas Barth 12 Dec '21

12 Dec '21

Hi, in my local installation there is a file in /var/lib/mailman3/queue/bounces/ since a couple of days. Any hint how to get rid of it? 'mailman unshunt' doesn't do it, but also, it's in queue/bounces and now queue/shunt. Andi

3 4

Hyperkitty - 'MySQL server has gone away'
by dancab＠caltech.edu 10 Dec '21

10 Dec '21

I just deployed Mailman3 last night. This is the first error message I've encountered from Hyperkitty. It looks like a MySQL configuration issue. I've done some tuning to the wait/timeouts but I'm still getting the error message. I suspect the root cause is the size of the message. mailman qfile shows the message has 84746 lines and the .pck file is 6.9M. Let me know if there's more specific tuning that needs to be done to cover larger messages. My MySQL wait/timeouts are set as follows: MySQL [mysql]> SHOW VARIABLES LIKE "%timeout%"; +-----------------------------+----------+ | Variable_name | Value | +-----------------------------+----------+ | connect_timeout | 120 | | delayed_insert_timeout | 300 | | have_statement_timeout | YES | | innodb_flush_log_at_timeout | 1 | | innodb_lock_wait_timeout | 50 | | innodb_rollback_on_timeout | ON | | interactive_timeout | 28800 | | lock_wait_timeout | 31536000 | | net_read_timeout | 90 | | net_write_timeout | 90 | | rpl_stop_slave_timeout | 31536000 | | slave_net_timeout | 60 | | wait_timeout | 28800 | +-----------------------------+----------+ 13 rows in set (0.002 sec) MySQL [mysql]> SHOW VARIABLES LIKE "%wait%"; +---------------------------------------------------+----------+ | Variable_name | Value | +---------------------------------------------------+----------+ | innodb_lock_wait_timeout | 50 | | innodb_spin_wait_delay | 6 | | lock_wait_timeout | 31536000 | | performance_schema_events_waits_history_long_size | 0 | | performance_schema_events_waits_history_size | 0 | | wait_timeout | 28800 | +---------------------------------------------------+----------+ 6 rows in set (0.004 sec) ############################################## ####################### ERROR 2021-11-05 09:26:28,656 261 django.request Internal Server Error: /hyperkitty/api/mailman/archive Traceback (most recent call last): File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 74, in execute return self.cursor.execute(query, args) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 319, in _query db.query(q) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/connections.py", line 259, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (2006, 'MySQL server has gone away') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailmanve/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailmanve/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailmanve/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/hyperkitty/views/mailman.py", line 118, in _decorator return func(request, *args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view return view_func(*args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/hyperkitty/views/mailman.py", line 164, in archive add_to_list(mlist_fqdn, msg) File "/opt/mailmanve/lib/python3.6/site-packages/hyperkitty/lib/incoming.py", line 153, in add_to_list email.save() File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 749, in save force_update=force_update, update_fields=update_fields) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 787, in save_base force_update, using, update_fields, File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 890, in _save_table results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/base.py", line 929, in _do_insert using=using, raw=raw, File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/query.py", line 1204, in _insert return query.get_compiler(using=using).execute_sql(returning_fields) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/models/sql/compiler.py", line 1394, in execute_sql cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 68, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers return executor(sql, params, many, context) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/utils.py", line 90, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/utils.py", line 86, in _execute return self.cursor.execute(sql, params) File "/opt/mailmanve/lib/python3.6/site-packages/django/db/backends/mysql/base.py", line 74, in execute return self.cursor.execute(query, args) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/cursors.py", line 319, in _query db.query(q) File "/opt/mailmanve/lib/python3.6/site-packages/MySQLdb/connections.py", line 259, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (2006, 'MySQL server has gone away')

1 1

Lookup Table Questions
by Peter Williams 08 Dec '21

08 Dec '21

Hello, I am currently working on upgrading our Mailman system from Mailman 3.3.1 to Mailman 3.3.5. Our configuration utilizes containers that run on Alpine Linux. While working on updating the containers I noticed that the recent version of Alpine has dropped support for Berkeley DB lookup tables. Due to this change I think our only option is to switch over from using hash tables to regexp tables (or switch the OS the containers are running on). In addition, while I was working on the updates I realized that even though the Berkeley DB support has been dropped Mailman seems to work ok with the new default lookup table for Postfix on Alpine: LMDB. I was hoping to get a few answers to some of the questions I have with regards to the options we have moving forward. Any help is greatly appreciated! - The Mailman documentation notes that either hash or regexp tables are supported. Is it ok to use LMDB or will I run into issues at some point? - If LMDB tables are not a good idea to use, are there any drawbacks to switching over to regexp tables? My main concern is that we currently have 7000+ mailing lists, and I'm worried that switching over to regexp may result in slower lookups. I am also wondering if there are potential issues if the 'mailman aliases' command is run simultaneously alongside another 'mailman aliases' command. In the past it seems like the hash table was locked (which was good), and I'm not sure if this behavior is kept by moving over to regexp. This may be more of a Postfix question and I apologize in advance if I am asking the wrong mailing list for this. Thank you for any guidance you can provided with this and have a nice day, Peter

2 1

missing graphics in Postorius
by David Newman 08 Dec '21

08 Dec '21

After installing MM3 on Debian 10 using the venv docs, no graphics appear in the admin or list pages, just broken links. The mailmanweb log has lines like this: ERROR 2021-12-07 06:04:10,002 18262 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. which is odd because there is the line for "localhost" in settings.py, and /etc/hosts correctly ties this to 127.0.0.1. There are entries like this in /var/log/nginx/error.log saying the files just aren't there: 2021/12/06 22:00:30 [error] 18123#18123: *65 open() "/opt/mailman/web/static/postorius/img/mailman_logo_small_trans.png" failed (2: No such file or directory), client: x.x.x.x, server: somehost.example.com, request: "GET /static/postorius/img/mailman_logo_small_trans.png HTTP/2.0", host: "somehost.example.com", referrer: "https://somehost.example.com/mailman/lists/" (I've obfuscated names and addresses here, but "somehost.example.com" refers to a valid FQDN in the log.) I thought I'd followed all the venv docs, but the /opt/mailman/web/static/postorius directory doesn't exist. Did I miss something? Thanks. dn

2 3

SMTPSenderRefused - howto enable STARTTLS for local mail drop
by Stefan Bauer 07 Dec '21

07 Dec '21

Dear users, how can we configure mailman3, to use STARTTLS when dropping mails to local postfix for final delivery? Mailman seems to not support this. Even the web-interface complains: SMTPSenderRefused at /accounts/login/(530, b'5.7.0 Must issue a STARTTLS command first', 'postorius(a)lists.mydomain.tld')Request Method: POST Request URL: https://mm3.mydomain.tld/mailman3/accounts/login/ Django Version: 2.2.12 Exception Type: SMTPSenderRefused Exception Value: (530, b'5.7.0 Must issue a STARTTLS command first', 'postorius(a)lists.mydomain.tld')Exception Location: /usr/lib/python3.8/smtplib.py in sendmail, line 880 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 Python Path: ['.', '', Thank you. Stefan

3 10