October 2023 - Mailman-users - lists.mailman3.org

Hyperkitty href url to css cache files is not correct
by Alexander Maier 05 Oct '23

05 Oct '23

Hello guys i just created my first mailing list on uberspace. Everything works fine at the moment but I have a problem with the stylesheets of hyperkitty. I recognized that hyperkitty creates for each new access to its website a css CACHE file which is stored at '/static/CACHE/css/'. The url in the HTML file sets the href to /static/CACHE/css/ but the files are only accessible with '/hyperkitty/static/CACHE/css/'. I tried out some probably solutions but nothing works... Could you guys help me?

2 3

Template variables in list:user:notice:post
by Jörg Michael Schulz 05 Oct '23

05 Oct '23

when I add $hyperkitty_url in the postorius template list:user:notice:post, this variable is not expanded, but rests in clear text, like: Das Archiv befindet sich hier: $hyperkitty_url Moreover, when I use $listname. (the dot after the variable name!), no confirmation arrives. Leaving a space between the variable name and the ‚.' helps.

3 2

400 error on held messages
by Dan Caballero 05 Oct '23

05 Oct '23

I've got a couple of lists throwing this error when attempting to view "Held Messages" HTTP Error 400: invalid literal for int() with base 10: 'oAAAANSUhEUgAACfYAAAiVBORw0KGgoAAAANSUhEUgAACfYAAAYKCAIAAAAQvT9CAAAACXBIWXMAAC4jAAAuIwF4pT92AAAg\r\n' Any ideas on what could be causing this? Database corruption of some kind? Dan Caballero Caltech

2 4

Mailman 3 Privacy Policies, GDPR, etc and social logins
by Jered Floyd 05 Oct '23

05 Oct '23

Greetings, I host a variety of lists for social, community, and software projects, and updated my infrastructure from Mailman 2 to Mailman 3 last year. As part of this, I enabled Django allauth modules to simplify login and management for subscribers. Recently, Facebook notified me that they would be disabling the "application" because it failed to provide a sufficient Privacy Policy. Previously I had linked the app to [ https://www.gnu.org/software/mailman/privacy.html, | https://www.gnu.org/software/mailman/privacy.html, ] but they have said: Platform Terms 4.b: Your privacy policy must comply with applicable law and regulations and must accurately and clearly explain what data you are Processing, how you are Processing it, the purposes for which you are Processing it, and how Users may request deletion of that data. During testing, we found that your privacy policy doesn’t explain how users can request data deletion. Update your privacy policy to include this information before you submit an appeal. This is a bit of a headache. Do we have a draft of a community Privacy Policy for a vanilla Mailman 3 install that meets Facebook's requirements? Is this going to be a constantly unraveling thread of future GDPR and Right to Be Forgotten troubles, since there doesn't seem to be an easy way to scrub a subscriber from Hyperkitty archives if they request so? How have others addressed this situation? Regards, --Jered

2 2

All list messages shunted due to mailman core database lock
by Ryan Curtin 04 Oct '23

04 Oct '23

Hi there, I have been trying to debug a git commit development list for a project I maintain: http://lists.mlpack.org/mailman3/hyperkitty/list/mlpack-git@lists.mlpack.or… The list is run on mailman3 as provided by Debian. Messages are successfully received---you can see all the test messages in the archives I just linked to if you want to click on it. However, no messages are actually relayed to subscribers. I spent a while digging into logs and found that every message sent to the list results in an error like this in /var/log/mailman3/mailman.log: ``` Oct 02 17:01:26 2023 (2957556) Uncaught runner exception: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?] [parameters: ('2023-10-02 21:01:21.702224', 99565, 2)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Oct 02 17:01:26 2023 (2957556) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3/dist-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/acknowledge.py", line 46, in process member = mlist.members.get_member(sender) File "/usr/lib/python3/dist-packages/mailman/model/roster.py", line 120, in get_member memberships = self._get_all_memberships(email) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/roster.py", line 116, in _get_all_memberships return members_a.union(members_u).all() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3373, in all return list(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3534, in __iter__ self.session._autoflush() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1633, in _autoflush util.raise_(e, with_traceback=sys.exc_info()[2]) File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1622, in _autoflush self.flush() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2540, in flush self._flush(objects) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2682, in _flush transaction.rollback(_capture_exception=True) File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ compat.raise_( File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2642, in _flush flush_context.execute() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/unitofwork.py", line 422, in execute rec.execute(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/unitofwork.py", line 586, in execute persistence.save_obj( File "/usr/lib/python3/dist-packages/sqlalchemy/orm/persistence.py", line 230, in save_obj _emit_update_statements( File "/usr/lib/python3/dist-packages/sqlalchemy/orm/persistence.py", line 994, in _emit_update_statements c = cached_connections[connection].execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1011, in execute return meth(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement ret = self._execute_context( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context self._handle_dbapi_exception( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception util.raise_( File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.OperationalError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?] [parameters: ('2023-10-02 21:01:21.702224', 99565, 2)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Oct 02 17:01:26 2023 (2957556) SHUNTING: 1696280486.719109+114cb2cc738a61874a5eed7e3f66a3ac111f5b90 ``` I have tried a handful of things: * Restart mailman3 and mailman3-web systemd services. * Ensure that there are no stale locks in /var/lib/mailman3/locks/ when mailman3 core is stopped. * Move the database in /var/lib/mailman3/data/mailman.db out of the way and replace it with a copy, in case some process is holding it open. * Unshunt all the messages with `sudo /usr/bin/mailman3 unshunt` (didn't realize this would drop all the shunted messages, but not a big deal). Most threads I have read appear to be related to the Django interface encountering a locked database, but this looks different---it seems mailman core is having the problem, not anything having to do with mailman3-web or Django. Does anyone have any thoughts on things I can do to fix this error? I am not a mailman3 expert (and to be perfectly honest I don't want to be one, I just want to post things to the list :)). One extra caveat: rebooting the machine I am using is not a realistic option. Thanks in advance for any help. Ryan -- Ryan Curtin | "Not like this... not like this." ryan(a)ratml.org | - Switch

2 2

parallel processing of out queue messages
by Dan Caballero 04 Oct '23

04 Oct '23

Hello, I have tried increasing the number of runners to alleviate a backlog of messages in the "out" queue. I increased the out runners to from 32 to 64. However, I'm not seeing a significant increase in the processing of "out" messages. I've seen at most 12 ".bak" files in the out queue after increasing the runner instances. Is there another configuration needed beyond the number of runner instances to get more messages processed at once? Thanks as always for your help! -- Dan

3 5

Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)
by Wikinaut 02 Oct '23

02 Oct '23

After having changed and re-changed "only" the line in /etc/mailman3/mailman-web.py (which looks to be only a "blinder" and the real problem could be a different one) POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' the web access via Postorius is not working any more and throws "Error 500" My logfile /var/log/mailman3/web/mailman-web.log shows now File "/usr/share/mailman3-web/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/dist-packages/django/core/management/__init__.py", line 420, in execute django.setup() File "/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 116, in populate app_config.import_models() File "/usr/local/lib/python3.9/dist-packages/django/apps/config.py", line 269, in import_models self.models_module = import_module(models_module_name) File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 680, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 790, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/django_q/models.py", line 12, in <module> from django_q.signing import SignedPackage File "/usr/lib/python3/dist-packages/django_q/signing.py", line 7, in <module> from django_q import core_signing as signing File "/usr/lib/python3/dist-packages/django_q/core_signing.py", line 9, in <module> from django.utils.encoding import force_bytes, force_str, force_text ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) I already run pip install -U postorius to update that (looks okay to me): Requirement already satisfied: postorius in /usr/local/lib/python3.9/dist-packages (1.3.8) Collecting postorius Using cached postorius-1.3.8-py3-none-any.whl Downloading postorius-1.3.7.tar.gz (3.2 MB) Requirement already satisfied: django-mailman3>=1.3.8 in /usr/local/lib/python3.9/dist-packages (from postorius) (1.3.9) Requirement already satisfied: readme-renderer[md] in /usr/lib/python3/dist-packages (from postorius) (24.0) Requirement already satisfied: django<4.2,>=3.2 in /usr/local/lib/python3.9/dist-packages (from postorius) (4.1.9) Requirement already satisfied: mailmanclient>=3.3.3 in /usr/local/lib/python3.9/dist-packages (from postorius) (3.3.5) Requirement already satisfied: sqlparse>=0.2.2 in /usr/lib/python3/dist-packages (from django<4.2,>=3.2->postorius) (0.4.1) Requirement already satisfied: asgiref<4,>=3.5.2 in /usr/local/lib/python3.9/dist-packages (from django<4.2,>=3.2->postorius) (3.7.2) Requirement already satisfied: typing-extensions>=4 in /usr/local/lib/python3.9/dist-packages (from asgiref<4,>=3.5.2->django<4.2,>=3.2->postorius) (4.6.3) Requirement already satisfied: django-allauth in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (0.44.0) Requirement already satisfied: pytz in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (2021.1) Requirement already satisfied: django-gravatar2>=1.0.6 in /usr/lib/python3/dist-packages (from django-mailman3>=1.3.8->postorius) (1.4.4) Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from mailmanclient>=3.3.3->postorius) (2.25.1) Requirement already satisfied: cmarkgfm>=0.2.0 in /usr/lib/python3/dist-packages (from readme-renderer[md]->postorius) (0.4.2) dpkg -l | grep django ii python3-django 2:2.2.28-1~deb11u2 all High-level Python web development framework ii python3-django-allauth 0.44.0+ds-1+deb11u1 all Django app for local and social authentication (Python 3 version) ii python3-django-appconf 1.0.3-1 all helper class handling configuration defaults of apps - Python 3.x ii python3-django-compressor 2.4-2 all Compresses linked, inline JS or CSS into single cached files - Python 3.x ii python3-django-extensions 3.0.3-3 all Useful extensions for Django projects (Python 3 version) ii python3-django-filters 2.4.0-1 all filter Django QuerySets based on user selections ii python3-django-gravatar2 1.4.4-2 all Python3 library that provides essential Gravatar support ii python3-django-guardian 2.0.0-2 all per object permissions of django for Python3 ii python3-django-haystack 3.0-1 all modular search for Django (Python version) ii python3-django-hyperkitty 1.3.4-4 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.5-2 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-picklefield 3.0.1-1 all Pickled object field for Django (Python3 version) ii python3-django-postorius 1.3.4-2+deb11u1 all Web user interface to access GNU Mailman3 ii python3-django-q 1.2.1-1 all Django multiprocessing distributed task queue (Python 3 version) ii python3-djangorestframework 3.12.1-1 all Web APIs for Django, made easy for Python3 debian 11 (bullseye) Looks to be a problem between django 4 and /usr/local/lib/python3.9/dist-packages/django/utils/encoding.py ? Please can anybody help?

4 8