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

list footer web customization procedure
by Philippe B Dec. 20, 2021

Dec. 20, 2021

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

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

Dec. 10, 2021

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

SMTPSenderRefused - howto enable STARTTLS for local mail drop
by Stefan Bauer Dec. 7, 2021

Dec. 7, 2021

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

Sort Lists in Postorious
by Jonathan Wright Nov. 30, 2021

Nov. 30, 2021

Is there a way to sort the lists displayed on the main page of Postorious?

3 2

Renaming a server after building
by Philip Colmer Nov. 27, 2021

Nov. 27, 2021

We're getting closer to migrating from Mailman 2 to Mailman 3. In preparation, I want to get new servers built ready to accept the migrated data from our old MM2 servers before we shut them down. So, the new servers will be something like "new-lists.example.com" to complement the existing "lists.example.com" servers. When we are ready to do the migration, we'll rename the MM2 servers to "old-lists" and rename the MM3 servers to "lists" and then migrate the data. Looking at the settings in the Django admin interface, I *thought* I had figure out how best to do this: - Under /admin/sites/site/, click on the existing domain name and change it to match the correct FQDN. - Under /admin/django_mailman3/maildomain/, click on the exist mail domain and change the mail domain to match the correct FQDN. However, although the above works, if I then go back to the *Mailman* interface and go to /mailman3/domains/, the web interface recreates a domain for the original domain name that was in place when the server was created, i.e. we end up with "lists" and "new-lists". We've tried deleting that "new-lists" domain, rebooting and trying again but "new-lists" keeps on being created again. What am I overlooking here? Is there a better/approved way to achieve what we want to achieve? Thanks. Philip

2 1

Hyperkitty: Error when rebuilding Index
by M4tze Nov. 26, 2021

Nov. 26, 2021

Dear list members, if there is any Hyperkitty expert here, I have issues in Hyperkitty (just updated Maxkings Docker images) when rebuilding the Index. Unfortunately, there are more than 25,000 mails and I do not know which one is/might be broken. Does the error mean that the rebuilding process is incomplete or does it simply skip the erroneous message? Thank you in advance - M4tze Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 297, in handle self.update_backend(label, using) File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 342, in update_backend max_pk = do_update( File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 100, in do_update current_qs = list(current_qs) File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 269, in __len__ self._fetch_all() File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 1308, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 53, in __iter__ results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 317, in _query self._post_get_result() File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 352, in _post_get_result self._rows = self._fetch_row(0) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 325, in _fetch_row return self._result.fetch_row(size, self._fetch_type) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position 3209: invalid continuation byte

2 1

mass subscribers disablement!?
by Christian Stalberg Nov. 26, 2021

Nov. 26, 2021

I added the additional hosts to ALLOWED HOSTS in settings_local.py and mailman is distributing mail to subscribers again. However, I then received many emails of valid users subscriptions being disabled. What would cause that? Can subscriber management be done via command line?

2 5

Post-installation documentation?
by David Newman Nov. 26, 2021

Nov. 26, 2021

Is post-installation documentation available for a full Mailman3 installation on a new Debian 11 machine? I am looking for a high-level "do these steps next to get a list working" document rather than an API command reference. I followed the venv documentation and the installation went ok, but still have questions about what to do next, e.g.: - why do the venv docs and admin FAQ give different nginx configs for the reverse proxy? https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… - Does the 'Secret_Hyperkitty_API_Key' need to go anywhere else besides /opt/mailman/mm/mailman-hyperkitty.cfg? - For Django (presumably in /etc/mailman3/settings.py, but the docs don't say), what values to use with Postfix to set up the email back end? I have a working test list, but am not altogether sure it's set up correctly. Thanks in advance for pointers to docs beyond the installation steps. dn

3 17

List in list, mutiple reply-to addresses
by Stefan Bauer Nov. 26, 2021

Nov. 26, 2021

Dear List, we habe observerd the following behavior, when a list is member of another list, the reply-to-address has multiple entires: list iu-all@mydomain member: iu-int@mydomain list iu-int@mydomain member: john@mydomain Case) Sender: mike@mydomain To: iu-all@mydomain john receives following mail: from: iu-int@mydomain reply-to: mike@mydomain, iu-all@mydomain If john now hits reply in mailclient, mail goes to ALL instead of just the from-address, as mailman extended the reply-to header. How can this be changed? thank you. Stefan

2 7

Unsubscribe all (any plan to use mass-subscription API?)
by Alan So Nov. 22, 2021

Nov. 22, 2021

Tested that "Unsubscribe all" in Postorius1.3.6 is not making use of mass-subscription API while mass removal of a list of addresses already make use of the API. Any plan to change to use the API in 1.3.7? Thanks.

1 0