- Mailman-users - lists.mailman3.org

Hiding an ML from a site
by Odhiambo Washington 08 Feb '24

08 Feb '24

I host two MLs on the same server/same MM3 instance. Under the Django Admin interface, I created two sites. I expected that each ML will belong to its own site and should not be visible on another site. On https://mm3-lists.kictanet.or.ke/mm/lists/, you can see the two lists. How do I stop the "Users" list from showing up on this site ( https://mm3-lists.kictanet.or.ke/mm/lists/) since it belongs to its own site - https://exim4u.org/mm/lists/ ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

5 10

search this list searches more then just this list
by Marco van Tol 06 Feb '24

06 Feb '24

Hi there, We run the following versions: mailman-core: 3.3.9 mailman-core-api: 3.1 mailman-core-python: 3.11.6 hyperkitty: 1.3.8 We have several lists on our server, I will write down a list of example list names that are good enough for the purpose of my question. xx(a)domain.tld <mailto:xx@domain.tld> yy-xx(a)domain.tld <mailto:yy-xx@domain.tld> zz-xx(a)domain.tld <mailto:zz-xx@domain.tld> When I now visit the archives for xx(a)domain.tld <mailto:xx@domain.tld> and enter a search phrase in “search this list”, the results include the other 2 lists. It looks like “search this list” searches for keyword in any listname that matches the one from "this list". Is there a way to really only search “this list” when I go to the archives for xx(a)domain.tld <mailto:xx@domain.tld>? I have tried to change the url for the results to have a ‘^’ in front of the listname, but that gives an error :-) Thanks in advance! Marco van Tol

4 23

Disable all mail capabilities
by Hope Less 02 Feb '24

02 Feb '24

I have a decades old list that was abandoned on my server. I upgraded it to mailman3 but it never came back to life. It is causing me some grief. I want to keep the archives up but totally disable any mail capabilities. I have turned off mail for the domain but I still get 'crap' that tries to relay. I've manually tried to remove stuff from the transport tables in Postfix but I still get mail. I'm not sure where the problem lies. If I can't stop this I'll have to remove the list entirely which includes the archives. I really wish to leave the archives up. Any idea on how I can remove the mail capabilities and leave the rest? Thank You.

4 4

Aborted connection message in log in every 5 minutes
by zoltan＠circle-interactive.co.uk 31 Jan '24

31 Jan '24

Hi Everyone, we have mailman 3.3.8 venv test installation which in general works fine however our mysql error log is filled up with messages below because they are so frequent. 2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) As suggested here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I tried to correlate with error logs and /opt/mailman/web/logs/mailmanweb.log shows some hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)" /opt/mailman/web/logs/uwsgi-error.log Message: OperationalError(2013, "Lost connection to MySQL server at 'handshake: reading initial communication packet', sy stem error: 104") but they have not such frequency so unsure if they are related. Thanks for the suggestions

5 14

after upgrade: OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode
by Hans Mayer 31 Jan '24

31 Jan '24

Dear All, recently I did a system os upgrade debian 11.8 -> 12.4 / bullseye -> bookworm This did also upgrade Mailman3 version 3.3.3 -> 3.3.8 as a used the packages which came with Debian OS. Initially after the upgrade I had some troubles with the MM3 services to start, but I fixed this. Now almost everything is running. Only the Archives are not working. The browser shows a server error, when I look at the mailman-web.log I see ERROR 2024-01-31 15:14:14,403 2699563 django.request Internal Server Error: /mailman3/hyperkitty/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 423, in execute return Database.Cursor.execute(self, query, params) sqlite3.OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode When I check the schema I find such a column in table "mailinglist" I assume there is only one solution, to uninstall and delete everything and start from scratch. Or is there a way the check all tables with a script and do an table update for missing columns ? Or a partial installation of hyperkitty, as I don't care about the archives. I am using sqlite3 as DB backend. Kind regards Hans --

2 1

transport map (postfix_lmtp) does not update - new lists not working
by Nils 29 Jan '24

29 Jan '24

End of last year, I've re-installed mailman3 using the virtualenv installation method on ubuntu 20.04. Since then, the transport map (/opt/mailman/mm/var/data/postfix_lmtp) has not been updated even though, new mailing lists were created. The old mailing lists, that existed before the re-installation work perfectly fine but those created after are not accessible. Because the entries for those new lists are missing in the transport map, postfix replies with a "mail for ... loops back to myself" error. I'm quite sure, that I did all the steps in the documentation (except that I use a slightly different apache2 vhost configuration). I double checked on the cronjobs. crontab -u mailman -e @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly Any idea, what I could have missed??? Kind regards, Nils

2 2

Fresh installation mailman3-suite via "pipx" - any experiences yet?
by Wikinaut 27 Jan '24

27 Jan '24

I recently found the "pipx" wrapper very useful and wanted to ask you if this could be facilitate the fresh installation of the mailman3-suite. Has anyone in the list already experiences installing mailman and mailmanweg through "pipx"? Here are my general tipps for using pipx # https://pipx.pypa.io/stable/installation/#on-linux sudo apt install pipx python3-venv To install a package systemwide for all users, I recommend the tip from https://github.com/pypa/pipx/issues/754#issuecomment-951162846 . sudo PIPX_HOME=/opt/pipx PIPX_BIN_DIR=/usr/local/bin pipx install <package>

4 6

Single Click Unsubscribe
by J D 26 Jan '24

26 Jan '24

I know this has been discussed in the past: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… However, Google has recently announced that they will be enforcing one-click unsubscribe for bulk senders: https://techcrunch.com/2023/10/03/gmail-to-enforce-harsher-rules-in-2024-to… Thoughts?

5 5

mailman-web compress - Invalid template socialaccount/login_cancelled.html
by Odhiambo Washington 24 Jan '24

24 Jan '24

Running an install on Debian12 VM. Getting a new error message that I haven't seen previously: (venv) mailman@debian12:~$ mailman-web compress Compressing... Invalid template socialaccount/login_cancelled.html: Invalid block tag on line 7: 'element', expected 'endblock'. Did you forget to register or load this tag? Invalid template account/verified_email_required.html: Invalid block tag on line 7: 'element', expected 'endblock'. Did you forget to register or load this tag? Error parsing template socialaccount/signup.html: socialaccount/base.html done Compressed 2 block(s) from 78 template(s) for 1 context(s). -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

7 13

share directories between postfix and mailman 3
by Thomas Schachtner 24 Jan '24

24 Jan '24

Hi there, I think I have (finally) set up a working instance of mailman 3 on a host separate from the companion postfix mail server actually sending out the mails. One server (postfix) is directly in the internet and the other one is in an internal network not directly reachable from the internet (but connected using a reverse proxy). The services on the hosts are available to one another (i. e. the postfix server is reachable using 127.0.0.1:25 from mailman and mailman is reachable using 127.0.0.1:8024 from postfix using a permanent ssh tunnel betwenn the two hosts). I think that this solution could work quite reliably... (at least I hope so.) But that's not the full deal. Postfix needs access to some hashed configuration files containing the transport maps and the domains of the mailman installation, and mailman needs the contents of the postfix configuration file. As a quick and dirty solution, I've established a process which periodically copies the /var/lib/mailman3 directory from the mailman box to the postfix box using rsync. But I would like to have a more professional solution, like a directly shared directory between both. I did not yet find any suggestions on how to achieve this. Are there any best practices recommendations? I already tried sharing the directories using sshfs, but that did not work. I connected the remote directory postfix.example.com:/var/lib/mailman3 to my local directory /var/lib/mailman3 using sshfs root@postfix.example.com:/var/lib/mailman3 /var/lib/mailman3 This seemed to work pretty fine, as all files and directories seemed to be available, but when starting mailman 3, the following error message was shown: FileExistsError: A race condition might have happened. /var/lib/mailman3 actually exists and is not a directory. Any idea why this message is shown? So, is it a bad idea to use sshfs? Do I have to install an NFS server? But I am not sure if sharing directories using NFS across the Internet is a good idea... Any suggestions? Best regards Tom

3 6

Re: Process on migrating mailman
by Odhiambo Washington 24 Jan '24

24 Jan '24

On Tue, Jan 23, 2024 at 4:22 AM Mark Labeste <marqueejen13(a)gmail.com> wrote: > About 500 list. Not sure how to check size of the archives. > > On Thu, Jan 18, 2024 at 4:44 PM Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > >> >> >> On Thu, Jan 18, 2024 at 8:49 AM Mark Labeste <marqueejen13(a)gmail.com> >> wrote: >> >>> Any suggestion on how to migrate mailing list and archirve with >>> diffirent server and domain. For the mailing list from >>> sample.domain1.example.com to sample.domain2.example.com >>> >>> Old Mailing list >>> Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) >>> [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] >>> Domain Domain1.example.com >>> >>> New Mailing list >>> Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) >>> Mailman Core API Version 3.1 >>> Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) >>> [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] >>> Domain domain2.example.com >> >> >> >> How many lists? How big are the archives? >> >> Looking at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…, >> it seems like it's not a trivial exercise. >> >> However, I am wondering about the consequences of: >> 1. dumping the DBs and doing 's/DOMAIN1/DOMAIN2/g' in the dumps, then >> re-importing >> 2. editing settings.py and webserver config to reflect the DOMAIN2 >> 3. reconfiguring your MTA to handle list mails using the DOMAIN2 >> >> I am imagining a virtualenv type of installation. >> > The archives are in the database so nothing to worry about, Now that I think about this again, after dumping and importing the database as shown above, you need to rerun the 'mailman-web migrate` once again to import any DB schema changes between the versions. Actually, just run all the options from https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… . -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 3

log rotation for bounce.log
by Quanah Gibson-Mount 22 Jan '24

22 Jan '24

I noticed that our smtp.log and bounce.log files haven't been rotated in years. I see the reason for smtp.log not being rotated is due to <https://gitlab.com/mailman/mailman/-/issues/931>. Does this same issue affect bounce.log or is it safe to rotate similar to mailman.log?

2 1

Extract a list of the lists and the administrators who manage it
by pau.baiges＠csuc.cat 22 Jan '24

22 Jan '24

Hello, Is there a way to extract all the lists and show the administrators who manage those lists? Thanks!

3 2

emails to list missing from archive after upgrade
by Quanah Gibson-Mount 19 Jan '24

19 Jan '24

So next issue post upgrade: I sent three emails to one of the lists today. All of them went to the list, as I got copies of each one, and the headers clearly show them coming from the list. However, when I go look at the archives for the list, they don't show up at all. And it's been over 8 hours since I sent them. --Quanah

2 3

Delivery to mail@domain.tld failed with code 444, [Errno 111] Connection refused
by christopher.claus＠tgcamberg1848.de 19 Jan '24

19 Jan '24

Hi together, I´m using Mailman3.3.9 and postfix in docker containers seperatly. Everything worked fine since this afternoon. The error occurs, after postfix transports an incoming mail to mailman. After processing the mail, sending to all recepients failed >> Delivery to mail(a)domain.tld failed with code 444, [Errno 111] Connection refused I checked the configuration of postfix and added a wide IP-range to mynetworks: postfix-main.cf mynetworks = mailman-core tgc_mailman_core t 127.0.0.0/8 [::1]/128 [fe80::]/64 172.18.0.0/16 172.21.0.0/16 [2001:8d8:1800:283]/64 172.0.0.0/24 relay_domains = $mydestination #smtpd_sender_restrictions = reject_unknown_sender_domain,reject_unknown_reverse_client_hostname smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_relay_restrictions = permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination smtpd_recipient_restrictions = permit_sasl_authenticated check_recipient_access hash:/etc/postfix/filtered_domains permit_mynetworks reject_unauth_destination smtpd_data_restrictions = reject_unauth_pipelining Does anyone have a clue for me as to why delivery to Postfix is failing? My last change a couple of days ago was adding an public ipv6-address to the host. But docker still works without IPv6. I thought about client-identification issues between maiolman-core and postfix but did noch find anything to fix ... Best regards, Christopher

2 2

moving list from mm3 -> mm3
by Jens Günther 19 Jan '24

19 Jan '24

Hey there, I'm still trying to figure out, how to move a bunch of lists from one mm3-instance to another. If somebody has a working solution, I would be really glad to hear from it. I came across this thread, but I don't think it tackles my question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (or maybe I missed the right parts) We have equal setups and versions: - maxxking docker install 0.4.5 - Core 3.3.8 - API 3.1 - Postorius 1.3.8 ## Config So I found the possibility to get the config of a list via REST-API: curl -u restadmin:restpass localhost:8001/3.1/lists/$short.$domain/config | jq > short.domain This is a nice collection of the configuration of a certain list. Does anybody know how I would get this data back to the newly created list in the second working mm3-instance? Shouldn't it be possible via POST command? I thought of something like: curl -u restadmin:restpass -d @short.domain -H "Content-Type: application/json" localhost:8001/3.1/lists/&short.&domain/config But it returns {"title": "405 Method Not Allowed"} and I don't know where to look in the docs, since it shows almost always a way through mailman shell. Here I found something about POST: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but how would it work exactly? ## Members, moderators, owners To export all members I normally run within mm-core-container as user mailman the following command: mailman members &short.&domain > &short.txt To fill them back in, it can be done in Postorius (or is there a way through API?). What I would love to know is how to get out Owners of the corresponding lists and reimport them in the new one (which will be the same at the end :-D but different instance). ## registered users This part is somehow tricky, since I have no clue how to do it. Some of the mailinglist-admins don't want to bother their list-owners again with registering newly on the other system. Is there a way to export all users (I think I found them in the DB in the table auth_users, somehow in combination with account_emailaddress) and get them over to the new instance (actually I just need part of them, but that's another question that I might solve lateron on my own). Maybe the answer is already here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)? Thank you in advance, I hope it's not too much or too nooby :-) Jens.

3 10

All users getting disabled after upgrade of mailman3
by Quanah Gibson-Mount 19 Jan '24

19 Jan '24

Hello, We just upgraded our mailman to the latest provided from Debian bookworm (I know, not the recommended installation method). Now everyone's having their addresses disabled due to "bounce" errors. This is odd, because I'm disabled, even though I received the 2 emails I sent to the list today (and that's the only list traffic today). I used the mailman shell command from <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> to see who has been disabled. I had to make one fix to it, it should be m.list_name not mlist.list_name. Confirmed that dozens of valid users have had their sub disabled. In the logs I see: Jan 18 19:25:17 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score = 1. Jan 18 19:37:11 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score = 2. Jan 18 19:37:11 2024 (952) Disabling delivery for quanah(a)fast-mail.org on list openldap-technical.openldap.org by bounce Jan 18 19:37:11 2024 (952) Member quanah(a)fast-mail.org on list openldap-technical.openldap.org, bounce score 2 >= threshold 2, disabling delivery. Jan 18 10:05:42 2024 (938) Peer: ('127.0.0.1', 36100) Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) handling connection Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'LHLO hypatia.openldap.org' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'MAIL FROM:<openldap-commit-bounces(a)openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) sender: openldap-commit-bounces(a)openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'RCPT TO:<openldap-commit-owner(a)openldap.org>' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) recip: openldap-commit-owner(a)openldap.org Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'DATA' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) Data: b'QUIT' Jan 18 10:05:42 2024 (938) ('127.0.0.1', 36100) connection lost Jan 18 10:05:42 2024 (938) Connection lost during _handle_client() Jan 18 10:05:45 2024 (940) <170557233590.937.7274928299237969540(a)hypatia.openldap.org> post to openldap-commit(a)openldap.org from openldap-commit-owner(a)openldap.org, 20265 bytes Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376(a)hypatia.openldap.org> low level smtp error: [Errno 111] Connection refused Jan 18 10:42:20 2024 (803) <170557453971.798.17359529178123532376(a)hypatia.openldap.org> delivery to quanah(a)openldap.org failed with code 444, [Errno 111] Connection refused But... postfix is working fine, and I've had hundreds of emails generated *by* mailman about it disabling people due to bounces. Thoughts on how to proceed appreciated. Regards, Quanah

2 4

Splitting hosts: mta&core vs postorius
by Ruth Ivimey-Cook 18 Jan '24

18 Jan '24

I'm trying to set up mailman3 on two hosts, one of which runs core + exim, the other runs postorius (&possibly hyperkitty). I have I think got core set up correctly, and postorius is sort of usable, but anything in the web ui that talks to core ends up with a white screen. I think what is happening is a postorius URL ends up with the core (or perhaps no) hostname, and as there's nothing there to answer it fails. I've checked the settings and I don't think I have misconfigured postorius. Is it possible that the bad url is being passed from core to postorius in some way and reused without changing the host? In the config at present, both hosts are visible to the browser, and each host can communicate with the other. Any ideas on how to pin down the problem better? Ruth

6 31

Process on migrating mailman
by Mark Labeste 18 Jan '24

18 Jan '24

Any suggestion on how to migrate mailing list and archirve with diffirent server and domain. For the mailing list from sample.domain1.example.com to sample.domain2.example.com Old Mailing list Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.6.8 (default, Sep 26 2019, 11:57:09) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] Domain Domain1.example.com New Mailing list Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.18 (main, Sep 22 2023, 17:58:34) [GCC 8.5.0 20210514 (Red Hat 8.5.0-20)] Domain domain2.example.com

3 3

how to migrate mailing lists to a new domain using mailman 3
by C. Souza 18 Jan '24

18 Jan '24

In a few days my current domain will be disabled (it is out of my control) and I would like to know how to migrate the mailing lists to the new domain name. As a solution I added a new domain in mailman 3 and created a script that replicates the lists in this new domain. To forward the emails received by the old lists, the script removes the members and adds the email of the new list. Is there a fashionable way to do that? Also, one problem that I don't have a solution is the archive of the old lists. How to bring them to the new ones? Thanks for your help. My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: Package Version ------------------- ---------- 1 aiosmtpd 1.2.4 2 alembic 1.5.3 3 arrow 0.17.0 4 asgiref 3.3.1 5 atpublic 2.1.2 6 authheaders 0.13.0 7 authres 1.2.0 8 bleach 3.3.0 9 blessed 1.17.12 10 certifi 2020.12.5 11 cffi 1.14.4 12 chardet 4.0.0 13 click 7.1.2 14 cmarkgfm 0.5.2 15 cryptography 3.3.1 16 decorator 4.4.2 17 defusedxml 0.6.0 18 Django 3.0.12 19 django-allauth 0.44.0 20 django-appconf 1.0.4 21 django-compressor 2.4 22 django-extensions 3.1.0 23 django-gravatar2 1.4.4 24 django-haystack 3.0 25 django-mailman3 1.3.5 26 django-picklefield 3.0.1 27 django-q 1.3.4 28 djangorestframework 3.12.2 29 dkimpy 1.0.5 30 dnspython 2.1.0 31 docutils 0.16 32 falcon 2.0.0 33 flufl.bounce 3.0.1 34 flufl.i18n 2.0.2 35 flufl.lock 3.2 36 gunicorn 20.0.4 37 HyperKitty 1.3.3 38 idna 2.10 39 importlib-resources 5.1.0 40 lazr.config 2.2.3 41 lazr.delegates 2.0.4 42 mailman 3.3.2 43 mailman-hyperkitty 1.1.0 44 mailman-web 0.0.3 45 mailmanclient 3.3.2 46 Mako 1.1.4 47 MarkupSafe 1.1.1 48 networkx 2.5 49 nose 1.3.7 50 oauthlib 3.1.0 51 packaging 20.9 52 passlib 1.7.4 53 pip 21.0.1 54 postorius 1.3.3 55 psycopg2-binary 2.8.6 56 publicsuffix2 2.20191221 57 pycparser 2.20 58 Pygments 2.7.4 59 PyJWT 2.0.1 60 pyparsing 2.4.7 61 python-dateutil 2.8.1 62 python-editor 1.0.4 63 python3-openid 3.2.0 64 pytz 2021.1 65 rcssmin 1.0.6 66 readme-renderer 28.0 67 requests 2.25.1 68 requests-oauthlib 1.3.0 69 rjsmin 1.1.0 70 robot-detection 0.4 71 setuptools 39.2.0 72 six 1.15.0 73 SQLAlchemy 1.3.23 74 sqlparse 0.4.1 75 typing-extensions 3.7.4.3 76 urllib3 1.26.3 77 uWSGI 2.0.19.1 78 wcwidth 0.2.5 79 webencodings 0.5.1 80 wheel 0.36.2 81 Whoosh 2.7.4 82 zipp 3.4.0 83 zope.component 4.6.2 84 zope.configuration 4.4.0 85 zope.deferredimport 4.3.1 86 zope.deprecation 4.4.0 87 zope.event 4.5.0 88 zope.hookable 5.0.1 89 zope.i18nmessageid 5.0.1 90 zope.interface 5.2.0 91 zope.proxy 4.3.5 92 zope.schema 6.0.1 -- Carlos Souza

2 1

Postorius and some CSS issue?
by Odhiambo Washington 12 Jan '24

12 Jan '24

Happy New Year to you too all. MM3 installed today using the virtualenv method. On my testbench, I am having this strange issue where the Postorius is not displaying correctly perhaps because of some CSS issue - or just my own hangovers! I have used the standard method as documented. The error I get: https://pastebin.ubuntu.com/p/dhvsHFG4jH/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 1

Loops back to myself
by David Krantz 12 Jan '24

12 Jan '24

Hi, I have a problem with my Mailman 3-setup. The symptom is that postfix rejects non-existing addresses for my list domains with <adr(a)example.com>: mail for example.com loops back to myself What I guess happens happens is that postfix for some reason accepts the mail as it is for a relay domain and finds that it is not deliverable locally as the address does not exist locally and then tries to relay it on to the appropriate MX server, which is itself and then fails and generates a bounce message. This is a bit annoying as I have set up postfix to only accept valid addresses. I have set the transport_maps, local_recipient_maps and relay_domains to the files generated by MM3. I run an older version of MM3 (3.0) but prefer to fix this without upgrading as upgrading is a relatively big undertaking. This is mostly a backscatter problem for spam I guess. Any ideas of very simple and easy to forget things that I've probably missed? Cheers // David

5 6

Review requested for some merge requests
by Stephen J. Turnbull 10 Jan '24

10 Jan '24

Reply-To set to Mailman Developers. Please check that your replies go there. Or you can comment on MRs directly if you have a GitLab login. I have three merge requests pending: [1] https://gitlab.com/mailman/mailman/-/merge_requests/1159 [2] https://gitlab.com/mailman/mailman/-/merge_requests/1160 [3] https://gitlab.com/mailman/mailman/-/merge_requests/1161 [1] fixes the logging initialization bug that prevented the `smtp` log from rotating properly, and maybe some others. I don't think it needs user review because it's a pure bugfix, but if you're curious and take a look, and you think it needs better documentation let me know. [2] adds a configuration variable `lmtp_max_size`. This is user-visible, so review of the documentation in docs/mta.rst and config/mailman.cfg for clarity and readability would be appreciated. [3] adds postfix-pgsql support for use of the PostgreSQL database to route Mailman traffic. It's really most useful in an edge case (migration of 10,000+ list Mailman 2 instances), but it's theoretically attractive on the principle of "single source of truth", and possibly for implementing a "microservices" style cloud instance (it eliminates the need for Mailman and Postfix to share a file system). Besides opinions on the value of the general idea I have two specific questions: - Postfix docs recommend not looking up domains in the database to reduce load on the database server. But on a dedicated Mailman system, you're going to be looking up pretty much everything twice anyway (once to check for local recipient and once to fetch the transport), and my experience so far is that this isn't a big load on Postgres, and it's not a drag on list traffic distribution. Should I implement domain lookup in Postgres? Should it be optional if the lists are being looked up in Postgres? - The current patch completely disables generation of the postfix_lmtp alias file, even for the `mailman aliases` command. Should I implement an option to force generation of the files for documentation (and maybe a backup in a very rare and contorted situation where Mailman can see Postgres but Postfix can't)? Thanks, Steve

3 3

Mailman 3 Core user assistance
by Tony Deshields 10 Jan '24

10 Jan '24

I currently have a docker mailman stack that utilizes Django LDAP backend for authentication. I have my users attributes mapped as you see below in my settings.py file. Whenever a user logs into postorius with their 'uid', mailman-core uses their 'uid' as their email address instead of the 'email' attribute. Is there anyway to change this functionality? I would like my users to be able to login with their enterprise uid but be mapped to their email but I feel like there is a disconnect between Django and MM3 core. Any assistance is much appreciated. AUTH_LDAP_USER_ATTR_MAP = { "uid" : "userPrincipalName", "first_name": "givenName", "last_name": "sn", "email" : "mail", }

2 1

Docker mailman image can't access https://publicsuffix.org/
by bob B 09 Jan '24

09 Jan '24

Thanks so it looks like Mailman can not get to publicsuffix. The wrinkle is I am running maxking's docker version. The host can get there, but not from the docker image. Any idea to to configure that? and this only comes into play when I set the dmarc settings.

3 8

The 'flufl.lock>=5.1' distribution was not found, but flufl.lock 8.0.2 was installed
by Nils 08 Jan '24

08 Jan '24

3 2

The doubled entries issue
by Lars Bjørndal 07 Jan '24

07 Jan '24

I've got the problem Multiple rows were found when one or none was required. I found the issue and a script here: https://gitlab.com/mailman/mailman/-/issues/657 I did su - mailman3 and ran: python scriptname.py and got: Traceback (most recent call last): File "/opt/mailman3/fix-doubled-entries.py", line 21, in <module> listmgr = get_list_manager() ^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/fix-doubled-entries.py", line 6, in get_list_manager return getUtility(IListManager) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman3/venv/lib64/python3.11/site-packages/zope/component/_api.py ", line 180, in getUtility raise ComponentLookupError(interface, name) zope.interface.interfaces.ComponentLookupError: (<InterfaceClass mailman.interfa ces.listmanager.IListManager>, '') (venv) 1[mailman3@dalen ~]$ Do I miss something? How can I fix the problem? Thanks, Lars

4 10

Archive import fails: "IndexError: list index out of range"
by Johannes Rohr 06 Jan '24

06 Jan '24

I am now importing the archives of my old mailman2 installation. Unfortunately, with some of the larger and older lists, import fails halfway through, with an exception, the last message of which is IndexError: list index out of range Below is an example. This means that the last few years are missing from the archive in several lists. Are there any suggestions what I could do to still get them importet? Thanks! Johannes File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, in get_msg_id token, value = get_dot_atom_text(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, in get_dot_atom_text raise errors.HeaderParseError("expected atom at a start of " email.errors.HeaderParseError: expected atom at a start of dot-atom-text but found '@localhost>' 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/lib/python3.8/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.8/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 387, in handle importer.from_mbox(mbfile, report_name) File "/opt/mailman/venv/lib/python3.8/site-packages/hyperkitty/management/commands/hyperkitty_import.py", line 212, in from_mbox progress_marker.tick(unquote(message.get("message-id", 'n/a'))) File "/usr/lib/python3.8/email/message.py", line 471, in get return self.policy.header_fetch_parse(k, v) File "/usr/lib/python3.8/email/policy.py", line 163, in header_fetch_parse return self.header_factory(name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 607, in __call__ return self[name](name, value) File "/usr/lib/python3.8/email/headerregistry.py", line 202, in __new__ cls.parse(value, kwds) File "/usr/lib/python3.8/email/headerregistry.py", line 535, in parse kwds['parse_tree'] = parse_tree = cls.value_parser(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2126, in parse_message_id token, value = get_msg_id(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 2073, in get_msg_id token, value = get_obs_local_part(value) File "/usr/lib/python3.8/email/_header_value_parser.py", line 1516, in get_obs_local_part if (obs_local_part[0].token_type == 'dot' or IndexError: list index out of range

6 10

Not receiving email from outlook or gmail.
by Mark Labeste 05 Jan '24

05 Jan '24

From mailman web it was able to deliver the email to outlook and gmail but when replying or confirming subcription it can't reach the mailman. This error is bounce back from outlook. Server at destination.email.com (192.10.10.10) returned '400 4.4.7 Message delayed' 1/4/2024 12:16:13 PM - Server at destination.email.com (192.10.10.10) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketTimedout: Socket error code 10060 Thanks, mARK

2 1

Programmatically modify Thread-Topic *before* message is sent out the door?
by Thomas Ward 03 Jan '24

03 Jan '24

We use a custom plugin to do numeric thread stamping, which has been working well in the code system. However, it was discovered by Microsoft that Microsoft Outlook and OWA prioritize the Thread-Topic header over the Subject header, which results in the oddness we've experienced in MS365 clients in testing. During our tasks though a custom handler goes through during the pipeline and modifies the Subject field accordingly, adding a thread tag to it. While this is 'fragile' it does work; the only problem is that Thread-Topic doesn't get altered. Programmatically, how would we alter the Thread-Topic during the handler's processing to prepend the corresponding prefix/tag so that when the message actually goes out the door it is properly sending with the modified Thread-Topic? Thomas

2 6

REST API for list owners/moderators
by mathias＠koerber.org 03 Jan '24

03 Jan '24

Does Mailman 3 have an REST API that allows list-owners/moderators to perform list-management functions without having access to the whole server/other lists etc? ie, an API that uses the same credentials as Postorious but allows mass-subscription/un-subscription/membership-export etc and changes to list settings, membership settings (mod etc) via REST or python? The documentation seems to only indicate a single one-admin-user REST API that should not even be accessible from outside?

2 1

Message getting shunted with enabling Dmarc replace with list address
by bob B 03 Jan '24

03 Jan '24

So we host a mailing list for domain X, the MX record points to us, we are domain y. If we have Dmarc set to "no dmarc mitigations" I can send a message from my email in domain Y and it goes to the list in domain x and is processed and sent out. If I set the dmarc to "replace with list address". the same message gets shunted. I included the logs below Not sure why it is trying to contact publicsuffix.org? ************* /mailman/core/var/logs/mailman.log Jan 02 20:41:50 2024 (29) No cached copy of the public suffix list found Jan 02 20:41:55 2024 (29) Uncaught runner exception: HTTPSConnectionPool(host='publicsuffix.org', port=443): Max retries exceeded with url: /list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)')) Jan 02 20:41:55 2024 (29) Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/urllib3/connection.py", line 174, in _new_conn conn = connection.create_connection( File "/usr/lib/python3.10/site-packages/urllib3/util/connection.py", line 95, in create_connection raise err File "/usr/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection sock.connect(sa) TimeoutError: timed out During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 703, in urlopen httplib_response = self._make_request( File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 386, in _make_request self._validate_conn(conn) File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn conn.connect() File "/usr/lib/python3.10/site-packages/urllib3/connection.py", line 358, in connect self.sock = conn = self._new_conn() File "/usr/lib/python3.10/site-packages/urllib3/connection.py", line 179, in _new_conn raise ConnectTimeoutError( urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)') During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/requests/adapters.py", line 489, in send resp = conn.urlopen( File "/usr/lib/python3.10/site-packages/urllib3/connectionpool.py", line 787, in urlopen retries = retries.increment( File "/usr/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment raise MaxRetryError(_pool, url, error or ResponseError(cause)) urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='publicsuffix.org', port=443): Max retries exceeded with url: /list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)')) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/core/runner.py", line 272, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3.10/site-packages/mailman/runners/incoming.py", line 80, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/lib/python3.10/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 316, in check if maybe_mitigate(mlist, address): File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 292, in maybe_mitigate org_dom = get_organizational_domain(from_domain) File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 142, in get_organizational_domain parse_suffix_list() File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 109, in parse_suffix_list filename = ensure_current_suffix_list() File "/usr/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 77, in ensure_current_suffix_list content = get(config.dmarc.org_domain_data_url) File "/usr/lib/python3.10/site-packages/mailman/utilities/protocols.py", line 39, in get response = requests.get(url, timeout=REQUEST_TIMEOUT, **kws) File "/usr/lib/python3.10/site-packages/requests/api.py", line 73, in get return request("get", url, params=params, **kwargs) File "/usr/lib/python3.10/site-packages/requests/api.py", line 59, in request return session.request(method=method, url=url, **kwargs) File "/usr/lib/python3.10/site-packages/requests/sessions.py", line 587, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3.10/site-packages/requests/sessions.py", line 701, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3.10/site-packages/requests/adapters.py", line 553, in send raise ConnectTimeout(e, request=request) requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='publicsuffix.org', port=443): Max retries exceeded with url: /list/public_suffix_list.dat (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f8b38d318a0>, 'Connection to publicsuffix.org timed out. (connect timeout=5)')) Jan 02 20:41:55 2024 (29) SHUNTING: 1704228115.0417743+619bfacfe7e6d030991468aa2707d065418c56e5

2 1

Editing the "example.org" site
by Stephen J. Turnbull 03 Jan '24

03 Jan '24

Hi all, I don't know how many people will need this, but I just realized that you can edit Django's SITE 1 and (probably, 100% untested but I'm going on the clock so want to get this done quick :-) use that. When you add your first domain, there's a link in that page (not a button, a link!) to edit the domain list. Then you can click on the link to "example.org" in the list, and edit both display name (which I assumed) and the domain name. Maybe I'm just slow, but I've been adding SITE 2 = "Whatever site <whatever.tld>" the whole time. :-) But then you have to edit the SITE = 1 statement in settings.py (which I often forget and hilarity ensues). Of course adding a web site and editing settings.py (which you have to do anyway for other variables) works too, but this seems cleaner to me. Steve

2 3

Can't edit lists anymore: "Something went wrong HTTP Error 404"
by Nils 30 Dec '23

30 Dec '23

When I try to edit any list at "postorius/lists/LISTNAME.SUBDOMAIN.DOMAIN.TLD/", I get this error. The lists are displayed correctly at "postorius/lists/". Selecting any of those lists leads to that error. First step of creating a new list is possible but I get the same error right after the creation of the new list. These lines in the mailman.log seem suspicious: Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" *404* 26 Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] Postorius Version 1.3.5 Here are the full logs of this event: mailman3/web/mailman-web.log ERROR 2023-12-29 11:59:30,571 2416033 postorius Un-handled exception: HTTP Error 404: {"title": "404 Not Found"} Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/postorius/views/list.py", line 301, in get primary_email = set_preferred(request.user, mm_user) File "/usr/lib/python3/dist-packages/postorius/utils.py", line 77, in set_preferred mm_user.preferred_address = primary_email.email File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 57, in __setattr__ super(User, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py", line 131, in __setattr__ return super(RESTObject, self).__setattr__(name, value) File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/user.py", line 145, in preferred_address response, content = self._connection.call(url, {'email': email}) File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, urllib.error.HTTPError: HTTP Error 404: {"title": "404 Not Found"} WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ WARNING 2023-12-29 11:59:30,580 2416033 django.request Not Found: /postorius/lists/testliste.lists.DOMAIN.TLD/ [pid: 2416033|app: 0|req: 9/9] 2003:ca:bf1d:b000:efc2:8dfa:6fd:715f () {72 vars in 1618 bytes} [Fri Dec 29 11:59:30 2023] GET /postorius/lists/testliste.lists.DOMAIN.TLD/ => generated 6285 bytes in 466 msecs (HTTP/1.1 404) 7 headers in 227 bytes (1 switches on core 0) mailman3/mailman.log Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD HTTP/1.1" 200 384 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/owner HTTP/1.1" 200 640 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/roster/moderator HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/config HTTP/1.1" 200 2132 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/archivers HTTP/1.1" 200 61 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste(a)lists.DOMAIN.TLD/requests?request_type=subscription HTTP/1.1" 200 90 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/lists/testliste.lists.DOMAIN.TLD/member/USERNAME%40DOMAIN.TLD HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b HTTP/1.1" 200 286 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "GET /3.1/addresses/USERNAME(a)DOMAIN.TLD HTTP/1.1" 200 369 Dec 29 11:59:30 2023 (6255) 127.0.0.1 - - "POST /3.1/users/fa17aa7aa1e946b6a72706b48ddbc14b/preferred_address HTTP/1.1" 404 26 Kind regards

2 3

"From address" for list moderation notification
by ronn.ramirez＠pge.com 30 Dec '23

30 Dec '23

Hi Mailman Group, I noticed that the from address for list moderation notifications are coming from a certain user address. May you please help me figure out where to change this? In this example, I would like to change the From address "listadmin(a)domain.com" ================================================================ -----Original Message----- From: Admin <listadmin(a)domain.com> Sent: Thursday, December 28, 2023 12:00 AM To: dummy-list <dummy-list(a)domainx.com> Subject: The dummy-list(a)domainx.com list has 2 moderation requests waiting. The dummy-list(a)domainx.com list has 2 moderation requests waiting. Held Messages: Sender: user1(a)domain.com Subject: You missed a call | Transcription Available . Reason: The message is not from a list member Sender: user2(a)domain.com Subject: Update/Access Required Notice on Friday, September 29, 2023 Reason: The message is not from a list member Please attend to this at your earliest convenience. =================================================================

2 3

Again, after systemupgrade the log file in /var/log/mailman was owned by list:list instead of mailman:mailman and starting failed for this reason [support request]
by Wikinaut 28 Dec '23

28 Dec '23

I made for a repeated time (after system update and/or system reboot) the experience,that my mailman3 installation fails to start because of permission error to write the log file. For some unknown reason, an empty file /var/og/mailman/mailman.log was apparently owned by list:list. I deleted that file and mailman3 core could now be started. The start problem i solved. I asked myself and you, how can this happen for many times? Has anyone an idea what the reason could be? There is still a user list from a previous mailman3 installation, where I assigned the (former user for mailman2), but I suppose the problem is a different problem than a simple user definition. The other log files are always correctly assigned to mailman:mailman <pre> -rw-rw---- 1 mailman mailman 7487 Dec 22 18:21 bounce.log 0 -rw-rw---- 1 mailman mailman 0 Oct 8 22:46 debug.log 4 -rw-rw---- 1 mailman mailman 1909 Dec 24 09:10 mailman.log 57448 -rw-rw---- 1 mailman mailman 58820418 Dec 24 09:00 mailman.log.1 108 -rw-rw---- 1 mailman mailman 108407 Oct 24 12:18 mailman.log.2.gz 0 -rw-rw---- 1 mailman mailman 0 Oct 8 22:46 plugins.log 232 -rw-rw---- 1 mailman mailman 229585 Dec 24 09:10 smtp.log 4 drwxr-xr-x 2 mailman mailman 4096 Oct 20 00:00 web </pre>

3 10

subscribing to a list from a WordPress site
by Johannes Rohr 25 Dec '23

25 Dec '23

Dear all, is there a wordpress plugin/widget allowing visitors to subscribe to a mailman3 hosted mailing list? Else, what is the most convenient way? Sure, I could just link to the maiman site, but since joining a list is as easy as sending mail to LISTNAME-join, there should be a simple way to impement this. What is the best practice? Cheers, Johannes

2 1

Function "Mass subscription" does not allow any more the format `"Givenname Familyname" <mailaddress>`
by Wikinaut 22 Dec '23

22 Dec '23

Wheras my older lists handled these format apparently correctly, I now cannot add any more "Givenname Familyname" <mailaddress> ; or Givenname Familyname <mailaddress> In any of these cases, only the part <mailaddress> is added. Is this strange behaviour know? What can be done to have the correct function back to working again?

2 1

django-allauth failures, but only for some users (independent of browser?)
by Jered Floyd 22 Dec '23

22 Dec '23

Django-allauth seems to just be a basket of woes, but I figured I'd toss this one out there to see if anyone has seen similar: I have Google and Facebook social logins configured. They work fine for me. They work fine for most people. Huzzah! For some people, even when they use different browsers/OSes/etc, attempting a social login generates an error. On the callback, they get "Server error" "An error occurred while processing your request." These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! Any pointers for investigation? --Jered Internal Server Error: /accounts/google/login/callback/ ImproperlyConfigured at /accounts/google/login/callback/ You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. [...] Traceback (most recent call last): File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth2/views.py", line 84, in view return self.dispatch(request, *args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/providers/oauth2/views.py", line 162, in dispatch return complete_social_login(request, login) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/helpers.py", line 197, in complete_social_login sociallogin.lookup() File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 282, in lookup provider_id = self.account.get_provider().id File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 141, in get_provider provider = self._provider = adapter.get_provider( File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_provider app = self.get_app(request, provider=provider) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 284, in get_app apps = self.list_apps(request, provider=provider, client_id=client_id) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 231, in list_apps db_apps = SocialApp.objects.on_site(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 27, in on_site site = get_current_site(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/app-root/src/.local/lib/python3.9/site-packages/django/contrib/sites/models.py", line 63, in get_current raise ImproperlyConfigured( Exception Type: ImproperlyConfigured at /accounts/google/login/callback/ Exception Value: You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. Raised during: allauth.socialaccount.providers.oauth2.views.view [... internal state elided ...]

2 14

mailman3-web generating huge amount of error logs
by Helio Loureiro 22 Dec '23

22 Dec '23

Hi, Now my finished installation is generating a lot of errors and filling up /var/log/syslog 1GB in a few hours. The errors are like this one: Dec 21 08:42:17 new-server mailman-web[981806]: --- Logging error --- Dec 21 08:42:17 new-server mailman-web[981806]: Traceback (most recent call last): Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher Dec 21 08:42:17 new-server mailman-web[981806]: task = SignedPackage.loads(task[1]) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads Dec 21 08:42:17 new-server mailman-web[981806]: return signing.loads( Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads Dec 21 08:42:17 new-server mailman-web[981806]: base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age)) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign Dec 21 08:42:17 new-server mailman-web[981806]: result = super(TimestampSigner, self).unsign(value) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign Dec 21 08:42:17 new-server mailman-web[981806]: raise BadSignature('Signature "%s" does not match' % sig) Dec 21 08:42:17 new-server mailman-web[981806]: django.core.signing.BadSignature: Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match Dec 21 08:42:17 new-server mailman-web[981806]: During handling of the above exception, another exception occurred: Dec 21 08:42:17 new-server mailman-web[981806]: Traceback (most recent call last): Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 1100, in emit Dec 21 08:42:17 new-server mailman-web[981806]: msg = self.format(record) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 943, in format Dec 21 08:42:17 new-server mailman-web[981806]: return fmt.format(record) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 678, in format Dec 21 08:42:17 new-server mailman-web[981806]: record.message = record.getMessage() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/logging/__init__.py", line 368, in getMessage Dec 21 08:42:17 new-server mailman-web[981806]: msg = msg % self.args Dec 21 08:42:17 new-server mailman-web[981806]: TypeError: not all arguments converted during string formatting Dec 21 08:42:17 new-server mailman-web[981806]: Call stack: Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/bin/mailman-web", line 8, in <module> Dec 21 08:42:17 new-server mailman-web[981806]: sys.exit(main()) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py", line 90, in main Dec 21 08:42:17 new-server mailman-web[981806]: execute_from_command_line(sys.argv) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line Dec 21 08:42:17 new-server mailman-web[981806]: utility.execute() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute Dec 21 08:42:17 new-server mailman-web[981806]: self.fetch_command(subcommand).run_from_argv(self.argv) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 407, in run_from_argv Dec 21 08:42:17 new-server mailman-web[981806]: self.execute(*args, **cmd_options) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py", line 453, in execute Dec 21 08:42:17 new-server mailman-web[981806]: output = self.handle(*args, **options) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/management/commands/qcluster.py", line 22, in handle Dec 21 08:42:17 new-server mailman-web[981806]: q.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 78, in start Dec 21 08:42:17 new-server mailman-web[981806]: self.sentinel.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start Dec 21 08:42:17 new-server mailman-web[981806]: self._popen = self._Popen(self) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return _default_context.get_context().Process._Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self._launch(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch Dec 21 08:42:17 new-server mailman-web[981806]: code = process_obj._bootstrap(parent_sentinel=child_r) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap Dec 21 08:42:17 new-server mailman-web[981806]: self.run() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run Dec 21 08:42:17 new-server mailman-web[981806]: self._target(*self._args, **self._kwargs) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 168, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 172, in start Dec 21 08:42:17 new-server mailman-web[981806]: self.spawn_cluster() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 248, in spawn_cluster Dec 21 08:42:17 new-server mailman-web[981806]: self.pusher = self.spawn_pusher() Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 201, in spawn_pusher Dec 21 08:42:17 new-server mailman-web[981806]: return self.spawn_process(pusher, self.task_queue, self.event_out, self.broker) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 197, in spawn_process Dec 21 08:42:17 new-server mailman-web[981806]: p.start() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start Dec 21 08:42:17 new-server mailman-web[981806]: self._popen = self._Popen(self) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return _default_context.get_context().Process._Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen Dec 21 08:42:17 new-server mailman-web[981806]: return Popen(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__ Dec 21 08:42:17 new-server mailman-web[981806]: self._launch(process_obj) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in _launch Dec 21 08:42:17 new-server mailman-web[981806]: code = process_obj._bootstrap(parent_sentinel=child_r) Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap Dec 21 08:42:17 new-server mailman-web[981806]: self.run() Dec 21 08:42:17 new-server mailman-web[981806]: File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run Dec 21 08:42:17 new-server mailman-web[981806]: self._target(*self._args, **self._kwargs) Dec 21 08:42:17 new-server mailman-web[981806]: File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 358, in pusher Dec 21 08:42:17 new-server mailman-web[981806]: logger.error(e, traceback.format_exc()) Dec 21 08:42:17 new-server mailman-web[981806]: Message: BadSignature('Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match') Dec 21 08:42:17 new-server mailman-web[981806]: Arguments: ('Traceback (most recent call last):\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py", line 356, in pusher\n task = SignedPackage.loads(task[1])\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py", line 25, in loads\n return signing.loads(\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 35, in loads\n base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s, max_age=max_age))\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 70, in unsign\n result = super(TimestampSigner, self).unsign(value)\n File "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", line 55, in unsign\n raise BadSignature(\'Signature "%s" does not match\' % sig)\ndjango.core.signing.BadSignature: Signature "ofwl5GkP2_1nDnfM8-vAjAwl_Ss" does not match\n',) So any clue how to fix this? Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro

3 4

delete unverified accounts
by noemi 21 Dec '23

21 Dec '23

Hi, I'm noticing that a lot of 'spammers' are registering themself via postorius. They do not send emails, neither they are in any list, so they are not technically spammers, but they are a lot [maybe around 500 subscribed in the last month]. While waiting for a captcha system[0] for the main distribution, I'm looking for a rapid/easy way to delete this accounts; since they are not 'verified', I was wondering if I can locate this information in the mailman3 database or if there is some easier way to delete all unverified accounts. Do some of you any help or indications? I'm using GNU Mailman 3.3.9 (Tom Sawyer). Thanks, noemi for pangea.org [ https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… ]

2 1

Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3?
by Pierre Malard 20 Dec '23

20 Dec '23

Hi, Is it possible to upgrade from Debian 11 to Debian 12 with Mailman3 installed on Debian 11? I specify that I want to stay in the Debian repositories, not a "hand" installation of MM3. I tested on a specific server. It was long and tedious but it seemed to me that it was working. In fact everything seems to work except the archive management :-( Here is the procedure followed: Stopping MM services Backup of the database (PostgreSQL) and the base MM directory Switch server from Debian 11 to Debian 12 and restart migrate the database from PG 113 to PG 15 (pg_upgradecluster 13 does this very well) Modify the file /etc/mailman3/mailman.cfg with a URL reference "postgresql://" instead of "postgres://" (see https://lists.mailman3.org/archives/list/ mailman-users(a)mailman3.org/thread/CU6YU44V4WLRJI3WJH2VBWO2HCUF4YEA/) update MM3 databases with "mailman-web migrate" restart MM3 and MM3-web With that MM3 works but not the archiving management! Note that there are no real error messages in the logs… In fact when we go to a list archive, we have pretty waiting wheels... infinite :-( The only reference in mailman3-web.log: [pid: 1429|app: 0|req: 12/12] NNN.NNN.NNN.NNN () {68 vars in 1445 bytes} [Mon Dec 18 16:35:56 2023] GET /hyperkitty/list/admin@ teledetection.fr/ => generated 37443 bytes in 37 msecs (HTTP/1.1 200) 7 headers in 221 bytes (1 switches on core 1) If you have any solution... Thank you in advance, have a good day and happy Christmas -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Il n'y a pas de Paradis, mais il faut tâcher de mériter qu'il y en ait un ! » Jules Renard (1864-1910) - Journal, 10 septembre 1903 |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

5 9

Migrating mailman3 to latest ubuntu lts
by Helio Loureiro 19 Dec '23

19 Dec '23

Hi, I'm trying to migrate several lists from an ubuntu 18.04, where it was installed via packages (mailman 3.1.1), to ubuntu 22.04. Since ubuntu 22.04 is broken in terms of packages for mailman3, I'm trying to install manually following the site instructions. I just dumped the mysql DB we have nowadays, mailman3 and mailman3-web, and loaded in the new server. I also copied the configurations and fixed the paths since now mailman3 lives on /local/mailman and it uses venv. I also copied /var/lib/mailman3 into /local/mailman/var/lib/mailman3. mailman seems to accept pretty much of the work done. (venv) mailman@new-server ~ (v3.3.9)> mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: mysql+pymysql://mailman3:********@localhost/mailman3?charset=utf8mb4&use_unicode=1 devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:*********** Even configuration is working fine. (venv) mailman@new-server ~ (v3.3.9)> mailman conf [ARC] authserv_id: [ARC] dkim: yes [ARC] dmarc: yes [ARC] domain: [ARC] enabled: no [ARC] privkey: [ARC] selector: [ - a lot of stuff - ] [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [webservice] admin_pass: ************************* [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] configuration: python:mailman.config.gunicorn [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no [webservice] workers: 2 But it is failing to start displaying the domain name from the previous machine. (venv) mailman@new-server ~ (v3.3.9)> mailman start Starting Mailman's master runner Generating MTA alias maps Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1969, in _exec_single_context self.dialect.do_execute( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 922, in do_execute cursor.execute(statement, parameters) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 558, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 822, in _read_query_result result.read() File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 1200, in read first_packet = self.connection._read_packet() File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 772, in _read_packet packet.raise_for_error() File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/protocol.py", line 221, in raise_for_error err.raise_mysql_exception(self._data) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/err.py", line 143, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.OperationalError: (1054, "Unknown column 'domain.alias_domain' in 'field list'") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/local/mailman/venv/bin/mailman", line 33, in <module> sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) File "/local/mailman/venv/lib/python3.10/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_control.py", line 109, in start call_name(config.mta.incoming).regenerate() File "/local/mailman/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 109, in regenerate self._generate_lmtp_file(fp) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 149, in _generate_lmtp_file mlist = _FakeList(list_name, mail_host) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 75, in __init__ self.mail_host = _get_alias_domain(mail_host) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 63, in _get_alias_domain d = domain_manager.get(domain) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/database/transaction.py", line 106, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/local/mailman/venv/lib/python3.10/site-packages/mailman/model/domain.py", line 162, in get if domains.count() < 1: File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 3132, in count self._legacy_from_self(col).enable_eagerloads(False).scalar() File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 2825, in scalar ret = self.one() File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 2798, in one return self._iter().one() # type: ignore File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 2847, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 2308, in execute return self._execute_internal( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 2190, in _execute_internal result: Result[Any] = compile_state_cls.orm_execute_statement( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/orm/context.py", line 293, in orm_execute_statement result = conn.execute( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1416, in execute return meth( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/sql/elements.py", line 516, in _execute_on_connection return connection._execute_clauseelement( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1639, in _execute_clauseelement ret = self._execute_context( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1848, in _execute_context return self._exec_single_context( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1988, in _exec_single_context self._handle_dbapi_exception( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 2343, in _handle_dbapi_exception raise sqlalchemy_exception.with_traceback(exc_info[2]) from e File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1969, in _exec_single_context self.dialect.do_execute( File "/local/mailman/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 922, in do_execute cursor.execute(statement, parameters) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 322, in _query conn.query(q) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 558, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 822, in _read_query_result result.read() File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 1200, in read first_packet = self.connection._read_packet() File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/connections.py", line 772, in _read_packet packet.raise_for_error() File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/protocol.py", line 221, in raise_for_error err.raise_mysql_exception(self._data) File "/local/mailman/venv/lib/python3.10/site-packages/pymysql/err.py", line 143, in raise_mysql_exception raise errorclass(errno, errval) sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1054, "Unknown column 'domain.alias_domain' in 'field list'") [SQL: SELECT count(*) AS count_1 FROM (SELECT domain.id AS domain_id, domain.mail_host AS domain_mail_host, domain.description AS domain_description, domain.alias_domain AS domain_alias_domain FROM domain WHERE domain.mail_host = %(mail_host_1)s) AS anon_1] [parameters: {'mail_host_1': 'old-server.mydomain.com'}] (Background on this error at: https://sqlalche.me/e/20/e3q8) But I can see some processes are starting. (venv) mailman@new-server ~ (v3.3.9)> ps auxwww | grep "[p]ython" | grep mailman mailman 1411605 0.0 0.0 32180 22212 ? Ss 10:44 0:00 /local/mailman/venv/bin/python /local/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application mailman 1411607 0.0 0.0 44244 32412 ? S 10:44 0:00 /local/mailman/venv/bin/python /local/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application mailman 1411671 1.0 0.2 98584 83004 ? Ss 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg mailman 1411681 1.0 0.2 98392 82504 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 mailman 1411682 97.7 10.1 3396160 3346868 ? R 10:45 1:58 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 mailman 1411683 1.0 0.2 98588 82816 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 mailman 1411684 1.0 0.2 98580 82904 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 mailman 1411685 1.0 0.2 172312 82772 ? Sl 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 mailman 1411686 1.1 0.2 98588 82652 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 mailman 1411687 1.1 0.2 98608 83016 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 mailman 1411688 1.0 0.2 98584 82936 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 mailman 1411689 1.1 0.2 107040 90972 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 1411690 1.0 0.2 98592 82784 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 mailman 1411691 41.3 0.5 187380 171012 ? S 10:45 0:50 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 mailman 1411692 1.0 0.2 98472 83028 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 mailman 1411693 1.0 0.2 98448 82608 ? S 10:45 0:01 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 mailman 1411705 0.0 0.2 107040 75968 ? S 10:45 0:00 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 1411709 0.0 0.2 107040 75968 ? S 10:45 0:00 /local/mailman/venv/bin/python /local/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 mailman 1413629 0.0 0.0 17644 8812 ? Rs 10:47 0:00 /local/mailman/venv/bin/python /local/mailman/venv/bin/mailman start Best Regards, Helio Loureiro http://helio.loureiro.eng.br https://github.com/helioloureiro

4 17

Spam sent to list owner causes bounce increment for list owner
by Allan Hansen 19 Dec '23

19 Dec '23

Hi all, Someone sent a spam message to the list owner (me) of one of my lists. Then I got booted from the list. The scenario in more detail: The list server forwards the message to me, as I’m the list owner. This message is sent from <list>- <mailto:artists-bounces+hansen=rc.org@list.rc.org>bounces+hansen=rc.org(a)list.rc.org <mailto:bounces+hansen=rc.org@list.rc.org> to hansen(a)rc.org <mailto:hansen@rc.org>. My service provider’s spam filter rejects the spam (correctly) in a message and informs the list server. The list server sends a message to <list>- <mailto:artists-bounces+hansen=rc.org@list.rc.org>bounces+hansen=rc.org(a)list.rc.org <mailto:bounces+hansen=rc.org@list.rc.org> (the fake sender) saying that the message to hansen(a)rc.org <mailto:hansen@rc.org> (the recipient) could not be delivered because it was spam. The list server also blames hansen(a)rc.org <mailto:hansen@rc.org> (me) for the bounce and increments my bounce score, which, to me, is unfair. So I wonder: Is the Mailman host at list.rc.org <http://list.rc.org/> at fault for not catching the spam before it reaches the list server? (One could argue that) Is my rc.org <http://rc.org/> service provider at fault for sending the bounce message to the server instead of the to the original sender? Is Mailman at fault for thinking that the bounce message was caused by a list message FROM me, instead of a bounced message TO the list owner? Yours, Allan

2 2

MM3 Postfix FROM header issue
by eboltz＠lhtservices.com 18 Dec '23

18 Dec '23

Installed MM3 on Debian 11, followed the steps from the MM3 website. I'm running into issues with Postfix headers. I can only get postfix to send emails to/from the list if I set the sender_canonical_maps in the main.cf file. I don't want to have to use that as I'd like the recipient to receive the following in their email header: <Subscriber> via <List Name> <FROM:LIST@DOMAIN>. But if I do the sender_canonical_maps, then the <FROM:LIST@DOMAIN> and all email headers are overwritten by the maps email address. When I check the /var/log/mail.log without the sender_canonical_maps setting enabled, then the initial email sender is either rejected because 'Recipient address rejected: User unknown in virtual alias table' or '550-From header sender domain not verified (example.com), 550-On your sending > Verified senders page 550 verify the sender domain or email to be allowed to send' I have smtp_sasl_passwd_maps disabled, since I'm trying a different SMTP relay Here is my main.cf setup # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 2 on # fresh installs. compatibility_level = 2 # Mailman related settings #owner_request_special = no transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains #relay_domains = ${{$compatibility_level} < {2} ? {$mydestination} : {}} hash:/var/lib/mailman3/data/postfix_domains # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_security_level=may #smtp_tls_CApath=/etc/postfix/o365_smtp_cert.pem smtp_tls_security_level=may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = localhost alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain relayhost = [mail.smtp2go.com]:587 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 sender_canonical_maps = regexp:/etc/postfix/sender_canonical smtp_use_tls = yes smtp_always_send_ehlo = yes unknown_local_recipient_reject_code = 550 always_add_missing_headers = yes #smtp_sasl_auth_enable = yes #smtp_sasl_password_maps = hash:/etc/postfix/sasl/sasl_passwd smtp_sasl_security_options = noanonymous header_size_limit = 409600 default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 header_checks = regexp:/etc/postfix/header_checks mynetworks = 127.0.0.0/8 [::fff:127.0.0.0]/104 [::1]/128

4 18

Enable Notifications on Mailman3 Threads
by jdamos＠iu12.org 18 Dec '23

18 Dec '23

In my environment, I am trying to enable notifications on a thread just like this one. When someone responds, I want the list to get a notification and or the person that is getting responded to. Any thoughts? Thank you!

2 2

List users from different domains getting blocked.
by bob B 14 Dec '23

14 Dec '23

I am running MM3 and have a list that has users from different organizations and email domains. So let's say I am orga.com and hosting mailman Bill is borg.com Cindy is mew.com When Bill sends a message to my MM3 list it gets sent out, However, cindy's email system rejects it cause it sees the message is sent from Bill(a)borg.com but it came from my MM3 server which is under orga.com, so it rejects it. I have been told more organizations are checking this and starting to reject these types of messages and also we could get blacklisted because it looks like we are spoofing. The only solutions I can think of are: -Have the receiving organizations whitelist my server, but that is probably not feasible. -set the list to anonymous..... But then you don't know who sent the email. Anyway around this? or is there a way to have the sender's email included in the list message but keep the list anonymous? or am I missing something else? and if I send amessage from my organaxztion to MM# it will go out to the peopl n the list, and if and some of those people are at other organizations. When the recive the email, sometoimes their mail system reject it with a DMAR message. I have been told thisis beacue the other organazatione dmeail system sees I snet the message

3 2

customized welcome message
by Nils 07 Dec '23

07 Dec '23

2 6

templates/socialaccount/login.html - any reason not to include?
by Jered Floyd 07 Dec '23

07 Dec '23

When using a social login button, there is a completely unstyled page as an interstitial before login. I copied the upstream allauth/templates/socialaccount/login.html and changed the first line from: {% extends "socialaccount/base_entrance.html" %} to {% extends "django_mailman3/profile/base.html" %} This seems to work properly and look correct. Is there a reason not to PR this? --Jered

1 0

mailman3-web language preference and translation settings
by Nils 07 Dec '23

07 Dec '23

Hi, I've tested mailman3 and now installed it on productive server. The customer complains that the translation to German is incomplete on the productive server while it was complete on the test server. I can't find a way to confirm this because I only see the English frontend of mailman3-web and I don't know how to switch language in the frontend (I have my OS set to English). Kind regards

2 4

no bounce-processing with verp_probes: yes
by Stefan Bauer 07 Dec '23

07 Dec '23

Dear Users, during one of our upgrades to 3.3.x we set verp_probes: yes according to upgrade notes[1]. However it looks like this disabled bounce handling completely. Howto verify (MM 3.3.9): Set verp_probes: yes verp_delivery_interval: 1 restart mailman3 create test-list add an undeliverable recipient to the list that is known to bounce. send 6 mails to list. see, that all the bounce-messages are received by mailman according to postfix log[2] check bounce.log - no entry. get bounce_score from API[3] - shows bounce_score 0. Can anyone confirm? Any help is greatly appreciated. Thank you. Stefan [1] https://docs.mailman3.org/en/latest/upgrade-3.2.html [2] from=<>, size=8565, nrcpt=1 (queue active) ... to=<v-test-bounces+undeliverable-recipient=realdomain.tld(a)lists.lists.tld>, relay=127.0.0.1[127.0.0.1]:8024 status=sent [3] curl -s -q --user a:b http://localhost:8001/3.1/members/find?subscriber=undeliverable-recipient@r…

2 2

Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line
by Thomas Ward 06 Dec '23

06 Dec '23

We use a multi-hop SMTP system to go from the inside of our network out to the Internet at the domain test.lists.example.com. The setup is this way for ingress: {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 Connector) -> Mailman for delivery to listserv Egress is this: Mailman -> Postfix SMTP Relay (smtpproxy) -> INTERNET -- When a message is sent an invalid list (we'll call it invalid(a)test.lists.example.com) we end up with a nasty side effect in the system. The "no such recipient" response gets sent to the smtpproxy machine and then *it gets redelivered back to Mailman* as a redelivery as if it isn't accepting a permanent-failure condition code. This results in a nasty mail loop that results with a "too many hops" error that doesn't state "invalid recipient" and I have no idea why this is the case. Can anyone provide any insight into how to prevent this type of routing loop caused by the egress of messages? Thomas

2 4

mailman_web/urls.py changes in Postorius 1.3.10
by Lieuallen, Thomas Otis 05 Dec '23

05 Dec '23

The latest release of Postorius includes these lines in mailman_web/urls.py: # Include alternate Postorius and HyperKitty URLs. path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), It appears that these paths override the originals (/mailman3 & /archive). I’m using apache and have had to add ProxyPass lines for these new alternate URLs, as /mailman3 and /archive don’t appear to be presented anymore by mailman-web. All the links at the top (Postorious, lists, domains, bans, system info, users, and archives) – all have /postorius or /hyperkitty as the start of their URLs. If I make a copy of that urls.py in /etc/mailman3 and point to it with ROOT_URLCONF – and comment out those alternate lines, the links go back to the way they were (/mailman3 and /archives). Or, as I mentioned, I can add the ProxyPass lines for /postorius and /hyperkitty to apache. One way or another, it doesn’t seem to be behaving as an alternate. Or have I overlooked something? Thank you Tom Lieuallen

2 1

Error message from monthly cronjob
by Johannes Rohr 05 Dec '23

05 Dec '23

Dear all, Mailman3 on my system is installed in virtualenv. Each month I get the following error message. This error does not seem to have a serious impact on the functioning of mailman, still, what does it mean and how do I get rid of it? Thanks for any hints! Johannes -------- Weitergeleitete Nachricht -------- Betreff: Cron <mailman@*** /opt/mailman/venv/bin/mailman-web runjobs monthly Datum: Fri, 1 Dec 2023 05:56:40 +0100 (CET) Von: Cron Daemon <root(a)mail.rooot.de> An: mailman@*** ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django_extensions/management/commands/runjobs.py", line 40, in runjobs job().execute() File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/jobs/update_and_clean_index.py", line 37, in execute run_with_lock(update_index, remove=True) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 177, in run_with_lock with lock: File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 470, in __exit__ self.unlock() File "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", line 420, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked

2 1

Does anyone use b4 tool with Mailman3 archive
by Prasanth Nair 05 Dec '23

05 Dec '23

Hello all, I know this may not be the right place to ask. But, just in case someone has any experience using the b4 tool (https://github.com/mricon/b4) with the Mailman3 archives? Any idea, how to configure this tool to receive patch series from a mailman archive list? This tool is mainly used for the following purposes: - Retrieve patch series from a public mailing list (e.g. lore.kernel.org) - Compare patch series - Apply patch series to the git repository - Retrieve code-review trailers Kind regards, Prasanth Nair

2 2

nextcloud as auth provider for postorius
by mailman3＠huckley.de 02 Dec '23

02 Dec '23

Hello, have anybody successful setup nextcloud auth provider for postorius? I have done configured the OAuth 2.0-Client in nextcloud/index.php/settings/admin/security. I have add the nexcloud as social application in mailman3/admin/socialaccount/socialapp/. If i try to login via nexcloud, postorius redirect me to the nextcloud, where i successful login, and redirected to postorius But i'm not logged in postorius. what I'm missing? Have anybody a howto? Thanks Falk

5 4

Captcha or similar for new signups?
by peter＠chubb.wattle.id.au 30 Nov '23

30 Nov '23

Hi Folks, Does anyone have a recipe for adding captcha or similar to stop bot accounts signing up with Postorius? We're seeing a heap of fake signups resulting in confirmation emails going to people who haven't signed up, with user names like 'CAOXpYhPFPBFr' -- I'd like to make it just a little harder for bots to sign up. Too many confirmation emails going to non-existent email addresses reduces our mail reputation, and increases the likelihood that legit email is flagged as spam. Peter C

2 1

Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error'))
by Mark Labeste 30 Nov '23

30 Nov '23

Hi Admin, Any idea on this error? It happen when you wrote a tread it send the mail but not save on the archive. Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8407) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8406) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8400) Connection to HyperKitty failed: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8400) Could not archive the message with id <168853565119.17959.11384406081068301715(a)email1.example.com> Nov 28 20:34:51 2023 (8400) archiving failed, re-queuing (mailing-list testmaillist.example.com, message <168853565119.17959.11384406081068301715(a)email1.example.com>) Nov 28 20:34:51 2023 (8400) Exception in the HyperKitty archiver: ('Connection aborted.', OSError(0, 'Error')) Nov 28 20:34:51 2023 (8400) Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 710, in urlopen chunked=chunked, File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 386, in _make_request self._validate_conn(conn) File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn conn.connect() File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/connection.py", line 429, in connect tls_in_tls=tls_in_tls, File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 450, in ssl_wrap_socket sock, context, tls_in_tls, server_hostname=server_hostname File "/opt/mailman/venv/lib64/python3.6/site-packages/urllib3/util/ssl_.py", line 493, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket _context=self, _session=session) File "/usr/lib64/python3.6/ssl.py", line 776, in __init__ self.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake self._sslobj.do_handshake() File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake self._sslobj.do_handshake() OSError: [Errno 0] Error

3 3

Re: [Mailman-Developers] Re: SSL error while connecting to hyperkitty
by Abhilash Raj 29 Nov '23

29 Nov '23

On Sat, Aug 31, 2019, at 10:20 AM, sandeep kumar wrote: > Hi Abhilash > > Thanks for the reply. > > Just two more answers please -:) > > Can I use the sample apache.conf in example_project in my webserver virtual host...?? See this thread for the apache configuration: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You'd need to adjust the paths and SSL configuration. > > And what should be the configuration details to be given in uwsgi server...?? http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-wsgi-server > > Regards > Sandeep > > > On Sat, Aug 31, 2019 at 10:25 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: >> __ >> On Sat, Aug 31, 2019, at 8:49 AM, sandeep kumar wrote: >>> Hi Abhilash >>> >>> Thanks for your reply. -:) >>> >>> We are using apache httpd as webserver to redirect. >>> >>> the proxy pass in webserver is >>> >>> ProxyPass / http://localhost:8000 >>> ReverseProxyPass / http://localhost:8000 >> >> >> Can you put `base_url: http://localhost:8000/hyperkitty` in your mailman-hyperkitty.cfg and see that it works? :) >> >> This should not try any funny SSL redirection. >> >>> I don't have idea of deploying this in production, so I just went on searching and I found wsgi (say uwsgi) is required to send the requests from webserver to mailman. Correct me if I am wrong. >>> >>> I have few queries listed below. Please reply to them. >>> >>> Should I use the wsgi.py present in the directory of mailman-suite ...?? >> >> Yes, that is the one which is supposed to be used. >> >>> >>> What should be the ProxyPass ..?? Where should the first hit go from webserver ---> uwsgi ---> ?? >> >> uwsgi is web server running Mailman's web componenet. It doesn't need to hit anything. You can restart it directly when you want to restart Mailman's web component, you don't need to do anything to your web server (httpd) for this. >> >> >> >>> >>> Can we run "python manage.py runserver" every time to start mailman suite..?? Can we make mailman-suite start/stop just by restarting the HTTPD..?? >> >> >> No, use a wsgi server, like uwsgi or gunicorn to run mailman-suote. `python manage.runserver` is a command used during development shouldn't be used at all in prod. >> >>> >>> What should be the entry in Hyperkitty.cfg file after all the above steps..?? I mean at the end >>> >>> Please reply to the above queries. Thanks for your help >>> Regards >>> Sandeep >>> >>> >>> >>> >>> >>> On Sat, Aug 31, 2019 at 8:45 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> On Sat, Aug 31, 2019, at 1:36 AM, sandeep kumar wrote: >>>> > Hi Team >>>> > >>>> > Iam seeing following errors while mailman is trying to archive in >>>> > mailman.log >>>> > >>>> > >>>> > This is my base URL in mailman-hyperkitty.cfg >>>> > >>>> > base_url: http://localhost/hyperkitty >>>> >>>> Are you sure this is the URL? this is http and Mailman shouldn't try to connect to this using HTTPS. >>>> >>>> Is your web server configured to redirect all HTTP traffic to HTTPS? If that is the case, then it is going to fail. >>>> >>>> Which wsgi server are you using? uwsgi? >>>> >>>> Can you also show your ProxyPass configuration? >>>> >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > *During handling of the above exception, another exception >>>> > occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/adapters.py", >>>> > line 449, in send timeout=timeout File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-py3.6.egg/urllib3/connectionpool.py", >>>> > line 638, in urlopen _stacktrace=sys.exc_info()[2]) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/urllib3-1.24.1-py3.6.egg/urllib3/util/retry.py", >>>> > line 398, in increment raise MaxRetryError(_pool, url, error or >>>> > ResponseError(cause))urllib3.exceptions.MaxRetryError: >>>> > HTTPSConnectionPool(host='domain.com <http://domain.com>', port=443): >>>> > Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=SecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate >>>> > verify >>>> > failed (_ssl.c:841)'),))During handling of the above exception, another >>>> > exception occurred:Traceback (most recent call last): File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", >>>> > line >>>> > 154, in _archive_message url = self._send_message(mlist, msg) File >>>> > "/var/lib/mailman/mailman-hyperkitty/mailman_hyperkitty/__init__.py", >>>> > line >>>> > 201, in _send_message files={"message": ("message.txt", >>>> > message_text)}) >>>> > File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/api.py", >>>> > line 116, in post return request('post', url, data=data, json=json, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/api.py", >>>> > line 60, in request return session.request(method=method, url=url, >>>> > **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 533, in request resp = self.send(prep, **send_kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 668, in send history = [resp for resp in gen] if allow_redirects >>>> > else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 668, in <listcomp> history = [resp for resp in gen] if >>>> > allow_redirects else [] File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 247, in resolve_redirects **adapter_kwargs File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/sessions.py", >>>> > line 646, in send r = adapter.send(request, **kwargs) File >>>> > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/requests-2.21.0-py3.6.egg/requests/adapters.py", >>>> > line 514, in send raise SSLError(e, >>>> > request=request)requests.exceptions.SSLError: >>>> > HTTPSConnectionPool(host=domain.com <http://domain.com>', port=443): Max >>>> > retries exceeded with url: >>>> > /hyperkitty/api/mailman/archive?key=SecretArchiverAPIKey (Caused by >>>> > SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate >>>> > verify >>>> > failed (_ssl.c:841)'),))* >>>> > >>>> > >>>> > Rgrds >>>> > Sandeep >>>> > >>>> > On Sat, Aug 31, 2019 at 10:20 AM sandeep kumar <sandeep7790(a)gmail.com> >>>> > wrote: >>>> > >>>> > > Team any help >>>> > > >>>> > > Sent from my iPhone >>>> > > >>>> > > > On 30-Aug-2019, at 11:18 PM, sandeep kumar <sandeep7790(a)gmail.com> >>>> > > wrote: >>>> > > > >>>> > > > Hi Team >>>> > > > >>>> > > > Iam using httpd to work with ssl on mailman 3 using proxy pass. >>>> > > > >>>> > > > After this configuration Iam not able to connect to hyperkitty. It is >>>> > > throwing ssl certificate error in mailman.log file. >>>> > > > >>>> > > > What should be the configuration of hyperkitty while using https in >>>> > > mailman..? >>>> > > > >>>> > > > Please help me with this Iam struck here from past 4 days >>>> > > > >>>> > > > Rgrds >>>> > > > Sandeep >>>> > > > >>>> > > > Sent from my iPhone >>>> > > >>>> > >>>> > >>>> > -- >>>> > Regards >>>> > Sandeep Kumar >>>> > +91-9642669192 >>>> > _______________________________________________ >>>> > Mailman-Developers mailing list -- mailman-developers(a)python.org >>>> > To unsubscribe send an email to mailman-developers-leave(a)python.org >>>> > https://mail.python.org/mailman3/lists/mailman-developers.python.org/ >>>> > Mailman FAQ: https://wiki.list.org/x/AgA3 >>>> > >>>> > Security Policy: https://wiki.list.org/x/QIA9 >>>> > >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>> >>> >>> -- >>> Regards >>> Sandeep Kumar >>> +91-9642669192 >>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> > > > -- > Regards > Sandeep Kumar > +91-9642669192 > -- thanks, Abhilash Raj (maxking)

4 3

Putting mailman3 server behind a netscaler
by Lieuallen, Thomas Otis 29 Nov '23

29 Nov '23

(I sent this a week ago, but apparently it got lost, trying to resend.) We’ve been using MM2 for eons and are working on a migration to MM3. So, bear with me as I’m still coming up to speed. I’m running MM 3.3.8 and Postorious 1.3.8. Our mailing lists include members within our organization as well as a number outside. We don’t want to expose our MM3 server directly to the open internet, so wish to hide the web portion behind our netscaler and our regular pool of web servers. Those web servers will proxy MM3 web pages on over to our MM3 machine to handle. This seems to work. Email will meander in via MX and mail relay servers. I found and followed directions in this email regarding changing URL paths: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… So, say our MM3 server is: mm3.fqdn I am trying to publish and use urls like www.fqdn/mailman3-admin<http://www.fqdn/mailman3-admin>, www.fqdn/mailman3/lists<http://www.fqdn/mailman3/lists>. Again, that works for me. However, MM3 still has its concept of what URLs should be. I hoped I could fix that by way of templates, but I’m not sure there’s a template for everything. I added some templates, but have not replaced all. I was wondering and hoping that some central change could fix any default templates en-mass. Most recently, I changed the mailman admin email yesterday and the confirmation email directed me to mm3.fqdn/…/confirm-email/…. I looked at the stock templates and nothing there had that wording. I just looked at postorious docs and nothing jumps out at me there. 1. Have I gone down a bad rabbit hole? 2. Is there a way to change the advertised web server address? 3. Should I just continue rolling out my own templates and hope and assume that will take care of this issue? Thank you Tom Lieuallen Oregon State University

2 2

Importing archive from mm21
by Lars Bjørndal 29 Nov '23

29 Nov '23

I imported an archive from a list created in September 2013 with the following command: mailman-web hyperkitty_import -l annonsering(a)hodr.no --since 2013-09-01 <mbox file> No errors reported. I then did mailman-web update_index_one_list annonsering(a)hodr.no No, when I go to https://hodr.no/archives/list/annonsering@hodr.no/, I cannot choose mails earlier than January 2023. What's the problem, do you think? Lars

2 3

All messages to a new list/domain shunted from "in" queue with no logged exceptions
by Jered Floyd 26 Nov '23

26 Nov '23

OK -- my turn to ask a question... I created a new domain and lists in my (functioning) Mailman 3 install. Messages to these new lists are successfully delivered via LMTP to Mailman and then disappear. They are in the shunt queue, with a source queue of "in". There are no exceptions logged in my mailman.log. An example from a qfile: { '_parsemsg': False, 'envsender': 'noreply(a)[domain].com', 'lang': 'en', 'listid': '[listname].[domain].com', 'original_size': 2654, 'received_time': datetime.datetime(2023, 11, 25, 14, 0, 6, 968185), 'rule_hits': [], 'rule_misses': [], 'to_list': True, 'version': 3, 'whichq': 'in'} Unshunting the message has no effect, and no logs are generated. Any suggestions? Thanks, --Jered

3 12

Mailman3 stopped sending out mail
by Abhijith PA 22 Nov '23

22 Nov '23

Hello. Recently my mailman3 instance stopped distributing mail. But mailman's own mail (notification, digest etc) and archiving are working OK. I couldn't figure what is going wrong From mail.log --- Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: client=mail.xxxx.xx[5.79.72.163] Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: client=mail.xxxx.xx[5.79.72.163] Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx SSL Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx SSL Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed I am not sure why 'postfix/qmgr[13211]: 04C2412038F: removed' is happening. from /var/log/mailman3/smtp.log: Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) handling connection Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'LHLO lists.xxxx.xx' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'MAIL FROM:<abhijith(a)xxxx.xx>' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) sender: abhijith(a)xxxx.xx Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'RCPT TO:<test3(a)xxxx.xx>' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) recip: test3(a)xxxx.xx Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'DATA' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'QUIT' Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) connection lost Dec 31 10:03:21 2018 (6323) Connection lost during _handle_client() Here again I am doubtful about 'Connection lost during _handle_client()'. Please help. Abhijith PA

3 5

Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html
by Michael.Sanderson＠ubc.ca 21 Nov '23

21 Nov '23

Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get (venv) $ mailman-web compress Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html done Compressed 2 block(s) from 78 template(s) for 1 context(s). The Invalid template errors for socialaccount/login_cancelled.html and account/verified_email_required.html are gone, but we still have a parsing error. This is an installation on RHEL9 with python 3.11 based on the virtualenv installation method at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Michael Sanderson

6 6

moving lists to another server
by bryan.kartzman＠yu.edu 21 Nov '23

21 Nov '23

I have both my mailman lists and django config in postgres databases. If I want to move my lists to another server that is running mailman 3, aside from copying the databases to the other server, what other things (perhaps all files under /var/lib/mailman3?, etc) would I need to bring over to the other server?

6 21

Migrating from Listserv 17 to Mailman 3
by Cooper, Robert A 21 Nov '23

21 Nov '23

Howdy! Does anyone have or know of a guide to migrate from Listserv 17, including list archives, to Mailman 3? I've found documentation on moving to Mailman 2, but those don't seem to apply to the newer version. Thanks, RobertC

2 1

copies of sent "admin" messages
by David Bremner 21 Nov '23

21 Nov '23

I'm dealing with (presumably bogus) spam reports for messages from foo-bounces(a)list.domain As far as I can tell these messages are triggered by the alleged-victim/apparent-attacker sending messages to foo-subscribe followed immediately by foo-unsubscribe. I have the size and time from postfix and/or mailman's smtp.log, but I don't have the message content. Are these messages stored somewhere by Mailman? Can I have them stored for a month or so in order to deal with these bureaucratic incidents? David

3 3

Where do I find the check_hk_archive script
by Lars Bjørndal 19 Nov '23

19 Nov '23

In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run the check_hk_archive script found in hyperkitty/contrib. When trying `git clone https://gitlab.com/mailman/hyperkity`I get: Username for 'https://gitlab.com': Is it possible to get the script without an account on gitlab? Thanks, Lars -- Lars Bjørndal <lars(a)lamasti.net> Ostadalsveien 64, 0753 Oslo. Mobil: 958 37 537

2 3

configuration to send to recipients in a spread out manner to avoid being considered spam
by testeur 19 Nov '23

19 Nov '23

Hi, I s there a mean to configure the list for that emails be sent to recipients in a spread out manner to avoid being considered spam ? cause AOL, YAHOO seems to consider emails sent to recipients as spam or an "Excessively high volume of emails". there's just 40 (aol, yahoo) emails suscribed to the list. thx.

2 2

How to Personalise Email Content with Usernames in Mailman 3
by Zaheer Abbas 18 Nov '23

18 Nov '23

Hello, I am currently working with Mailman 3 and looking to enhance the personalization of the emails sent through our mailing list. Specifically, I wish to include the recipient's username in the email content, similar to a personalized greeting (e.g., "Dear [username]"). My questions are: 1. Does Mailman 3 support the inclusion of personalized data (like usernames)? 2. If yes, how can I do that? Is there any placeholder for that? Any guidance or suggestions on how to achieve this would be greatly appreciated. Thank you for your time and assistance.

3 4

Add rule to auto-discard "AutoReply" messages from list members
by Thomas Ward 18 Nov '23

18 Nov '23

When people are communicating on Mailman3 lists, some set up automatic responders for out-of-office, etc. and get let through the system to list recipients. Unfortunately, this is bad behavior and appears to not be caught by default. I'd like to set up some kind of rule globally rather than per-list that would check if a message is an automatic reply (based on a set of criteria we've come up with programmatically on our previous custom implementation of lists) and then default-discard those messages. Is there a way with custom rules to implement this? We're looking for certain strings on the subject line or other headers to determine "Discard" cases in our custom list implementations, but we are hoping we can implement this with customized rules in Mailman3 to achieve this goal. How would we structure that type of rule, and do we check the message object or the msgdata instead? Thomas

5 6

Possible SQLAlchemy 2.0.23 incompatibility (requires investigation)
by Jered Floyd 15 Nov '23

15 Nov '23

I just did a container rebuild and Mailman failed to load, with the below errors on the console. Pinning SQLAlchemy 2.0.22 resolved this; I haven't tried to further debug. (2.0.23 was release on November 3.) --Jered Traceback (most recent call last): File "/opt/app-root/src/.local/bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/commands/cli_control.py", line 109, in start call_name(config.mta.incoming).regenerate() File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/mta/postfix.py", line 109, in regenerate self._generate_lmtp_file(fp) File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/mta/postfix.py", line 148, in _generate_lmtp_file for list_name, mail_host in list_manager.name_components: File "/opt/app-root/src/.local/lib/python3.9/site-packages/mailman/model/listmanager.py", line 140, in name_components for mail_host, list_name in result_set.with_entities( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2833, in __iter__ result = self._iter() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2847, in _iter result: Union[ScalarResult[_T], Result[_T]] = self.session.execute( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2308, in execute return self._execute_internal( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2180, in _execute_internal conn = self._connection_for_bind(bind) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 2047, in _connection_for_bind return trans._connection_for_bind(engine, execution_options) File "<string>", line 2, in _connection_for_bind File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/state_changes.py", line 139, in _go ret_value = fn(self, *arg, **kw) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1143, in _connection_for_bind conn = bind.connect() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 3268, in connect return self._connection_cls(self) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 145, in __init__ self._dbapi_connection = engine.raw_connection() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 3292, in raw_connection return self.pool.connect() File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 452, in connect return _ConnectionFairy._checkout(self) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 1378, in _checkout del fairy File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 146, in __exit__ raise exc_value.with_traceback(exc_tb) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/pool/base.py", line 1306, in _checkout result = pool._dialect._do_ping_w_event( File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 709, in _do_ping_w_event return self.do_ping(dbapi_connection) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/dialects/mysql/pymysql.py", line 104, in do_ping if self._send_false_to_ping: File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/util/langhelpers.py", line 1146, in __get__ obj.__dict__[self.__name__] = result = self.fget(obj) File "/opt/app-root/src/.local/lib/python3.9/site-packages/sqlalchemy/dialects/mysql/pymysql.py", line 93, in _send_false_to_ping insp = langhelpers.get_callable_argspec(Connection.ping) AttributeError: 'function' object has no attribute 'ping'

1 1

Database problem after system upgrade
by Lars Bjørndal 15 Nov '23

15 Nov '23

I've upgraded from Fedora 37 to 38, and the postgresql server will not start: nov. 14 23:22:18 dalen.lamasti.net postgresql-check-db-dir[1410]: An old version of the database format was found. nov. 14 23:22:18 dalen.lamasti.net postgresql-check-db-dir[1410]: Use 'postgresq l-setup --upgrade' to upgrade to version '15' nov. 14 23:22:18 dalen.lamasti.net postgresql-check-db-dir[1410]: See /usr/share /doc/postgresql/README.rpm-dist for more information. When I run `postgresql-setup --upgrade` I get: runuser: warning: cannot change directory to /opt/postgresql: no such file or directory * Upgrading database. /usr/bin/postgresql-setup: line 307: cd: /opt/postgresql: no such file or directory ERROR: pg_upgrade tool failed ERROR: Upgrade failed. * See /var/lib/pgsql/upgrade_postgresql.log for details. Why does the upgrade tool look for files in /opt/postgresql and not in /var/lib/pgsql? How to fix it? Thanks, Lars

3 6

Mailserver Log entries following through mailman?
by Andreas Barth 11 Nov '23

11 Nov '23

Hi, is there some way to find an ID to follow an email through mailman? In the exim logfile there is only something like C="250 Ok" (whereas in mails sent to another exim there is something like C="250 OK id=…"). (What I sometimes need to do is to follow an mail whether it is sent through mailman and to where.) Or should I raise an issue as whishlist request? Regards, Andi

3 3

ModuleNotFoundError: No module named 'mailman_web'
by gordon＠dickens.com 10 Nov '23

10 Nov '23

I have had mailman3 working great on Debian 11, however, I just upgraded to Debian 12 and, following the upgrade, mailman3 is not working and I am getting the following error message: ModuleNotFoundError: No module named 'mailman_web' Does anybody have any recommendations? Thanks! Gordon

5 24

Default templates
by Steve Brown 10 Nov '23

10 Nov '23

I'm new to this list and newly a Mailman list administrator. I know I can customize message templates and have done so for my list's Welcome message. My problem is knowing what I'm replacing when I create a "new" template. How/where can I see he default content? Steve Brown

2 2

user disabled other problems
by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia 06 Nov '23

06 Nov '23

Good morning, I have to understand something more about disabled users. I renabled some users, but they continue to non teceive the newsletter. Is there a more detailed log that I can analize to discover dis problem? Thank you -- Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it

4 5

Template - "You can use these variables in the templates" - The variable for "leave" is missing
by Wikinaut 04 Nov '23

04 Nov '23

The current template input page shows this text: You can use these variables in the templates. $hyperkitty_url: Permalink to archived message in Hyperkitty $listname: Name of the Mailing List e.g. ant(a)example.com $list_id: The List-ID header e.g. ant.example.com $display_name: Display name of the mailing list e.g. Ant $short_listname: Local part of the listname e.g. ant $domain: The domain part of the listname e.g. example.com $info: The mailing list's longer descriptive text $request_email: The email address for -request address $owner_email: The email address for -owner address $site_email: The email address to reach the owners of the site $language: The two letter language code for list's preferred language e.g. fr, en, de I suggest to add the variable for leaving a mailing list here. But what is the variable name?

4 6

Mailman 3 deployment: ok to use same database instance for core, web, and hyperkitty tables?
by s.dobrau＠ucl.ac.uk 04 Nov '23

04 Nov '23

Hello, We are currently working on a migration plan for Mailman -> Mailman 3. We have around over 3000 mailing lists with a total of 50K members and 500 worth of archived data. Our plan is to have core+web (instance 1) and Hyperkitty (instance 2). With the archives on the FS local to the Hyperkitty. And all 3 tables (core, web, Hyperkitty) pointing to the same database on a remote SQL (mysql-enterprise) instance. Using class mailman.database.mysql.MySQLDatabase (and whatever necessary on the Django/Hyperkitty instance). Is this feasible, if so what would be the recommended compute/storage requirements. If not what other alternatives have we got ? A remote or local PostgreSQL instance is also possible if recommended. Thank you very much in advance and all the best ! Regards, Serban

4 4

Immediate notification to the administrator
by pau.baiges＠csuc.cat 02 Nov '23

02 Nov '23

Hello In Mailman, I have all the lists marked with the "Immediate notification to the administrator" option. Should list moderators receive immediate notification of new requests as well as daily reminders about the pending ones? List moderators (and list administrators) receive daily reminders of pending requests for approval, such as subscriptions to a moderated list or submissions that are held for some reason. Enabling this option results in immediate notifications being sent upon the arrival of new requests. When there's a message being held because it needs approval, it automatically sends an email to the list owners. However, it also states that it sends a daily reminder if the email remains unapproved, but it's not doing that. I'll show you how I have /etc/postfix/transport configured. I receive the first "owner" email, but not the daily one. list-owner(a)llistes.csuc.cat relay:[ip]:25 list(a)llistes.csuc.cat .. list-admin(a)llistes.csuc.cat ... list-bounces(a)llistes.csuc.cat ... list-confirm(a)llistes.csuc.cat ... list-join(a)llistes.csuc.cat ... list-leave(a)llistes.csuc.cat ... list-request(a)llistes.csuc.cat ... list-subscribe(a)llistes.csuc.cat ...

5 9

Weird behavior with Outlook and any MM3 List
by Thomas Ward 01 Nov '23

01 Nov '23

I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. Has anyone observed this behavior before? If so, have you found any workarounds? Thomas

2 2

Reduction of spam - FROM_LOCAL_HEX
by Kyriakos Terzopoulos 31 Oct '23

31 Oct '23

Hi, After fixing all issues with mailman I want to reduce the chance for email being marked as spam, especially from Gmail. I have added SPF and DKIM records and I am now using dkimvalidator to debug the emails being sent. Here is what I'm getting from spam evaluation: *0.3 FROM_LOCAL_HEX From: localpart has long hexadecimal sequence* My guess is that the From address is very large, for example: mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu Is there any way to mitigate this problem? Thank you, *Kyriakos Terzopoulos* Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

4 3

psycopg2 error?
by Odhiambo Washington 30 Oct '23

30 Oct '23

This is the first time I am seeing this with MM3 so maybe it's something new in the latest releases? Using the virtualenv method to install MM3 in a fresh Debian 12 VM, I have run into an error while starting the mailman3 service. I cannot figure out what this error means. <CUT> root@debian12:/home/wash# systemctl status mailman3.service × mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Thu 2023-10-26 09:36:41 EAT; 8s ago Process: 1893842 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 789ms Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: dbapi = dbapi_meth(**dbapi_args) Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: ^^^^^^^^^^^^^^^^^^^^^^^^ Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", line 690, in import_dbapi Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: import psycopg2 Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line 51, in <module> Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: from psycopg2._psycopg import ( # noqa Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: SystemError: initialization of _psycopg raised unreported exception Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 26 09:36:41 debian12.wash.lan systemd[1]: Failed to start mailman3.service - GNU Mailing List Manager. </CUT> No log entry in any of the log files in /opt/mailman/mm/var/logs/. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 11

disabled users
by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia 27 Oct '23

27 Oct '23

Hello, Wher I find the disabled user of a mailing list and wher I can reactivate them? I do not find this nor in web interface neither in command line utility. Thank you best regards -- Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibrescia.it

3 6

(Custom) Plugins: Proper file path(s) for adding a handler?
by Thomas Ward 25 Oct '23

25 Oct '23

I want to add a custom handler that implements customized thread IDs in the system. I already have the DB logic worked out, but the documentation for plugins is NOT clear on how to define a handler in a plugin, nor does the example plugin in the documentation on Gitlab have any custom handlers. I'm looking to add a custom handler so that the private pipeline for threaded-subject-list can use thread-subject (the custom handler) instead of subject-prefix (builtin). I'm unclear how to add this properly in a plugin that would be read properly by Mailman, though. Any tips on the filestructure needed for the Python code/plugin package in order to properly be set up and work? Thomas

3 14

rDNS issue? Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid
by Kyriakos Terzopoulos 25 Oct '23

25 Oct '23

Hi all, I'm on the latest mailman installation in a HestiaCP server. The past few days I have been investigating some spam issues and by using dkimvalidator.com I found the following: 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list manager* 3.2 HELO_DYNAMIC_IPADDR Relay HELO'd using suspicious hostname (IP addr 1)* Note the last line on the above debug information which raises the spam score of the email. Some research showed me that I needed a rDNS entry in my server. I'm on a Hetzner cloud VM so I used the Hetzner console to change the rDNS entry from: static.XXX.XXX.XXX.XXX.clients.your-server.de to my initial server hostname for example: *hestia.myserver.com <http://hestia.myserver.com>* However, after some propagation, I found today that even though I can send email to any normal address created in the server's control panel, mailing list emails do not get sent. I see the following in the logs: Mailman SMTP log: Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> *response exception: (550, b'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'*, 'testlist-bounces+myusername=myproject.eu(a)myproject.eu') Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> smtp to testlist(a)myproject.eu for 1 recips, completed in 45.07745146751404 seconds Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> post to testlist(a)myproject.eu from testlist-confirm+07d3315fa11a75588857fc93d1832ba74fb09fdd(a)myproject.eu, 1633 bytes, 1 failures Oct 24 14:17:47 2023 (3759611) <169814622178.3759638.4589434779084932533@localhost> delivery to myusername(a)myproject.eu failed with code 550, b*'Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid'* Exim4 log: 2023-10-24 14:17:47 H=([127.0.0.1]) [XXX.XXX.XXX.XXX] rejected MAIL <testlist-bounces+myusername=myproject.eu(a)myproject.eu>: *Helo name contains an IP address (HELO was [127.0.0.1]) and not is valid* The weird thing is that when I do a mailman-web sendtestemail this email is sent successfully. Also please note that before the rDNS change I did not have an issue with mail sending. Last but not least, after some search I set in Exim4 the following: PRIMARY_HOST_NAME = *hestia.myserver.com <http://hestia.myserver.com>* Any help would be greatly appreciated. *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

2 4

Without being logged in, at least one mailing list - flagged as no-show - is listed in https://mydomain/hyperkitty/
by Wikinaut 25 Oct '23

25 Oct '23

The list is not yet used (i.e. "inactive"), but clearly flagged as " Show list on index page = no" I regard this as a bug.

1 1

More Mailman releases!
by Abhilash Raj 24 Oct '23

24 Oct '23

Hello Everyone, I am pleased to announce several new releases for GNU Mailman project. Thanks to all the contributors for making these releases possible! 1. Postorius 1.3.10 [1] 2. Hyperkitty 1.3.8 [2] 3. Django-mailman3 1.3.10 [3] 4. Mailman-web 0.0.7 [4] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 [2]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst Do note that for Postorius, I released 1.3.9, but I forgot to update dependency metadata to require `django-mailman3>=1.3.10` (which is required for the new bootstrap 5 upgrade across packages) and so I also released Postorius 1.3.10 just after. Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available at https://docs.mailman3.org/en/latest/. Finally, similar to Mailman Core, note that PyPI doesn't accept signatures anymore so each packages' release page now has the tarball uploaded to them along with the signature: Django-mailman3: https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 -- thanks, Abhilash Raj (maxking)

9 17

120 gmail users removed from lists !
by elemac＠free.fr 24 Oct '23

24 Oct '23

Hello, on 15th October, 120 users with gmail address where suddenly removed from lists in mailman3, something changed in google ?

8 11

Gmail bounces as a result to high send rate
by Mohsen Masoudfar 24 Oct '23

24 Oct '23

I managed to receive the bounced emails to my mailbox and I can now see the stated reason for th eissue, the bulk of the emails are marked as "expired" due to the following response: "smtp; Message expired: unable to deliver in 840 minutes.< Our system has detected an unusual rate of unsolicited mail. To protect our users from spam, mail has been temporarily rate limited. Please visit https://support.google.com/mail/?p=UnsolicitedRateLimitError to review our Bulk Email Senders Guidelines." The issue is exclusive to Gmail, no other email provider responded with a comparable message. I followed their recommendation, but I am not sure how to reduce the rate on Postfix side. Can I do it per list? or once per server? Thanks.

2 1

Internal Server Error: /mailman/accounts/fedora/login/
by Kilian Kilger 24 Oct '23

24 Oct '23

Hi mailing list, I own a mailman box. I regularily (many times a day) get mail with an internal server error. I am using Debian and the included mailman3-full package. I guess someone tries to hack my instance. But I don't understand why this leads to the internal server error. I am also wondering why the request URL is /mailman/accounts/fedora/login, as I am using Debian (understandable if the request happens via an outside trigger). I have no clue about the internal workings of mailman though. I use Debian 11 bullseye and thus version 3.3.3. I can trigger the internal server error by myself by visiting the request URL. Despite these emails the instance seems to work fine. Best regards, Kilian. Internal Server Error: /mailman/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: <URL>/mailman/accounts/fedora/login/?process=login&next=/mailman/accounts/password/reset/ Django Version: 2.2.24 Python Executable: /usr/bin/uwsgi-core Python Version: 3.9.2 Python Path: ['.', '', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/local/lib/python3.9/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.9/dist-packages'] Server time: Fr, 17 Sep 2021 06:12:57 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in view 71. return self.dispatch(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch 97. return handler(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in get 56. return self.post(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py" in post 67. client = _openid_consumer(request) Exception Type: TypeError at /accounts/fedora/login/ Exception Value: _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request information: USER: AnonymousUser

3 2

General question mailman3: message sender acceptance "always"
by Wikinaut 23 Oct '23

23 Oct '23

I received one mail from a sender who's not a member for moderation (=ok). Mailman2 had the moderation option "allow this sender to sender further mails" (I call this: to add this sender to the additional "white list" of white-listed addresses.) I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). Is it a bug or feature?

2 4

pip install -U mysqlclient
by Odhiambo Washington 23 Oct '23

23 Oct '23

Hello everyone, After successfully updating my MM3 venv install, I thought I could also keep everything else up to date. One app refuses - mysqlclient. All the rest did update. PS: I have a full backup of the venv so no worries there :) <CUT> (venv) [mailman@gw /opt/mailman/mm]$ pip install -U mysqlclient Requirement already satisfied: mysqlclient in ./venv/lib/python3.11/site-packages (2.1.1) Collecting mysqlclient Using cached mysqlclient-2.2.0.tar.gz (89 kB) Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [25 lines of output] Trying pkg-config --exists mysqlclient Command 'pkg-config --exists mysqlclient' returned non-zero exit status 1. Trying pkg-config --exists mariadb Command 'pkg-config --exists mariadb' returned non-zero exit status 1. Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module> main() File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) ^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 355, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=['wheel']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 325, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-usp5tphe/overlay/lib/python3.11/site-packages/setuptools/build_meta.py", line 341, in run_setup exec(code, locals()) File "<string>", line 154, in <module> File "<string>", line 48, in get_config_posix File "<string>", line 27, in find_package_name Exception: Can not find valid pkg-config name. Specify MYSQLCLIENT_CFLAGS and MYSQLCLIENT_LDFLAGS env vars manually [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. </CUT> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 4

no access to Postorius web pages after upgrade
by David Newman 22 Oct '23

22 Oct '23

Upgrading to MM3 3.39, Postorius 1.3.10, Hyperkitty, 1.3.8, Django-mailman3 1.3.11, and Mailman-web 0.0.8 in a venv all seemed to go OK. Mailman3 lists work as expected, and admins can log in via Django. However, any attempt to reach lists, domains, users, etc. now returns a 404 Not Found error. All the Postorius stuff worked as expected before the upgrade. In the nginx server logs, any Hyperkitty and Postorius URLs are now appended to /opt/www/roundcubemail, which is this web server's root directory but not the root for Mailman3 (I run Roundcubemail and MM3 on the same server; don't judge me :-). Here is the nginx error, with obfuscation of client and server info: 2023/10/22 10:43:24 [error] 2264140#2264140: *135 "/opt/www/roundcubemail/postorius/domains/index.php" is not found (2: No such file or directory), client: 1.2.3.4, server: lists.example.com, request: "GET /postorius/domains/ HTTP/2.0", host: "lists.example.com", referrer: "https://lists.example.com/mailman3/listinfo" And here are the relevant bits of the Nginx config. Again, this worked before the upgrade. server { listen 443 ssl http2; server_name lists.example.com; root /opt/www/roundcubemail; # begin mailman3 stuff location /static/ { alias /opt/mailman/web/static/; } location /mailman3/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /archives/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /accounts/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /admin/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /mailman/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } location /user-profile/ { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } # end mailman3 stuff } Also, I'm not sure if it's relevant but after upgrading, the migrate command throws a warning like this: (venv) mailman@mail10:~$ mailman-web migrate System check identified some issues: WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Thanks in advance for clues on getting all Postorius/Django links working again. dn

2 3

[migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite
by Wikinaut 22 Oct '23

22 Oct '23

As suggested by @Mark last week, I exported my databases mailman3, mailman2web of what was mailman 3.3.0 (or so) and imported these on my new working system. Apparently, a database migration step is needed to run the new mailman3 with some older databases: because when I want to login to view my mailing lists, I got "An error occurred while processing your request." in the web. Log files and error mail messages say inter alia: Internal Server Error: /accounts/login/ OperationalError at /accounts/login/ (1054, "Unknown column 'socialaccount_socialapp.provider_id' in 'field list'" and Internal Server Error: /archives/ OperationalError at /archives/ (1054, "Unknown column 'hyperkitty_mailinglist.archive_rendering_mode' in 'field list'") Please can you assist: How can I add the missing tables, is there an update script (running "python migrate.py" was not fixing this).

2 2

New messages are not archived - may be a path issue
by Wikinaut 21 Oct '23

21 Oct '23

(I read thoroughly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… "New messages not being archived", but could not find what's wrong on my machine.) This is what I found in /var/log/mailman3/mailman.log : HyperKitty failure on https://mail.opteryx.org/mailman3/archives/api/mailman/archive: This page either doesn't exist, or it moved somewhere else. I have double checked all settings in the /etc/mailman3/ configuration files and are not able to get message archived. There is not REST error message any more, but perhaps a problem with the paths. I have no idea any more where to fix this.

3 3

(venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"
by Wikinaut 21 Oct '23

21 Oct '23

I followed all single steps until this: https://docs.list.org/en/latest/install/virtualenv.html#run-database-migrat… (I will improve the documentation with the missing parts later today), Now I got this and got stucked and need your help: django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE full stack: (venv) mailman@mail:/run$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 420, in execute django.setup() File "/opt/mailman/venv/lib/python3.11/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/venv/lib/python3.11/site-packages/django/apps/registry.py", line 124, in populate app_config.ready() File "/opt/mailman/venv/lib/python3.11/site-packages/allauth/account/apps.py", line 15, in ready raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE

6 28

[Bug] Archiver: when deleting an archive, the control flow is lost (return-to should go to https://example.com/archives/ but does not)
by Wikinaut 21 Oct '23

21 Oct '23

How to reproduce: When deleting an archive, the confirmation page for the requested delete action is (correct) https://example.com/archives/list/test@example.com/delete/ When you now click the button DELETE, then the web control flow ist lost. BUG Instead of https://example.com/archives/ the https://example.com is shown, which appears to be a bug. REMARK: The archive-to-be-deleted was indeed deleted. This behaviour was observed with both installations on a fresh server: - debian12 install (package mailman3-full) ; and - venv install (recommended on your page)

2 1

Message of migrated list showing "unsubscribe@%(host_name)s" in footer
by alex＠presland.net 21 Oct '23

21 Oct '23

Apologies if I've not found a previous post for this; I did look before starting a new thread. We migrated a number of mailman lists last weekend and I spotted this evening that an email from the list contained a footer along the lines of the following (all bits in CAPITALS were successfully representing the list. ===== LISTNAME mailing-list -- LISTNAME@DOMAIN To unsubscribe, email LISTNAME-unsubscribe@%(host_name)s ===== 1) I don't know why %(host_name)s hasn't been automagically substituted 2) I can't find anywhere to change this footer in the Mailman3 Postorius interface

2 3

After importing my old databases, the mail local_recipient map is suddenly not working any more
by Wikinaut 20 Oct '23

20 Oct '23

After importing old databases everythimng looks fine now. But the mail local_recipient maps are not working (/etc/postfix/main.cf looks fine, as before, and postfix was restarted). Mails to test(a)example.org rejected with Error 550 Recipient address rejected: User unknown in local recipient table /* as in your installation guide */ transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains The files appears to be present: /var/lib/mailman3/data# dir 4 -rw-rw---- 1 mailman mailman 339 Oct 20 21:13 postfix_domains 8 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_domains.db 4 -rw-rw---- 1 mailman mailman 2714 Oct 20 21:13 postfix_lmtp 12 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_lmtp.db What else is needed to get the list-addresses working and not rejected? It worked before the import.

1 3

Memory issues on a small server with 2 GB RAM - Question: Has anyone a similar server up and running with mailman3 ?
by Wikinaut 20 Oct '23

20 Oct '23

I see that about every 15 minutes (or later), tasks are killed by the systems OOM-Killer (out-of-memory). Is there something wrong with the current Tom Sawyer version, or is this specific server's memory size too low? Remark: I already reduced the mariadb innodb-buffer pool to ~100 MB (because mariadb got killed now and then before this change). Now it is our lovely mailman3 which got killed as the program with the largest memory footprint... Any idea?

1 1

Mailman Core 3.3.9 Release
by Abhilash Raj 20 Oct '23

20 Oct '23

Hello Everyone, Mailman 3.3.9 is now published to PyPI! Thanks to everyone who helped make this release possible. Minimum supported Python version for this release is 3.9, we had to drop support for 3.7 & 3.8 due to incompatibilities with importlib-resources package. Maximum Python version supported right now is 3.11, we haven't yet added 3.12 to CI, so un-sure if there are any errors there. The full change log for the release can be found in the docs as usual: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… You can download the release via PyPI or via Gitlab Release: https://gitlab.com/mailman/mailman/-/releases/v3.3.9 For those of you who need to verify signatures for packages, PyPI doesn't allow publishing signatures anymore so I pushed them to Gitlab Releases along with a copy of the same tarball uploaded to PyPI. I'll be working on the release for the web components tomorrow. -- thanks, Abhilash Raj (maxking)

1 0

[Older bug, but still unsolved] When deleting one or more threads in an archive, django send error mails (based upon "Thread matching query does not exist")
by Wikinaut 20 Oct '23

20 Oct '23

I installed the venv version to scrutizine whether this old bug is still present (yes it is). How to reproduce: Delete one thread in via the archive - thread - view page. Remark: Thread is deleted as wanted. However, django complains via several (here: two) error mails: 1st mail: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/test(a)example.com/top-threads Internal Server Error: /archives/list/test(a)example.com/top-threads DoesNotExist at /archives/list/test(a)example.com/top-threads Thread matching query does not exist. ... 2nd mail: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/test(a)example.com/posted-to Internal Server Error: /archives/list/test(a)example.com/posted-to DoesNotExist at /archives/list/test(a)example.com/posted-to Thread matching query does not exist. ... I wish to fix this problem, how can I help, what can I do? Do you need the full error stack?

1 0

Mailman3 Development Related List?
by Thomas Ward 20 Oct '23

20 Oct '23

I have some technical questions around custom plugins for Mailman3, related to DB access, etc. within a specific custom plugin. Is there a dedicated list for that, or is this list proper for such questions? Namely, I'm searching for more information regarding existing interfaces, etc. that're exposed from different mailman.* python components and whether we can utilize those without having to implement extra psycopg2 instances/connectivity, etc. but don't want to bombard the users list with technical chatter unless it's intended to be used that way. Thomas

2 1

mailman3 and bookworm
by Servizio Informatico U.I.C.I. Sezione territoriale di Brescia 19 Oct '23

19 Oct '23

Hello, Have you experience in installation of mailman3-full on bookworm? I tried to install it but it returns many errors of python. Thank you -- Roberto Burceni Servizio informatico sezionale Tel. 0302209417 (lunedì e giovedì mattina dalle 9:00 alle 13:00, martedì emercoledì pomeriggio dalle 14:00 alle 18:00 E-mail: servizioinformatico(a)uicibrescia.it Sito web: https://www.uicibresci

3 2

Moving mm3 -> mm3 to different host
by Axel Rau 19 Oct '23

19 Oct '23

Hi all, There are lots of threads for mm2 -> mm3 moves, but only one thread mm3 -> mm3. Some time ago, I found a post from Mark, explaining the steps, but I can't find it again. I have created a working mm3 installation on the new host with both mailman and mail-web dbs imported. hyperkitty archive seems to in the db. What are the next steps to complete the transfer? - rsyncing messages, lists and templates to new host - Setting up DNS CNAMES to the new server - Adapting exim to accept mails to the aliased domain - Can I keep the old listname, with the old domain name? -What else has to be done ? Thanks, Axel -- --- PGP-Key: CDE74120 ☀ mobile: +49 160 7568212 computing @ chaos claudius

2 1

Unusual behavior: Standard discussion lists with prefix are sometimes having prefix *dropped*
by Thomas Ward 19 Oct '23

19 Oct '23

I noticed some unusual behavior in Mailman3 stable release on PyPI and such. Namely, there are instances where replies are being processed and the prefix tags are simply being **lost** and dropped by Mailman3, instead of being properly prepended where they're supposed to go. Is this a known bug or does it need its own bug in the gitlab tracker? Thomas

2 2

Thread IDs on messages incrementing per reply?
by Thomas Ward 19 Oct '23

19 Oct '23

Trying to use the thread prefix component to *tag* thread IDs in a system, but not increment per message. It looks like replies are being received and then thread prefixes are getting incremented. "[Test-%07d]" is the prefix I"m using on a given test list, but we want it to increment by thread ID and *not* per message. (6 messages for instance have been sent, two were replies to [Test-0000004] and though the system properly archived it in the same conversation, it still incremented the digit counter). Is there a way to achieve this in Mailman3 without me having to write some kind of custom code for this? Thomas

2 5

Rootkit issues
by Kyriakos Terzopoulos 18 Oct '23

18 Oct '23

Hi, After installing mailman and using it for a few days, I got several complaints from my hosting company for abuse. After checking the server, it seems that there is a rootkit (Blitz) running with the mailman process. Has anyone come across this issue? Are there any specific steps to secure the mailman user? Thank you *Kyriakos Terzopoulos *Web developer / e-learning expert *Tel:*+30 211 213 9858 *Mobile:* +30 694 526 4512 * E-mail: *kyriakos.terzopoulos(a)gmail.com * Skype:* kyriakos.terzopoulos Find me on Facebook <http://www.facebook.com/cirrus3d> Follow me on Twitter <http://twitter.com/#%21/cirrus3d>

6 9

Simple ubi8/mailman3 container image
by Jered Floyd 17 Oct '23

17 Oct '23

Abhilash maintains a very complete and well-documented container deployment for Mailman 3, but when I was setting up my environment a few months ago I wanted to build on top of RHEL 8 as well as use a database instance shared across multiple applications. So I ended up creating a bare-bones container image that suited my needs and was closer to just doing a simple local install, but keeping the isolation, reproducibility, and rollback benefits of running as a container. I've been meaning to polish it up and share in case it is useful to others, but finally recognizing that I likely won't get to that soon I've just put it on GitHub here: [ https://github.com/jeredfloyd/mailman-container | https://github.com/jeredfloyd/mailman-container ] Doing a "podman build" of this should result in a container image that is very much like the result of doing a venv install. This uses the Red Hat Universal Base Image (UBI), which can be freely redistributed, gets upstream security updates, and is eligible for support on a paid RHEL subscription. --Jered

1 0

ATT00001.txt file in Outlook users
by pau.baiges＠csuc.cat 17 Oct '23

17 Oct '23

Hello, Users who have Outlook receive an attached txt file with the name ATT00001.txt when they receive an email from a mailman3 list. Is there a way to stop it from sending this file? Thank you so much

2 1

Post installation issues (recipients refused) with Exim4 in a virtual host environment
by Kyriakos Terzopoulos 17 Oct '23

17 Oct '23

Hi, I have set up (I believe successfully) and configured the following in a Virtualhost environment (with HestiaCP): - A record for lists.mydomain.com - Venv - Mailman core - Mailman web (run migrate, collectstatic, compress, compilemessages) Postorius - gunicorn, hyperkitty - Nginx - SMTP exim4 conf I can see Posrorius and I have logged in and created my first mailing list: [image: Screenshot 2023-10-11 at 10.57.31 AM.png] My issue is that even though I have subscribed to my list as you can see above, I am not receiving the confirmation email. I get a "recipients refused" error. The smtp log for mailman is as follows: Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> recipients refused: {' kyriakos.terzopoulos(a)gmail.com': (550, b'Verification failed for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu>\nUnrouteable address\nSender verify failed')} Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> smtp to testlist(a)myproject.eu for 1 recips, completed in 0.26796579360961914 seconds Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> post to testlist(a)myproject.eu from testlist-confirm+c9b20c5290bec43147a7e96a6b8cd825daf913d7(a)myproject.eu, 1667 bytes, 1 failures Oct 11 10:41:20 2023 (1533666) <169701007904.1534165.14569329382406660776@localhost> delivery to kyriakos.terzopoulos(a)gmail.com failed with code 550, b'Verification failed for <testlist-bounces+kyriakos.terzopoulos=gmail.com(a)myproject.eu>\nUnrouteable address\nSender verify failed' I have used the configuration for exim that is here <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…> and I have also tested with the alternative approach that is documented in there. ------ Debug info follows: First, here is my installation directory: [image: image.png] The following are the services that are running successfully (albeit with some warnings): ------ *Mailman:* ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-10-05 12:32:08 EEST; 28min ago Process: 1563357 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Main PID: 1563364 (python3) Tasks: 18 (limit: 9255) Memory: 929.7M CPU: 22.818s CGroup: /system.slice/mailman3.service ├─1563364 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/master -C /etc/mailman3/mailman.cfg ├─1563370 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=archive:0:1 ├─1563371 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=bounces:0:1 ├─1563372 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=command:0:1 ├─1563373 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=in:0:1 ├─1563374 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=lmtp:0:1 ├─1563375 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=nntp:0:1 ├─1563376 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=out:0:1 ├─1563377 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=pipeline:0:1 ├─1563378 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 ├─1563379 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=retry:0:1 ├─1563380 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=task:0:1 ├─1563381 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 ├─1563382 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=digest:0:1 ├─1563420 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 └─1563421 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=rest:0:1 Oct 05 12:32:07 hestia. mydomain.eu systemd[1]: Starting GNU Mailing List Manager... Oct 05 12:32:08 hestia. mydomain.eu mailman[1563357]: Starting Mailman's master runner Oct 05 12:32:08 hestia. mydomain.eu mailman[1563357]: Generating MTA alias maps Oct 05 12:32:08 hestia. mydomain.eu systemd[1]: *mailman3.service: Can't open PID file /opt/mailman/venv/master.pid (yet?) after start: Ope*> Oct 05 12:32:08 hestia. mydomain.eu systemd[1]: Started GNU Mailing List Manager. *Note the above warning for the master.pid file. However the file exists and is writeable* ------ *Mailman web service* ● mailmanweb.service - GNU Mailman Web UI Loaded: loaded (/etc/systemd/system/mailmanweb.service; disabled; vendor preset: enabled) Active: active (running) since Thu 2023-10-05 12:51:46 EEST; 9min ago Main PID: 1578503 (gunicorn) Tasks: 2 (limit: 9255) Memory: 67.2M CPU: 753ms CGroup: /system.slice/mailmanweb.service ├─1578503 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application └─1578505 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/gunicorn -c /etc/mailman3/gunicorn.conf mailman_web.wsgi:application Oct 05 12:51:46 hestia.mydomain.eu systemd[1]: Started GNU Mailman Web UI. Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! *WARNING: configuration file should have a valid Python extension*. Oct 05 12:51:46 hestia. mydomain.eu gunicorn[1578503]: !!! *Another warning above, however the service is starting normally.* ------ *Django Qcluster* ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; disabled; vendor preset: enabled) Active: active (running) since Thu 2023-10-05 12:51:40 EEST; 10min ago Main PID: 1578463 (mailman-web) Tasks: 8 (limit: 9255) Memory: 101.2M CPU: 30.915s CGroup: /system.slice/qcluster.service ├─1578463 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578465 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578466 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578467 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578468 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578469 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings ├─1578470 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings └─1578471 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/mailman-web qcluster --pythonpath /etc/mailman3 --settings settings Oct 05 12:51:40 hestia. mydomain.eu systemd[1]: Started HyperKitty async tasks runner. Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578463]: 09:51:40 [Q] INFO Q Cluster washington-solar-muppet-alanine starting. Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578466]: 09:51:40 [Q] INFO Process-1:1 ready for work at 1578466 Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578467]: 09:51:40 [Q] INFO Process-1:2 ready for work at 1578467 Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578468]: 09:51:40 [Q] INFO Process-1:3 ready for work at 1578468 Oct 05 12:51:40 hestia. mydomain.eu mailman-web[1578469]: 09:51:40 [Q] INFO Process-1:4 ready for work at 1578469 Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578470]: 09:51:41 [Q] INFO Process-1:5 monitoring at 1578470 Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578465]: 09:51:41 [Q] INFO Process-1 guarding cluster washington-solar-muppet-alanine Oct 05 12:51:41 hestia. mydomain.eu mailman-web[1578465]: 09:51:41 [Q] INFO Q Cluster washington-solar-muppet-alanine running. Oct 05 12:51:41 hestia.mydomain.eu mailman-web[1578471]: 09:51:41 [Q] INFO Process-1:6 pushing tasks at 1578471 ------ Nginx (hestia CP virtual hosts) server { listen 1.2.3.4:80; server_name lists.mydomain <http://lists.mydomain.com>.eu; location /static/ { alias /opt/mailman/venv/web/static/; } location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } ------ Happy to share my other mailman or EXIM4 configuration files if needed. Thanks in advance. Kyriakos ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image.png Content-Type: image/png Name: =?UTF-8?B?U2NyZWVuc2hvdCAyMDIzLTEwLTExIGF0IDEwLjU3LjMx4oCvQU0ucG5n?= Replaced multipart/alternative part with first alternative.

3 8

Setting up on ubuntu server 22.04
by Kyriakos Terzopoulos 15 Oct '23

15 Oct '23

Hi guys, I have an Ubuntu 22.04 server running on a Hetzner machine, with HestiaCP (Exim4) on it. I cannot for the life of me start the service of mailman3 core. Following the installation tutorial I have tried with the venv approach and I am having the following issues: 1) It is not clear to me whether the mailman configuration should be outside venv (and outside the mailman shell). 2) For the above reason I have created a config file: /etc/mailman3/mailman.cfg and the mailman3 service outside venv. When starting the service I get the following: ImportError: cannot import name 'path' from 'importlib_resources' (/opt/mailman/venv/lib/python3.10/site-packages/importlib_resources/__init__.py) I've set up the database, the mailman user and the virtual environment. I know I am missing something here (e.g. Python version? other dependencies?). In general would it be better or/and easier to set this up on a new machine in my Hetzner cloud e.g. on Debian which seems to have packages of mailman available? Thanks in advance for all your help. Kyriakos

5 12

Memory usage cgroup and free -m
by golden_rock＠hotmail.com 12 Oct '23

12 Oct '23

Hi, Currently the mailman3 cgroup slice uses up to 875MB: Control Group Tasks %CPU Memory Input/s Output/s system.slice/mailman3.service 16 0.1 875.3M - - Is 875MB a normal expected amount, or more than expected? To confirm that this is truly used and not "cached", I use the new Available column from the "free -m" output, which is the pre-computed available memory for a new process, added in recent years. The output of free -m under the Available column when mailman3 is running is : 161 MB When I stop the mailman service, the output of free -m Available column goes up to: 1071 MB Showing that the 875MB previously were not available for release for new processes. If I start mailman service again, the output of free -m Available column goes back to : 325MB and will be reducing gradually over time. I looked around on posts, documentation and others, but didn't find guides related to reducing RAM usage, is that a possibility or is this memory usage expected?

2 1

Archive search failing on one list
by Mark 12 Oct '23

12 Oct '23

Hi, I have several lists all happily running with private archives. They all use the one domain name. A new list was added recently and although mail delivery and archiving are fine, this new list's search function is failing. For example, on searching for the word "Derbyshire" (which is mentioned in one of the archived messages) the results page displays: "Sorry no email could be found for this query." The logs show: +++++++++++++++++++++++++++++++++++++ /var/log/mailman3/web/mailman-web.log +++++++++++++++++++++++++++++++++++++ [pid: 1156|app: 0|req: 55/55] 2001:8004:5310:2405:ce66:5ff:41fc:60db () {76 vars in 1537 bytes} [Sat Sep 23 23:57:43 2023] GET /mailman3/hyperkitty/search?mlist=LISTNAME-1%40DOMAIN.COM&q=Derbyshire => generated 13752 bytes in 3188 msecs (HTTP/1.1 200) 5 headers in 164 bytes (1 switches on core 0) 23:57:51 [Q] INFO Process-1:1 processing [rebuild_mailinglist_cache_for_month] 23:57:51 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_recent] 23:57:51 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month mlist = MailingList.objects.get(name=mlist_name) File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get raise self.model.DoesNotExist( hyperkitty.models.mailinglist.MailingList.DoesNotExist: MailingList matching query does not exist. +++++++++++++++++++++++++++++++++++++ On all the other lists, which all have successful search results, the logs shows examples like so (searching for "Farnborough") ... ************************************* [pid: 1156|app: 0|req: 486/486] 2001:8004:5310:2405:ce66:5ff:41fc:60db () {76 vars in 1531 bytes} [Sun Sep 24 00:38:24 2023] GET /mailman3/hyperkitty/search?mlist=LISTNAME-2%40DOMAIN.COM&q=Farnborough => generated 141638 bytes in 11039 msecs (HTTP/1.1 200) 6 headers in 333 bytes (1 switches on core 0) ************************************* ... which seems to be pretty much the same but with out the "MailingList.DoesNotExist" error. Any clues on where I should be looking to fix this would be gratefully received. Thanks, Mar

3 9

impossible to administrate *.com emails
by testeur 10 Oct '23

10 Oct '23

Hi, I don't understand why this problem ! In the web interface, i can't administrate email finishing with ".com" (ex : gmail.com, hotmail.com, etc) I obtain : "Forbidden You don't have permission to access this resource." did i miss something in the web configuration ? Regards, PG testeur

2 2

Alias for a list name
by Lars Bjørndal 08 Oct '23

08 Oct '23

I've migrated a list from mm 21 to mm 3 sucessfully. The mm 21 runs on domains managed by Postfix as virtual alias domains. That way it was possible to alias a shorter name for a list to the list name. To run mm 3 through Postfix, I use local_recipient_maps and transport_maps. What I want to achieve, is alias medlem(a)list.saf-org.no to saf-medlem(a)list.saf-org.no I tried to put medlem(a)list.saf-org.no: saf-medlem(a)list.saf-org.no and get the following error when running newaliases: postalias: warning: /etc/aliases, line 231: name must be local Is it possible to do this aliasing in a simple way? Thanks, Lars

2 6

OIDC (was: username)
by Jörg Schulz 07 Oct '23

07 Oct '23

The most recent version of Django-allauth has some nice changes, it's now straightforward to include oidc. Just include SOCIALACCOUNT_EMAIL_AUTHENTICATION=True ## This allows existing users to login MAILMAN_WEB_SOCIAL_AUTH = [ "allauth.socialaccount.providers.openid_connect"] in settings.py and use the Django admin to configure the socialauth.... While it is _possible_ to add things like ---- SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "mm3", "name": "TheNameThat shows up in the button", "client_id": "configuredID", "secret": "yourOIDCproviderGivesItToYou", "settings": { "server_url": "https://keycloak.wherever.com/realms/yourRealm/.well-known/openid-configura…", "token_auth_method": "client_secret_basic", }, } ] } } ---- I think it's preferable to do that within the Django Admin Gui. Does anybody dare to include this info in the documentation, or are we afraid the next django_allauth breaks things again (this time: Keycloak has been replaced by openid_connect)? -------- Weitergeleitete Nachricht -------- Betreff: Re: [MM3-users] Re: username Datum: Wed, 13 Sep 2023 07:34:35 +0000 Von: info(a)joergschulz.de An: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Hi, probably you are looking for https://django-allauth.readthedocs.io/en/latest/index.html and https://github.com/lokeish/django-all-auth-and-keycloak-integration but https://github.com/pennersr/django-allauth/commit/ab704687f438c06fd23e72bce… will be helpful once implemented. Am 12. September 2023 um 05:54 schrieb "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp <mailto:turnbull.stephen.fw@u.tsukuba.ac.jp?to=%22Stephen%20J.%20Turnbull%22%20%3Cturnbull.stephen.fw%40u.tsukuba.ac.jp%3E>>: bryan.kartzman(a)yu.edu writes: > Just to let you know, there is a maintained SAML2 plugin available > on github (https://github.com/grafana/django-saml2-auth) that I was > able to install and get to work with AZURE SSO. There are multiple ways to solve this problem. My employer wanted a host-wide solution so they chose Shibboleth. Some day I'll go out and collect the ones I can find and document them (in summary form: source site, recency of stable version, recency of maintenance, etc). Steve

1 0

username
by bryan.kartzman＠yu.edu 06 Oct '23

06 Oct '23

Where is the username that a user uses to login on the postorius web page stored? I checked the postgres table public.user and while the display name is there, the username is not. I can't find it anywhere in the database.

3 9

Mailman issues after re-boot
by Paul Rubin 06 Oct '23

06 Oct '23

*<>* After a lengthy power failure I had to reboot a machine that has been running for several years. the WEB-UI does not seem to be able to see mailman-core. I have looked for log entries that might explain what the issue is and I am stumped to even find logs that will update when I get an error on the browser. Mailman is definitely running, postgres is running and mailman web is running. if I go to the lists page I see lists, if I try to access a specific list I get Server error: An error occurred while processing your request. I looked in /var/logs/mailman /opt/mailman/web/mailmanweb All I can find is: django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name.16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/goodstein.goodstein.org/ File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in <module> from django.utils.translation import ungettextImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/__init__.py) Also I have to run mailman from "mailman start" because the systemctl returns this: ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2023-09-12 10:06:31 EDT; 13s ago Process: 31159 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=1/FAILURE) CPU: 806msSep 12 10:06:31 mail mailman[31159]: Error in atexit._run_exitfuncs:Sep 12 10:06:31 mail mailman[31159]: Traceback (most recent call last):Sep 12 10:06:31 mail mailman[31159]: File "/usr/lib64/python3.8/logging/__init__.py", line 2126, in shutdownSep 12 10:06:31 mail mailman[31159]: h.flush()Sep 12 10:06:31 mail mailman[31159]: File "/opt/mailman/venv/lib64/python3.8/site-packages/mailman/core/logging.py", line 67, in flushSep 12 10:06:31 mail mailman[31159]: if self._stream:Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream'Sep 12 10:06:31 mail systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURESep 12 10:06:31 mail systemd[1]: mailman3.service: Failed with result 'exit-code'.Sep 12 10:06:31 mail systemd[1]: Failed to start GNU Mailing List Manager. Please tell me where to start looking or adjusting. Reply from Mark Sapiro,* Edited to include responses:* Mark Sapiro <https://gitlab.com/msapiro>@msapiro <https://gitlab.com/msapiro>· 1 day ago <https://gitlab.com/mailman/mailman-web/-/issues/23#note_1557601916> Owner Add reaction More actions The mailman-users(a)mailman3.org list is probably a more appropriate place for issues like this. django.urls.exceptions.NoReverseMatch: Reverse for 'list_unsubscription_requests' not found. 'list_unsubscription_requests' is not a valid view function or pattern name. 16688 ERROR 2023-09-12 13:56:58,430 1760 django.request Internal Server Error: /mailman3/lists/ goodstein.goodstein.org/ /opt/mailman/venv/lib64/python3.8/site-packages/postorius/urls.py should contain re_path( r'^unsubscription_requests$', list_views.list_unsubscription_requests, name='list_unsubscription_requests', ), Y *Yes this exists* and /opt/mailman/venv/lib64/python3.8/site-packages/postorius/views/list.py should define list_unsubscription_requests. *Yes there is a method by this name defined* File "/opt/mailman/venv/lib64/python3.8/site-packages/haystack/admin.py", line 8, in from django.utils.translation import ungettext ImportError: cannot import name 'ungettext' from 'django.utils.translation' (/opt/mailman/venv/lib64/python3.8/site-packages/django/utils/translation/ *init*.py) See https://docs.djangoproject.com/en/4.2/internals/deprecation/#deprecation-re… - ungettext() is removed from django>=4.0 Sep 12 10:06:31 mail mailman[31159]: AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' I don't understand this one offhand, but what is the content of /etc/systemd/system/mailman3.service, in particular the settings for User, Group and ExecStart? *The service looks right:* 1 [Unit] 2 Description=GNU Mailing List Manager 3 After=syslog.target network.target postgresql.service 4 5 [Service] 6 Type=forking 7 PIDFile=/opt/mailman/mm/var/master.pid 8 User=mailman 9 Group=mailman 10 ExecStart=/opt/mailman/venv/bin/mailman start 11 ExecReload=/opt/mailman/venv/bin/mailman restart 12 ExecStop=/opt/mailman/venv/bin/mailman stop 13 14 [Install] 15 WantedBy=multi-user.target *It seems I may have two versions of the mailman script:* mail:/opt/mailman # which mailman /usr/bin/mailman mail:/opt/mailman # ls -al /usr/bin/mailman -rwxr-xr-x 1 root root 382 May 10 2021 /usr/bin/mailman mail:/opt/mailman # ls -al /opt/mailman/venv/bin/mailman -rwxr-xr-x 1 mailman mailman 231 Sep 12 10:02 /opt/mailman/venv/bin/mailman Somehow, your installation is corrupted. I don't know how *I need to know what to remove, how to correctly update, etc., That said the two scripts appear to be very similar:* mail:/opt/mailman # head /usr/bin/mailman #!/usr/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' __requires__ = 'mailman==3.3.4' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( mail:/opt/mailman # head /opt/mailman/venv/bin/mailman #!/opt/mailman/venv/bin/python3 # -*- coding: utf-8 -*- import re import sys from mailman.bin.mailman import main if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) sys.exit(main()) mail:/opt/mailman # *Given the two years since the last reboot I also tried following * https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was running the latest* pip install -U mailman postorius django-mailman3 hyperkitty mailman-web

6 31

Missing Base64 encoding from control message reply
by lists-mailman3＠janaberger.de 06 Oct '23

06 Oct '23

Dear all, I have a setup with GNU Mailman 3.3.8 where a user tried to subscribe. When replying to the "confirm" message, the user received a completely garbled response, like so: N�z˥��ʋ�zf��&��j��u�[zZ0:��v��,j�z֢��k�e�0 4Dҹ��r�^b��r�ߊ��*'��yם��{ax�L�X��0:��v��,j�z֢��k�d�m�-��zz�rn��l]y+��-E�( �^N��'��M��tۯ��Mz��^i��׮��}�o�\ӷ��6sN�zf��ݮ��r��z˥��b�{h��݉��f�r�ne== (The line above contains numerous unprintable characters, etc.) The user then forwarded the .eml file to me, which clearly shows the contents of the mail as plain text while being announced as base64 (Content-Transfer-Encoding: base64): START OF EML Return-Path: <LISTNAME-bounces(a)lists.DOMAIN.COM> Received: from DOMAIN.COM ([144.76.173.241]) by mx-ha.USERDOMAIN.NET (mx06 [IP]) with ESMTPS (Nemesis) id 1M27WV-1qhRFk39Sr-00AQcR for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:37 +0200 Received: from localhost (localhost.localdomain [127.0.0.1]) by DOMAIN.COM (Postfix) with ESMTP id 4058B3BD5EEF for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:37 +0200 (CEST) Received: from DOMAIN.COM ([127.0.0.1]) by localhost (DOMAIN.COM [127.0.0.1]) (amavis, port 10024) with ESMTP id x0ngnlRnGraH for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:37 +0200 (CEST) Received: from [IP] (unknown [IP]) by DOMAIN.COM (Postfix) with ESMTP id DC8603BD5EEE for <USER(a)USERDOMAIN.NET>; Thu, 21 Sep 2023 19:10:36 +0200 (CEST) Subject: =?utf-8?q?The_results_of_your_email_commands?= From: LISTNAME-bounces(a)lists.DOMAIN.COM To: USER(a)USERDOMAIN.NET Content-Transfer-Encoding: base64 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-ID: <169531623416.29.5762261018677554285@mailman-core> Date: Thu, 21 Sep 2023 17:10:34 +0000 Precedence: bulk X-Mailman-Version: 3.3.8 List-Id: <LISTNAME.lists.DOMAIN.COM> List-Help: <mailto:LISTNAME-request@lists.DOMAIN.COM?subject=help> List-Owner: <mailto:LISTNAME-owner@lists.DOMAIN.COM> List-Subscribe: <mailto:LISTNAME-join@lists.DOMAIN.COM> List-Unsubscribe: <mailto:LISTNAME-leave@lists.DOMAIN.COM> Envelope-To: <USER(a)USERDOMAIN.NET> X-Spam-Flag: NO The results of your email command are provided below. - Original message details: From: USER <USER(a)USERDOMAIN.NET> Subject: Re: Your confirmation is needed to join the LISTNAME(a)lists.DOMAIN.COM mailing list. Date: Thu, 21 Sep 2023 19:10:26 +0200 Message-ID: <3c1eaaf8-1677-432f-b9dc-07f18902c06c(a)email.android.com> - Results: Confirmation token did not match - Done. END OF EML Is this possibly a bug in Mailman? Any ideas on what else could be causing this?

4 12

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

Templates via Webinterface are i) not set, and ii) set templates (files) are not shown in the Webinterface
by Wikinaut 30 Sep '23

30 Sep '23

I use mailman3 since a while, for some of my lists I have been using - list:member:digest:footer.txt - list:member:regular:footer.txt When I go to "Vorlagen" (LC: DE) (templates) in the web interface, I do _not_ see these two templates! When I got o my newest mailing list and when I setup templates via the Webinterfaces, these are shown there, but are neither working nor seen as files. What's wrong here? Is that a problem of the localisation language (DE)? Bug, feature or misunderstanding of myself?

2 2

Is there a way of recording bounce messages?
by Andrew Hodgson 28 Sep '23

28 Sep '23

Hi. I recently had an incident of all gmail.com members being bounced off one email list (around 180 subscribers). The messages recording the bounce don't include the original DSN. Is there a way of getting the DSN recorded? I'm sure it will give me some nonsense Gmail refusal message but I would like to identify if messages are bouncing for specific users, or if I am harming my reputation by sending to disabled accounts etc. Thanks. Andrew.

5 17

Mailing list name with capital letters?
by mrl＠psfc.mit.edu 26 Sep '23

26 Sep '23

How can I create a mailing list with capital letters? Right now, only the first letter can be capitalized. Some of my mailing list names in mailman 2 had capital letters. When I migrated them to mailman 3, the capital letters remained. So it should be possible to create new ones? Thanks. - Mark

3 3

Mailman 3 - Header Filter
by Thomas Lehker 25 Sep '23

25 Sep '23

I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. Header: ^subject: subject: subject Pattern: Automatic Reply 'Automatic Reply' "Automatic Reply" Action: Discard DISCLAIMER: The information contained in this message is privileged and confidential. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please reply to the message and delete/destroy any copy of this message. Information in this message that does not relate to the official business of the firm shall be understood as neither given nor endorsed by it.

4 4

Issues with @gmail.com addresses
by Mohsen Masoudfar 25 Sep '23

25 Sep '23

Hi, since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. I checked the logs and I see that the emails are going out: to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) But it seems the users are getting email delivered to them. I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. Is there any way to help this list members? Thanks

8 21

Strange password problem
by Eggert Ehmke 25 Sep '23

25 Sep '23

This happened several times recently with Postorius Version 1.3.8: -I try to log in as admin -rejected because of wrong password (password is stored in browser) -used forgotten password function -reset password to the stored value from browser -login works now. Works also when logged out/in again -however, the next day this behaviour repeats. Any hints?

6 22

how to administrate mailman3 in CLI ?
by testeur 23 Sep '23

23 Sep '23

Hello, I have installed mailman3 and i want to administrate it with rest api, i ve read https://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usi… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… i tryied with mailman command, but it don't do some actions (eg. delete held messages...). i tryied mailman shell... i tryied with curl to manage it, i can see if there is a pending message with : curl --user restadmin:restpass http://localhost:8001/3.1/lists/ml@domain.tld/held/count|| python3 -m json.tool| but how to delete all held messages ? is it possible in one time ? And how to select a specific message to discard /accept / defer ? do i have to use a POST ? Regards, PatG

3 4

Message getting held due to max number of recipients and maximum message size
by Wong, Wesley 22 Sep '23

22 Sep '23

Hi all, I am running into an issue with messages getting held for a list with the following reasons: The message is being held because: Message has more than 10 recipients The message is larger than the 40 KB maximum size Either the message will get posted to the list, or you will receive notification of the moderator's decision. Currently, the settings are set to 0 for both settings on the list so I am not sure where mailman is getting the default settings. Is this default hard coded somewhere in the Mailman core? The version of Mailman running is 3.3.6. Any help for this issue is greatly appreciate. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 3

Hyperkitty
by Massimiliano Paragnani 21 Sep '23

21 Sep '23

I set up the mailman3 services and lists, and we can send mail to the list successfully. However in the Archive section I couldn't see anything. My configuration: ubuntu, milman core 3.2.2, postresql, postorius 1.2.4, hyperkitty 1.3.2 This is my mailman conf result: [antispam] header_checks: [antispam] jump_chain: hold [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: no [bounces] register_bounces_every: 15m [database] class: mailman.database.postgresql.PostgreSQLDatabase [database] debug: no [database] url: postgres://mailman3:--------------@localhost/mailman3 [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s [digests] mime_digest_keep_headers: Date From To Cc Subject Message-ID Keywords In-Reply-To References Content-Type MIME-Version Content-Transfer-Encoding Precedence Reply-To Message List-Post [digests] plain_digest_keep_headers: Message Date From Subject To Cc Message-ID Keywords Content-Type [dmarc] cache_lifetime: 7d [dmarc] org_domain_data_url: https://publicsuffix.org/list/public_suffix_list.dat [dmarc] resolver_lifetime: 5s [dmarc] resolver_timeout: 3s [language.ar] charset: utf-8 [language.ar] description: Arabic [language.ar] enabled: yes [language.ast] charset: iso-8859-1 [language.ast] description: Asturian [language.ast] enabled: yes [language.ca] charset: utf-8 [language.ca] description: Catalan [language.ca] enabled: yes [language.cs] charset: iso-8859-2 [language.cs] description: Czech [language.cs] enabled: yes [language.da] charset: iso-8859-1 [language.da] description: Danish [language.da] enabled: yes [language.de] charset: utf-8 [language.de] description: German [language.de] enabled: yes [language.el] charset: iso-8859-7 [language.el] description: Greek [language.el] enabled: yes [language.es] charset: iso-8859-1 [language.es] description: Spanish [language.es] enabled: yes [language.et] charset: iso-8859-15 [language.et] description: Estonian [language.et] enabled: yes [language.eu] charset: iso-8859-15 [language.eu] description: Euskara [language.eu] enabled: yes [language.fi] charset: iso-8859-1 [language.fi] description: Finnish [language.fi] enabled: yes [language.fr] charset: iso-8859-1 [language.fr] description: French [language.fr] enabled: yes [language.gl] charset: utf-8 [language.gl] description: Galician [language.gl] enabled: yes [language.he] charset: utf-8 [language.he] description: Hebrew [language.he] enabled: yes [language.hr] charset: iso-8859-2 [language.hr] description: Croatian [language.hr] enabled: yes [language.hu] charset: iso-8859-2 [language.hu] description: Hungarian [language.hu] enabled: yes [language.ia] charset: iso-8859-15 [language.ia] description: Interlingua [language.ia] enabled: yes [language.it] charset: iso-8859-1 [language.it] description: Italian [language.it] enabled: yes [language.ja] charset: euc-jp [language.ja] description: Japanese [language.ja] enabled: yes [language.ko] charset: euc-kr [language.ko] description: Korean [language.ko] enabled: yes [language.lt] charset: iso-8859-13 [language.lt] description: Lithuanian [language.lt] enabled: yes [language.nl] charset: iso-8859-1 [language.nl] description: Dutch [language.nl] enabled: yes [language.no] charset: iso-8859-1 [language.no] description: Norwegian [language.no] enabled: yes [language.pl] charset: iso-8859-2 [language.pl] description: Polish [language.pl] enabled: yes [language.pt] charset: iso-8859-1 [language.pt] description: Protuguese [language.pt] enabled: yes [language.pt_BR] charset: iso-8859-1 [language.pt_BR] description: Protuguese (Brazil) [language.pt_BR] enabled: yes [language.ro] charset: iso-8859-2 [language.ro] description: Romanian [language.ro] enabled: yes [language.ru] charset: koi8-r [language.ru] description: Russian [language.ru] enabled: yes [language.sk] charset: utf-8 [language.sk] description: Slovak [language.sk] enabled: yes [language.sl] charset: iso-8859-2 [language.sl] description: Slovenian [language.sl] enabled: yes [language.sr] charset: utf-8 [language.sr] description: Serbian [language.sr] enabled: yes [language.sv] charset: iso-8859-1 [language.sv] description: Swedish [language.sv] enabled: yes [language.tr] charset: iso-8859-9 [language.tr] description: Turkish [language.tr] enabled: yes [language.uk] charset: utf-8 [language.uk] description: Ukrainian [language.uk] enabled: yes [language.vi] charset: utf-8 [language.vi] description: Vietnamese [language.vi] enabled: yes [language.zh_CN] charset: utf-8 [language.zh_CN] description: Chinese [language.zh_CN] enabled: yes [language.zh_TW] charset: utf-8 [language.zh_TW] description: Chinese (Taiwan) [language.zh_TW] enabled: yes [logging.archiver] datefmt: %b %d %H:%M:%S %Y [logging.archiver] format: %(asctime)s (%(process)d) %(message)s [logging.archiver] level: info [logging.archiver] path: mailman.log [logging.archiver] propagate: no [logging.bounce] datefmt: %b %d %H:%M:%S %Y [logging.bounce] format: %(asctime)s (%(process)d) %(message)s [logging.bounce] level: info [logging.bounce] path: bounce.log [logging.bounce] propagate: no [logging.config] datefmt: %b %d %H:%M:%S %Y [logging.config] format: %(asctime)s (%(process)d) %(message)s [logging.config] level: info [logging.config] path: mailman.log [logging.config] propagate: no [logging.database] datefmt: %b %d %H:%M:%S %Y [logging.database] format: %(asctime)s (%(process)d) %(message)s [logging.database] level: warn [logging.database] path: mailman.log [logging.database] propagate: no [logging.debug] datefmt: %b %d %H:%M:%S %Y [logging.debug] format: %(asctime)s (%(process)d) %(message)s [logging.debug] level: info [logging.debug] path: debug.log [logging.debug] propagate: no [logging.error] datefmt: %b %d %H:%M:%S %Y [logging.error] format: %(asctime)s (%(process)d) %(message)s [logging.error] level: info [logging.error] path: mailman.log [logging.error] propagate: no [logging.fromusenet] datefmt: %b %d %H:%M:%S %Y [logging.fromusenet] format: %(asctime)s (%(process)d) %(message)s [logging.fromusenet] level: info [logging.fromusenet] path: mailman.log [logging.fromusenet] propagate: no [logging.http] datefmt: %b %d %H:%M:%S %Y [logging.http] format: %(asctime)s (%(process)d) %(message)s [logging.http] level: info [logging.http] path: mailman.log [logging.http] propagate: no [logging.locks] datefmt: %b %d %H:%M:%S %Y [logging.locks] format: %(asctime)s (%(process)d) %(message)s [logging.locks] level: info [logging.locks] path: mailman.log [logging.locks] propagate: no [logging.mischief] datefmt: %b %d %H:%M:%S %Y [logging.mischief] format: %(asctime)s (%(process)d) %(message)s [logging.mischief] level: info [logging.mischief] path: mailman.log [logging.mischief] propagate: no [logging.plugins] datefmt: %b %d %H:%M:%S %Y [logging.plugins] format: %(asctime)s (%(process)d) %(message)s [logging.plugins] level: info [logging.plugins] path: plugins.log [logging.plugins] propagate: no [logging.root] datefmt: %b %d %H:%M:%S %Y [logging.root] format: %(asctime)s (%(process)d) %(message)s [logging.root] level: info [logging.root] path: mailman.log [logging.root] propagate: no [logging.runner] datefmt: %b %d %H:%M:%S %Y [logging.runner] format: %(asctime)s (%(process)d) %(message)s [logging.runner] level: info [logging.runner] path: mailman.log [logging.runner] propagate: no [logging.smtp] datefmt: %b %d %H:%M:%S %Y [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg [logging.smtp] format: %(asctime)s (%(process)d) %(message)s [logging.smtp] level: info [logging.smtp] path: smtp.log [logging.smtp] propagate: no [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures [logging.smtp] success: $msgid post to $listname from $sender, $size bytes [logging.subscribe] datefmt: %b %d %H:%M:%S %Y [logging.subscribe] format: %(asctime)s (%(process)d) %(message)s [logging.subscribe] level: info [logging.subscribe] path: mailman.log [logging.subscribe] propagate: no [logging.vette] datefmt: %b %d %H:%M:%S %Y [logging.vette] format: %(asctime)s (%(process)d) %(message)s [logging.vette] level: info [logging.vette] path: mailman.log [logging.vette] propagate: no [mailman] cache_life: 7d [mailman] default_language: en [mailman] email_commands_max_lines: 10 [mailman] filtered_messages_are_preservable: no [mailman] html_to_plain_text_command: /usr/bin/lynx -dump $filename [mailman] layout: debian [mailman] listname_chars: [-_.0-9a-z] [mailman] noreply_address: noreply [mailman] pending_request_life: 3d [mailman] post_hook: [mailman] pre_hook: [mailman] sender_headers: from from_ reply-to sender [mailman] site_owner: max.paragnani(a)gmail.com [mta] configuration: python:mailman.config.postfix [mta] delivery_retry_period: 5d [mta] incoming: mailman.mta.postfix.LMTP [mta] lmtp_host: 127.0.0.1 [mta] lmtp_port: 8024 [mta] max_autoresponses_per_day: 10 [mta] max_delivery_threads: 0 [mta] max_recipients: 500 [mta] max_sessions_per_connection: 0 [mta] outgoing: mailman.mta.deliver.deliver [mta] remove_dkim_headers: no [mta] smtp_host: localhost [mta] smtp_pass: [mta] smtp_port: 25 [mta] smtp_user: [mta] verp_confirm_format: $address+$cookie [mta] verp_confirm_regexp: ^(.*<)?(?P<addr>[^+]+?)\+(?P<cookie>[^@]+)@.*$ [mta] verp_confirmations: no [mta] verp_delimiter: + [mta] verp_delivery_interval: 0 [mta] verp_format: ${bounces}+${local}=${domain} [mta] verp_personalized_deliveries: no [mta] verp_probe_format: $bounces+$token@$domain [mta] verp_probe_regexp: ^(?P<bounces>[^+]+?)\+(?P<token>[^@]+)@.*$ [mta] verp_probes: no [mta] verp_regexp: ^(?P<bounces>[^+]+?)\+(?P<local>[^=]+)=(?P<domain>[^@]+)@.*$ [nntp] host: [nntp] password: [nntp] port: [nntp] remove_headers: nntp-posting-host nntp-posting-date x-trace x-complaints-to xref date-received posted posting-version relay-version received [nntp] rewrite_duplicate_headers: To X-Original-To CC X-Original-CC Content-Transfer-Encoding X-Original-Content-Transfer-Encoding MIME-Version X-MIME-Version [nntp] user: [passwords] configuration: python:mailman.config.passlib [passwords] password_length: 8 [plugin.master] class: [plugin.master] component_package: [plugin.master] configuration: [plugin.master] enabled: no [shell] banner: Welcome to the GNU Mailman shell [shell] history_file: [shell] prompt: >>> [shell] use_ipython: no [styles] default: legacy-default [webservice] admin_pass: --------------------------------- [webservice] admin_user: restadmin [webservice] api_version: 3.1 [webservice] hostname: localhost [webservice] port: 8001 [webservice] show_tracebacks: yes [webservice] use_https: no

7 20

Re: Importing mbox files into archive defect with lines with From
by Alex Schuilenburg 21 Sep '23

21 Sep '23

Hi Stephen On 19/09/2023 19:59, Stephen J. Turnbull wrote: > Did you intend to send this to me only? Nope, apologies. I'm happy to add the list back in - I thought I hit reply-to-list. > Alex Schuilenburg writes: > > > Yes, I retested with from the git head as well. Same result. It > > sees the line > > > > From 1st April 2019, our turnover has exceeded the threshold for > > > > as the start of a new message and reports no anomolies although > > there is clearly one. > > If there is an empty line preceding that one, and the "F" is in the > first column (no marginal whitespace), that is considered correct > behavior for processing an mbox file. As an email separator agreed, provided the body has all "First " (preceded by a blank line and nothing preceding on the same line) suitably escaped. > If you don't like it, don't use the mbox format. The maildir > message-per-file format is widely supported, and if you want a > folder-per-file rather than message-per-file format, MMDF is fairly > widely supported, and does not suffer from the ambiguities of mbox. > All three (with variations) are supported by recent Python 3. Understood. My issue is the lists were imported from MM2.1 in 2020 into MM3.2.1 onto hyperkitty+mariadb/mysql. So the current installation has no mbox files - archives are stored in a mysql database. > > The old MM3 installation I am migrating away from is obviously > > broken in that its mbox archive when downloaded is not escaped, > > That's interesting. I presume that's because HyperKitty saves > messages in a database rather than as mbox files, and the old mbox > exporter just flattened and concatenated the messages. Or perhaps > that also uses mailbox.mbox and old enough versions of that didn't > From-stuff. Spot on. I have to move the lists onto a new Debian 12 server using the native mailman 3.3.8 & mailman-web 0+20200530-2 packages. I tried dropping in the old mailman3 database under the new software but that did not work. Instead I manually imported the old mailman3 data directly into the new mailman3 database as, after inspections, there were no new tables and only a couple of additional fields which have suitable defaults. So dumped the mailman3 data with mysqldump --no-create-info --no-create-db --disable-keys --complete-insert --ignore-table=mailman3.alembic_version mailman3 and simply imported the dump into the new schema. OK so far. The lists showed up in postorius, obviously without archives in hyperkitty. > The normal way to upgrade a HyperKitty archive is to do nothing, just > upgrade the software. I guess you moved to a new host and deleted the > database? The preferred way is to dump the database to SQL, and then > load it in to the new database directly rather than downloading the > mbox files and importing. No ambiguity and much faster. Thats what I thought initially, but that failed as per https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…. As my old installation appears to have the django_migrations table inconsistent with the state of the database, and Debian have been unresponsive so far. Unfortunately the same mailman3-style manual import of mailman3web from old mailman3web db into the new db was not possible. There were additional tables and fields that needed values rather than defaults. Instead I opted to download the mbox exports from the old installation via the web interface and import them into the new installation for expediency.This is where I was when I posted the message. However, the old installation's mbox archive export (from the database) was problematic (e.g. 5min timeout) but after getting around those issues I ended up with some broken mbox files (e.g. the "From 1st April ..." line within a message, resulting in hyperkitty_import failures). > > although I tested downloading this thread archive and it is clearly > > escaped. Unfortunately I cannot tell if hyperkitty_import works > > using the git head since I am restricted to using the version > > provided with Debian 12. > > In July it worked for me on a site with 5300 archived lists. I assume > some of them had From-stuffed lines. Can't be sure, most of the posts > are machine-generated, but lines beginning with "From " are pretty > common in natural English. I'd be surprised if there were not any. I have 2003 lists and several occurrences. > > > There are indeed two versions though of mailbox.py on the VM: > > > > /usr/lib/python3/dist-packages/mailman/utilities/mailbox.py: from > > mailman3 (3.3.8-2~deb12u1) > > /usr/lib/python3.11/mailbox.py from libpython3.11-stdlib (3.11.2-6) > > The first applies one small change to the second (a so-called > "monkey-patch") for use by Mailman core. It should only be visible > to Python by the name "mailman.utilities.mailbox". The HyperKitty > utilities import the name "mailbox". If overwriting the first with > the second changes HyperKitty's behavior, something is wrong with > sys.path. Then I guess that is the case in Debian 12. > > > the latter of which appears far more substantial , so I dropped > > that module over the former and reran hyperkitty_import over the > > '>' escaped mbox, and while it did import without error, it did > > leave the escape in place (i.e. the 'From ...' was quoted when > > viewed). > > This is considered correct behavior. It is not possible to determine > whether the escape was in the original, or added by a receiving MTA. > Better to leave it. I thought that ">From " would be escaped to ">>From ", and so on, so the escape could easily be reversed when imported. I tested exports from the mailman-users lists and lines beginning "From " (preceded by a blank line) are escaped to ">From ", so incorrectly figured this would be unescaped by hyperkitty_import. After all, I would expect that an export of the archive to mbox, followed by a delete of the archive, followed by a hyperkitty_import of the archive, should leave you at the same place. Not with ">From " escapes in the new archives. In fact I also had a number of messages with "Message-ID: <>" and worse: all messages with attachments had the text/plain content empty. So mbox exports from MM 3.2.1 on Debian 10 (using hyperkitty+mysql) are broken. > > > The unescaped mbox import died in the same way. > > As expected. > > > Anyhow, thanks for your suggestion. For now I can stick with a > > manual repair and spaced escape of From_. > > If the old database is still available, I recommend dumping that and > loading it into a fresh version of the DBMS. > ... Thanks for the pointer. As I had already done the same with mailman3, so repeated the excercise. The following dump and import worked. oldhost> mysqldump --no-create-info --no-create-db --disable-keys --complete-insert mailman3web > mailman3web.sql newhost> mysql MariaDB [(none]> use mailman3web MariaDB [mailman3web]> source mailman3web.sql Thanks again -- Alex

2 3

Can't send emails to list users
by Rob Passalacqua 19 Sep '23

19 Sep '23

I've looked on the forums and haven't found someone with the exact same issue as me. It appears that my mailman 3 server is either only sending to the first3 recipients on the list or only sending out mail to users that are members in Django because only 3 recipients are getting the emails. Here is my /var/log/mailman3/smtp.log: Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.028921127319335938 seconds Sep 01 08:00:04 2023 (1405) <169357680279.2857929.16011221517221650936(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1107 bytes Sep 01 08:00:04 2023 (1405) <169357680284.2857929.17642987556878027498(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.00876307487487793 seconds Sep 01 08:00:04 2023 (1405) <169357680284.2857929.17642987556878027498(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1384 bytes Sep 01 08:02:03 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.08111977577209473 seconds Sep 01 08:02:03 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from itroost(a)mydomain.com, 22320 bytes Sep 01 08:08:21 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.08126330375671387 seconds Sep 01 08:08:21 2023 (1405) <BY5PR04MB6787FC43405D111FDBF24BBBD2E5A(a)BY5PR04MB6787.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from itroost(a)mydomain.com, 22320 bytes Sep 01 08:08:33 2023 (1405) <SJ0PR04MB7469F9DA4C471D4CF0AA8329C8E5A(a)SJ0PR04MB7469.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.19033193588256836 seconds Sep 01 08:08:33 2023 (1405) <SJ0PR04MB7469F9DA4C471D4CF0AA8329C8E5A(a)SJ0PR04MB7469.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from marcomm(a)mydomain.com, 627057 bytes Sep 08 13:16:05 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 08 13:16:05 2023 (1402) Peer: ('127.0.0.1', 39988) Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) handling connection Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'LHLO lists.mydomain.com' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'MAIL FROM:<radiga(a)mydomain.com>' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) sender: radiga(a)mydomain.com Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) recip: undergraduates(a)lists.mydomain.com Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'DATA' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) Data: b'QUIT' Sep 08 13:16:05 2023 (1402) ('127.0.0.1', 39988) connection lost Sep 08 13:16:05 2023 (1402) Connection lost during _handle_client() Sep 08 13:16:07 2023 (1405) <169420056594.1401.9589247638462690499(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005960226058959961 seconds Sep 08 13:16:07 2023 (1405) <169420056594.1401.9589247638462690499(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1151 bytes Sep 08 14:26:48 2023 (1405) <CYYPR04MB90325509F556F72D6E562F1CA2EDA(a)CYYPR04MB9032.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.11815094947814941 seconds Sep 08 14:26:48 2023 (1405) <CYYPR04MB90325509F556F72D6E562F1CA2EDA(a)CYYPR04MB9032.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from radiga(a)mydomain.com, 19719 bytes Sep 11 16:28:09 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 11 16:28:09 2023 (1402) Peer: ('127.0.0.1', 54070) Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) handling connection Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'LHLO lists.mydomain.com' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'MAIL FROM:<mbutterworth(a)mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) sender: mbutterworth(a)mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'RCPT TO:<graduates(a)lists.mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) recip: graduates(a)lists.mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) recip: undergraduates(a)lists.mydomain.com Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'DATA' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) Data: b'QUIT' Sep 11 16:28:09 2023 (1402) ('127.0.0.1', 54070) connection lost Sep 11 16:28:09 2023 (1402) Connection lost during _handle_client() Sep 11 16:28:12 2023 (1405) <169447129087.1401.7570255973486097010(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 1 recips, completed in 0.0067327022552490234 seconds Sep 11 16:28:12 2023 (1405) <169447129087.1401.7570255973486097010(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from graduates-bounces(a)lists.mydomain.com, 1125 bytes Sep 11 16:28:12 2023 (1405) <169447129099.1401.13948217098256502621(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005612611770629883 seconds Sep 11 16:28:12 2023 (1405) <169447129099.1401.13948217098256502621(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1225 bytes Sep 12 08:00:04 2023 (1405) <169452720292.3537648.2620214486815282831(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.027950286865234375 seconds Sep 12 08:00:04 2023 (1405) <169452720292.3537648.2620214486815282831(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1054 bytes Sep 12 08:00:04 2023 (1405) <169452720295.3537648.16444246393071130094(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.0057718753814697266 seconds Sep 12 08:00:04 2023 (1405) <169452720295.3537648.16444246393071130094(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1151 bytes Sep 12 08:33:17 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.08274292945861816 seconds Sep 12 08:33:17 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from mbutterworth(a)mydomain.com, 53024 bytes Sep 12 08:33:26 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.061426639556884766 seconds Sep 12 08:33:26 2023 (1405) <BYAPR04MB4438A507A16AE14A6CFF7E33A1F2A(a)BYAPR04MB4438.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from mbutterworth(a)mydomain.com, 53024 bytes Sep 12 13:19:19 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 12 13:19:19 2023 (1402) Peer: ('127.0.0.1', 54328) Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) handling connection Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'LHLO lists.mydomain.com' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'MAIL FROM:<oanderson(a)mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) sender: oanderson(a)mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'RCPT TO:<graduates(a)lists.mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) recip: graduates(a)lists.mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) recip: undergraduates(a)lists.mydomain.com Sep 12 13:19:19 2023 (1402) ('127.0.0.1', 54328) Data: b'DATA' Sep 12 13:19:20 2023 (1402) ('127.0.0.1', 54328) Data: b'QUIT' Sep 12 13:19:20 2023 (1402) ('127.0.0.1', 54328) connection lost Sep 12 13:19:20 2023 (1402) Connection lost during _handle_client() Sep 12 13:19:22 2023 (1405) <169454636036.1401.8937840345817588576(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 1 recips, completed in 0.0059452056884765625 seconds Sep 12 13:19:22 2023 (1405) <169454636036.1401.8937840345817588576(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from graduates-bounces(a)lists.mydomain.com, 1152 bytes Sep 12 13:19:22 2023 (1405) <169454636048.1401.2318933518942482920(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005008220672607422 seconds Sep 12 13:19:22 2023 (1405) <169454636048.1401.2318933518942482920(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1251 bytes Sep 12 15:25:29 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 12 15:25:29 2023 (1402) Peer: ('127.0.0.1', 44946) Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) handling connection Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'LHLO lists.mydomain.com' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'MAIL FROM:<oanderson(a)mydomain.com>' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) sender: oanderson(a)mydomain.com Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) recip: undergraduates(a)lists.mydomain.com Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'DATA' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) Data: b'QUIT' Sep 12 15:25:29 2023 (1402) ('127.0.0.1', 44946) connection lost Sep 12 15:25:29 2023 (1402) Connection lost during _handle_client() Sep 12 15:25:30 2023 (1405) <169455392982.1401.10957221749647131956(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.006732940673828125 seconds Sep 12 15:25:30 2023 (1405) <169455392982.1401.10957221749647131956(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1237 bytes Sep 13 08:00:04 2023 (1405) <169461360294.3599633.12410089636004689205(a)lists.mydomain.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.027216196060180664 seconds Sep 13 08:00:04 2023 (1405) <169461360294.3599633.12410089636004689205(a)lists.mydomain.com> post to graduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1079 bytes Sep 13 08:00:04 2023 (1405) <169461360298.3599633.9616667478508973418(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.00615382194519043 seconds Sep 13 08:00:04 2023 (1405) <169461360298.3599633.9616667478508973418(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from systemadmins(a)mydomain.com, 1377 bytes Sep 13 08:37:09 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to graduates(a)lists.mydomain.com for 4 recips, completed in 0.438995361328125 seconds Sep 13 08:37:09 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to graduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 1787833 bytes Sep 13 08:37:37 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.41765809059143066 seconds Sep 13 08:37:37 2023 (1405) <BYAPR04MB5813FE78DC3323A0822D9FE4DBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 1787833 bytes Sep 13 08:37:37 2023 (1405) <BYAPR04MB581366BC29E904B4A7E7EFCCDBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.05196428298950195 seconds Sep 13 08:37:37 2023 (1405) <BYAPR04MB581366BC29E904B4A7E7EFCCDBF1A(a)BYAPR04MB5813.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from oanderson(a)mydomain.com, 22280 bytes Sep 14 11:13:14 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 11:13:14 2023 (1402) Peer: ('127.0.0.1', 46146) Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) handling connection Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'LHLO lists.mydomain.com' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'MAIL FROM:<informationservices(a)mydomain.com>' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) sender: informationservices(a)mydomain.com Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'RCPT TO:<undergraduates(a)lists.mydomain.com>' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) recip: undergraduates(a)lists.mydomain.com Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'DATA' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) Data: b'QUIT' Sep 14 11:13:14 2023 (1402) ('127.0.0.1', 46146) connection lost Sep 14 11:13:14 2023 (1402) Connection lost during _handle_client() Sep 14 11:13:16 2023 (1405) <169471159483.1401.16856017446433914677(a)lists.mydomain.com> smtp to undergraduates(a)lists.mydomain.com for 1 recips, completed in 0.005692005157470703 seconds Sep 14 11:13:16 2023 (1405) <169471159483.1401.16856017446433914677(a)lists.mydomain.com> post to undergraduates(a)lists.mydomain.com from undergraduates-bounces(a)lists.mydomain.com, 1210 bytes Sep 14 11:15:53 2023 (1405) <SJ0PR04MB85671FB097F25CF9F4874740BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> smtp to undergraduates(a)lists.mydomain.com for 4 recips, completed in 0.08924412727355957 seconds Sep 14 11:15:53 2023 (1405) <SJ0PR04MB85671FB097F25CF9F4874740BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> post to undergraduates(a)lists.mydomain.com from informationservices(a)mydomain.com, 22049 bytes Sep 14 14:34:11 2023 (1402) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 14:34:11 2023 (1402) Peer: ('127.0.0.1', 60848) Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) handling connection Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'LHLO lists.mydomain.com' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'MAIL FROM:<informationservices(a)mydomain.com>' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) sender: informationservices(a)mydomain.com Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'RCPT TO:<ug(a)lists.mydomain.com>' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) recip: ug(a)lists.mydomain.com Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'DATA' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) Data: b'QUIT' Sep 14 14:34:11 2023 (1402) ('127.0.0.1', 60848) connection lost Sep 14 14:34:11 2023 (1402) Connection lost during _handle_client() Sep 14 14:34:14 2023 (1405) <169472365226.1401.465743651937418379(a)lists.mydomain.com> smtp to ug(a)lists.mydomain.com for 1 recips, completed in 0.00711822509765625 seconds Sep 14 14:34:14 2023 (1405) <169472365226.1401.465743651937418379(a)lists.mydomain.com> post to ug(a)lists.mydomain.com from ug-bounces(a)lists.mydomain.com, 1153 bytes Sep 14 14:34:33 2023 (1405) <SJ0PR04MB856797E91A59977ABCF9BAB7BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> smtp to ug(a)lists.mydomain.com for 4 recips, completed in 0.054645538330078125 seconds Sep 14 14:34:33 2023 (1405) <SJ0PR04MB856797E91A59977ABCF9BAB7BFF7A(a)SJ0PR04MB8567.namprd04.prod.outlook.com> post to ug(a)lists.mydomain.com from informationservices(a)mydomain.com, 21976 bytes Sep 14 16:36:56 2023 (1305) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 16:36:56 2023 (1305) Peer: ('127.0.0.1', 54478) Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) handling connection Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'LHLO lists.mydomain.com' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) sender: rpassalacqua(a)mydomain.com Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) recip: test(a)lists.mydomain.com Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'DATA' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) Data: b'QUIT' Sep 14 16:36:56 2023 (1305) ('127.0.0.1', 54478) connection lost Sep 14 16:36:56 2023 (1305) Connection lost during _handle_client() Sep 14 16:36:58 2023 (1307) <169473101747.1304.15129450588472089900(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.0060198307037353516 seconds Sep 14 16:36:58 2023 (1307) <169473101747.1304.15129450588472089900(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1067 bytes Sep 14 16:38:48 2023 (1307) <BY5PR04MB71216AD8880847E842960CB6B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.05848550796508789 seconds Sep 14 16:38:48 2023 (1307) <BY5PR04MB71216AD8880847E842960CB6B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8680 bytes Sep 14 17:39:38 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 17:39:38 2023 (4281) Peer: ('127.0.0.1', 38814) Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) handling connection Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'LHLO lists.mydomain.com' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) sender: rpassalacqua(a)mydomain.com Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) recip: test(a)lists.mydomain.com Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'DATA' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) Data: b'QUIT' Sep 14 17:39:38 2023 (4281) ('127.0.0.1', 38814) connection lost Sep 14 17:39:38 2023 (4281) Connection lost during _handle_client() Sep 14 17:39:40 2023 (4283) <169473477870.4280.4174702240504737654(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005831241607666016 seconds Sep 14 17:39:40 2023 (4283) <169473477870.4280.4174702240504737654(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1085 bytes Sep 14 17:42:59 2023 (4283) <BY5PR04MB71215FF54B65F1D74C4567C0B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.06569862365722656 seconds Sep 14 17:42:59 2023 (4283) <BY5PR04MB71215FF54B65F1D74C4567C0B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 32685 bytes Sep 14 18:03:41 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 18:03:41 2023 (4281) Peer: ('127.0.0.1', 42054) Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) handling connection Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'LHLO lists.mydomain.com' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) sender: rpassalacqua(a)mydomain.com Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) recip: test(a)lists.mydomain.com Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'DATA' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) Data: b'QUIT' Sep 14 18:03:41 2023 (4281) ('127.0.0.1', 42054) connection lost Sep 14 18:03:41 2023 (4281) Connection lost during _handle_client() Sep 14 18:03:42 2023 (4283) <169473622130.4280.7069249432915457814(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.006022214889526367 seconds Sep 14 18:03:42 2023 (4283) <169473622130.4280.7069249432915457814(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1065 bytes Sep 14 18:07:57 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 14 18:07:57 2023 (4281) Peer: ('127.0.0.1', 50610) Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) handling connection Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'LHLO lists.mydomain.com' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) sender: rpassalacqua(a)mydomain.com Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) recip: test(a)lists.mydomain.com Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'DATA' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) Data: b'QUIT' Sep 14 18:07:57 2023 (4281) ('127.0.0.1', 50610) connection lost Sep 14 18:07:57 2023 (4281) Connection lost during _handle_client() Sep 14 18:07:58 2023 (4283) <169473647867.4280.14938940229014329856(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.0055654048919677734 seconds Sep 14 18:07:58 2023 (4283) <169473647867.4280.14938940229014329856(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1098 bytes Sep 14 18:10:17 2023 (4283) <BY5PR04MB71217ABD906F6FE7AFD2B4B9B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.06551766395568848 seconds Sep 14 18:10:17 2023 (4283) <BY5PR04MB71217ABD906F6FE7AFD2B4B9B3F7A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8688 bytes Sep 14 18:10:20 2023 (4283) <BY5PR04MB7121FAB23617A4597304E327B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.03918266296386719 seconds Sep 14 18:10:20 2023 (4283) <BY5PR04MB7121FAB23617A4597304E327B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8880 bytes Sep 15 09:16:03 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 15 09:16:03 2023 (4281) Peer: ('127.0.0.1', 38006) Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) handling connection Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'LHLO lists.mydomain.com' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) sender: rpassalacqua(a)mydomain.com Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) recip: test(a)lists.mydomain.com Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'DATA' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) Data: b'QUIT' Sep 15 09:16:03 2023 (4281) ('127.0.0.1', 38006) connection lost Sep 15 09:16:03 2023 (4281) Connection lost during _handle_client() Sep 15 09:16:05 2023 (4283) <169479096385.4280.8198285364938859931(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005726337432861328 seconds Sep 15 09:16:05 2023 (4283) <169479096385.4280.8198285364938859931(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1069 bytes Sep 15 09:16:54 2023 (4283) <BY5PR04MB71219485E3D6DBF7FFEF45E5B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.04341244697570801 seconds Sep 15 09:16:54 2023 (4283) <BY5PR04MB71219485E3D6DBF7FFEF45E5B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 9719 bytes Sep 15 11:12:26 2023 (4281) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 15 11:12:26 2023 (4281) Peer: ('127.0.0.1', 59844) Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) handling connection Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'LHLO lists.mydomain.com' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) sender: rpassalacqua(a)mydomain.com Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) recip: test(a)lists.mydomain.com Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'DATA' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) Data: b'QUIT' Sep 15 11:12:26 2023 (4281) ('127.0.0.1', 59844) connection lost Sep 15 11:12:26 2023 (4281) Connection lost during _handle_client() Sep 15 11:12:28 2023 (4283) <169479794718.4280.8209850830279553803(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005163669586181641 seconds Sep 15 11:12:28 2023 (4283) <169479794718.4280.8209850830279553803(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1098 bytes Sep 15 11:12:49 2023 (4283) <BY5PR04MB71214E309721B3CC9F3072F9B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.0408024787902832 seconds Sep 15 11:12:49 2023 (4283) <BY5PR04MB71214E309721B3CC9F3072F9B3F6A(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8817 bytes Sep 18 16:51:02 2023 (1286) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 18 16:51:02 2023 (1286) Peer: ('127.0.0.1', 56034) Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) handling connection Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'LHLO lists.mydomain.com' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) sender: rpassalacqua(a)mydomain.com Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) recip: test(a)lists.mydomain.com Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'DATA' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) Data: b'QUIT' Sep 18 16:51:02 2023 (1286) ('127.0.0.1', 56034) connection lost Sep 18 16:51:02 2023 (1286) Connection lost during _handle_client() Sep 18 16:51:03 2023 (1288) <169507746274.1285.2209553928985210953(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.005767107009887695 seconds Sep 18 16:51:03 2023 (1288) <169507746274.1285.2209553928985210953(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1075 bytes Sep 18 16:58:09 2023 (1288) <BY5PR04MB7121D7152C07846F0FCFB100B3FBA(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.07815432548522949 seconds Sep 18 16:58:09 2023 (1288) <BY5PR04MB7121D7152C07846F0FCFB100B3FBA(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8756 bytes Sep 19 08:49:33 2023 (1286) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Sep 19 08:49:33 2023 (1286) Peer: ('127.0.0.1', 59616) Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) handling connection Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'LHLO lists.mydomain.com' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'MAIL FROM:<rpassalacqua(a)mydomain.com>' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) sender: rpassalacqua(a)mydomain.com Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'RCPT TO:<test(a)lists.mydomain.com>' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) recip: test(a)lists.mydomain.com Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'DATA' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) Data: b'QUIT' Sep 19 08:49:33 2023 (1286) ('127.0.0.1', 59616) connection lost Sep 19 08:49:33 2023 (1286) Connection lost during _handle_client() Sep 19 08:49:36 2023 (1288) <169513497462.1285.8696625500767060363(a)lists.mydomain.com> smtp to test(a)lists.mydomain.com for 1 recips, completed in 0.007772684097290039 seconds Sep 19 08:49:36 2023 (1288) <169513497462.1285.8696625500767060363(a)lists.mydomain.com> post to test(a)lists.mydomain.com from test-bounces(a)lists.mydomain.com, 1076 bytes Sep 19 08:50:23 2023 (1288) <BY5PR04MB7121991E697D92F88D586AFFB3FAA(a)BY5PR04MB7121.namprd04.prod.outlook.com> smtp to test(a)lists.mydomain.com for 3 recips, completed in 0.04478025436401367 seconds Sep 19 08:50:23 2023 (1288) <BY5PR04MB7121991E697D92F88D586AFFB3FAA(a)BY5PR04MB7121.namprd04.prod.outlook.com> post to test(a)lists.mydomain.com from rpassalacqua(a)mydomain.com, 8828 bytes

3 4

Importing mbox files into archive defect with lines with From
by andrew.bernard＠gmail.com 19 Sep '23

19 Sep '23

A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. Is this a known bug? If not, how do I report it?

8 15

Modify approval email
by pau.baiges＠csuc.cat 19 Sep '23

19 Sep '23

Good morning, Is there a way to modify the email that is sent by default to list owners when a non-list member sends email to the list? Basically the default email that is sent is this: ________________________________________________________ As list administrator, your authorization is requested for the following mailing list posting: List: lis1(a)llistes.csuc.cat From: jim(a)csuc.cat Subject: test The message is being held because: El missatge no és d'un membre de la llista At your convenience, visit your dashboard to approve or deny the request. _____________________________________________________________________ We would like to add the link to the page to accept the email from the list itself. I think I remember that in the old mailman it could be done Thanks!

4 4

I'm seeing a lot of database locked errors
by bryan.kartzman＠yu.edu 19 Sep '23

19 Sep '23

We switched the mailman database from sqlite to postgresql a while back to minimize any database locking but I'm seeing a lot of errors for the django sqlite database. Is it possible to move that to postgres as well? 16:18:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:39 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:18:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:39 [Q] INFO Processed [compute_thread_positions] 16:18:44 [Q] INFO Process-1:2 processing [compute_thread_positions] 16:18:44 [Q] INFO Processed [compute_thread_positions] 16:18:44 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:18:44 [Q] INFO Processed [compute_thread_positions] 16:18:44 [Q] INFO Process-1:3 processing [compute_thread_positions] 16:18:44 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:18:44 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:44 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] INFO Process-1:2 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:3 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:2 processing [compute_thread_positions] 16:18:49 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:49 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:18:49 [Q] INFO Processed [compute_thread_positions] 16:19:39 [Q] INFO Process-1:4 processing [compute_thread_positions] 16:19:39 [Q] INFO Process-1:3 processing [compute_thread_positions] 16:19:39 [Q] INFO Process-1:1 processing [compute_thread_positions] 16:19:39 [Q] ERROR Failed [compute_thread_positions] - database is locked : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) 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/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 40, in walk_successors obj.save(update_fields=["thread_depth", "thread_order"]) File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 743, in save self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 780, in save_base updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 853, in _save_table updated = self._do_update(base_qs, using, pk_val, values, update_fields, File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 903, in _do_update return filtered._update(values) > 0 File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 760, in _update return query.get_compiler(self.db).execute_sql(CURSOR) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1471, in execute_sql cursor = super().execute_sql(result_type) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py", line 1142, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 383, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: database is locked

2 14

LDAP user email verification
by Tony Deshields 15 Sep '23

15 Sep '23

I'm running the docker-mailman setup with LDAP integrated. My users that authenticate against LDAP are still required to verify their email address however, I do not want this functionality. I was looking for guidance on possibly configuring it so my LDAP users do not have to verify their email address.

3 3

Restore/export existing Mailman lists + hyperkitty archives on a new server
by Kimmo L 14 Sep '23

14 Sep '23

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 13 Sep '23

13 Sep '23

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 13 Sep '23

13 Sep '23

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 13 Sep '23

13 Sep '23

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 10 Sep '23

10 Sep '23

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 09 Sep '23

09 Sep '23

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 06 Sep '23

06 Sep '23

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 05 Sep '23

05 Sep '23

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 04 Sep '23

04 Sep '23

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 04 Sep '23

04 Sep '23

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

How to debug DMARC check?
by Gilles Filippini 03 Sep '23

03 Sep '23

Hi, I've been running a dockerized mailman3 server for several years with DMARC mitigation set to conditional. I use the 0.4 version of the mailman3 docker images. Recently I had to update my network configuration to prevent spammers using IPv6 to circumvent the no-relay configuration of my exim4 server. Previously, I had both exim4 and mailman3 on the same docker bridge 172.19.0.0/16 and exim4 was configured to relay email from this network only. There was no problem regarding DMARC mitigation : most of the emails didn't need to be altered. Now I have added an internal docker network 172.29.0.0/16 and configured exim4 to relay from this internal network only. Since this network is not accessible from the host, IPv6 spammers are blocked (*). But since this modification mailman alters every emails with DMARC mitigation. Any hint how to debug this issue? Thanks in advance, _g. (*) With IPv6 incoming connexions mailman docker replaces the client address with the IPv4 address of the host one the bridge network: 172.19.0.1.

2 4

Add date stamps to django (I think) logfiles?
by kjohnson＠eclypse.org 01 Sep '23

01 Sep '23

The webserver and archive part of mailman writes some logfiles on my system with entries like: 17:19:05 [Q] INFO Process-1 guarding cluster twenty-pluto-arizona-pasta 17:19:05 [Q] INFO Process-1:4 pushing tasks at 2831 17:19:05 [Q] INFO Q Cluster twenty-pluto-arizona-pasta running. These seem to match this format in settings.py: 'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s' except that I would expect asctime to have a date attached. A pointer to relevant documentation would be very much appreciated. Thanks. Ken

3 2

Installing Mailman3 on Debian Bullseye
by Franklin Weng 30 Aug '23

30 Aug '23

Hi, After several times attempts I finally successfully build a (reliable enough) mailman3 instance on Debian. I had a blog article describing how I did it. Maybe there were something you find it ridiculous, but they are all what I found important and may not be shown in the current documents. https://blogs.slat.org/node/1012 Hope this helps. Franklin

6 9

log rotation in maxking-docker-version
by Jens Günther 27 Aug '23

27 Aug '23

Hey there, while checking some logs I was realising that there is no log rotation and some of them piled up to 5GB over the past year(s). Does anybody know how to activate it (if it's possible) or ... Ok, I found a clue and it's still open :-) https://github.com/maxking/docker-mailman/issues/535 -> does anybody have a different approach? Regards, Jens.

2 3

Can't start mailman after reboot.
by mrl＠psfc.mit.edu 24 Aug '23

24 Aug '23

I have successful rebooted my computer server several times, and mailman has always started without a problem Now mailman won't start. See below. I tried to see if it was a problem with mysql. But I can successfully connect to the sql server using the mailman username and password, from the command line. What else can I try??? Thanks. - Mark Aug 24 12:52:17 psfcmail2 systemd[1]: Starting GNU Mailing List Manager... Aug 24 12:52:18 psfcmail2 mailman[28151]: Traceback (most recent call last): Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/bin/mailman", line 8, in <module> Aug 24 12:52:18 psfcmail2 mailman[28151]: sys.exit(main()) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ Aug 24 12:52:18 psfcmail2 mailman[28151]: return self.main(*args, **kwargs) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main Aug 24 12:52:18 psfcmail2 mailman[28151]: rv = self.invoke(ctx) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return super().invoke(ctx) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1657, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return _process_result(sub_ctx.command.invoke(sub_ctx)) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return ctx.invoke(self.callback, **ctx.params) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke Aug 24 12:52:18 psfcmail2 mailman[28151]: return __callback(*args, **kwargs) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func Aug 24 12:52:18 psfcmail2 mailman[28151]: return f(get_current_context(), *args, **kwargs) Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/commands/cli_control.py", line 91, in start Aug 24 12:52:18 psfcmail2 mailman[28151]: status, lock = master_state() Aug 24 12:52:18 psfcmail2 mailman[28151]: File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/bin/master.py", line 104, in master_state Aug 24 12:52:18 psfcmail2 mailman[28151]: os.kill(pid, 0) Aug 24 12:52:18 psfcmail2 mailman[28151]: PermissionError: [Errno 1] Operation not permitted Aug 24 12:52:19 psfcmail2 mariadbd[22160]: 2023-08-24 12:52:19 3191 [Warning] Aborted connection 3191 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets)

2 3

Only allow users to subscribe from certain domains
by bob B 23 Aug '23

23 Aug '23

Does Mailman have anyway to just allow users to subscribe themselves to a list from certain domains... ie any user from test.com or test2.com I do not believe this exists, but have a list manger who is asking. I feel they will have to either, approve all requests, or have a web frontend built that could filter that out and then send the subscribe commands in the backend. Thanks

2 2

applying patch 1130
by David Newman 22 Aug '23

22 Aug '23

Please forgive a dumb question from a non-programmer: How to apply the !1130.diff patch to a venv installation? https://gitlab.com/mailman/mailman/-/merge_requests/1130 I am looking to upgrade Debian 11 to 12. The latter uses python3.11, which no longer has a dependency on importlib_resources. As a result, MM3 won't start unless all references to importlib_resources instead call importlib.resources, now part of stdlib. I tried patching all importlib.resource references by hand, and MM3 starts – but that can't be the "right" way to do this. Also, the diff references a src directory that doesn't exist under /opt/mailman. Thanks in advance for patching clues. dn

3 5

importlib_resources issue?
by Dave McGuire 21 Aug '23

21 Aug '23

Hi folks, I'm trying to test a fresh venv-based install from this procedure: https://docs.mailman3.org/en/latest/install/virtualenv.html Platform is SmartOS (Solaris 11) with Python 3.10. The installation goes fine, but initial startup bombs with: ImportError: cannot import name 'path' from 'importlib_resources' (/opt/mailman/venv/lib/python3.10/site-packages/importlib_resources/__init__.py) I assume this is related to importlib_resources moving into stdlib at some point. Is there a reasonable way around this? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 2

Internal Server Error: /mailman3/hyperkitty/api/mailman/archive
by Mail Person 21 Aug '23

21 Aug '23

Hello everyone. I am trying to sort out an error happening when messages are sent to the mailman server. The emails are being sent to the list but I get this error each time: Internal Server Error: /mailman3/hyperkitty/api/mailman/archive OperationalError at /hyperkitty/api/mailman/archive (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") Request Method: POST Request URL: http://localhost/mailman3/hyperkitty/api/mailman/archive?key=7OF5IogiQItSUK… Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: Thu, 17 Aug 2023 17:13:09 +0000 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Traceback: File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute 84. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 71. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 209. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 315. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 226. _mysql.connection.query(self, query) The above exception ((1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1")) was the direct cause of the following exception: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/http.py" in inner 40. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in _decorator 71. return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/django/views/decorators/csrf.py" in wrapped_view 54. return view_func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mailman.py" in archive 117. add_to_list(mlist_fqdn, msg) File "/usr/lib/python3/dist-packages/hyperkitty/lib/incoming.py" in add_to_list 153. email.save() File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save 740. self.save_base(using=using, force_insert=force_insert, File "/usr/lib/python3/dist-packages/django/db/models/base.py" in save_base 777. updated = self._save_table( File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _save_table 870. result = self._do_insert(cls._base_manager, using, fields, update_pk, raw) File "/usr/lib/python3/dist-packages/django/db/models/base.py" in _do_insert 907. return manager._insert([self], fields=fields, return_id=update_pk, File "/usr/lib/python3/dist-packages/django/db/models/manager.py" in manager_method 82. return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py" in _insert 1186. return query.get_compiler(using=using).execute_sql(return_id) File "/usr/lib/python3/dist-packages/django/db/models/sql/compiler.py" in execute_sql 1375. cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in execute 67. return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute_with_wrappers 76. return executor(sql, params, many, context) File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute 84. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/utils.py" in __exit__ 89. raise dj_exc_value.with_traceback(traceback) from exc_value File "/usr/lib/python3/dist-packages/django/db/backends/utils.py" in _execute 84. return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py" in execute 71. return self.cursor.execute(query, args) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in execute 209. res = self._query(query) File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py" in _query 315. db.query(q) File "/usr/lib/python3/dist-packages/MySQLdb/connections.py" in query 226. _mysql.connection.query(self, query) Exception Type: OperationalError at /hyperkitty/api/mailman/archive Exception Value: (1366, "Incorrect string value: '\\xF0\\x9F\\x90\\xBA\\x0A\\x0A...' for column 'content' at row 1") Request information: USER: AnonymousUser

2 2

Ansible role to install Mailman3
by samuel.d.darwin＠gmail.com 04 Aug '23

04 Aug '23

Hi, Before installing the Mailman Suite, I searched on https://galaxy.ansible.com/ for Ansible roles that might automate the whole process. https://github.com/galaxyproject/ansible-mailman3 turned out to be quite good. However, it was slightly out-of-date. I cloned it, made a few bug fixes, and corrected linting errors. Then, going further, added optional basic installations of Nginx, Postfix, PostgreSQL into the role. If anyone is installing Mailman they are welcome to try it out. https://github.com/cppalliance/ansible-mailman3 Now, I see there was a discussion on this very list about https://github.com/rivimey/ansible-mailman3 which was also a fork of natefoo's repo. What are the differences? As Stephen Turnbull wrote: "her (rivimey's) setup may be more complicated than most folks need (IIRC, she has a multi-homed setup with Mailman core, Postorius, and HyperKitty on three separate IPs on a separate subnet in the DMZ, while Mailman was really designed for three Mailman applications running on the same host, along with the database server and MTA)." My version of the role didn't follow the tactic of "three separate IPs on a separate subnet in the DMZ". Mainly, it adds postfix and postgres. Fixes small errors. Also, in a git branch of the repository named mailman3-core, I removed all the web code, so there is a version of the role that only installs core. We will use that while bundling the web components into another Django app, already deployed with docker. There is an open question about maintenance. Among the three roles mentioned here, which is being actively kept up-to-date? Perhaps there are no guarantees from any of them. At this instant in time, https://github.com/cppalliance/ansible-mailman3 is the most recent. Would it make sense to mention these roles in the official documentation? Not sure. Installing mailman3 is complicated and because of that, is a good fit for Ansible.

3 2

Mailman3 core didn't start after reboot, because mysql wasn't running yet.
by Mark London 29 Jul '23

29 Jul '23

Hi - We had a power outage, and after my Ubuntu server rebooted , mailman 3 tried to start before mysql was running. I guess because it wasn't a clean reboot, the mysql server took much longer than normal to start, while checking databases. So mailman3 couldn't start. Normal reboots never had this problem. Should it have kept trying? In any event, mailman3 core didn't start, but mailman3-web did start. But it wasn't very happy, of course. And any time someone tried to access the mailing list website, it would send me an error message. I had hundreds of such emails in the morning., that started with the one below. Is there a way to configure my system to make sure this doesn't happen again? Thanks. - Mark Service Unavailable: /mailman3/ Report at /mailman3/ Service Unavailable: /mailman3/ Request Method: GET Request URL:https://lists.psfc.mit.edu/mailman3/ Django Version: 4.1.8 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.10.6 Python Path: ['.', '', '/riusMiddleware')

4 6

Something wrong in Django admin interfaces
by Franklin Weng 21 Jul '23

21 Jul '23

Hi, Since both Mark and Danil kindly told me that my wish to disable web anonymous account registering requires new version of mailman and django-mailman, I found that newest Debian bookwarm (12) has * mailman 3.3.8-1 (including mailman3-full and mailman3-web 20200530-2.1) * python3-django-mailman3 : 1.3.9-1 * python3-mailman-hyperkitty : 1.2.1 So I re-installed mailman3 (and took notes so that I could write a blog). After installing that, I found that it has problems in django admin page. When I clicked any features like users, Mail domains, Failed tasks... anyone, no matter New or Change, the web page was covered by the first page. All the configuration fields/labels are covered by the first page. Please see the screenshot: https://nextcloud.slat.org/index.php/s/e5KKEEbqDK6DpiN https://nextcloud.slat.org/index.php/s/nLgMRQ9ACyxCwoc It was not able to do the administration tasks. I looked at django-mailman issues https://gitlab.com/mailman/django-mailman3/-/issues but didn't find anything useful. Does anyone have similar issues? What can I do to solve this? Thanks, Franklin

2 1

Any possible way to reduce robot spam accounts?
by Franklin Weng 21 Jul '23

21 Jul '23

Hi, I just installed a mailman3 instance, even haven't announced to anyone yet, there are a lot of spam robot accounts registering into my system. (See https://nextcloud.slat.org/index.php/s/WWHo7F3igYxn8LY for screenshot) I really have no idea how the robots find my system since I haven't told anyone the ip or URL of my mailman instance. And, they're registering on the system, not the mailing list since I have only one list for testing now and it wasn't assaulted by spam yet. No matter what, what I want to ask is that, is there a way to either * just let users join from email (lists-join(a)lists.url) instead of registering on the mailman instance? or * use a scheme like CAPTCHA to reduce the successful opportunity of robot registering? Any help is appreciated! Franklin

4 7

List mails blocked from GMX - web.de > Spamfolder
by itservice＠knut-krueger.de 19 Jul '23

19 Jul '23

How can I configure Mailman3 so that Mails from the list will not be blocked by gmx.net I tried to send with the same user (mailman.cf) at my mail server, which will not be blocked by gmx. unfortunately, I get no bounce back message. They do just not appear in the mail folder of gmx. At web.de they go to the SPAM folder.

4 4

Import old mails into list
by franklin＠slat.org 19 Jul '23

19 Jul '23

Hi, I just built a new mailman3 instance. I installed directly on Debian using mailman3-full and follow /usr/share/doc/mailman3/README.Debian to set up database/web. Then I'd like to import some old mail (in a mbox file) into this list. I searched for any documentation but all I got is Import list data (from 2.1): https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/comma… How do I import an archive into a new mailing list: https://wiki.list.org/DOC/How%20do%20I%20import%20an%20archive%20into%20a%2… The first is import list data, not list contents (mails). The second is very old, written in 2007, and now I even can't find bin/arch commands. Also, this post in this mailing list: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Which nobody replied yet. And when I tried `django-admin hyperkitty_import` it even told me "Unknown command: 'hyperkitty_import'". Could anyone please tell me how to import old mails from mbox file into a new mailing list? Thanks, Franklin

2 1

Configure administrative users via command line?
by kjohnson＠eclypse.org 18 Jul '23

18 Jul '23

I recently migrated a mailing list from Mailman 2.x to Mailman 3.x. Sending messages to and receiving messages from the list seems to work well. The web interface archives seem to be working well. Xapian is configured as the search engine. With only 60K some messages, archive search seems very fast. How can I configure administrative users via command line? I need to process a moderation request. I have root access on the server. A pointer to the appropriate documentation would be more than welcome. Thank you to anyone who can provide help. Ken

2 3

where do I find the text of a bounce email ?
by Per Jessen 01 Jul '23

01 Jul '23

All, I am trying to figure why a particular outbound message was bounced, so I'm looking for the text of the NDR that was sent - where do I find that ? Fyi, the outbound message was accepted by the first relay, and then presumably later bounced by the actual recipient server (Office365). Any and all hints much appreciated. -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

3 5

Viewing/editing bounce score/status in Postorius
by Tom Smyth 01 Jul '23

01 Jul '23

Is this possible? As of 1.3.2 I can't find it. Perhaps it's in a newer version? I'm working on upgrading. Thanks! -- Tom Smyth (he/him)

2 1

Hyperkitty list overview error: thread matching query does not exist
by Darren Hart 29 Jun '23

29 Jun '23

When attempting to visit the hyperkitty archives list overview for one of my two lists: Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). The following appears in /var/log/mailman3/web/mailman-web.log: ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 135, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 251, in overview_posted_to for thread in mlist.recent_threads: File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 142, in recent_threads return self.cached_values["recent_threads"]() File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py", line 59, in __call__ return self.get_or_set(*args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 281, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 281, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. The hyper kitty archives for a second list on this Mailman3 instance is working correctly. How can I fix this view of the archives? Or how can I get more information on what might be failing? Thanks, Darren

3 6

archives html user interface menu selection retention after refresh
by Ken Alker 29 Jun '23

29 Jun '23

I have just started studying the archives feature and I've noticed that if I select "Most Active" in the top menu and then I refresh my browser, the refreshed screen jumps back to Recent after the refresh. In fact, if ANY of the five menu items across the top are selected and then a browser refresh is performed, the result is that one is always taken back to the Recent menu item. It was not apparent to me for a couple of days that this was happening and I'd convinced myself there was some bug in the Recent vs. Most Active lists because the Most Active list changed entirely after I did a refresh, when, in fact, I was then viewing the Recent list again. Confusing. Is there some way that whatever menu item was being viewed before a refresh could be retained so that the same menu item is shown after a refresh? Thinking this through even further, I suppose a side-affect of this request could be that visiting the same page much later (ie. not immediately after a refresh) may result in the page NOT defaulting to the Recent menu item any longer (unless once could clear the "last menu item" memory when the viewer moves AWAY from or closes the page). I don't have enough familiarly with the interface to suggest if this would be a bad side-effect, or good, but would this, indeed become a side-affect that would have to be thought through?

2 1

Re: How do I specify the TCP port number for Postgresql?
by kjohnson＠eclypse.org 28 Jun '23

28 Jun '23

Thank you for this helpful and prompt reply! Ken

1 0

How do I specify the TCP port number for Postgresql?
by kjohnson＠eclypse.org 28 Jun '23

28 Jun '23

The mailman.cfg file on the system I am working on includes this line: url: postgres://mailman3:mailman3:@localhost/mailman3 This works fine as long as the postgresql server is at the default port number of 5432. How do I specify a different TCP port number? My guess is that a change to this line is needed, but unfortunately, it is not obvious to me how to make that change, and I have been unable to find this information in the mailman3 documentation or in a previous mailing list post. Feel free to point me at the documentation or post that I have overlooked. Thanks, Ken

2 1

Archive date/time vs elapsed time
by Mark 28 Jun '23

28 Jun '23

Hi In the archive's "Recent", "Most active" etc displays, the date and time of each post is shown. However, when viewing by "Thread" listing, each post shows the elapsed time since it was posted ie. the number of days, hours since it was posted (eg. 1 day, 2 hours). Is it possible to set Hyperkitty to display the "Thread" listing with the date/time in place of that elapsed time? Thanks Mark

2 4

Postorius claims 2 messages held when there are none - out of sync
by Ken Alker 27 Jun '23

27 Jun '23

When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this?

3 8

Message is received but is not sent out. Another, similar message, is processed fine.
by Allan Hansen 27 Jun '23

27 Jun '23

Hi all, One of my subscribers is trying to send a message to a list, but it is not being posted. The smtp.log shows that her first message was posted, but a second message (with 2 retries) was not: mailman@list:~/logs$ grep herName smtp.log Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=40109' Jun 18 11:22:05 2023 (1243316) ('127.0.0.1', 56686) sender: herName(a)hotmail.com Jun 18 11:25:01 2023 (1243318) <CH3PR12MB82593510B90D8F05177C606BBE5EA(a)CH3PR12MB8259.namprd12.prod.outlook.com> post to theList(a)domain.tlc from herName(a)hotmail.com, 40061 bytes Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18343' Jun 18 11:52:42 2023 (1243316) ('127.0.0.1', 48448) sender: herName(a)hotmail.com Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=19123' Jun 18 19:01:04 2023 (1243316) ('127.0.0.1', 59550) sender: herName(a)hotmail.com Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) >> b'MAIL FROM:<herName(a)hotmail.com> SIZE=18930' Jun 26 17:18:11 2023 (1243316) ('127.0.0.1', 44732) sender: herName(a)hotmail.com At the second retry she copied me and I saw nothing untowards in her message. She's not getting any error return messages and her subscription is OK. Both messages were multipart/alternative and both contained Hebrew text. I told her I'd look at this, but I'm at a loss. Yours, Allan

3 6

Problems after upgrading from bullseye to bookworm
by Eggert Ehmke 27 Jun '23

27 Jun '23

I upgrade my server to bookworm. In the process python was upgraded from 3.7 to 3.9 . I reinstalled the virtualenv and the mailman packages. When I now start mailman-web, I get this in web/logs/uwsgi-error.log: pkg_resources.DistributionNotFound: The 'flufl.lock>=4.0' distribution was not found and is required by hyperkitty What did I miss? ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

5 5

attachment.html
by Sam Darwin 27 Jun '23

27 Jun '23

Hi, Using a typical modern email client such as Gmail, the messages are usually html formatted. Then, Hyperkitty displays attachment.html on every message. Can that be removed? I was searching for the topic "attachment.html" in the archives and there wasn't much information. What finally cracked the code was Mark's comment: If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. It turns out "Filter content" affects many settings. It's easy to skip over that. I wonder if the UI might call attention somehow, with a graphic element, or with text: "Settings on this page will not take effect. Because 'Filter content' has not been enabled". It is right that "Filter content" must be set in order to remove attachment.html ? And now, a search will have more results. :-)

2 3

clicking on a username when viewing a thread results in "Page not found"
by Ken Alker 27 Jun '23

27 Jun '23

If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? Also, why is it that some usernames are not clickable (ie. black text with no hyperlink)? Thanks! Ken

3 4

old usernames appearing in mailman.log
by Ken Alker 27 Jun '23

27 Jun '23

I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system. Several months ago, the system had been upgraded from mailman V2 to mailman V3.2.2. The server has been active for over 20 years. I've just taken on the project so I'm new to all of this, and one thing I noticed that caught my eye, and has left me curious, is that for the first a couple of seconds starting just after midnight every night (just after log rotation) mailman.log would have many (dozens, or hundreds) of lines entered in it just like this one: Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET /3.0/users/old-user(a)domain.tld HTTP/1.1" 404 58 where "old-user(a)domain.tld" is the email address of a user who either had unsubscribed or changed their email address (I don't know which, I just know they are no longer a member/subscriber to the list). Each successive entry in the log would have a different "old username" in it. I don't understand why these entries would be in the log and what they mean. Can someone shed some light on this for me? This is merely a question of curiosity, and not one of import. (Since migrating from 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.) Ken

2 8

Global ban using regex
by Henrik Rasmussen 27 Jun '23

27 Jun '23

Using some regex testers and generators like https://regex101.com and https://www.site24x7.com/tools/regex-parser.html, the regex (.*)(a)inker\.azerbaijan\.su seems to match EVERYTHING(a)inker.azerbaijan.su (EVERYTHING is constantly changing in current spam mails). However, entering the regex to the Global Ban Add ban /postorius/bans/ result in: `An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got (.*)(a)inker\.azerbaijan\.su.'` Same result when using [Ban list] in postorius/lists/[LISTNAME]/bans/. Entering a none regex addresses like eknejfj(a)inker.azerbaijan.su works fine. Does Mailman use a different regex syntax I am using GNU Mailman 3.3.4 (Tom Sawyer) and Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] (maxking/mailman-core:0.3 and maxking/mailman-web:0.3)

2 1

starting gunicorn per mailman.log yet gunicorn not installed
by Ken Alker 27 Jun '23

27 Jun '23

I see the below in my mailman.log, yet I installed uwsgi and NOT gunicorn. My mainmanweb.service file includes "ExecStart=/opt/mailman/venv/bin/uwsgi --ini /etc/mailman3/uwsgi.ini" and not the gunicorn equivalent. Does this log entry make sense in my case? [2023-06-22 12:44:36 -0700] [411132] [INFO] Starting gunicorn 20.1.0

4 7

messages stuck in the bad queue
by Ken Alker 26 Jun '23

26 Jun '23

I am working on a mail server that was migrated from mailman V2 to mailman V3 in February. I just noticed that there are over 1000 messages in the bad queue. All of the messages in the bad queue are dated 2/2/23 and all have a timestamp within a one-hour window of each other. I used mailman qfile to inspect five random emails in the bad queue and so far they are all "successfully subscribed" emails, but I presume there are no guarantees there aren't others mixed in there that might be legitimate emails (ie. I just unshunted 140 emails in the shunt queue and they were all good emails and all got processed). I figure that the easiest way to inspect these 1000 emails is just to have them re-delivered. I tried moving one from the bad queue to the shunt queue and I ran "mailman unshunt" but nothing happened. Is there a way to reprocess the bad queue? Also, what exactly is the bad queue? Thank you, Ken KA6KEN (happy field day weekend)

2 4

re-injecting emails that were not archived
by Ken Alker 25 Jun '23

25 Jun '23

I have just migrated from a mailman 3.2.2 Debian package installation to a mailman 3.3.8 source install (in a Python virtual environment as mailman user) on an Ubuntu 20.04.6 LTS system. Several months ago, the system had been upgraded from mailman V2 to mailman V3.2.2. I noticed when I came onto the project last week that there were 140 messages stuck in the "shunt" queue for the two lists hosted by this server (I have no idea why and the old logs were not available and I don't recall the results of "mailman qfile", assuming that had shed some light on the reason why they were shunted). In any event, I unshunted these messages and they flowed out to the subscriber's email addresses successfully. What I was not expecting is that the system did not inject any of these emails into the archive. AFAICT, the messages are no longer anywhere on the system (but I could be mistaken). Here are my questions: 1) Why would these emails not have been injected into the archive? 2) Is there some way for me to re-inject these messages into the two lists? The only place I (THINK I) have them is in my own personal IMAP box since I'm a subscriber to the lists. 3) Can this be done without the emails being re-delivered to subscribers? Thank you, Ken

2 1

Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question
by Ken Alker 25 Jun '23

25 Jun '23

As an aside, for anyone else who is trying to do the same (and to give some background into my procedures so far), I have been following these references: <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-virtualenv> My goal is to create the least change to file locations and configuration files as possible (I may move things into more "source-installed centric" locations once I have things working again), thus, many files are still in the original Debian package-allocated directories. That said, I was forced to move mailman3web.db to /opt/mailman/web as sqlite (and, hence, mailman-web) simply could not open the database as user mailman from my virtual environment (even with mailman3web.db file permissions set to 777 and owner.group set to mailman.mailman). So far I've gotten mailman running properly and handling the mailing lists, however, I have not gotten the web interface working again.

2 6

Importing MBOX from custom listserv to MM3?
by Thomas Ward 25 Jun '23

25 Jun '23

We are looking at moving from a home grown listserv system at a client to potentially MailMan3 for the lists platform instead. We have historic thread data from the homegrown systems in mbox form. Is there a way to import that into MM3 for indexing in the archiver there so we dont need to keep the (literally massive) MBOX file? Sent from my Galaxy

2 2

Importing mbox file into MM3
by Mark 23 Jun '23

23 Jun '23

Hi All I'm trying to import a large mbox file from a MM2 list into a new list on MM3. The new MM3 list has 3 test emails in its archive. # cd /usr/share/mailman3-web/ # python3 manage.py hyperkitty_import -l LISTNAME@DOMAIN /home/mark/tmp/LISTNAME.mbox Importing from mbox file /home/mark/tmp/LISTNAME.mbox to LISTNAME@DOMAIN Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list LISTNAME@DOMAIN'. That all seems pretty good. Then I attempt to rebuild the archive. # python3 manage.py update_index_one_list LISTNAME@DOMAIN Indexing 3 emails The import or rebuild has failed as it's just rebuilding the existing archive of the 3 test messages. What am I doing wrong? Thanks Mark

2 2

Where in database are subject prefix sequences stored?
by Thomas Ward 22 Jun '23

22 Jun '23

I am using numeric prefixes for a list, such that it's `[ListName-000012]`. Where would that sequence indicator be stored in the database? Postorious' database? Hyperkitty's database? I ask because I'm rebuilding a home-grown listserv solution using Mailman3 and the main requirement is the thread IDs being *properly sequential* with the current implementation, so I have to set the "next ID in sequence" to a start value. I don't see this clearly in the DB where the sequence value would be stored, so if anyone knows that'd be great to know so I can get this working. Thomas

2 2

Help needed to create filters that were working in Mailman 2.
by mrl＠psfc.mit.edu 22 Jun '23

22 Jun '23

How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? I could do this using the anti-spam filters in mailman 2, as there was a Accept option. But there is no Accept option in Mailman 3 (that I can find). I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. Thanks for any suggestions. - Mark

3 4

toward improving correctness when running on single core system ...
by Nelson Strother 21 Jun '23

21 Jun '23

I recognize that most real computer systems now are equipped with multiple CPUs, usually with each CPU having multiple cores or hardware threads. But when one obtains a computer system from a service provider with a small expected load, it is likely that a virtual computer system will provide only a single core. Yes, one can obtain a multi-core virtual system, maybe for only twice the cost; but it would seem wasteful to make that choice solely to support starting and stopping the Mailman3 program when the system load at all other times is satisfied by a single core system. From my observations, mailman 3.3.8 is unreliable when running on a single core system. When `mailman start` is issued, there is a moderately high probability that one or more of the thirteen runner processes will not survive this startup phase. Depending upon the current usage of the mailman installation, one may or may not notice this fact. In either case, `mailman status` provides the same information, with no hint of missing or damaged capabilities when one or more of the runner processes are stillborn. [1] One potential improvement would be to increase the lifetime of the locks used by each of the runner processes during `mailman start`. [2] Based on a small sample of runs of `mailman start`, this change may provide correctness (i.e. I have yet to see a runner process go MIA). But it still seems unsatisfactory for availability / performance, as the elapsed wall clock time for the system to settle down and be functional and responsive is approximately 13 minutes. While this is an improvement from the 20 minute or greater delays observed before making this change, it still differs greatly from the nearly instantaneous startup time experienced on multicore / multiprocessor systems. The best "performance" I have yet obtained on this single core system is WITHOUT the change in [2] below, but by crossing abstraction boundaries and reducing the amount of time this single CPU spends futilely busy waiting for itself when it has not provided an opportunity for another process (maybe even the process currently holding the desired lock) to make any progress. [3] With this change, "only" 9 minutes elapsed wall clock time is wasted (with maybe only the middle 4 minutes at 100% CPU utilization) before the system settles down and is functional and responsive. However, ample room for improvement remains. [4] Please suggest better ideas or corrections. Nelson [1] For a few examples of these failures, see: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] Here is a diff from the original mailman/database/factory.py (or .../mailman/.local/lib/python3.9/site-packages/mailman/database/factory.py if you wish to apply this to an installed system): > 25a26 > > from datetime import timedelta > 53c54,55 > < with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck')): > --- > > with Lock(os.path.join(config.LOCK_DIR, 'dbcreate.lck'), > > timedelta(seconds=30)): which increases the delay from the default of 15 seconds to 30 seconds before another process will be empowered to break the lock being held by one of mailman's runner processes, which leads to the death of a process. [3] Here is a diff from the original .../mailman/.local/lib/python3.9/site-packages/flufl/lock/_lockfile.py : > 7a8 > > import subprocess > 338a340,344 > > if sys.platform.startswith('linux') and \ > > (len(subprocess.check_output(["lscpu", "-p"]).splitlines()) == 5): > > # there is only one processor [four lines of comments, and only one line for one CPU] > > # let another process run before joining the traffic jam for this lock > > os.system('sleep 20s') For possible similar benefits on other platforms, one should also include variations on this theme using something like e.g.: > > if sys.platform.startswith('win32') and \ > > subprocess.check_output('wmic path win32_Processor get NumberOfLogicalProcessors').strip().endswith(b'1'): I seriously doubt all (or even any?) other users of the flufl.lock package would benefit from this exact change ... but many may benefit from sleeping for e.g. a half-second when on a single core? In the case of Mailman3, sleeping for a fixed duration shorter than 20 seconds retains the original problem of broken locks and runner process death, while sleeping for a fixed duration longer than 20 seconds leads to an increase in both the wall clock delay time as well as the CPU time consumed during `mailman start`. I have not experimented with random or staggered delays, which may further reduce the number of simultaneously blocked waiters for this lock. [4] I have seen `mailman start`complete in less than 1 second wall clock time on a multicore / multiprocessor system. All of these observations made with mailman 3.3.8 as installed via pip.

5 8

How to tell who moderated a post?
by bryan.kartzman＠yu.edu 21 Jun '23

21 Jun '23

Is there any way to tell which moderator of a list approved a particular post to that list?

2 3

Re: mailman3 auto-disabling of subscriptions
by Mark Sapiro 19 Jun '23

19 Jun '23

On 6/17/23 17:02, Mike Wertheim wrote: > I set `remove_dkim_headers: yes` in the [mta] section of mailman.cfg. > > I'm seeing a bunch of these errors in the logs: > 2023-06-17 18:57:11 1qAbMA-005Y7W-HP ** mike.wertheim(a)gmail.com > <mailto:mike.wertheim@gmail.com> R=dnslookup_single_domain > T=remote_smtp_single_domain H=alt2.gmail-smtp-in.l.google.com > <http://alt2.gmail-smtp-in.l.google.com> [172.253.62.26]: SMTP error > from remote mail server after end of data: 550-5.7.26 Unauthenticated > email from gmail.com <http://gmail.com> is not accepted due to > domain's\n550-5.7.26 DMARC policy. Please contact the administrator of > gmail.com <http://gmail.com> domain\n550-5.7.26 if this was a legitimate > mail. Please visit\n550-5.7.26 > https://support.google.com/mail/answer/2451690 > <https://support.google.com/mail/answer/2451690> to learn about the\n550 > 5.7.26 DMARC initiative. > w13-20020a05622a190d00b003fde5babbf5si1170418qtc.14 - gsmtp Your issue is mail From: the gmail.com domain to the list and sent to gmail users is being bounced because it fails DMARC. I.e. Gmail applies a DMARC policy of p=reject to mail From: gmail.com even though it's published DMARC policy is p=none. You need to apply DMARC mitigations to this mail. Unfortunately, this requires setting DMARC Mitigate unconditionally to Yes. Mailman 2.1 has a feature to apply DMARC mitigation to messages From: specific domains regardless of any domain specific DMARC Policy. Unfortunately this hasn't been implemented in Mailman 3 yet. I just filed https://gitlab.com/mailman/mailman/-/issues/1084 for that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1

Where does sender postorius@ come from?
by Jens Günther 19 Jun '23

19 Jun '23

I just realized, that mails for registering an account and/or resetting ones password are obviously sent from postorius@SERVE_FROM_DOMAIN. Why are they not sent from MAILMAN_ADMIN_EMAIL? The problem is: - an account is trying to register with a mailaddress from a HostEurope-server - HostEurope-Servers are doing Sender-Callouts (bad practise :-D) to verify that a mailaccount exists - mail is then bouncing, b/c those are not answered (shoud I?): status=bounced (host [80.237.138.5] said: 550-Sender verification is required but failed. - bounce then can't be processed, since mailaccount does not exist :-D status=bounced (mail for SERVE_FROM_DOMAIN loops back to myself) Am I missing something are shouldn't it be better to send those mails from MAILMAN_ADMIN_EMAIL? (I don't want to mess with these sender callouts or change anything, HostEurope has been a little bit of a pain in the ... with mailinglists and not much help at all). Thanks in advance, Jens.

3 8

Proxy error.
by Mark London 18 Jun '23

18 Jun '23

My server has several aliases. And Chrome's cookies sometimes get messed up because of it. Several users get a proxy error when trying to connect to the mailman website. One person just fixed it by clearling cookies, although this is not a great solution. Error log says "You may need to add 'psfcmail2.psfc.mit.edu' to ALLOWED_HOSTS". But it is already there in /etc/mailman/settings.py Or should it go elsewhere? Thanks. - Mark Chrome: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server Apache/2.4.52 (Ubuntu) Server at lists.psfc.mit.edu Port 443Error log: ERROR 2023-06-18 19:11:11,568 2114 django.security.DisallowedHost Invalid HTTP_HOST header: 'psfcmail2.psfc.mit.edu'. You may need to add 'psfcmail2.psfc.mit.edu' to ALLOWED_HOSTS. Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 56, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/utils/deprecation.py", line 135, in __call__ response = self.process_request(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/middleware/common.py", line 48, in process_request host = request.get_host() File "/opt/mailman/venv/lib/python3.10/site-packages/django/http/request.py", line 152, in get_host raise DisallowedHost(msg) django.core.exceptions.DisallowedHost: Invalid HTTP_HOST header: 'psfcmail2.psfc.mit.edu'. You may need to add 'psfcmail2.psfc.mit.edu' to ALLOWED_HOSTS

1 1

mailman3 auto-disabling of subscriptions
by Mike Wertheim 17 Jun '23

17 Jun '23

I'm running an email list on mailman3. My users are getting inundated by messages saying that their subscriptions have been disabled due to their bounce score exceeding the mailing list's bounce_score_threshold. But there is nothing wrong with these users' email accounts. They are all perfectly fine. Apparently the issue is somehow related to spam. Whenever I (as admin) get these emails, I just unsubscribe the user and then re-subscribe them. But also, the user gets confused and emails me about it, which unnecessarily takes up their time and mine. The relevant list settings are currently... bounce score threshold: 5 bounce info stale after: 7d bounce disabled warning interval: 7d bounce disable warnings: 5 What's the best way to fix this? I'm considering reducing "bounce info stale after" to "2d" and/or increasing "bounce disabled warning interval" to "90d".

3 5

Postorius -owner messages
by ssehi＠nebraska.edu 16 Jun '23

16 Jun '23

I manage a number of lists for non-technical users that are considered owners of their own lists. Some of them have expressed that they would like to emulate some other mailing list services' "Quiet" owners for people that need to be able to access the list settings for administrative reconciliation as well as a fallback, but want to leave subscription requests or approval of messages to others that are more involved in the day-to-day management. They'd like to disable owner delivery for themselves, and I'd like to not make the change for them using the shell every time I get one of their requests. We have a Postorius front end set up and working, but it doesn't appear that disabling delivery using the List-based preferences in the Postorius interface stops those Owner communications. Is there a way to allow users to disable that natively in Postorius? Thanks, Sam

2 2

Apache proxy error messages.
by Mark London 15 Jun '23

15 Jun '23

I have two users who are getting a proxy error message when they try to connect her our mailman server: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request Reason: Error reading from remote server Apache/2.4.52 (Ubuntu) Server at lists.psfc.mit.edu Has anybody else in an errorlike this before? One person manage to get around this by going in incognito mode on the browser. Does that make any sense?

2 1

unrequested unsubscription
by Mike Wertheim 15 Jun '23

15 Jun '23

I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. A few of the list members are reporting that they received Email Address Unsubscription Confirmation emails, but claim that they never requested to be unsubscribed. (All are Gmail users. but they might be coincidental, since most list members are Gmail users.) Has anyone seen this behavior before? Any ideas on what might be happening?

3 3