- Mailman-users - lists.mailman3.org

Restore/export existing Mailman lists + hyperkitty archives on a new server
by Kimmo L Sept. 14, 2023

Sept. 14, 2023

Hello! My plan is to install fresh Mailman3 host, which means that i need to migrate/transfer my existing mailman mailing lists + hyperkitty archives to new host. Unfortunately i didnt find any good documentation about this. I tried myself to export and import mailmanweb/mailman databases (from old PostgreSQL to new PostgreSQL) and recreate indexes(mailman-web update_index). Now i can see and search hyperkitty archives, but if try to open one of the mailing list, i get error - HTTP Error 500: {"title": "500 Internal Server Error"} So im pretty sure, that I'm gonna have to transport some more stuff over, which I have no idea. Maybe existing users and user rights. If its not a big trouble, can someone kindly share, what exactly should i need to export/import and what would be the right steps/commands/moves. Br, Kimmo

4 52

Strange issue with bounce processing
by Brian Carpenter Sept. 13, 2023

Sept. 13, 2023

Dear List, First of all Merry Christmas to those of you that are observing it. I have an issue on one of my Mailman 3 servers. The bounce runner is not running, even after restarting mailman core. All the other runners are working fine. Here is the problem, after restarting it, a number of messages show up in queue/bounces from a single list. However the bounce runner is still not running. So I remove these messages from queue/bounces folder and restart mailman core. The same messages show up from the same single list again in queue/bounces. In the var/logs/bounce.log file, addresses from this list are being logged as being removed after starting mailman core. They correlate with the messages showing up in queue/bounces. I assume these "cached" bounces are what is interfering with the running of the bounce runner. I don't see anything in the mailman or mailmansuite log that would explain this behavior. How can I fix this? Thank you for any assistance. -- Brian Carpenter Harmonylists.com Emwd.com

3 6

Question about "envelope-from" header
by Stephen Daniel Sept. 13, 2023

Sept. 13, 2023

Mailman Gurus -- I run a small mailman3 implementation in a VM inside Google's cloud. The same VM runs both mailman3 and postfix. Because outbound SMTP is blocked by Google, my postfix relays outbound mail through smtp-relay.gmail.com, using credentials from my google workspace account. Works pretty well. For reasons unrelated to my mailing lists, I'd like to have the same VM provide a couple of mail aliases. Mail that comes in to " alias1(a)mydomain.com" should be relayed to "random1(a)somedomain.com". I am trying to do this by setting up virtual aliases in postfix, as per http://www.postfix.org/virtual.5.html. This works except that smtp-relay.gmail.com rejects the forwarded message because of "invalid credentials". I believe that email going out through smtp-relay.gmail.com can only come from a small set of previously authorized domains, and a random person who sends to "alias1(a)mydomain.com" is unlikely to be on that list. I think I could fix this by having postfix edit the "envelope-from" header as it relays the mail, so that the "envelope-from" header contains something like "admin(a)mydomain.com". Not sure, but I think so. My question is this: If I edit the envelope-from header in my outbound emails to say "admin(a)mydomain.com" am I going to break my email lists? Will bounce processing still work? Will replies to the list still work? Thanks! -- Stephen Daniel

3 2

Mailman messages are getting a TAG in some email clients.....how????
by bob B Sept. 13, 2023

Sept. 13, 2023

So I know about the setting "Anonymous list" but regardless of that setting some email clients put the list name in [] when it displays messages in your inbox. Does anyone know how email clients are doing this? I have users who email clients do not do this, and was wondering if it is a setting in their client or just not possible. Here is a link to an image showing the tag for a list called TEST6 https://imgur.com/a/7VyJtsD

3 3

How to let mailman log every single email that it sends out?
by Mohsen Masoudfar Sept. 10, 2023

Sept. 10, 2023

I'm curious about the configuration required to have Mailman record logs for every individual email it sends. I see that it sends to the entire list, but I'm interested in obtaining log entries for each email sent to every individual subscriber on the list. How can I access this information? Is it a postfix setting, or a Mailman3 setting? I have checked /var/log/mail.log and all the logs under /var/log/Mailman3/* Mailman is running on Ubuntu 18.3 Thank you! Mohsen

4 5

Issue with Docker Postfix and Mailman3 Configuration
by recida8902＠picvw.com Sept. 9, 2023

Sept. 9, 2023

Dear Support Team, I am writing to seek assistance with an issue I am facing while configuring Docker Postfix with Docker Mailman3. I have successfully set up the configuration, and I can send emails without any problems. However, I am encountering an issue where incoming emails are not being received by the Mailman application. When I send an email from my configured email address, it is successfully delivered to the intended recipients. However, when someone else sends an email to the same address, it does not reach the Mailman application, and no error messages are generated. I have already tried the following troubleshooting steps: 1. Checked the Mailman container logs: I reviewed the logs using the docker logs command, but I did not find any error messages or warnings related to the incoming email issue. 2. Verified the Mailman installation: I ensured that Mailman is correctly installed and configured according to the provided documentation. All dependencies are met, and the outgoing email functionality is working as expected. 3. Checked the Mailman configuration: I reviewed the configuration files of Mailman and ensured that all necessary settings are properly configured. However, I couldn't identify any specific variables or options related to incoming email handling. Despite these efforts, I am still unable to receive incoming emails in the Mailman application. I would greatly appreciate any guidance or assistance you can provide to help resolve this issue. Please let me know if there is any additional information or logs that would be helpful for troubleshooting. Thank you in advance for your time and support.

2 1

social login added, but can't connect new login to existing users
by Jörg Schulz Sept. 6, 2023

Sept. 6, 2023

after lots of research in this list, we managed to add a keycloak login to mailman3. MAILMAN_WEB_SOCIAL_AUTH = ["allauth.socialaccount.providers.keycloak"] # OIDC_CREATE_USER = False SOCIALACCOUNT_PROVIDERS = { 'keycloak': { 'KEYCLOAK_URL': 'https://keycloak.my.domain', 'KEYCLOAK_REALM': 'nct' # 'SCOPE': ['profile', 'email', 'preferred_username'], } } and some entries in https://mailman.my.domain/admin/socialaccount/socialapp This works perfectly for non-existing users/emails. They are created and they are able to subscribe to lists. But, when a user already exists, this does not work; the user gets a password reset email like "...an account using that email address already exists. In case you have forgotten about this, please use the password forgotten procedure to recover your account:..." Which kind of setting/tweak is needed to associate social login accounts to existing mail addresses?

4 4

Postorius no connection to REST API
by rrosner5＠gmail.com Sept. 5, 2023

Sept. 5, 2023

Hello, I've seen some similar problems, but have not yet found anything that would work for me. I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: /usr/share/mailman3-web/manage.py mmclient Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> client.system Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call response, content = Http().request(url, method, data_str, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request conn.connect() File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect raise socket_err File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect sock.connect((self.host, self.port)) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 74, in system return self._connection.call('system/versions')[1] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API From /var/log/mailman3/mailman.log of the last restart: Aug 08 15:28:56 2021 (5322) in runner caught SIGTERM. Stopping. Aug 08 15:28:56 2021 (5322) in runner exiting. Aug 08 15:28:57 2021 (5322) in runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5321) command runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5321) command runner exiting. Aug 08 15:28:57 2021 (5320) bounces runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5320) bounces runner exiting. Aug 08 15:28:57 2021 (5319) archive runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5323) lmtp runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5323) lmtp runner exiting. Aug 08 15:28:58 2021 (5319) archive runner exiting. Aug 08 15:28:57 2021 (5329) virgin runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5330) digest runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5330) digest runner exiting. Aug 08 15:28:58 2021 (5329) virgin runner exiting. Aug 08 15:28:58 2021 (5324) nntp runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5318) Master watcher caught SIGTERM. Exiting. Aug 08 15:28:59 2021 (5318) Master watcher caught SIGTERM. Exiting. Aug 08 15:28:59 2021 (5323) lmtp runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5324) nntp runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5320) bounces runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5329) virgin runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5324) nntp runner exiting. Aug 08 15:28:59 2021 (5326) pipeline runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5319) archive runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5330) digest runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5325) out runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5328) retry runner caught SIGTERM. Stopping. Aug 08 15:29:00 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:29:01 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:29:01 2021 (5325) out runner exiting. Aug 08 15:29:03 2021 (5326) pipeline runner exiting. Aug 08 15:29:03 2021 (5327) rest runner exiting. Aug 08 15:29:11 2021 (5328) retry runner exiting. Aug 08 15:29:48 2021 (5318) Master stopped Aug 08 15:30:30 2021 (5545) Master started Aug 08 15:30:34 2021 (5546) archive runner started. Aug 08 15:30:34 2021 (5549) in runner started. Aug 08 15:30:34 2021 (5550) lmtp runner started. Aug 08 15:30:34 2021 (5554) rest runner started. Aug 08 15:30:35 2021 (5553) pipeline runner started. Aug 08 15:30:35 2021 (5552) out runner started. Aug 08 15:30:36 2021 (5551) nntp runner started. Aug 08 15:30:36 2021 (5547) bounces runner started. Aug 08 15:30:36 2021 (5556) virgin runner started. So everything seems to be starting smoothly. An excerpt from /var/log/mailman3/web/mailman-web.log: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/share/mailman3-web/settings.py", line 486, in <module> from settings_local import * File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 724, in exec_module File "<frozen importlib._bootstrap_external>", line 859, in get_code File "<frozen importlib._bootstrap_external>", line 916, in get_data PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2'

7 31

Postfix-Fehler mit mailman-web
by Jens Günther Sept. 4, 2023

Sept. 4, 2023

Hello, I installed mailman with Docker already a while ago, now running v0.4.5 with: Mailman Core-Version 3.3.8 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.9 Postorius Version 1.3.8 Already a while I get this type of error: 2023-08-26T08:21:59.517986+02:00 postfix/smtpd[2843414]: connect from unknown[192.168.176.6] 2023-08-26T08:21:59.522238+02:00 postfix/smtpd[2843414]: NOQUEUE: reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host rejected: cannot find your hostname, [192.168.176.6]; from=<$admin(a)mydomain.de> to=<$recipient> proto=ESMTP helo=<mailman-web> 2023-08-26T08:21:59.575145+02:00 postfix/smtpd[2843422]: connect from unknown[192.168.176.6] 2023-08-26T08:21:59.581227+02:00 postfix/smtpd[2843422]: NOQUEUE: reject: RCPT from unknown[192.168.176.6]: 450 4.7.25 Client host rejected: cannot find your hostname, [192.168.176.6]; from=<root(a)$mailman.mydomain.de> to=<root@localhost> proto=ESMTP helo=<mailman-web> 2023-08-26T08:21:59.581548+02:00 postfix/smtpd[2843422]: disconnect from unknown[192.168.176.6] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Where - $admin(a)mydomain.de is set in MAILMAN_ADMIN_EMAIL (mm-web) and as site_owner in mailman-extra.cfg (mm-core) and as DEFAULT_FROM_EMAIL in settings_local.py (mm-web) - $mailman.mydomain.de is set in SERVE_FROM_DOMAIN (mm-web) For me it seems, that mm-web-container is trying to send mail, but don't know why and which ... I can't reproduce it. Does anybody have a clue on wehere I can have a look what happens ... and how to change it? Thank you, Jens.

3 8

Mailman REST API not available. Please start Mailman core.
by joseverde＠gmail.com Sept. 4, 2023

Sept. 4, 2023

Okay, so I got the webservice of Mailman3 up and running, but when I go to mailman3/postorius/lists/, I get the following error: Something went wrong Mailman REST API not available. Please start Mailman core. When I logged in to the admin user, it threw a server 500 error, but I could refresh and see myself logged in. If I try to go to lists or mailman settings, however, I get the error above.

4 15