- Mailman-users - lists.mailman3.org

config.pck from mailman2 has characters that won't import with import21
by Greg Newby July 26, 2024

July 26, 2024

Hi. I've set up MM3 in a venv successfully and am importing my legacy lists. I no longer have a running instance of mailman2, so don't know how I can change the offending list settings (i.e., in config.pck). The problem seems to be a digest footer from the previous incarnation of the list (list name is edited below, to protect the innocent): (venv) mailman@mail:~$ mailman import21 abc(a)lists.abcabcabc.org /var/lib/mailman/lists/abc/config.pck Unable to convert mailing list attribute: msg_footer with value "_______________________________________________ ${display_name} mailing list -- ${listname} To unsubscribe send an email to ${short_listname}-leave@${domain} %(web_page_url)slistinfo/%(_internal_name)s" Unable to convert mailing list attribute: digest_footer with value "_______________________________________________ ${display_name} mailing list -- ${listname} To unsubscribe send an email to ${short_listname}-leave@${domain} %(web_page_url)slistinfo/%(_internal_name)s" Importing members [------------------------------------] 0% Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/commands/cli_import.py", line 89, in import21 import_config_pck(mlist, config_dict) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", line 578, in import_config_pck import_roster(mlist, config_dict, members, MemberRole.member) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", line 625, in import_roster _import_roster(mlist, config_dict, iterator, role, action=action) File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", line 645, in _import_roster if IBanManager(mlist).is_banned(email): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py", line 103, in is_banned re.match(ban.email, email, re.IGNORECASE) is not None): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 167, in match return _compile(pattern, flags).match(string) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile p = _compiler.compile(pattern, flags) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile p = _parser.parse(p, flags) ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 979, in parse p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub itemsappend(_parse(source, state, verbose, nested + 1, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse raise source.error("multiple repeat", re.error: multiple repeat at position 11 It seems that I might need to install mailman2 somewhere to try to change the config.pck. Are there any other options? I have dozens of lists with the same problem. Thanks. Greg Newby

4 4

Run a mailman program outside of mailman shell
by Greg Newby July 25, 2024

July 25, 2024

Hi again folks. I have hundreds of lists to convert from MM2.1 to MM3, and intend to write a Python program do this this rather than running commands in mailman shell (and rather than running 'command()' functions in mailman shell, if possible). However, when I write a simple Python program to run the types of commands found in the Mailman docs, such as these <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>, I get errors. This is a venv installation, following these instructions <https://docs.mailman3.org/en/latest/install/virtualenv.html>. The Mailman3 installation is working fine and I have a handful of lists in production that I set up manually. Here's a very simple program, import-try1.py, just to create a list: #!/opt/mailman/venv/bin/python3 from mailman.app.lifecycle import create_list l = create_list('testlist2(a)lists.aaabbb.org') Here's the output I get (yes, the domain exists and already has lists - I'm putting aaabbb instead of the actual domain name): ./import-try1.py Traceback (most recent call last): File "/opt/mailman/./import-try1.py", line 4, in <module> l = create_list('testlist2(a)lists.aaabbb.org') ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 74, in create_list getUtility(IEmailValidator).validate(fqdn_listname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.12/site-packages/zope/component/_api.py", line 180, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfaces.address.IEmailValidator>, '') I get different errors with other sets of commands. The same commands work fine from `mailman shell`, i.e., (venv) mailman@mail:~$ mailman shell Welcome to the GNU Mailman3 shell on aaabbb.org >>> from mailman.app.lifecycle import create_list >>> l = create_list('testlist2(a)lists.aaabbb.org') >>> Output from mailman info, with the passwords omitted: GNU Mailman 3.3.9 (Tom Sawyer) Python 3.12.3 (main, Apr 10 2024, 05:33:47) [GCC 13.2.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:secretaaabbb@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:reallysecretaaabbb I suspect I just need to either change the interpreter (1st line of my program), or find the correct 'import' lines (I've tried numerous variations; the above is the simplest example). Help will be appreciated! Greg

4 5

Error when click on mailing list: An error occurred while processing your request.
by adam.heathcote＠utas.edu.au July 25, 2024

July 25, 2024

Hey there, We have a Mailman3 server with quite a few lists all running with no issues. Recently I imported a list from our old Mailman 2 server which went fine. I attempted to remove the current owner and add myself but now when clicking on the list, Postorius shows: An error occurred while processing your request. The output of /opt/mailman/web/logs/mailmanweb.log is here: ERROR 2024-07-09 17:11:33,371 2795 django.request Internal Server Error: /mailman3/lists/net-ops.list.utas.edu.au/ Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 103, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/generic.py", line 76, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/views/generic/base.py", line 142, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib64/python3.9/site-packages/postorius/views/list.py", line 411, in get return render(request, 'postorius/lists/summary.html', data) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/defaulttags.py", line 52, in render output = self.nodelist.render(context) File "/opt/mailman/venv/lib64/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) TypeError: sequence item 1: expected str instance, NoneType found I've tried removing it and reimporting it to no avail. Is there anything I can besides manually creating it and adding the members and owners from the old server? Cheers

2 5

First time mailman installation
by roland＠giesler.za.net July 25, 2024

July 25, 2024

I have installed mailman3 on Ubuntu including postorius & hyperkitty (from the packages). I have questions now which are not quite clear to me from the docs: 1. How do I specify my mail server details (which is my own server running postfix, etc) 2. How do I create new lists from the postorius UI, or can I only do that in the config files or the command line console for mailman3? thanks!

3 2

Mailman3 service won't start - Ubuntu 20.04
by willie.castillo＠caemilusa.com July 23, 2024

July 23, 2024

This is a fresh install (Ubuntu and mailman3), followed all steps in this document (https://docs.mailman3.org/en/latest/install/virtualenv.html) However, when trying to start mailman3 automatically (step https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma…) it won't start, it's throwing this error: × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2024-07-22 17:34:27 UTC; 8min ago Process: 1429 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 985ms Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: id SERIAL NOT NULL, Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: email VARCHAR, Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: list_id VARCHAR, Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: PRIMARY KEY (id) Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: ) Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: ] Jul 22 17:34:27 tpalxinflistsp1 mailman[1429]: (Background on this error at: https://sqlalche.me/e/20/f405) Jul 22 17:34:27 tpalxinflistsp1 systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Jul 22 17:34:27 tpalxinflistsp1 systemd[1]: mailman3.service: Failed with result 'exit-code'. Jul 22 17:34:27 tpalxinflistsp1 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. Ran "journalctl -xeu mailman3" for details and got this" Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 314, in _invoke_with Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return bind.execute(self) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1418, in execute Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return meth( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/sql/ddl.py", line 180, in _execute_on_connection Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return connection._execute_ddl( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1529, in _execute_ddl Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ret = self._execute_context( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1846, in _execute_context Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: return self._exec_single_context( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1986, in _exec_single_context Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: self._handle_dbapi_exception( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2353, in _handle_dbapi_exception Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: raise sqlalchemy_exception.with_traceback(exc_info[2]) from e Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: self.dialect.do_execute( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: File "/opt/mailman/venv/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 924, in do_execute Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: cursor.execute(statement, parameters) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: sqlalchemy.exc.ProgrammingError: (psycopg2.errors.InsufficientPrivilege) permission denied for schema public Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: LINE 2: CREATE TABLE ban ( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ^ Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: [SQL: Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: CREATE TABLE ban ( Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: id SERIAL NOT NULL, Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: email VARCHAR, Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: list_id VARCHAR, Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: PRIMARY KEY (id) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ) Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: ] Jul 22 17:43:29 tpalxinflistsp1 mailman[1722]: (Background on this error at: https://sqlalche.me/e/20/f405) Jul 22 17:43:29 tpalxinflistsp1 systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit mailman3.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jul 22 17:43:29 tpalxinflistsp1 systemd[1]: mailman3.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The unit mailman3.service has entered the 'failed' state with result 'exit-code'. Jul 22 17:43:29 tpalxinflistsp1 systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. ░░ Subject: A start job for unit mailman3.service has failed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit mailman3.service has finished with a failure. ░░ ░░ The job identifier is 1101 and the job result is failed.

2 6

Unable to remove non-member
by kapoortoman＠gmail.com July 23, 2024

July 23, 2024

Hi Everyone, I ran across a strange issue today. A client reported the inability to remove a non-member in the following format: z_email/domain.org.za(a)domain.org.za The reported error from Postorius was: "The user could not be removed" I used https://mailtester.ninja/ to validate the email address and it is syntactically correct. -- JayceonChandler

2 1

Mailman3 on AlmaLinux 9 - Python3.9 errors
by willie.castillo＠caemilusa.com July 19, 2024

July 19, 2024

Hi, I'm trying to configure mailman3 on my AlmaLinux 9 server and when checking the mailman3 status, I get the following: # mailman3 status Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 227, in _catch_revision_errors yield File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 439, in _upgrade_revs for script in reversed(list(revs)) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 793, in iterate_revisions revisions, heads = fn( File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 1420, in _collect_upgrade_revisions current_revisions = self.get_revisions(lower) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 525, in get_revisions return sum([self.get_revisions(id_elem) for id_elem in id_], ()) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 525, in <listcomp> return sum([self.get_revisions(id_elem) for id_elem in id_], ()) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 549, in get_revisions return tuple( File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 550, in <genexpr> self._revision_for_ident(rev_id, branch_label) File "/usr/lib/python3.9/site-packages/alembic/script/revision.py", line 619, in _revision_for_ident raise ResolutionError( alembic.script.revision.ResolutionError: No such revision or branch '2156fc3f6f7d' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/libexec/mailman3/mailman", line 8, in <module> sys.exit(main()) File "/usr/lib/python3.9/site-packages/click/core.py", line 1128, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.9/site-packages/click/core.py", line 1052, in main with self.make_context(prog_name, args, **extra) as ctx: File "/usr/lib/python3.9/site-packages/click/core.py", line 914, in make_context self.parse_args(ctx, args) File "/usr/lib/python3.9/site-packages/click/core.py", line 1615, in parse_args rest = super().parse_args(ctx, args) File "/usr/lib/python3.9/site-packages/click/core.py", line 1370, in parse_args value, args = param.handle_parse_result(ctx, opts, args) File "/usr/lib/python3.9/site-packages/click/core.py", line 2347, in handle_parse_result value = self.process_value(ctx, value) File "/usr/lib/python3.9/site-packages/click/core.py", line 2309, in process_value value = self.callback(ctx, self, value) File "/usr/lib/python3.9/site-packages/mailman/bin/mailman.py", line 95, in initialize_config initialize(value) File "/usr/lib/python3.9/site-packages/mailman/core/initialize.py", line 229, in initialize initialize_2(propagate_logs=propagate_logs) File "/usr/lib/python3.9/site-packages/mailman/core/initialize.py", line 187, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/usr/lib/python3.9/site-packages/mailman/database/factory.py", line 58, in create SchemaManager(database).setup_database() File "/usr/lib/python3.9/site-packages/mailman/database/factory.py", line 109, in setup_database alembic.command.upgrade(alembic_cfg, 'head') File "/usr/lib/python3.9/site-packages/alembic/command.py", line 320, in upgrade script.run_env() File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 563, in run_env util.load_python_file(self.dir, "env.py") File "/usr/lib/python3.9/site-packages/alembic/util/pyfiles.py", line 92, in load_python_file module = load_module_py(module_id, path) File "/usr/lib/python3.9/site-packages/alembic/util/pyfiles.py", line 108, in load_module_py spec.loader.exec_module(module) # type: ignore File "<frozen importlib._bootstrap_external>", line 850, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/lib/python3.9/site-packages/mailman/database/alembic/env.py", line 77, in <module> run_migrations_online() File "/usr/lib/python3.9/site-packages/mailman/database/alembic/env.py", line 71, in run_migrations_online context.run_migrations() File "<string>", line 8, in run_migrations File "/usr/lib/python3.9/site-packages/alembic/runtime/environment.py", line 851, in run_migrations self.get_context().run_migrations(**kw) File "/usr/lib/python3.9/site-packages/alembic/runtime/migration.py", line 608, in run_migrations for step in self._migrations_fn(heads, self): File "/usr/lib/python3.9/site-packages/alembic/command.py", line 309, in upgrade return script._upgrade_revs(revision, rev) File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 435, in _upgrade_revs return [ File "/usr/lib64/python3.9/contextlib.py", line 137, in __exit__ self.gen.throw(typ, value, traceback) File "/usr/lib/python3.9/site-packages/alembic/script/base.py", line 259, in _catch_revision_errors raise util.CommandError(resolution) from re alembic.util.exc.CommandError: Can't locate revision identified by '2156fc3f6f7d' Any ideas why?

4 10

Strange URL in error message
by waps＠tantalus.jena.thur.de July 18, 2024

July 18, 2024

(Debian 12) I have the problem that the hyperkitty archive is empty. The file /var/log/mailman3/mailman.log show sometimes the message urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.XXXXX-project.demailman3', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa48b43a910>: Failed to establish a new connection: [Errno -2] Name or service not known')) (there is a slash missing between 'project.de' and 'mailman3'). My goal is, of course, to have an running archive. But I think the error message could be a hint about the reason) Do you have an idea what can I do about this?

2 5

deployment recommendation(?)
by noc＠iem.at July 18, 2024

July 18, 2024

(sorry, if this comes in double; i sent the same mail yesterday, but it seems it didn't make it (i did check the archives); so i'm re-sending via the webinterface) hi, it's summer here in europe, and students have left the campus. so - like every summer - I ponder on the idea of migrating our old mailman2 instance that has served us for the last twenty years to a new and shiny mailman3. and - like always - i'm a bit unsure about the best way to proceed to find the optimum deployment strategy for a long-running (decades) medium-sized (our largest list has ~1800 members) installation. one of our primary objectives is receiving *security updates*. we also would like to stay on top of development (that is: use the latest and greatest *stable* mailman3 release). in my heart i am a Debian person, so my mailman2 installation just used the Debian packages. the new deployment machine, will be Debian based as well. now https://docs.mailman3.org/en/latest/install/install.html lists three options: # Debian packages this is what I would normally pick, but: my past experience with mailman3 in Debian was... rather suboptimal. (my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). i see that the packages in current Debian/stable ("bookworm"), are lagging slightly (3.3.8, rather than 3.3.9), though that's to be expected from a distro with stable releases. otoh, Debian/unstable still ships 3.3.8, which is a bit disappointing. in any case, the really nice thing about (Debian-official) Debian packages is that they are typically - stable - guarantee an upgrade path between releases # Docker packages this is of course the simplest from a deployment perspective, but then i'm a bit worried about the security perspective. in my perception, docker deployments tend to get installed and then forgotten, and while the host OS keeps getting updates, the docker images are just left as is. so they tend to get stale. i would like to know how this is handled # virtualenv this is the deployment method recommended in the docs. however, it doesn't say why this method is any better than the others. also, the website says that it was last updated in 2019, so: is this recommendation still relevant? personally i do not have much experience with deployment of long-running software in virtualenv, and i'm esp worried a bit when it comes to switching python releases (which will happen multiple times in the next few years) i use virtualenv all the time for my pet projects, but there it doesn't matter much, if the venv breaks: i just delete it and start from scratch. but those are not long-running services. so: what are the drawbacks, limitations, advantages and benefits of the various deployment methods? i'd really like to make the switch this year! gmfasdr IOhannes

4 3

Setting PYTHONPATH in the virtual environment installation
by Keith Christian July 15, 2024

July 15, 2024

Before switching from a "git clone" installation to the virtual environment install, "/home/mailman3/mailman/src/mailman" was recommended as the PYTHONPATH setting. Here are some paths that exist in the Mailman3 virtual environment on the server in question: /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/__init__.py /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/__pycache__ /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/docs /opt/mailman3/venv/lib/python3.9/site-packages/mailman/archiving/mailarchive.py What is the proper setting for PYTHONPATH in this case? Thanks. ----------- Keith

2 1