- Mailman-users - lists.mailman3.org

Upgrading mailman 3 venv installation
by Morris Jones Sept. 30, 2021

Sept. 30, 2021

Congratulations on the new release for Mailman 3 Core! I'm not a daily pip/python user, so I'm probably behind on the safe and proper way to update my installation (which is working pretty well). In my virtual environment, I ran `pip list -o` and got a significant list. I noticed that all of the mailman packages seemed to be "Type sdist" and the framework packages "Type wheel". (Dunno what "Type" means in this context.) So I tried `pip list -o | grep sdist` and got a smaller list: (venv) mailman@mail:~$ pip list -o | grep sdist atpublic 2.1.1 2.3 sdist django-allauth 0.43.0 0.45.0 sdist django-mailman3 1.3.4 1.3.7 sdist flufl.i18n 3.1.3 3.2 sdist flufl.lock 5.0.3 6.0 sdist HyperKitty 1.3.3 1.3.4 sdist lazr.config 2.2.2 2.2.3 sdist mailman 3.3.2 3.3.5 sdist mailmanclient 3.3.1 3.3.3 sdist mysqlclient 2.0.1 2.0.3 sdist postorius 1.3.3 1.3.6 sdist Is this a reasonable list of the packages that I should update? Are there framework updates I should be concerned with? I'm remembering that a specific non-current version of django was required for mailman. The one I have installed is 3.0.11, with 3.2.7 listed as Latest. My plan is to archive the virtualenv directory, upgrade the packages listed above. If something breaks, I should be able to restore the archived virtualenv. I'm running a single server, Ubuntu 18.04.6, with Zimbra running alongside. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

2 3

Ann: Mailman Core 3.3.5b1 is out
by Abhilash Raj Sept. 29, 2021

Sept. 29, 2021

Hello Everyone, I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a pre-release for 3.3.5, which is slated to come out in 3 weeks from now. I am planning for a 2 week beta period, after which I'll release the first RC and then stable a week after. Right now I am not planning to release a second beta version, but if there are several changes in Core in the next week or so, then I might. This release includes a lot of bug fixes and some new features. It also includes a security enhancement that improves the authentication of REST API by adding resistance to some timing channel attacks. A full list of changes in this version can be found here[1]. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… We have also made improvements in the i18n workflow and now the email templates are updated from the translated messages in the .po files that we get from Weblate. Documentation for translators is available here[2] if you want to help translate Mailman into your native language. [2]: https://docs.mailman3.org/en/latest/translation.html This is a pre-release version, if you want to test it with your setup, you can install it using: $ pip install --pre mailman==3.3.5b1 If you want to download a release tarball, you can do so from here: https://pypi.org/project/mailman/3.3.5b1/#files This release received a lot of contributions from community, which I am really happy about! I'd like to thank everyone who made this release possible! -- thanks, Abhilash Raj (maxking)

5 8

Centralizing logging
by Odhiambo Washington Sept. 29, 2021

Sept. 29, 2021

Hello crew, Installing Mailam3 on FreeBSD. In mailman.cgf, I have set: var_dir: /usr/local/mailman/var When I ran "mailman -C mailman.cgf info" it created the necessary directory tree. There is /usr/local/mailman/var/logs/ However, there is this process that *forced* me to create usr/local/mailman/*logs/mailmansuite.log *as opposed to it just writing to var/logs/ path above Is there a way to make it write its log $var_dir ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

2 2

Ann: Postorius 1.3.6b1 is now out
by Abhilash Raj Sept. 29, 2021

Sept. 29, 2021

Hey Everyone, I am pleased to announce that Postorius 1.3.6b1 is now out. This is the first pre-release for 1.3.6, which is slated to release next week soon after Mailman Core 3.3.5 release. This release requires Mailman Core 3.3.5 release, so if you are trying out this release, please also upgrade Mailman Core to 3.3.5rc1 (which was just released today). This release includes several new features and bug fixes. A full list of changes is available here[1]. With this release, we have also improved on the localization of the interface, if you want to help out before the release of the stable 1.3.6, please see the instructions for translators here[2]. We use Weblate for translations, so if you are familiar with that, you can directly head over there[3]. Since this is a pre-release version, you can install this using pip via: $ pip install --upgrade --pre postorius django-mailman3 mailmanclient Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). A release tarball is available on PyPI: https://pypi.org/project/postorius/1.3.6b1/#files Finally, thanks to all the folks who helped with this release in any capacity and made it possible. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 [2]: https://docs.mailman3.org/en/latest/translation.html [3]: https://hosted.weblate.org/projects/gnu-mailman/postorius/ [4]: https://docs.mailman3.org/en/latest/upgrade-3.2.html#virtualenv-install thanks, Abhilash

4 5

Not sure which part of Mailman 3 is generating this exception
by Philip Colmer Sept. 28, 2021

Sept. 28, 2021

I've found the following exception in "mailman.log": [28/Sep/2021:11:17:18 +0000] "GET /3.1/lists/test(a)mm3.lavasoftware.org HTTP/1.1" 200 374 "-" "GNU Mailman REST client v3.3.3" 2021-09-28 11:17:18 [FALCON] [ERROR] GET /3.1/lists/test(a)mm3.lavasoftware.org/config => Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute cursor.execute(statement, parameters) psycopg2.OperationalError: SSL error: sslv3 alert bad record mac The above exception was the direct cause of the following exception: Traceback (most recent call last): File "falcon/app.py", line 361, in falcon.app.App.__call__ File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/rest/listconf.py", line 282, in on_get value = getter.get(self._mlist, attribute) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/rest/helpers.py", line 228, in get value = list(value) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/model/mailinglist.py", line 348, in filter_types for content_filter in results: File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3535, in __iter__ return self._execute_and_instances(context) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3560, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1011, in execute return meth(self, multiparams, params) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement ret = self._execute_context( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context self._handle_dbapi_exception( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception util.raise_( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 608, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) SSL error: sslv3 alert bad record mac [SQL: SELECT contentfilter.id AS contentfilter_id, contentfilter.mailing_list_id AS contentfilter_mailing_list_id, contentfilter.filter_type AS contentfilter_filter_type, contentfilter.filter_pattern AS contentfilter_filter_pattern FROM contentfilter WHERE %(param_1)s = contentfilter.mailing_list_id AND contentfilter.filter_type = %(filter_type_1)s] [parameters: {'param_1': 1, 'filter_type_1': 0}] (Background on this error at: http://sqlalche.me/e/13/e3q8) [2021-09-28 11:17:18 +0000] [2076] [ERROR] Error handling request /3.1/lists/test(a)mm3.lavasoftware.org/config Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/venv/lib/python3.8/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/database/transaction.py", line 51, in wrapper config.db.commit() File "/opt/mailman/venv/lib/python3.8/site-packages/mailman/database/base.py", line 52, in commit self.store.commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 1046, in commit self.transaction.commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/orm/session.py", line 508, in commit t[1].commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1762, in commit self._do_commit() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1793, in _do_commit self.connection._commit_impl() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 773, in _commit_impl self._handle_dbapi_exception(e, None, None, None, None) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1514, in _handle_dbapi_exception util.raise_(exc_info[1], with_traceback=exc_info[2]) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 771, in _commit_impl self.engine.dialect.do_commit(self.connection) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 392, in connection self._handle_dbapi_exception(e, None, None, None, None) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1514, in _handle_dbapi_exception util.raise_(exc_info[1], with_traceback=exc_info[2]) File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 390, in connection return self._revalidate_connection() File "/opt/mailman/venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 469, in _revalidate_connection raise exc.InvalidRequestError( sqlalchemy.exc.InvalidRequestError: Can't reconnect until invalid transaction is rolled back I'm happy to report it as an issue against the appropriate part on GitLab but it isn't entirely clear to me which part of the suite is causing this. I think it is Core but I'm not absolutely sure. Philip

2 1

DKIM and ARC - *anyone* got this working?
by Philip Colmer Sept. 28, 2021

Sept. 28, 2021

Has anyone using Mailman 3 successfully got DKIM *and* ARC working? I don't mind which MTA you are using or which add-ons you are using to provide the support for DKIM and ARC. I'm just trying to see if there is actually anyone that has both pieces working. By working, I mean sending an email to a Mailman 3 list and receiving the email back from Mailman 3 and the receiving MTA confirms that both DKIM and ARC headers are valid. If you have got it working, please can you share which MTA you are using and the software you are using for DKIM and ARC. Thank you. Regards Philip

1 0

Language confusion in held mail notifications
by Henrik Rasmussen Sept. 28, 2021

Sept. 28, 2021

I just upgraded from Mailman 3.2.0 (La Villa Strangiato) to Mailman 3.3.4 (Tom Sawyer) - Docker Mailman v0.3.12. As the language is not possible to set, and the default language is English, I set my user profile to Spanish and the list config to German, to figure out where the changes would take affect. After sending a mail to the list as the moderated list user, the resulting notification returned to the users email address is mostly in German, but the reason indicated is in Spanish "El mensaje proviene de un miembro moderado". > Ihre Nachricht an 'testlist@mailman' mit dem Betreff > > Test 202109221045 > > wurde zurückgehalten, bis eine Moderator*in sie freigegeben hat. > > Der Grund dafür ist: > > El mensaje proviene de un miembro moderado > > Ihre Nachricht wird entweder an die Liste zugestellt, oder Sie werden > über die die Entscheidung der Moderator*innen benachrichtigt. I would expect that Mailman would respect the user's language setting (in case the user have a profile) or otherwise the list language setting (if no user profile). /Henrik Rasmussen

3 6

Anyone using Rspamd with Mailman 3?
by Philip Colmer Sept. 25, 2021

Sept. 25, 2021

If you are, and you have DKIM and/or ARC working from Rspamd, would you mind sharing your configuration please? Thanks. Philip

4 8

Docker-mailman 0.4.0 release
by Abhilash Raj Sept. 23, 2021

Sept. 23, 2021

Hey Everyone, I tagged and released 0.4.0 version of container images for Mailman. This release includes several fixes that have been accumulating in the repo for how Mailman is setup in the containers. This release does not include any mailman component version bump from 0.3.12 release. More specifically, the major change is that we no longer require static IP configuration in the container images (like previously) and can handle dynamic addresses that are allocated to the containers by Docker. This should help simplify the setup for folks using Kubernetes or other setup than the provided docker-compose files. The migration steps are documented here[1]. Please checkout the release in Github[2] for more details on the changes made in this release. If you are having issues with upgrading your setup to this release, please open an issue on the issue tracker[3] for help. [1]: https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release [2]: https://github.com/maxking/docker-mailman/releases/tag/v0.4.0 [3]: https://github.com/maxking/docker-mailman/issues -- thanks, Abhilash Raj (maxking)

1 0

disable body transcoding
by Markus Schaaf Sept. 23, 2021

Sept. 23, 2021

Hi, I have disabled all message modifications and filtering from within the webUI, and created empty header and footer template files. Still, some list messages get their body encoding changed to base64, breaking DKIM. What can I do to prevent this? (I'm a newbie to mailman3, so please give somewhat complete commands. I have read other threads with similar questions, but did not understand some shortened configuration commands.) BR

3 6