- Mailman-users - lists.mailman3.org

outgoing messages not sent in a busy loop
by Igor Serebryany 13 Mar '24

13 Mar '24

incoming messages are showing up in hyperkitty but not going out as emails to list members. i've tried enabling the following debug logging: format: %(asctime)s (%(process)d) %(message)s datefmt: %b %d %H:%M:%S %Y propagate: no level: info path: mailman.log [logging.smtp] level: DEBUG [logging.smtp-failure] level: DEBUG [logging.runner] level: DEBUG [logging.debug] level: debug [logging.smtp-failure] level: debug with these options, if i run `tail -f *` in the `log` directory of mailman, i get the following in essentially a busy loop: ``` ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1c9ad050> ==> debug.log <== Mar 13 19:08:46 2024 (17) [NNTPRunner] starting oneloop Mar 13 19:08:46 2024 (17) [NNTPRunner] ending oneloop: 0 Mar 13 19:08:46 2024 (18) [OutgoingRunner] finishing filebase: 1710356926.1738262+0a50dc0e393ba4de10bcdadb5376d4330f670c77 Mar 13 19:08:46 2024 (18) [OutgoingRunner] doing periodic Mar 13 19:08:46 2024 (18) [OutgoingRunner] committing transaction Mar 13 19:08:46 2024 (18) [OutgoingRunner] checking short circuit Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing filebase: 1710356926.2733445+d044aeb93be86fbf662b6e0feffc89d0f2e4eb66 Mar 13 19:08:46 2024 (18) [OutgoingRunner] processing onefile Mar 13 19:08:46 2024 (18) [outgoing] <function deliver at 0x7fef1cda27a0>: <CADJyiOV1RAth=3CkNoHJ1qTVzedzX8BG0k6iwe019jXau30pLw(a)mail.gmail.com> ==> smtp.log <== Mar 13 19:08:46 2024 (18) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fef1cb0f390> ``` which doesn't give me a lot to go on. anyone know what could be causing this or any way to get additional debug information?

2 1

Hyperkitty tracebacks: possible DB corruption?
by peter＠chubb.wattle.id.au 13 Mar '24

13 Mar '24

Hi Folks, Just recently I've started seeing backtraces from Django when trying to view old threads in hyperkitty. They say that more than one LastView is being returned, and at a later date cannot delete a LastView. I'm using the Debian-packaged hyperkitty and postorius, but this code hasn't changed from upstream. The backtraces come when a logged in used revisits a thread. So I see: Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ MultipleObjectsReturned at /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ get() returned more than one LastView -- it returned 2! Then later on I see: LastView.objects.delete(pk=del_id) ^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Manager' object has no attribute 'delete' Here are the backtraces: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/thread.py", line 162, in thread_index last_view_obj, created = LastView.objects.get_or_create( File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 581, in get_or_create return self.get(**kwargs), False File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 439, in get raise self.model.MultipleObjectsReturned( and Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/2022/1/ AttributeError at /hyperkitty/list/devel(a)sel4.systems/2022/1/ 'Manager' object has no attribute 'delete' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 127, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 173, in _thread_list LastView.objects.delete(pk=del_id)

3 6

localtime() cannot be applied to a naive datetime
by Freerk Bosscha 12 Mar '24

12 Mar '24

Since yesterday I get the following error-message when I go to the webinterface: ValueError at /admin/login/ localtime() cannot be applied to a naive datetime Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Exception Type: ValueError Exception Value: localtime() cannot be applied to a naive datetime Exception Location: /usr/lib/python3/dist-packages/django/utils/timezone.py in localtime, line 207 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: vr, 1 Mrt 2024 11:52:50 +0100 Mailman info: mailman info GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman3:xxxxxxx If this issue was posted before, i'm sorry, i haven't found it: Any ideas how to solve this issue would be appreciated Environment: Request Method: GET Request URL: https://mailman.pgtrynwalden.nl/mailman3/admin/login/?next=/mailman3/admin/ Django Version: 2.2.28 Python Version: 3.9.2 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 35. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 145. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 143. response = response.render() File "/usr/lib/python3/dist-packages/django/template/response.py" in render 106. self.content = self.rendered_content File "/usr/lib/python3/dist-packages/django/template/response.py" in rendered_content 83. content = template.render(context, self._request) File "/usr/lib/python3/dist-packages/django/template/backends/django.py" in render 61. return self.template.render(context) File "/usr/lib/python3/dist-packages/django/template/base.py" in render 169. with context.bind_template(self): File "/usr/lib/python3.9/contextlib.py" in __enter__ 117. return next(self.gen) File "/usr/lib/python3/dist-packages/django/template/context.py" in bind_template 246. updates.update(processor(self.request)) File "/usr/lib/python3/dist-packages/postorius/context_processors.py" in postorius 38. mailman_day=(timezone.localtime(timezone.now()).day == MAILMAN_DAY), File "/usr/lib/python3/dist-packages/django/utils/timezone.py" in localtime 207. raise ValueError("localtime() cannot be applied to a naive datetime") Exception Type: ValueError at /admin/login/ Exception Value: localtime() cannot be applied to a naive datetime

2 2

Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)
by Wikinaut 08 Mar '24

08 Mar '24

Hello, I miss sadly the option of both: i) discarding the current message of a sender (not member of a closed list) ; and in the same action ii) adding this person to the whitelist, i.e. accept further mails from this sender. How can this be achieved?

3 4

Re: [Mailman-Developers] Re: Help on Gitlab
by Mark Sapiro 08 Mar '24

08 Mar '24

Plese keep the thread on the list. On 3/8/24 6:36 AM, Daniel Azubuine wrote: > Sir, I get this error > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python: can't > open file '/home/daniel/Documents/repos/mailman/mailman/setup.py': > [Errno 2] No such file or directory > ERROR: invocation failed (exit code 2)/ > _______________________________________________ summary > ________________________________________________ > ERROR: qa: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/qa/bin/python > /home/daniel/Documents/repos/mailman/mailman/setup.py --name (exited > with code 2) > when i run tox -e qa. What is your tox version (tox --version)? You shouldn't need this, but adding ``` skipdist = True ``` in the [tox] section of tox.ini may help. > I also get this when i run tox -e py310-diffcov > ------------- > src/mailman/interfaces/listmanager.py (75.0%): Missing lines 37 > ------------- > Total: 4 lines > Missing: 1 line > Coverage: 75% > ------------- > > ERROR: InvocationError for command > /home/daniel/Documents/repos/mailman/mailman/.tox/py310-diffcov/bin/diff-cover coverage.xml --fail-under=100 --compare-branch origin/master (exited with code 1) This is expected output in this case. Line 37 in your src/mailman/interfaces/listmanager.py is not covered by any tests. Modifying the test_cannot_create_a_list_twice test in src/mailman/model/tests/test_listmanager.py to use assertRaisesRegex rather than assertRaises may help. See <https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertRai…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

mm3 installation question
by advorkin＠cs.princeton.edu 07 Mar '24

07 Mar '24

Hello, everyone. I just completed the initial installation by following the instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install I went with the apache/uswgi configuration. The site is up and running, but if I click Postorius, it gets redirected to https://mysite.com/postorius/lists and I get not found error message. The same goes for Lists and Archives. What did I do wrong? I've found some discussions online, but they seem to be related to a different installation, thus my confusion. Thank you!

4 10

mass unsubscribe/subscribe
by ronn.ramirez＠pge.com 06 Mar '24

06 Mar '24

Hi Mailman Admins, Whenever we mass subscribe or unsubscribe more than 500+ users, we would get a "500-internal-server-error" or a timeout. Is there something we can tweak or increase to way to increase this threshold?

3 2

export/import list?
by Dave McGuire 01 Mar '24

01 Mar '24

I'm migrating to a new Mailman3 instance, finally escaping a fairly old (3.1.1) and problematic distribution repo install on a Linux VM and moving to a venv install in a native SmartOS Zone. I've gotten everything running well and integrated with our (fairly complex) mail server. I'd like to begin migration of the lists on the old mm3 instance. Is there a way to export a list from one Mailman 3 instance and import it into another, on a different machine? Ideally some way to capture its settings, members, members' settings, etc? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

6 9

Migration from old server to new server failed
by Helio Loureiro 01 Mar '24

01 Mar '24

Hi, So we tried to the migration following the steps: - stop mailman in the old machine (v3.1.1 from ubuntu packages) - dump DB mailman3 and mailman3web - backup /var/lib/mailman3 content On the new machine: - checkout from git the version 3.1.1 to match production and install the services - stop mailman3 and mailman3-web on the new machine - load DBs into new machine - copy content from /var/lib/mailman3 into /local/mailman/var (which means: archives/ cache/ data/ ext/ lists/ locks/ messages/ public_suffix_list.dat queue/ templates/ web/) - start mailman3 and mailman-3web - run mailman3-web migrate And I stopped here. Because it crashed. (venv) mailman@new-mailman3-server ~ (v3.1.1) [0|SIGINT]> mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0003_alter_emailaddress_create_unique_verified_email... OK Applying account.0004_alter_emailaddress_drop_unique_email... OK Applying account.0005_emailaddress_idx_upper_email... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying auth.0009_alter_user_last_name_max_length... OK Applying auth.0010_alter_group_name_max_length... OK Applying auth.0011_update_proxy_permissions... OK Applying auth.0012_alter_user_first_name_max_length... OK Applying django_mailman3.0003_sessions... OK Applying django_q.0010_auto_20200610_0856... OK Applying django_q.0011_auto_20200628_1055... OK Applying django_q.0012_auto_20200702_1608... OK Applying django_q.0013_task_attempt_count... OK Applying django_q.0014_schedule_cluster... OK Applying hyperkitty.0016_auto_20180309_0056... OK Applying hyperkitty.0017_file_attachments... OK Applying hyperkitty.0018_threadcategory_color... OK Applying hyperkitty.0019_auto_20190127_null_description... OK Applying hyperkitty.0020_auto_20190907_1927... OK Applying hyperkitty.0021_add_owners_mods...Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) MySQLdb.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main execute_from_command_line(sys.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 96, in wrapped res = handle_func(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/migrate.py", line 349, in handle post_migrate_state = executor.migrate( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 135, in migrate state = self._migrate_all_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards state = self.apply_migration( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py", line 252, in apply_migration state = migration.apply(state, schema_editor) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/migration.py", line 130, in apply operation.database_forwards( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/operations/fields.py", line 108, in database_forwards schema_editor.add_field( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/schema.py", line 104, in add_field super().add_field(model, field) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 636, in add_field return self.create_model(field.remote_field.through) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 447, in create_model self.execute(sql, params or None) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py", line 199, in execute cursor.execute(sql, params) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers( File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers return executor(sql, params, many, context) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 84, in _execute with self.db.wrap_database_errors: File "/local/mailman/venv/lib/python3.10/site-packages/django/db/utils.py", line 91, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 87, in _execute return self.cursor.execute(sql) File "/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py", line 75, in execute return self.cursor.execute(query, args) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 179, in execute res = self._query(mogrified_query) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line 330, in _query db.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py", line 261, in query _mysql.connection.query(self, query) django.db.utils.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators' already exists") I tried to drop the table, but then it complained about another one. I dropped all the complained tables and as result hypperkitty never started. So I went back to see why the first error happened. Any clue what to do next? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 8

Google Summer of Code 2024
by Stephen J. Turnbull 26 Feb '24

26 Feb '24

Hi, everybody It's that time of year again! PSF is in GSoC 2024, I'm 99% certain PSF will accept Mailman as a suborg (don't ask about the 1%, it's embarrassing ;-). Student applications open on March 18. So ... If you have ideas for improving Mailman 3, whether misfeatures that need fixing or cool new features, please consult our ideas page https://wiki.list.org/DEV/Google%20Summer%20of%20Code%202024 to get an idea of level of detail and style of description needed (and to see if maybe it's already there. You can send them to me if they're already formed in your mind, or send them here for input from users on requirements, or to mailman-developers(a)python.org for input on implementation feasibility and appropriateness for GSoC. If you know anybody who would be interested in participating as a contributor, please encourage them to look at us. Rules are somewhat relaxed from years ago. They still don't accept below college age, but they no longer restrict to students. They're also offering multiple period lengths from 8 to 22 weeks (stipends vary according to period and by price level in country of residence, see https://developers.google.com/open-source/gsoc/help/student-stipends). They're not as generous as a few years ago, at least for the "rich" countries (US, UK, Japan). You don't need to be an experienced coder or project manager to be a secondary mentor, just willing to communicate with the code contributor. If you're interested in being a primary or secondary mentor, the burden is likely to be "as much as you want". We rarely get more than one good application, and we have enough "default" primary mentors to cover the likely maximum number of slots we could be allocated. It would be very helpful to us and to the PSF organization administrators if you express interest and get signed up by the end of next week, but as far as I know we can add or substitute mentors at any time. Potential mentors should 1. Have a Google account (needed for step 2, and required by GSoC) 2. Sign up with Python-GSoC at https://forms.gle/coJYxhor6FAZcZfU8 3. If you have been a GSoC mentor or org admin in the past, go to https://summerofcode.withgoogle.com and accept the contributor agreement and program rules for 2024. (Definitely if you did last year, probably for 2022 the system still remembers you, and unlikely it has more memory than that.) Steve

1 0