- Mailman-users - lists.mailman3.org

Help with some 'withlist' configuration changes
by David Partain 23 Jun '21

23 Jun '21

Hi, Firstly, a repeat that I have a relatively broken (and soon to be fixed, I hope) installation of mailman3 based on Ubuntu 18.04 distrib packages (3.1.1-9) that stumbles along by me dealing with a bunch of things by hand that I hope'll go away once I'm up to the current version. In this set-up, I get a fair number of items shunted. Since I have this wonky version where stuff isn't always exposed in the web interface, I have to fix these things by hand. An example is that something gets shunted because of too many recipients, where I do: sudo -u list mailman withlist somemailmanlist m.max_num_recipients = 0 commit() sudo -u list mailman unshunt I've managed to find a number of these, such as m.max_message_size, m.require_explicit_destination, and m.administrivia. My questions are undoubtedly foolish, but here goes: 1. Is there any way to print the entire 'm' structure? If so, I'd perhaps be able to figure out the answers to my other questions. 2. Is there a way for me to correct the following shunt-ing issues with 'withlist'? I've been unable to figure out how... a. 'moderation_reasons': [ 'Message has no subject'] / 'rule_hits': ['no-subject'] b. Some things get caught as 'rule_hits': ['nonmember-moderation']. However, if I look in the (web-based) config, it shows that non-members should be accepted but the messages are shunted nonetheless. I don't know what to look for in 'm' or how I might clear these messages. 3. I have no idea what these are telling me to do about digest messages. Suggestions? This is the entire info I get from 'mailman qfile': ------------------------------------------------------snip snip---------------------------------------------- [----- start pickle -----] <----- start object 1 -----> <----- start object 2 -----> { '_parsemsg': False, 'digest_number': 457, 'digest_path': '/var/lib/mailman3/lists/somelist/digest.31.457.mmdf', 'lang': 'en', 'listid': 'somelistid', 'version': 3, 'volume': 31, 'whichq': 'digest'} [----- end pickle -----] ------------------------------------------------------snip snip---------------------------------------------- 4. I have some that have 'rule_hits': [] (it's empty) but are shunted nonetheless. I can't see anything weird other than one of the messages has a utf-8 subject. Any ideas? 5. Some messages that were sent to -request addresses (e.g., subscribe messages, confirm, approve messages) are being shunted. What should I do with these? Thanks for your patience. Cheers, David

2 2

Mailman3 service on mailman-3.3.4 is not getting started
by Shashikanth Komandoor 23 Jun '21

23 Jun '21

Hi team, I am trying to install mailman 3.3.4, the currently available latest version at https://docs.mailman3.org/en/latest/install/virtualenv.html on RHEL 7.5. As part of the installation, I am not creating any user with the name *mailman* and instead going with the *root* user only. Along with that I am using the directory */var/lib/mailman* as the root directory. Also, I have rsyslog service running on my machine and using postgresql-11 as the database service. My mailman3 service looks like this: # cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=rsyslog.target network.target postgresql-11.service [Service] Type=forking PIDFile=/var/lib/mailman/var/master.pid User=root Group=root ExecStart=/var/lib/mailman/venv/bin/mailman start ExecReload=/var/lib/mailman/venv/bin/mailman restart ExecStop=/var/lib/mailman/venv/bin/mailman stop [Install] WantedBy=multi-user.target Now, the issue is while I am trying to start the service, it is showing the below error and the status looks like as following: # systemctl start mailman3 Job for mailman3.service failed because a configured resource limit was exceeded. See "systemctl status mailman3.service" and "journalctl -xe" for details. # systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; disabled; vendor preset: disabled) Active: failed (Result: resources) since Wed 2021-06-23 12:51:27 IST; 1min 7s ago Process: 16277 ExecStart=/var/lib/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Jun 23 12:51:27 psumm3.nic.in mailman[16277]: os.execl(*execl_args) Jun 23 12:51:27 psumm3.nic.in mailman[16277]: File "/usr/lib64/python3.6/os.py", line 527, in execl Jun 23 12:51:27 psumm3.nic.in mailman[16277]: execv(file, args) Jun 23 12:51:27 psumm3.nic.in mailman[16277]: TypeError: expected str, bytes or os.PathLike object, not NoneType Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Starting Mailman's master runner Jun 23 12:51:27 psumm3.nic.in mailman[16277]: Generating MTA alias maps Jun 23 12:51:27 psumm3.nic.in systemd[1]: PID file /var/lib/mailman/var/master.pid not readable (yet?) after start. Jun 23 12:51:27 psumm3.nic.in systemd[1]: Failed to start GNU Mailing List Manager. Jun 23 12:51:27 psumm3.nic.in systemd[1]: Unit mailman3.service entered failed state. Jun 23 12:51:27 psumm3.nic.in systemd[1]: mailman3.service failed. I can't understand where the issue might be. Thank you in advance. -- Thanks & Regards, Shashi Kanth.K 9052671936

2 1

PermissionError: [Errno 1] Operation not permitted
by Sarah H 22 Jun '21

22 Jun '21

The system we are running mailman 3 on crashed, it filled the drive, and when it was restarted and the issue cleared I found that mailman3 will not start, it returns the following: Jun 21 14:12:29 mailman[513274]: Traceback (most recent call last): Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/bin/mailman", line 11, in <module> Jun 21 14:12:29 mailman[513274]: load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 829, in __call__ Jun 21 14:12:29 mailman[513274]: return self.main(*args, **kwargs) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 782, in main Jun 21 14:12:29 mailman[513274]: rv = self.invoke(ctx) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke Jun 21 14:12:29 mailman[513274]: return super().invoke(ctx) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1259, in invoke Jun 21 14:12:29 mailman[513274]: return _process_result(sub_ctx.command.invoke(sub_ctx)) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 1066, in invoke Jun 21 14:12:29 mailman[513274]: return ctx.invoke(self.callback, **ctx.params) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/core.py", line 610, in invoke Jun 21 14:12:29 mailman[513274]: return callback(*args, **kwargs) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/click/decorators.py", line 21, in new_func Jun 21 14:12:29 mailman[513274]: return f(get_current_context(), *args, **kwargs) Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/cli_control.py", line 91, in start Jun 21 14:12:29 mailman[513274]: status, lock = master_state() Jun 21 14:12:29 mailman[513274]: File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/bin/master.py", line 104, in master_state Jun 21 14:12:29 mailman[513274]: os.kill(pid, 0) Jun 21 14:12:29 mailman[513274]: PermissionError: [Errno 1] Operation not permitted Jun 21 14:12:29 systemd[1]: mailman3.service: Control process exited, code=exited status=1 Jun 21 14:12:29 systemd[1]: mailman3.service: Failed with result 'exit-code'. this is via starting as root with systemctl start mailman3, or as the user mailman using /opt/mailman/venv/bin/mailman start originally there was a similar error PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/locks/master.lck' and another similar error (that I can't find presently) for the logfile, both were owned by root when I checked them so I changed the owner back to mailman. anyone have any insight? there isn't much in the way of description on the error so I'm not sure what it's lacking permissions on. (and tried chown -R for the /opt/mailman folder already since everything there should be owned by mailman anyway)

2 2

integrate subscribe form in Website -> CSRF-token
by Jens Günther 22 Jun '21

22 Jun '21

Hello, we wanted to integrate a subscribe-form in our website after Update from Mailman2 to Mailman3. Before it was quiet easy and supposedly still is, but we can't figure out what to do with the CSRF-token-problem. Is there anywhere a documentation on this? We can't find one. If not, I would like to post more on what we tried with the html-code and what is coming up afterwards. (forbidden 403 - CSRF-verification failed. Request aborted.) Thanks in advance! Jens.

4 4

Bounce Score
by Jeff 22 Jun '21

22 Jun '21

Is there an easy way to determine a list member’s bounce score and/or reset that to zero? Thanks much, Jeff

2 1

How to identify the exact reason behind the shunting of the mails ?
by Shashikanth Komandoor 20 Jun '21

20 Jun '21

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in-built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values. I am almost running 2000 lists with 128 GB RAM and 24 Cores on a single VM and on which all the mailman 3 components are running. I have been running this setup in production for the past 2 years and 6 months. From the beginning of the above setup until recent days, I observed a few mails moving to the shunt queue now and then. But from recent days it is observed that many mails are moving to the shunt queue. I browsed many websites but I could not get a proper resolution for identifying the exact reason behind the shunting of the mails. Because of which I had been asking the user to resend the mails instead of suggesting the user regarding the issue properly. I in fact used the command "mailman qfile <filename.pck>" even then I don't understand what might be wrong with the mail composition. Most of the time I see *unknown-8bit* in To or CC fields and I don't know if it is linked with the reason for shunting or not and I don't get any clue from it either. Is there any chance to find out the reason for shunting of the mails through any means ? -- Thanks & Regards, Shashi Kanth.K 9052671936

2 6

ModuleNotFoundError: No module named 'settings'
by Michela 18 Jun '21

18 Jun '21

Hello! I've just set up Mailman 3 with Hyperkitty and Postorius in venv via pip by using the guide at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… on Oracle Linux 8.3 with Python 3.6.8. The process seemed to go smoothly and without errors. The log file, /opt/mailman/web/logs/uwsgi-error.log, contains the following stack trace, however. Note the bit toward the bottom: "ModuleNotFoundError: No module named 'settings'" Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 224, in fetch_command app_name = commands[subcommand] KeyError: 'qcluster' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_web/manage.py", line 30, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/core/management/__init__.py", line 231, in fetch_command settings.INSTALLED_APPS File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 76, in __getattr__ self._setup(name) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 63, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv/lib64/python3.6/site-packages/django/conf/__init__.py", line 142, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked ModuleNotFoundError: No module named 'settings' [uwsgi-daemons] throttling "/opt/mailman/venv/bin/mailman-web qcluster" for 245 seconds [uwsgi-daemons] respawning "/opt/mailman/venv/bin/mailman-web qcluster" (uid: 1002 gid: 1002) Mailman and mailman-web do start without errors when I run them via their systemd unit files and Postorius serves up pages (without styles and such, which I'll fix later). SELinux is disabled, at least while I work through this issue. I've gone over the configuration files, and everything appears to be in order as written in the installation instructions, but that's likely not the case. :) My configuration files outside of the Mailman virtual environment are in /etc/mailman/: (venv) [mailman@host ~]$ ls /etc/mailman3/ mailman.cfg __pycache__ settings.py uwsgi.ini When searching the web about this, I only found one result, on this very list, but it didn't have quite enough information for me to solve my issue. It might also not quite be the same problem: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Might you be able to point me in the right direction on solving this issue? Please tell me if there is any more information I can provide to that end. Best, Michela

7 9

Mailman - delete or backup old archived messages
by olenkoigetublim＠gmail.com 18 Jun '21

18 Jun '21

Hello Mailman team! I have been using Mailman-Suite (Hyperkitty + Postorius) quite a long time now and now i was wondering if there is any way to erase or export old archived messages and back them up elsewhere (for example messages, that are older then 1 year). Didnt find any suitable option under "python3 manage.py" command and also didnt find any up to date post which related to mailman3 and python3. Additional info: *Database: Postgresql13 *Mailman version: 3.3.4 *Python version: 3.6 Br, Dim

2 1

Mailman archive issues (Hyperkitty)
by klillipuu＠gmail.com 16 Jun '21

16 Jun '21

Hello All! I hope its a right place to write my concern about Mailman Hyperkitty. I have same quite odd issues lately and since I'm less experienced with Mailman, any help is welcome. So i have like hybrid version pip installation, where mailman v3 is using python3 and hyperkitty is using python2 (if im correct). I also mention, that hyperkitty is a pretty old version - 1.1.4. The main issue is that if i try to open some large-scale archived list, then i get "504 Gateway Time-out" error on webUI. Any ideas, where could i start improving the situation - should i try to upgrade some packages or do i need to give more resources to host ? Extra information: * I have also noticed some memory violation issues which has caused by uwsgi. * Segfaulting process - kernel: python[25870]: segfault at 24 ip 00007f9decb9a6ea sp 00007ffc413bb3d0 error 6 in libpython2.7.so.1.0[7f9decb10000+17e000] Output from mailman.log: HyperKitty failure on http://localhost/hyperkitty/api/mailman/archive: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (504) Exception in the HyperKitty archiver: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html> (1808) Traceback (most recent call last): File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3.5/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.16.1</center> </body> </html>

5 13

#mailman irc channel moving to libera.chat
by Abhilash Raj 15 Jun '21

15 Jun '21

Hey Everyone, As some of you might already know that Freenode IRC server now has new owners and most of the volunteer staff have decided to move away from it to create a new IRC server libera.chat[1] due to the policies of the new owners. Along with many other open source projects, we have also decided to move away from freenode to use libera.chat instead. We have registered #mailman there and will be using that as primary IRC channel for Mailman things. Freenode has also decided to drop all registrations, so, #mailman channel there is no longer registered to any member of Mailman Core team as of some time earlier today (Tue June 15th). [1]: https://libera.chat/ -- thanks, Abhilash Raj (maxking)

1 0