- Mailman-users - lists.mailman3.org

docker-mailman Bump to 3.3.4
by matthew＠alberti.us June 11, 2021

June 11, 2021

Hi Mailman Docker Maintainer(s) (maxking 😊 ), Just wanted to see if the docker-mailman will be bumped to 3.3.4. I believe docker-mailman release 0.3.11 is the latest release, and that gives us Mailman 3.3.3. Thank you. - Matt Alberti

1 0

OS update 18.04 -> 20.04 with Python 3.6 -> 3.8
by Torge Riedel June 6, 2021

June 6, 2021

Hi, just want to report that updating my server's OS from Ubuntu 18.04 to 20.04 including an upgrade from Python 3.6 to 3.8 worked 75% on the mailman3 installation. Stopping and disabling the service before prevented most of the problems, but I forget to disable the cron jobs. **sigh** So whenever you have to upgrade your OS including python, don't forget the cron jobs. After OS upgrade I renamed both "venv" directories and rebuild them from my notes. Worked. Starting up mailman-core was easy. Getting mailman-web back to work was a little tricky: 1. After rebuild I forgot to run the post-update script, overseen that in my notes. **sigh #2** 2. My uwsgi-emperor was totally confused and needed some guidance and manual remove of .sock file 3. Finally I got this in the logs: /opt/mailman/web/venv/lib/python3.8/site-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, failure to do so will cause the tasks to be retriggered before completion. Seehttps://django-q.readthedocs.io/en/latest/configure.html#retry for details. warn( I checked the reference file from here: |https://gitlab.com/mailman/mailman-suite/raw/master/mailman-suite_project/settings.py?inline=false| and it misses the "retry" value. After adding it to Q_CLUSTER everything works fine. Kind regards Torge

1 0

Long-shot cry for help
by David Partain June 3, 2021

June 3, 2021

Hi, I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... 2. There's this one curious cron job... * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings (yes, I know python2.7 is a problem... see the last paragraph below). These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? ----------------------------------- Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Cheers, David

4 3

Send MySQL data to mailman list for distribution
by Zden Pos June 2, 2021

June 2, 2021

I'm trying to connect existing MySQL data to the Mailman distribution list. Actually, a message is sent from the web page. It remains on this page and is also stored in the MySQL table on the provider server. This is working fine. I have also existing Mailman distribution list generated from the cPanel on the provider server as well. This list is working fine when used for a direct mailing. I need to link the MySQL table to the Mailman distribution list. When the message is posted on the web page and stored in the MySQL table, it is also to be sent to members as per the Mailman distribution list. I don't know where to configure it. In the phpMyAdmn page of the MySQL or in the Malman menu ? Thank you for your help

3 2

Getting connection timed out
by blackout69 June 1, 2021

June 1, 2021

Hello everybody, for a couple of days I have been seeing several lines calling these on /var/log/mail.log May 22 18:22:57 glugct postfix/qmgr[21205]: 0ACE641C1B: from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) May 22 18:23:06 glugct postfix/qmgr[27175]: 0ACE641C1B: from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) May 22 18:23:36 glugct postfix/smtp[27177]: 0ACE641C1B: to=<myaddress(a)simail.it>, relay=none, delay=55152, delays=55122/0.07/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) May 22 19:33:06 glugct postfix/qmgr[27175]: 0ACE641C1B: from=<lug-bounces(a)catania.linux.it>, size=3698, nrcpt=9 (queue active) May 22 19:33:36 glugct postfix/smtp[28757]: 0ACE641C1B: to=<myaddress(a)simail.it>, relay=none, delay=59352, delays=59322/0.04/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) May 22 18:33:06 glugct postfix/qmgr[27175]: 955D241C15: from=<direttivo-bounces(a)catania.linux.it>, size=11026, nrcpt=3 (queue active) May 22 18:33:36 glugct postfix/smtp[27474]: 955D241C15: to=<myaddress(a)simail.it>, relay=none, delay=124379, delays=124349/0.02/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) May 22 19:43:06 glugct postfix/qmgr[27175]: 955D241C15: from=<direttivo-bounces(a)catania.linux.it>, size=11026, nrcpt=3 (queue active) May 22 19:43:36 glugct postfix/smtp[28975]: 955D241C15: to=<myaddress(a)simail.it>, relay=none, delay=128579, delays=128549/0.04/30/0, dsn=4.4.1, status=deferred (connect to mail.simail.it[217.27.113.30]:25: Connection timed out) But always on a single email address.What could it depend on?Probable that the mail.simail.it server is blacklisted? Thank you in advanc -- blackout69

4 11

How to store additional information about lists?
by Andreas Barth May 30, 2021

May 30, 2021

Hi together, I need to add custom attributes to the mailing lists: "responsible department": Free text field who is responsible from an organisational pov (not a person but an entity) Enhance the boolean public to a tri-state: public, restricted audience and private (restricted audience means: some people could subscribe themself - how that works is a different topic but w/o the information this can't be achived) - of course this could also be implemented as a second boolean that e.g. splits "not public" into "restricted audience" and "private" (means: nothing goes wrong for code that doesn't know this difference). Any hints how to do that best? Is it possible to store custom attributes, or should that be stored elsewhere? Andi

4 19

email command join - problem
by sky.x＠nazelenej.sk May 28, 2021

May 28, 2021

Hi All Im using Mailman core 3.3.4 on Ubuntu 20.04 with python 3.8 anf have this problem with email command join. When send command to ml-request@ join address=some.email(a)domain.com Response is: Confirmation email sent to 3dsome.email(a)domain.com It add characters 3d to email and realy sent confirmation to it. Also help command for join return me join [digest=<no|mime|plain>] [address=user(a)example.com] But digest doesnt work as after command join digest=no address=some.email(a)domain.com i get join bad argument: digest=no I will be thankfull for any help/advice. S.

3 5

trying to clean up the "held messages" mess
by Bjoern Franke May 28, 2021

May 28, 2021

Hi, I migrated a Mailman3 installation on Debian10 yesterday evening from Debian packages to PIP (thanks to [1]). I think some bugs which existed before are now cleaned out, but mailman still threw exceptions when trying to get the "held messages". I went through the pendedkeyvalue table of the MySQL DB to get all request ids of the held messages and their lists and discarded the messages via curl and the REST API. Mailman also logged the discarding was successful. The amount of held messages is now reduced, but e.g. a list with 120 held messages before has till 59 held messages. And now I'm confused: where are they? Best Regards Bjoern [1]https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10

2 3

non-member moderation: list default vs default processing
by dancab＠caltech.edu May 24, 2021

May 24, 2021

I've started testing and importing lists from Mailman2 to Mailman3. I've found that there's an inconsistency with the non-members moderation setting. As a result we have non-members unable to email a list via Mailman3 that had no problem on Mailman2. Each time this problem has come up I've had to change the moderation setting from "List Default" to "Default Processing". But I've also noticed that some non-members were imported and already have "Default Processing" configured. Can you help me understand what determines this setting in Mailman3? It seems this would be something addressed via the mailman import21 option I've been using to import the lists. Thanks. ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu

2 4

Intermittent: pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77
by Torge Riedel May 24, 2021

May 24, 2021

|Hi list, sometimes I get the following error in mailman core's log: "pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77". I attached the full log after this mail. I check the provided link in the log (|||http://sqlalche.me/e/2j85|) and also searched for it on the internet and found the following possible reasons: 1. DB user does not have permissions at all -> I doubt that, because in general mailman is working ok 2. DB user is not allowed to connect from remote -> I doubt that too, because everything is on one host and DB user is allowed to connect from localhost 3. Multi-Threading -> pymysql is mentioned to be not thread-safe and each thread needs its own connection May this be caused by multi-threading? What do I have to do (is there anything I can do?) to solve this on my own?||||| Kind regards Torge || |Full log follows: [2021-05-23 07:31:45 +0200] [8244] [ERROR] Error handling request /3.1/lists?advertised=true&count=10&page=1 Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context cursor, statement, parameters, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute cursor.execute(statement, parameters) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute result = self._query(query) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query conn.query(q) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result result.read() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read self._read_result_packet(first_packet) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet self._get_descriptions() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions field = self.connection._read_packet(FieldDescriptorPacket) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet % (packet_number, self._next_seq_id)) pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77 The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 274, in falcon.api.API.__call__ File "falcon/api.py", line 269, in falcon.api.API.__call__ File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 322, in on_get resource = self._make_collection(request) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 172, in _make_collection request, self._get_collection(request)) File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 167, in _paginate return list_start, total_size, collection[list_start:list_end] File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/utilities/queries.py", line 42, in __getitem__ return self._query[index] File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3149, in __getitem__ return list(res) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3481, in __iter__ return self._execute_and_instances(context) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3506, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1020, in execute return meth(self, multiparams, params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_clauseelement distilled_params, File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1324, in _execute_context e, statement, parameters, cursor, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1518, in _handle_dbapi_exception sqlalchemy_exception, with_traceback=exc_info[2], from_=e File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ raise exception File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context cursor, statement, parameters, context File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute cursor.execute(statement, parameters) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute result = self._query(query) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query conn.query(q) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result result.read() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read self._read_result_packet(first_packet) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet self._get_descriptions() File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions field = self.connection._read_packet(FieldDescriptorPacket) File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet % (packet_number, self._next_seq_id)) sqlalchemy.exc.InternalError: (pymysql.err.InternalError) Packet sequence number wrong - got 102 expected 77 [SQL: SELECT mailinglist.list_id AS mailinglist_list_id, mailinglist.preferred_language AS mailinglist_preferred_language, mailingli$ FROM mailinglist WHERE mailinglist.advertised = true ORDER BY mailinglist.list_id LIMIT %(param_1)s] [parameters: {'param_1': 10}] (Background on this error at: http://sqlalche.me/e/2j85) |

3 5