- Mailman-users - lists.mailman3.org

mailman-full question
by flatley Sept. 25, 2022

Sept. 25, 2022

Hello, i have successfully installed mailman3 with postgres using the venv method - testing the install of mailman-full package i have some questions - to configure the db in venv i would use mailman-web migrate - this works fine - but mailman-full install does not seem to include mailman-web or mailman3-web - the mailman info cmd works fine - do i need to also install mailman-web? i had thought the mailman-full included all components thanks

4 5

invalid parameter response of the rest-api
by Jacob Sievert Sept. 22, 2022

Sept. 22, 2022

Hello, Since a few days we get an error response from our automated membership script. We use the following code to control the membership for some lists: ``` def mailinglist_manage(list_address, members): """ make sure all 'members' are present on the list and no remove everyone else list_address : mail address of mailing list to manage addresses : mail address that are supposed to be on the list """ print("[*] update subscriptions for {}".format(list_address)) ml = mmc.get_list(list_address) # make sure we dont spam users ml.settings['send_welcome_message'] = False ml.settings.save() addresses = set(members.keys()) ml_members = ml.members ml_addresses = set((x.address.__str__() for x in ml_members)) for addr in ml_addresses - addresses: print("unsubscribe {} from {}".format(addr, list_address)) ml.unsubscribe(addr) for addr in addresses - ml_addresses: print("subscribe {} to {}".format(addr, list_address)) ml.subscribe(addr, members[addr], pre_verified=True, pre_confirmed=True, pre_approved=True) ``` Since Tuesday without any update performed by us we get the following error from the script when it's running: ``` Traceback (most recent call last): File "./mail_user_control.py", line 423, in <module> mailinglist_manage("XXX(a)EXAMPLE.COM", members) File "./mail_user_control.py", line 412, in mailinglist_manage pre_verified=True, pre_confirmed=True, pre_approved=True) File "/root/.local/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 339, in subscribe response, content = self._connection.call('members', data) File "/root/.local/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 400: Invalid Parameter "subscriber": . ``` If you have an idea why that code now returns this. I would be thankful. regards Jacob Sievert

4 7

Help understanding why some users don't receive emails
by Stephen Daniel Sept. 22, 2022

Sept. 22, 2022

Mailman3 people --- I'm a novice at running mailman, so any advice would be appreciated. I manage a few small lists using a mailman3 server. A few of my users complain they do not receive emails. Looking at one user in particular, I see in /var/log/syslog that postfix is sending the email. There is nothing in bounce.log. They are the only user who uses that particular email domain (embarqmail.com ). Is there anything I can do to debug why they do not get the emails? Or is this up to them and their email provider? Thanks! -- Steve Daniel

3 2

Hyperkitty displaying example.com
by Mark Dale Sept. 22, 2022

Sept. 22, 2022

Hi On a new installation I'm seeing "example.com" displayed at the top of the HyperKitty pages. I was expecting to see "lists.mydomainname.com", so I think I've missed something somewhere. Also, when a user signs up, the confirmation email reads as: ////////////////////////// SUBJECT: [example.com] Please Confirm Your E-mail Address FROM: postorius(a)lists.mydomainname.com BODY: Hello from example.com! You're receiving this e-mail because user yogibear has given your e- mail address to register an account on example.com. To confirm this is correct, go to https://lists.mydomainname.com/mailman3/accounts/confirm-email/NQ:1obAI3:Yw… Thank you for using example.com! example.com ////////////////////////// Any clues greatly appreciated. Thanks, Mark

2 2

Messages not being archived
by Mark Dale Sept. 20, 2022

Sept. 20, 2022

Hi I've just installed Mailman 3 using the Debian 11 package. Mailman-Version: 3.3.3 HyperKitty version 1.3.4 Postorius Version 1.3.4 The first list that I've added is receiving and sending mail okay, however the messages are not being archived. The logs report a HyperKitty error. I've copy-pasted that in at the end of this email. I've checked the following: ============================== /etc/mailman3/mailman.cfg contains: [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg ============================= The list has archiving configured on in Postorius. - Archive policy: Private archives - Active archivers: hyperkitty ============================= /etc/mailman3/mailman-hyperkitty.cfg has: [general] base_url: https://lists.mydomain.com/mailman3/archives #base_url: https://lists.mydomain.com/mailman3/hyperkitty/ api_key: aaaaaaaaaaaaaaaaaaaaaa ============================= /usr/share/mailman3-web/settings_local.py contains: ALLOWED_HOSTS = [ "localhost", '*' ] MAILMAN_ARCHIVER_KEY = 'aaaaaaaaaaaaaaaaaaaaaa' ============================= The headers of the emails received from the list show blanks for Archived-At and List-Archive: X-Mailman-Version: 3.3.3 Precedence: list Archived-At: <> List-Archive: <> ============================= /var/log/mailman3/mailman.log The errors in the log contain messages (that I'm clueless about) regarding HyperKitty. Sep 20 01:05:54 2022 (1293) HyperKitty failure on https://lists.mydomain.com/mailman3/archives/api/mailman/archive Sep 20 01:05:54 2022 (1293) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ... <title>503 Service Unavailable</title> ... Sep 20 01:05:54 2022 (1293) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ... ============================= If anyone can point me in the right direction to get the archive happening, that'd be grand. Cheers, Mark

1 1

How to delete non-users
by Allan Hansen Sept. 17, 2022

Sept. 17, 2022

Hi all, This is a bit of an emergency: I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. For individuals I have been able to delete their non-membership and they then could subscribe properly. I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). Can anyone help me find out how to a. delete all non-members of all my lists b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) Any help with this is appreciated. Yours, Allan I'm still at Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] My system used to be kept up to date by EMWD, but since Brian died have not been able to get it updated, and I'm too scared (from my attempts at installing MM3) to attempt it myself. If the above can only be solved via an update, I'd appreciate a referral.

3 10

Held message notifications ending up in junk
by Tibor Molnar Sept. 15, 2022

Sept. 15, 2022

Hi there, I wonder if anyone else if having this trouble that all the held message notifications are landing in junk folder. Regards, Tibor

4 5

Messages not going to held queue
by Mail Person Sept. 14, 2022

Sept. 14, 2022

Hi all, Not sure why, but messages set to be held for moderation are appearing to be discarded. I've tried creating a new test list, adjusting settings at the user and list level, but when a user sends a message that should be held for moderation, nothing happens. smtp.log shows the message is going through but it doesn't get to the moderation queue.

3 8

Message-Footer after migrating to Mailman3
by christopher.claus＠tgcamberg1848.de Sept. 13, 2022

Sept. 13, 2022

Hello together, I migrated a number of lists from mailman2 to mailman3 using the import functionality. Everthing works fine and the new lists are in use. Currently I´m using the maxking-docker-images with postorius: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.5 (default, Feb 19 2021, 09:27:16) [GCC 9.3.0] After this migration I started a refactoring with the list-styles specially with message-footers. Already the old lists in mailman2 were confused in some configuration details an I was clear to import this "misconfiguration" and clean it up afterwards. But this was much more difficult than expected: some lists are using a footer (from the mailman2-config) and there is no record in the template-section visible. Further I found no configuration item which points to this "old" footer. I found the file [code] /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt [/code] which includes the old footer: [code] _______________________________________________ $display_name Mailingliste -- $listname Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} [/code] but no configuration item to disable this behaviour. I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used - in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. In the logfiles I found an error and a warning: [code] ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer [/code] Obviously I have a problem with the hostname. I set [code] POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 [/code] where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost [code] wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… [/code] will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. Best regards, chrclaus

6 18

"The content of this message was lost."
by skenny＠scss.tcd.ie Sept. 12, 2022

Sept. 12, 2022

I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? Thanks for any advice. Stephen PS: The Mailman web interface "System Information" link reports: Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0]

2 2

How to set uWSGI buffer size in mailman3 with Dcoker
by bob B Sept. 8, 2022

Sept. 8, 2022

Running into an issue where users are getting a 502 bade gateway and we traced it down to the headers that are getting sent when they request web pages. This looks like our issue ********************* By default, uWSGI allocates a very small buffer (4096 bytes) for the headers of each request. If you start receiving “invalid request block size” in your logs, it could mean you need a bigger buffer. Increase it (up to 65535) with the buffer-size option. ********* So any idea on how to set this in mailman3 running in the maxking docker environment?

2 2

mailman3 not working for mailman21 lists
by blup＠fortytwo.ch Sept. 6, 2022

Sept. 6, 2022

I installed mailman3 on a server where mailman21 was installed before. Newly created mailinglists work fine. But if I create mailinglists with a name that was previously used on mailman21 nothing works (same behaviour with and without import of old configs and archives; no logs). I purged all old mailman21 config and data and also old postfix aliases (or at least I do think so). If I send a mail to old list list1(a)a.b and new list list2(a)a.b I get the following logs /var/log/mail.log Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2(a)c.a.b>, orig_to=<list2(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1(a)c.a.b>, orig_to=<list1(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) /var/log/mailman3/smtp.log ug 21 22:17:40 2022 (934) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 21 22:17:40 2022 (934) Peer: ('127.0.0.1', 44746) Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) handling connection Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) sender: .... Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list2(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list2(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list1(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list1(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() Aug 21 22:17:46 2022 (936) <166111306097.933.1775779871266718007@...> smtp to list2(a)a.b for 1 recips, completed in 3.1437485218048096 seconds How can I get more info on why the mail for list1 isn't processed? Where could old mailman21 or postfix info on list1 be stored that causes mailman3 to not handle the list properly? How can I diff the config between list1 and list2 from the command line? Regards Diana

5 12

FYI: Django security releases issued: 4.0.6 and 3.2.14
by Guillermo Hernandez (Oldno7) Aug. 29, 2022

Aug. 29, 2022

https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ Django security releases issued: 4.0.6 and 3.2.14 Posted by *Mariusz Felisiak* on Julio 4, 2022 In accordance with our security release policy <https://docs.djangoproject.com/en/dev/internals/security/>, the Django team is issuing Django 4.0.6 <https://docs.djangoproject.com/en/dev/releases/4.0.6/> and Django 3.2.14 <https://docs.djangoproject.com/en/dev/releases/3.2.14/>. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible. CVE-2022-34265: Potential SQL injection via Trunc(kind) and Extract(lookup_name) arguments Trunc() and Extract() database functions were subject to SQL injection if untrusted data was used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. This security release mitigates the issue, but we have identified improvements to the Database API methods related to date extract and truncate that would be beneficial to add to Django 4.1 before it's final release. This will impact 3rd party database backends using Django 4.1 release candidate 1 or newer, until they are able to update to the API changes. We apologize for the inconvenience. Thanks Takuto Yoshikai (Aeye Security Lab) for the report. This issue has severity "high" according to the Django security policy. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

5 18

Migrated from MM2 to MM3, all is well except *one* list
by Scott Courtney Aug. 28, 2022

Aug. 28, 2022

Hello, all I have migrated a multi-list server from MM2 to MM3, on Debian 11, and migrated about half a dozen lists with fairly large archives. Absolutely everything has been working for a couple of months, but I am still unable to get one specific list to send mail to its subscribers. Of course, the first place I started was the logs, but that's the problem -- even with logging turned up, it appears to be failing silently as it connects to the MTA. Here's a summary of the environment: OS: Debian Linux 11, 64-bit, on a virtual machine MTA: Exim 4.94.2 List server: Mailman 3.3.3 (installed from Debian repo) Database: MariaDB 10.5.15 All daemons are running on the same host, and communication is either UNIX socket or loopback network interface, for security. Web server: Apache 2.4.53, with proxy to WSGI per the MM3 setup guide Symptom: There are six lists on the server. All six can accept inbound traffic and will post the messages to the (always private, in this environment) archives. The web interface is working perfectly. Five of the lists also can send out messages to subscribers, but the sixth list cannot send traffic to the MTA, or is not attempting to do so. Tests run so far (all resulting in successful posting to archives, but no outbound mail): * Originate mail from inbound SMTP to the list address. * Originate mail from the web UI as a member/moderator. * Originate mail from the web UI as the site admin (also the list owner). * Originate mail from both inbound SMTP and web UI by multiple users. Log data for the inbound traffic (typical test message, some data redacted): 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz <= REDACTED H=REDACTED:25 P=esmtps X=TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128 CV=no K S=2552 DKIM=REDACTED id=REDACTED T="TEST 8.27.001" 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz => MY_LIST(a)lists.MY_DOMAIN R=mailman_main_director T=mailman3_transport H=127.0.0.1 [127.0.0.1] I=[127.0.0.1] C="250 Ok" 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz Completed Log data for MM3 smtp.log (again, partially redacted): Aug 27 15:11:57 2022 (690182) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 27 15:11:57 2022 (690182) Peer: ('127.0.0.1', 48170) Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) handling connection Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'LHLO REDACTED' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'MAIL FROM:<REDACTED>' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) sender: REDACTED Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'RCPT TO:<erevnite(a)lists.4th.com>' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) recip: MY_LIST(a)lists.MY_DOMAIN Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'DATA' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'QUIT' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) connection lost Aug 27 15:11:57 2022 (690182) Connection lost during _handle_client() Originally I thought the "connection lost" indicated a failure, but that is happening for all the lists, and also on successful traffic. Since it occurs after the QUIT command in the SMTP session, and based on some online searching, my current understanding is that this is harmless and simply indicates the MTA closed the socket after the QUIT. (Please correct me if that is wrong.) Log data for mailman.log, with partial redaction: Aug 27 15:11:57 2022 (690181) ACCEPT: <REDACTED> Aug 27 15:11:59 2022 (690178) HyperKitty archived message <REDACTED> to https://lists.MY_DOMAIN/hyperkitty/list/MY_LIST@lists.MY_DOMAIN/message/G3D… 19:11:59 [Q] INFO Enqueued 518 19:11:59 [Q] INFO Enqueued 519 19:11:59 [Q] INFO Enqueued 520 19:11:59 [Q] INFO Enqueued 521 19:11:59 [Q] INFO Enqueued 522 19:11:59 [Q] INFO Enqueued 523 19:11:59 [Q] INFO Enqueued 524 INFO 2022-08-27 19:11:59,648 690164 hyperkitty.views.mailman Archived message <REDACTED> to https://lists.MY_DOMAIN/hyperkitty/list/MY_LIST@lists.MY_DOMAIN/message/G3D… [pid: 690164|app: 0|req: 4688541/4688541] 2600:3c04::f03c:91ff:fe02:9cc1 () {64 vars in 1255 bytes} [Sat Aug 27 19:11:59 2022] POST /hyperkitty/api/mailman/archive?key=xombsjgLDqe6d1oxvBaQWH4ZT81uCEjH => generated 113 bytes in 110 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) 19:12:00 [Q] INFO Process-1:4 processing [update_from_mailman] 19:12:00 [Q] INFO Process-1:3 processing [sender_mailman_id] 19:12:00 [Q] INFO Process-1:2 processing [rebuild_thread_cache_new_email] 19:12:00 [Q] INFO Process-1:1 processing [compute_thread_positions] 19:12:00 [Q] INFO Processed [rebuild_thread_cache_new_email] 19:12:00 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_recent] 19:12:00 [Q] INFO Processed [sender_mailman_id] 19:12:00 [Q] INFO Process-1:3 processing [rebuild_mailinglist_cache_for_month] 19:12:00 [Q] INFO Process-1:1 processing [check_orphans] 19:12:00 [Q] INFO Processed [compute_thread_positions] 19:12:00 [Q] INFO Processed [rebuild_mailinglist_cache_for_month] 19:12:00 [Q] INFO Processed [check_orphans] 19:12:00 [Q] INFO Processed [rebuild_mailinglist_cache_recent] 19:12:00 [Q] INFO Processed [update_from_mailman] [pid: 690164|app: 0|req: 4693691/4693691] 184.94.240.88 () {60 vars in 929 bytes} [Sat Aug 27 19:21:50 2022] HEAD / => generated 0 bytes in 2 msecs (HTTP/1.1 301) 6 headers in 204 bytes (1 switches on core 0) [pid: 690164|app: 0|req: 4693694/4693694] 184.94.240.88 () {60 vars in 1009 bytes} [Sat Aug 27 19:21:50 2022] HEAD /postorius/lists/ => generated 7136 bytes in 142 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 1) There is nothing at all in the Exim log indicating an outbound transaction was attempted by Mailman. I know Exim and Mailman are communicating because all the lists use the same SMTP configuration for Exim and Mailman (i.e., the non-working list is not in any way exceptional). I've done a lot of searching online to find a solution, and I did see that a couple of others had asked about this type of problem, but the only one I found that got a response had an issue that didn't apply in my small environment. Absent any other ideas, I'm going to try inserting some trace logging into the Python code, but I can't figure out what's wrong here. I've even gone to the point of looking at the SQL rows to verify this list is exactly parallel to another working list, except its name and integer ID numbers for various unique auto-increment keys. Any suggestions are appreciated. Thanks!

2 2

Using REST with CLI using curl .... help needed
by Krešimir Mihalj Aug. 27, 2022

Aug. 27, 2022

Hi ! I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... To add member using CLI i tried this command: curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members and I got this response: Missing parameters: list_id, subscriber What is wrong in above command here ? ..... I need to add user: user(a)email.com to list: list(a)domain.com Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com I actually create PHP application .... but CLI example is easy to reproduce in PHP function AddUserToList($user,$lista) { $url = 'http://llocalhost:8001/3.0'; $request_url = $url . '/members'; $data = array("list_id" => $lista,"subscriber" => $user ); $postdata = json_encode($data); $ch = curl_init($request_url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_USERPWD, "restadmin:restpass"); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_POSTFIELDS, $postdata); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/json')); $result = curl_exec($ch); curl_close($ch); print_r ($result); } AddUserToList('user(a)email.com','list.domain.com');

6 8

DKIM header not added to subscribe/unsubscribe notification email
by Philip Colmer Aug. 24, 2022

Aug. 24, 2022

I have a Mailman 3 server set up with OpenDKIM and Postfix. Each of the lists has been configured so that the DMARC mitigation is "Replace From: with list address" and DMARC Mitigate unconditionally is selected. Everything seems to be working fine *except* when the system sends a notification email to the list owners of someone subscribing or unsubscribing. *Those* emails do not have the DKIM header added and are getting trapped by anti-spam systems as a result. Any suggestions as to why this might be, please? I cannot see anything in the configuration for OpenDKIM or Postfix that might allow just those messages to go out unsigned. In case it is relevant/important, this system is running: mailman 3.3.5 mailman-hyperkitty 1.2.0 mailman-web 0.0.5 mailmanclient 3.3.3 Thank you. Regards Philip

2 2

MM3 not starting
by max.diener＠hpi.de Aug. 22, 2022

Aug. 22, 2022

Hi, i am trying to install MM3 and had a few issues with it. First i was trying the Mailman3-full package for Debian which didnt work good for me. There was missing paths and files, after some research i found out it may not be well maintained right now. I was working to fix the issue i come up with but had no luck with it. After that i was trying this Howto: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 the Installation worked in some aspect. i had a running mailman3 service but the webinterfaces was not working. After some searching i found a issue that was stating that the current release had a bug in it wich made it not working. For instance was the config file different for "systemctl start mailman3" then when i was checking it "mailman info" and some paths was not like in the instructions again, this time i added the folders and put the files needed for it in to it but could not make it work. i kept digging and find out for prod it is best practice to install in a virtual environment so i waited for the bug to fix and took this Installation Instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was a little bit confused that there seems to be two spots from the official site where you can find Installation Instructions: https://wiki.list.org/DOC/ and https://docs.list.org/ since the last one made it seem like it was newer i choose the venv installation instructions. From the install instructions at https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was seeing that there is also some folders not showing up like mentioned in the howto: /op/mailman/mm was not there. In the part where you configure mailman core it says you need to add the /etc/mailman/mailman.cfg file it shows that the path is used for the hyperkitty config as well as it is the path vor the "var_dir: /opt/mailman/mm/var". i added the paths and at the point in the install instructions here https://docs.list.org/en/latest/install/virtualenv.html#starting-mailman-au… i checked if i can start mailman3 now but still fail to do so. when i check "journalctl -xe" i find the following information but cant get more information on how to fix it in the net with it: Aug 22 09:54:05 mailman3test mailman[55134]: Starting Mailman's master runner Aug 22 09:54:05 mailman3test mailman[55134]: Generating MTA alias maps Aug 22 09:54:05 mailman3test systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted Aug 22 09:54:12 mailman3test mailman[55146]: Traceback (most recent call last): Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/bin/runner", line 8, in <module> Aug 22 09:54:12 mailman3test mailman[55146]: sys.exit(main()) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Aug 22 09:54:12 mailman3test mailman[55146]: return self.main(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1055, in main Aug 22 09:54:12 mailman3test mailman[55146]: rv = self.invoke(ctx) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return ctx.invoke(self.callback, **ctx.params) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 760, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return __callback(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Aug 22 09:54:12 mailman3test mailman[55146]: return f(get_current_context(), *args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/bin/runner.py", line 188, in main Aug 22 09:54:12 mailman3test mailman[55146]: runner.run() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 255, in run Aug 22 09:54:12 mailman3test mailman[55146]: self.lmtp.start() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 210, in start Aug 22 09:54:12 mailman3test mailman[55146]: raise self._thread_exception Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 176, in _run Aug 22 09:54:12 mailman3test mailman[55146]: srv: AsyncServer = self.loop.run_until_complete(self.server_coro) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete Aug 22 09:54:12 mailman3test mailman[55146]: return future.result() Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1460, in create_server Aug 22 09:54:12 mailman3test mailman[55146]: infos = await tasks.gather(*fs, loop=self) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1400, in _create_server_getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: infos = await self._ensure_resolved((host, port), family=family, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1396, in _ensure_resolved Aug 22 09:54:12 mailman3test mailman[55146]: return await loop.getaddrinfo(host, port, family=family, type=type, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 856, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: return await self.run_in_executor( Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run Aug 22 09:54:12 mailman3test mailman[55146]: result = self.fn(*self.args, **self.kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags): Aug 22 09:54:12 mailman3test mailman[55146]: socket.gaierror: [Errno -2] Name or service not known Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Aug 22 09:55:01 mailman3test CRON[55177]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session closed for user root Aug 22 09:55:34 mailman3test systemd[1]: mailman3.service: start operation timed out. Terminating. Aug 22 09:55:35 mailman3test systemd[1]: mailman3.service: Failed with result 'timeout'. Anybody knows whats going on and what i am doing wrong?

2 1

MM21 -> MM3 Migration: Importing archives hitting a snag
by Odhiambo Washington Aug. 17, 2022

Aug. 17, 2022

With mailman installed using virtualenv /opt/mailman/mm/venv: I am trying to import list archives after importing the configs. python manage.py hyperkitty_import -l listname(a)site.name /var/list/archives/private/listname.mbox/listname.mbox python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory Where is manage.py PATH? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 1

List Migration from MM2.1 -> MM3
by Odhiambo Washington Aug. 15, 2022

Aug. 15, 2022

So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04. I have created a list in postorius - it has the same name as my old list in MM2. [image: MM3.png] Now, following - https://docs.mailman3.org/en/latest/migration.html - I change user to mailman so as to run the migration. mailman@lists:~$ pwd /opt/mailman mailman@lists:~$ id uid=1003(mailman) gid=1002(mailman) groups=1002(mailman),4(adm),38(list) mailman@lists:~$ */opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke <skunkworks(a)lists.my.co.ke> /var/list/lists/skunkworks/config.pck *# running without specifying the absolute path is not working! Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help. Error: No such list: skunkworks(a)lists.my.co.ke mailman@lists:~$ ls -al /var/list/lists/skunkworks/config.pck -rw-rw---- 1 root list 63765 Aug 14 11:10 /var/list/lists/skunkworks/config.pck mailman@lists:~$ exim -bt skunkworks(a)lists.my.co.ke skunkworks(a)lists.my.co.ke router = mailman3_router, transport = mailman3_transport mailman@lists:~$ What am I missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: MM3.png Replaced multipart/alternative part with first alternative.

2 8

Gunicorn problem?
by Odhiambo Washington Aug. 14, 2022

Aug. 14, 2022

Ubuntu 22.04, Mailman3. I am having two problems with the installation of MM3. This has been installed today by referring to https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 1. The following error while trying to access https://my.site.address/mailman3 root@lists:/opt/mailman/mm/var/logs# less error.log Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 47, in inner File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py", line 117, in __call__ File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 49, in inner response = get_exception_response(request, get_resolver(get_urlconf()), 403, exc) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 114, in response_for_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 153, in handle_uncaught_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/decorators.py", line 130, in _wrapped_view response = view_func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/views/defaults.py", line 97, in server_error return HttpResponseServerError(template.render()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 170, in render context.template_name = self.name File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 162, in _render def _render(self, context): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 938, in render bit = node File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 905, in render_annotated if context.template.engine.debug and not hasattr(e, 'template_debug'): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 106, in render url = self.url(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 103, in url return self.handle_simple(path) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 117, in handle_simple from django.contrib.staticfiles.storage import staticfiles_storage File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/contrib/staticfiles/storage.py", line 17, in <module> from django.utils.deprecation import RemovedInDjango31Warning ImportError: cannot import name 'RemovedInDjango31Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 133, in __call__ response = self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 130, in get_response # response middleware and then render the response File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 49, in inner response = get_exception_response(request, get_resolver(get_urlconf()), 403, exc) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 114, in response_for_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 153, in handle_uncaught_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/decorators.py", line 130, in _wrapped_view response = view_func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/views/defaults.py", line 97, in server_error return HttpResponseServerError(template.render()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 170, in render context.template_name = self.name File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 162, in _render def _render(self, context): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 938, in render bit = node File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 905, in render_annotated if context.template.engine.debug and not hasattr(e, 'template_debug'): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 106, in render url = self.url(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 103, in url return self.handle_simple(path) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 117, in handle_simple from django.contrib.staticfiles.storage import staticfiles_storage File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/contrib/staticfiles/storage.py", line 17, in <module> from django.utils.deprecation import RemovedInDjango31Warning ImportError: cannot import name 'RemovedInDjango31Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py) 2. I am a little lost on how one installation instance can be used to handle TWO different domains - domain1 and domain2, both using SSL. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 2

Cannot connect to SMTP server
by mkummini＠cmi.ac.in Aug. 14, 2022

Aug. 14, 2022

Hello. I am setting up a new mailman3 server (debian 11). `mailman3-full` is installed on the same server as postfix (our MTA). There is just one test mailing list now. When I send a message to it (I am a subscriber), mailman3 accepts the message through LMTP. Both the postfix log and mailman.log confirm this. Postfix log: Aug 14 03:21:25 mail postfix/lmtp[4097036]: 44E49272437D: to=<testlist(a)cmi.ac.in>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.15, delays=0.02/0.03/0.01/0.09, dsn=2.0.0, status=sent (250 Ok) mailman.log: Aug 14 03:21:26 2022 (4096856) ACCEPT: <Yvgc3WsoFlpZbypw(a)cmi.ac.in> (The digest.mmdf file shows the test message I sent. Hence mailman3 has received the message from postfix.) However, after this, the postfix log does not show any attempt by mailman3 to send the message to the list members. The following runners have started (after the most recent mailman3 restart) Aug 14 03:19:53 2022 (4096853) archive runner started. Aug 14 03:19:53 2022 (4096863) retry runner started. Aug 14 03:19:53 2022 (4096862) rest runner started. Aug 14 03:19:54 2022 (4096855) command runner started. Aug 14 03:19:54 2022 (4096854) bounces runner started. Aug 14 03:19:55 2022 (4096860) pipeline runner started. Aug 14 03:19:55 2022 (4096866) digest runner started. Aug 14 03:19:55 2022 (4096858) nntp runner started. Aug 14 03:19:55 2022 (4096857) lmtp runner started. Aug 14 03:19:55 2022 (4096865) virgin runner started. Aug 14 03:19:56 2022 (4096856) in runner started. Aug 14 03:19:57 2022 (4096859) out runner started. However, I get the following line each time I do a restart Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. Following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do…>, I tried to create an outgoing test runner, but that resulted in the following errors. >>> from mailman.runners.outgoing import OutgoingRunner >>> from mailman.testing.helpers import make_testable_runner >>> outgoing = make_testable_runner(OutgoingRunner, 'out') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 92, in make_testable_runner return EmptyingRunner(name) File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 79, in __init__ super().__init__(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 53, in __init__ super().__init__(slice, numslices) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 63, in __init__ section = getattr(config, 'runner.' + name) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 123, in __getattr__ return getattr(self._config, name) AttributeError: 'NoneType' object has no attribute 'runner.out' Here are the lines in mailman.cfg referring to smtp smtp_secure_mode : starttls smtp_host: localhost smtp_port: 587 If you could suggest how I could fix this issue, it would be great. Thank you. Manoj.

2 3

RE in Ban List
by Peter Chubb Aug. 12, 2022

Aug. 12, 2022

Hi I tried to add the regular expression sales@.* to the ban list for one of my lists and got: An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got sales@.*. Now, 'sales@.*' _is_ a valid regular expression --- so why did it fail? (I wanted to ban that set of addresses, because we get an awful lot of chinese spam from sales@some-company-name where the company name is variable) Peter C

2 1

MM3 not processing some mails from specific user
by Stefan Bauer Aug. 12, 2022

Aug. 12, 2022

Hi, we are running MM3¹ and from time to time, a mail to a mailing list is not processed by MM. MM sees the mail but still does nothing with it. If another user is sending _same_ mail, it is processed. Any idea what that could be? Here are some logs: Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) handling connection Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'LHLO mal01.mydomain.tld' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'MAIL FROM:<john.doe(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) sender: john.doe(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'RCPT TO:<ssa(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) recip: ssa(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'DATA' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'QUIT' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) connection lost Here is a snipped from same user, but different mail that is also not processed by MM: Subject: =?iso-8859-1?Q?Kleine_=C4nderung?= From: john.doe(a)mydomain.tld To: =?us-ascii?Q?ssa=40mydomain=2Etld?= <ssa(a)mydomain.tld> Date: Wed, 10 Aug 2022 12:33:36 +0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c" Thread-Index: AdistWce8WLKbSqIReeBnR+y5yR5Mw== Message-Id: <kcEE.3C4Toxi/SomLpNH7qUNdhg.gBB2y7Ws2AE(a)mx1.mydomain.tld> This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Das ist ein Test --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c-- Any help is greatly appreciated. Thank you. ¹ 3.1.1-9 (update is scheduled)

3 5

Getting information to connect mailman to new web host
by tg337＠drexel.edu Aug. 11, 2022

Aug. 11, 2022

We moved over to a new platform and now our lists.(domain).org address is not working. I'm trying to find the records I would need to update on the new site to connect them, and not sure how.

2 1

Mailman recovery test did not go as planned
by bob B Aug. 9, 2022

Aug. 9, 2022

I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. I need to perform a DR recovery test. I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). While Mailman was stopped, I had our database team take a backup dump of the database. I then restarted Mailman in docker. I threw some more messages at a test list. I validated that the new messages were delivered, and showed up in the archive. I shut down Mailman again. I had the database team restore the Mailman database from the backup. I started Mailman I logged into Mailman I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. When went into the list archive, I get a spinning icon and no messages showed up. I quit, restarted my browser, and logged in again, and the same thing. I then sent a test message to the list and the message was delivered to the list. Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Is this normal? After a restore did the new message cause a refresh of archived messages etc? Is there a way to do this without sending a message to a list after a restoration of the database? Are there better steps I should take when restoring the database? Thanks

3 6

Detectors and Bounces
by summersan＠nclack.k12.or.us Aug. 5, 2022

Aug. 5, 2022

Hello All, I've recently upgraded a Mailman 3 server from Debian 10.12 to Debian 11.4 [1]. In that process, I've also upgraded Mailman 3 from version 3.3.4 to version 3.3.5. I think the following guide was originally used when setting up Mailman 3 on the present server: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 . After that upgrade process, I've noticed that at least one `mailman` process and one `postgres` process were at something like 40 %CPU or higher for extended periods of time (seen using `top` command). Upon further inspection, and through some research online, it seemed like the issue might have to do with bounces (maybe not processing or something) [2][3][4][5][6][7][8]. In my logcheck logs, I was seeing this message multiple times a second: `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` I ended up trying to clear out the `/opt/mailman/mm/var/queue/bounces` and `/opt/mailman/mm/var/locks` directories to see if that would help. There seemed to be some sort of positive change, because the log message "spamming" seemed to decrease. The high %CPU for the `mailman` and `postgres` processes in question also seemed to go down over time. But the related `mailman` process would still run at a high %CPU from time to time. I tried checking the `mailman` process using `strace` at some point, but I didn't see an easily evident cause for what was going on—from what I remember, there was something about a "POLLIN" or something that kept looping. When I go to check the same `mailman` process with `strace` today, I just see occasional messages like this: `select(0, NULL, NULL, NULL, {tv_sec=45, tv_usec=43171}) = 0 (Timeout)` My Questions: Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? Should there normally be other detectors listed in the logs beyond the `DSN` one? If so, is there a setting I can change somewhere to make this happen? For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Here is an example of previous log lines: Running detector: <class 'flufl.bounce._detectors.sina.Sina'> Running detector: <class 'flufl.bounce._detectors.llnl.LLNL'> Running detector: <class 'flufl.bounce._detectors.exim.Exim'> Running detector: <class 'flufl.bounce._detectors.qmail.Qmail'> Running detector: <class 'flufl.bounce._detectors.exchange.Exchange'> Running detector: <class 'flufl.bounce._detectors.netscape.Netscape'> Running detector: <class 'flufl.bounce._detectors.dsn.DSN'> Running detector: <class 'flufl.bounce._detectors.caiwireless.Caiwireless'> Running detector: <class 'flufl.bounce._detectors.aol.AOL'> Running detector: <class 'flufl.bounce._detectors.yale.Yale'> Running detector: <class 'flufl.bounce._detectors.smtp32.SMTP32'> Running detector: <class 'flufl.bounce._detectors.groupwise.GroupWise'> Running detector: <class 'flufl.bounce._detectors.simplewarning.SimpleWarning'> Running detector: <class 'flufl.bounce._detectors.microsoft.Microsoft'> Running detector: <class 'flufl.bounce._detectors.postfix.Postfix'> Running detector: <class 'flufl.bounce._detectors.simplematch.SimpleMatch'> Running detector: <class 'flufl.bounce._detectors.yahoo.Yahoo'> Thank you for your time, Andy ----- Web References: [1] https://www.debian.org/News/2022/2022032602 [2] https://mail.python.org/archives/list/mailman-developers@python.org/thread/… [3] https://phabricator.wikimedia.org/T282348 [4] https://mail.python.org/archives/list/mailman-users@python.org/thread/MISUM… [5] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [6] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… [7] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [8] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…

2 9

Rpsamd greylist configuration for Mailman3
by Prasanth Nair Aug. 3, 2022

Aug. 3, 2022

Hello, I'm in the process of configuring Rspamd with the Mailman3 server. If Rspamd flags a message under 'greylist' and accepts it after the temporary rejection, is there any way mailman can move that message to the moderator's queue? if it is possible, can someone send me the instructions, please? Kind regards, Prasanth Nair

2 2

Mailman 3 questions (purge archives, list metrics, and auto discard held messages)
by bob B Aug. 2, 2022

Aug. 2, 2022

Some quick mailman3 questions --Just wanted to check that there is still no way for mailman3 to automatically purge archived emails after a set amount of time? it looks like you have to export the database, purge the messages, then re-import, is this still the only/best way to purge old archived messages? --I noticed on the list info page you have metrics, which is straightforward except for "volume" My volume number is not increasing? What is that counting exactly? --Is there any way to auto discard held messages after x amount of time? I assume not but had a user ask if that was an option. Thanks for the assistance in advance.

3 4

Mailman 3 Consultant needed
by Mark Taylor Aug. 1, 2022

Aug. 1, 2022

A customer we support wants to migrate a substantial Mailman 2 installation to Mailman 3. We have a team that can handle much, even perhaps most of this, but it’s an important project and we’d prefer to have a deep expert on the team for help/advice and the heavy lifting. Can anyone here recommend and engineer, perhaps even you, who could get involved with us commercially to help make a Mailman 2 to 3 migration successful? Thank you all, and I hope I’ve not violated any list guidelines by asking… You can contact me off-list if you prefer - I’m quite easy to find… Best regards to all, Mark Mark Taylor, Chief Executive Officer SiriUS: Infrastructure for Entrepreneurs® https://www.siriusopensource.com t: +001 509 254 5005

1 0

Programmatic Creation of Users
by jciesla＠techsupportme.com July 30, 2022

July 30, 2022

I am returning to Mailman after being away for a LONG time and I need to create 40 lists with ~350 subscribers spread across those lists. After a lot of testing I am now able to create users from the Core Shell and set (most of) the necessary values. Having jumped that hurdle I have hit a roadblock and I am hoping that the list can provide some insight and/or solutions. After a lot of research I now understand that what I am doing in the Core Shell is creating a User entity which has one or more email addresses as well as one or more roles and preferences that exist at the global level. This user entity can Subscribe to zero or more lists. If I am incorrect in the summation please let me know! Assuming that the previous information is correct that brings us to my current dilemma. Specifically, the User entity can Subscribe and interact with lists using the email commands, but they can't Login using the Postorius web interface. If I understand correctly the reason that they can't login is that the underlying Django system does not recognize their account because the account that was created in Core isn't accessible by Django. Instead the user needs to create a Django-specific account at which point the information from Core becomes available in the user's web UI. If that is in fact accurate then I want to take the next logical leap: is it possible to programmatically create an account in Django that is tied to the account that was created in Core? Any information is greatly appreciated! -John

2 1

User display name entry field input ignored
by Christian July 27, 2022

July 27, 2022

Whether I try and add users using mass subscribe, or individually, it seems the display name field entry is ignored. The default is then "none" for the user. Please advise. Thank you!

2 3

Shorted Subjects in Mailman
by Stephan Krinetzki July 27, 2022

July 27, 2022

Hello all, We have been experiencing the following problem lately: When a user sends a mail with an unusually long subject to a mailing list, this subject is shortened. Here are the two examples: Original subject: "[SAV-LINUX] Notice from Sophos Anti-Virus on lx1bcms-storage.physik.rwth-aachen.de" (82 characters long) Subject in Mailman: "[edv-support][SAV-LINUX] Notice from Sophos Anti-Virus on" (57 characters long) Is there a rule that Mailman truncates the subject or why does this happen? Is there any way to work around this? In the Mailman Topic Header, however, the full subject is always readable. Translated with www.DeepL.com/Translator (free version)

4 13

Problem replying via Hyperkitty
by Jeff July 27, 2022

July 27, 2022

Hello Everyone, A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) A couple of basic questions: 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? 2) what log files could I check to see what — if anything — happens to these emails? 3) Are there any settings that need to be set to make this work? Thanks much. Any help will be appreciated. Jeff

2 3

Apache Configuration for Subdomain
by Mail Person July 26, 2022

July 26, 2022

I'm trying to move my mailman3 web interface from example.com/mailman3 to just lists.example.com like this site. I am not having luck with the apache configuration. I've tried below but I just get a 403: <VirtualHost *:80> ServerAdmin admin(a)example.com ServerName lists.example.com ServerAlias www.lists.example.com <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /favicon.ico ! ProxyPass /static ! ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> </VirtualHost> Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /static /var/lib/mailman3/web/static

3 9

Apache Conf
by Guiseppin Thomas July 26, 2022

July 26, 2022

Hi, Currently, I use a nginx configuration for mailman. It's work perfectly. I tried to do the same with Apache, but the statics files are not delivered (404). Basically, it's the same configuration: /server { listen 80; server_name mailing.ddd.fr; access_log /var/log/nginx/mailing.access.log; error_log /var/log/nginx/mailing.error.log; location /static/ { alias /opt/mailman/static/; expires 30d; } proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; location / { proxy_pass http://localhost:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; } } <VirtualHost *:80> ServerName mailing.ddd.fr ErrorLog ${APACHE_LOG_DIR}/mailing.error.log CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined <Location /static/> Alias "/opt/mailman/static/" </Location> <Location /> ProxyPass http://localhost:8000/ ProxyPassReverse http://localhost:8000/ ProxyPreserveHost On </Location> </VirtualHost>/ I missed something ? Thanks.

5 10

Error while running mailman-web compilemessages
by Prasanth Nair July 26, 2022

July 26, 2022

Hello, I'm in the process of installing a Mailman3 server. I get the following error messages when I run the command 'mailman-web compilemessages'. It was working fine before and noticed this recently. Can someone suggest a solution to solve this issue, please? *Execution of msgfmt failed: /opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:25: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The character that terminates the directive number 1 is not a valid conversion specifier./opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:82: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: In the directive number 1, the character ')' is not a valid conversion specifier./opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:104: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The string ends in the middle of a directive./opt/mailman/venv/lib/python3.8/site-packages/django_extensions/locale/ar/LC_MESSAGES/django.po:109: 'msgstr' is not a valid Python format string, unlike 'msgid'. Reason: The string ends in the middle of a directive.msgfmt: found 4 fatal errors* Kind regards, Prasanth Nair

4 7

List and Domain listing slow
by Patrik Peng July 25, 2022

July 25, 2022

Hi there Recently we migrated 4000+ lists from Mailman 2 to 3 and noticed a drastic slowdown of response time (30+ secs) when listing lists or domains while logged in as any user. Affected are the following paths: * https://mm3.com/mailman3/lists/ * https://mm3.com/mailman3/domains/ When visiting one of the affected pages, a lot of API requests are visible in `mailman.log`: [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain1.com HTTP/1.1" 200 202 "-" "GNU Mailman REST client v3.3.3" [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain2.com HTTP/1.1" 200 188 "-" "GNU Mailman REST client v3.3.3" [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain3.com HTTP/1.1" 200 200 "-" "GNU Mailman REST client v3.3.3" [25/Jul/2022:11:02:02 +0200] "GET /3.1/domains/domain4.com HTTP/1.1" 200 218 "-" "GNU Mailman REST client v3.3.3" I'm suspecting an n+1 issue where a request is made for every list entry and even if the API response times are quick (15-20ms), this time accumulates. Regards, Patrik ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

1 0

Trouble importing a Mailman 3 Postgres database into a new Mailman 3 instance (Docker)
by skenny＠scss.tcd.ie July 22, 2022

July 22, 2022

Our in-production Mailman 3 service is running under Docker (maxking's mailman-web, mailman-core and Postgres database containers). I want to move Mailman to a different server, where I have a clean install of Mailman 3 up and running. When I take a database dump of the in-production database, and import it on the new server, a ton of errors are produced, and the core and web containers die after 15 seconds or so. I have noticed that if I first delete the mailmandb database on the new server, then create it anew, and _then_ do the import, everything is fine. I see all my lists in the web interface on the new server, it's all good. But deleting and then creating a new blank mailmandb database just prior to importing ... it can't be the right thing to do. Below is a sample of the errors that are reported on the stdout from my docker-compose command. I'd be very grateful for any pointers as to where to go next with this. Many thanks in advance, Stephen Kenny database_1 | ERROR: relation "auth_permission_id_seq" already exists database_1 | STATEMENT: CREATE SEQUENCE public.auth_permission_id_seq database_1 | START WITH 1 database_1 | INCREMENT BY 1 database_1 | NO MINVALUE database_1 | NO MAXVALUE database_1 | CACHE 1; database_1 | ERROR: insert or update on table "_request"well violates foreign key constraint "_request_mailing_list_id_fkey" database_1 | DETAIL: Key (mailing_list_id)=(774) is not present in table "mailinglist". database_1 | STATEMENT: COPY public._request (id, key, request_type, data_hash, mailing_list_id) FROM stdin; database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_group_id_permission_id_0cd325b0_uniq UNIQUE (group_id, permission_id); database_1 | ERROR: multiple primary keys for table "auth_group_permissions" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group_permissions database_1 | ADD CONSTRAINT auth_group_permissions_pkey PRIMARY KEY (id); database_1 | ERROR: multiple primary keys for table "auth_group" are not allowed database_1 | STATEMENT: ALTER TABLE ONLY public.auth_group database_1 | ADD CONSTRAINT auth_group_pkey PRIMARY KEY (id); database_1 | ERROR: relation "auth_permission_content_type_id_codename_01ab375a_uniq" already exists database_1 | ERROR: relation "account_emailaddress_user_id_2c513194" already exists database_1 | STATEMENT: CREATE INDEX account_emailaddress_user_id_2c513194 ON public.account_emailaddress USING btree (user_id); database_1 | ERROR: relation "account_emailconfirmation_email_address_id_5b7f8c58" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_email_address_id_5b7f8c58 ON public.account_emailconfirmation USING btree (email_address_id); database_1 | ERROR: relation "account_emailconfirmation_key_f43612bd_like" already exists database_1 | STATEMENT: CREATE INDEX account_emailconfirmation_key_f43612bd_like ON public.account_emailconfirmation USING btree (key varchar_pattern_ops); database_1 | ERROR: constraint "hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_thread_id_ab30508b_fk_hyperkitty_thread_id FOREIGN KEY (thread_id) REFERENCES public.hyperkitty_thread(id) DEFERRABLE INITIALLY DEFERRED; database_1 | ERROR: constraint "hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id" for relation "hyperkitty_tagging" already exists database_1 | STATEMENT: ALTER TABLE ONLY public.hyperkitty_tagging database_1 | ADD CONSTRAINT hyperkitty_tagging_user_id_9af832e2_fk_auth_user_id FOREIGN KEY (user_id) REFERENCES public.auth_user(id) DEFERRABLE INITIALLY DEFERRED; and finally .... mailman-core | Traceback (most recent call last): mailman-core | File "/usr/bin/mailman", line 8, in <module> mailman-core | sys.exit(main()) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1130, in __call__ mailman-core | return self.main(*args, **kwargs) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1054, in main mailman-core | with self.make_context(prog_name, args, **extra) as ctx: mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 920, in make_context mailman-core | self.parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1613, in parse_args mailman-core | rest = super().parse_args(ctx, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 1378, in parse_args mailman-core | value, args = param.handle_parse_result(ctx, opts, args) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2360, in handle_parse_result mailman-core | value = self.process_value(ctx, value) mailman-core | File "/usr/lib/python3.8/site-packages/click/core.py", line 2322, in process_value mailman-core | value = self.callback(ctx, self, value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/bin/mailman.py", line 95, in initialize_config mailman-core | initialize(value) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 218, in initialize mailman-core | initialize_2(propagate_logs=propagate_logs) mailman-core | File "/usr/lib/python3.8/site-packages/mailman/core/initialize.py", line 177, in initialize_2 mailman-core | config.db = getUtility(IDatabaseFactory, utility_name).create() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 55, in create mailman-core | SchemaManager(database).setup_database() mailman-core | File "/usr/lib/python3.8/site-packages/mailman/database/factory.py", line 84, in setup_database mailman-core | current_rev = context.get_current_revision() mailman-core | File "/usr/lib/python3.8/site-packages/alembic/runtime/migration.py", line 435, in get_current_revision mailman-core | raise util.CommandError( mailman-core | alembic.util.exc.CommandError: Version table 'alembic_version' has more than one head present; please use get_current_heads() mailman-core exited with code 1 mailman-web | Compiling locale files in /usr/lib/python3.8/site-packages mailman-web | Traceback (most recent call last): mailman-web | File "/opt/mailman-web/manage.py", line 10, in <module> mailman-web | execute_from_command_line(sys.argv) mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line mailman-web | utility.execute() mailman-web | File "/usr/lib/python3.8/site-packages/django/core/management/__init__.py", line 363, in execute mailman-web | settings.INSTALLED_APPS mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 82, in __getattr__ mailman-web | self._setup(name) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 69, in _setup mailman-web | self._wrapped = Settings(settings_module) mailman-web | File "/usr/lib/python3.8/site-packages/django/conf/__init__.py", line 170, in __init__ mailman-web | mod = importlib.import_module(self.SETTINGS_MODULE) mailman-web | File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module mailman-web | return _bootstrap._gcd_import(name[level:], package, level) mailman-web | File "<frozen importlib._bootstrap>", line 1014, in _gcd_import mailman-web | File "<frozen importlib._bootstrap>", line 991, in _find_and_load mailman-web | File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked mailman-web | File "<frozen importlib._bootstrap>", line 671, in _load_unlocked mailman-web | File "<frozen importlib._bootstrap_external>", line 848, in exec_module mailman-web | File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed mailman-web | File "/opt/mailman-web/settings.py", line 65, in <module> mailman-web | MAILMAN_ARCHIVER_FROM = (os.environ.get('MAILMAN_HOST_IP', gethostbyname(os.environ.get('MAILMAN_HOSTNAME', 'mailman-core'))),) mailman-web | socket.gaierror: [Errno -2] Name does not resolve mailman-web | python3: can't open file 'manage.py': [Errno 2] No such file or directory mailman-web exited with code 2

3 6

Messages Showing Up as "Forwarded"
by Mail Person July 22, 2022

July 22, 2022

Sorry if this is an easy question, but I've got mailman3 up and running and all my test messages show up with forwarding language around them rather than just the message, see below: ---------- Forwarded message ---------- From: Person <person(a)gmail.com> To: all(a)domain.com Cc: Bcc: Date: Thu, 21 Jul 2022 13:56:22 -0700 Subject: Hello Members This is a wonderful test ---------- Forwarded message ---------- From: Person <person(a)gmail.com> To: all(a)domain.com Cc: Bcc: Date: Thu, 21 Jul 2022 13:56:22 -0700 Subject: Hello Members _______________________________________________ Mailing list footer

2 1

Can't Start Mailman3 Core on Fresh Install
by Mail Person July 21, 2022

July 21, 2022

Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using MySQL as the backend. After installing using the mailman3-full package and configuring it, I'm getting the following error when trying to start the mailman3 service: l 21 04:28:44 eps mailman3[81963]: packet.raise_for_error() Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/protocol.py", line 221, in raise_for_error Jul 21 04:28:44 eps mailman3[81963]: err.raise_mysql_exception(self._data) Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/err.py", line 143, in raise_mysql_exception Jul 21 04:28:44 eps mailman3[81963]: raise errorclass(errno, errval) Jul 21 04:28:44 eps mailman3[81963]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using password: YES)") Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: http://sqlalche.me/e/e3q8) I'm not sure why the access issue is happening. Mailman3-web is running fine and I can see the site at mailman3/postorius/lists (but it says Page Not Found).

4 7

check/update delivery status via python script
by Eggert Ehmke July 19, 2022

July 19, 2022

Somehow I can't get the starting point in the documentation to do stuff like this. Besides, when I try to run examples from https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/ commands/docs/withlist.html[1] I run into errors like AttributeError: 'Withlist' object has no attribute 'process' Where to start? I thought I have some python experience but your API makes my head burn. -------- [1] https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/ commands/docs/withlist.html

2 2

Hacking attempts?
by Lists July 17, 2022

July 17, 2022

Hi, We are seeing thousands of these emails every day, looks like someone is trying to hack our Mailman3 but would appreciate someone with more knowledge of MM3 to confirm. Is this a problem with our setup? i.e. the “Internal Server Error” bit, or are the hackers just sending bad data that is causing the error? also how do we stop/block this? TIA and here is a typical email: Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/fedora/login/ Internal Server Error: /mailman3/accounts/fedora/login/ TypeError at /accounts/fedora/login/ _openid_consumer() missing 2 required positional arguments: 'provider' and 'endpoint' Request Method: GET Request URL: https://mailman.ardc.net/mailman3/accounts/fedora/login/?process=login&next… <https://mailman.ardc.net/mailman3/accounts/fedora/login/?process=login&next…> Django Version: 2.2.26 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: Thu, 14 Jul 2022 02:34:04 -0400 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 GET: process = 'login' next = '/mailman3/hyperkitty/list/44net(a)mailman.ampr.org <mailto:mailman3/hyperkitty/list/44net@mailman.ampr.org>/message/O5Z2YZBJZXFPH2ACAORN6BST7B2S3M3P/' POST: No POST data FILES: No FILES data COOKIES: No cookie data META: CONTEXT_DOCUMENT_ROOT = '/var/www/html' CONTEXT_PREFIX = '' DOCUMENT_ROOT = '/var/www/html' GATEWAY_INTERFACE = 'CGI/1.1' HTTPS = 'on' HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8' HTTP_ACCEPT_ENCODING = 'gzip,deflate' HTTP_CONNECTION = 'Keep-Alive' HTTP_HOST = 'mailman.ardc.net <http://mailman.ardc.net/>' HTTP_USER_AGENT = 'Mozilla/5.0 (compatible; BLEXBot/1.0; +http://webmeup-crawler.com/ <http://webmeup-crawler.com/>)' PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin' PATH_INFO = '/accounts/fedora/login/' QUERY_STRING = 'process=login&next=/mailman3/hyperkitty/list/44net(a)mailman.ampr.org <mailto:process=login&next=/mailman3/hyperkitty/list/44net@mailman.ampr.org>/message/O5Z2YZBJZXFPH2ACAORN6BST7B2S3M3P/' REMOTE_ADDR = '157.90.177.212' REMOTE_PORT = '63384' REQUEST_METHOD = 'GET' REQUEST_SCHEME = 'https' REQUEST_URI = '/mailman3/accounts/fedora/login/?process=login&next=/mailman3/hyperkitty/list/44net(a)mailman.ampr.org <mailto:mailman3/accounts/fedora/login/?process=login&next=/mailman3/hyperkitty/list/44net@mailman.ampr.org>/message/O5Z2YZBJZXFPH2ACAORN6BST7B2S3M3P/' SCRIPT_FILENAME = 'proxy:uwsgi://localhost//accounts/fedora/login/' <uwsgi://localhost//accounts/fedora/login/'> SCRIPT_NAME = '/mailman3' SERVER_ADDR = '44.1.1.29' SERVER_ADMIN = 'postmaster(a)ardc.net <mailto:postmaster@ardc.net>' SERVER_NAME = 'mailman.ardc.net <http://mailman.ardc.net/>' SERVER_PORT = '443' SERVER_PROTOCOL = 'HTTP/1.1' SERVER_SIGNATURE = '<address>Apache/2.4.53 (Debian) Server at mailman.ardc.net <http://mailman.ardc.net/> Port 443</address>\n' SERVER_SOFTWARE = 'Apache/2.4.53 (Debian)' SSL_TLS_SNI = 'mailman.ardc.net <http://mailman.ardc.net/>' uwsgi.core = 1 uwsgi.node = b'mailman' uwsgi.version = b'2.0.19.1-debian' wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'> wsgi.file_wrapper = '' wsgi.input = <uwsgi._Input object at 0x7f8e0b4a0410> wsgi.multiprocess = False wsgi.multithread = True wsgi.run_once = False wsgi.url_scheme = 'https' wsgi.version = '(1, 0)' Settings: Using settings module settings ABSOLUTE_URL_OVERRIDES = {} ACCOUNT_AUTHENTICATION_METHOD = 'username_email' ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'postmaster(a)ardc.net <mailto:postmaster@ardc.net>'),)" ALLOWED_HOSTS = ['*'] APPEND_SLASH = True AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')" AUTH_PASSWORD_VALIDATORS = '********************' AUTH_USER_MODEL = 'auth.User' BASE_DIR = '/usr/share/mailman3-web' CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}} CACHE_MIDDLEWARE_ALIAS = 'default' CACHE_MIDDLEWARE_KEY_PREFIX = '********************' CACHE_MIDDLEWARE_SECONDS = 600 COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'} COMPRESS_CACHEABLE_PRECOMPILERS = '()' COMPRESS_CACHE_BACKEND = 'default' COMPRESS_CACHE_KEY_FUNCTION = '********************' COMPRESS_CLEAN_CSS_ARGUMENTS = '' COMPRESS_CLEAN_CSS_BINARY = 'cleancss' COMPRESS_CLOSURE_COMPILER_ARGUMENTS = '' COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar' COMPRESS_CSS_HASHING_METHOD = 'mtime' COMPRESS_DATA_URI_MAX_SIZE = 1024 COMPRESS_DEBUG_TOGGLE = None COMPRESS_ENABLED = True COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter'], 'js': ['compressor.filters.jsmin.JSMinFilter']} COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f8e17d7a670> COMPRESS_MINT_DELAY = 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_OFFLINE_MANIFEST = 'manifest.json' COMPRESS_OFFLINE_TIMEOUT = 31536000 COMPRESS_OUTPUT_DIR = 'CACHE' COMPRESS_PARSER = 'compressor.parser.AutoSelectParser' COMPRESS_PRECOMPILERS = '()' COMPRESS_REBUILD_TIMEOUT = 2592000 COMPRESS_ROOT = '/var/lib/mailman3/web/static' COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage' COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'} COMPRESS_URL = '/mailman3/static/' COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/' COMPRESS_VERBOSE = False COMPRESS_YUGLIFY_BINARY = 'yuglify' COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal' COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal' COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar' COMPRESS_YUI_CSS_ARGUMENTS = '' COMPRESS_YUI_JS_ARGUMENTS = '' CSRF_COOKIE_AGE = 31449600 CSRF_COOKIE_DOMAIN = None CSRF_COOKIE_HTTPONLY = False CSRF_COOKIE_NAME = 'csrftoken' CSRF_COOKIE_PATH = '/' CSRF_COOKIE_SAMESITE = 'Lax' CSRF_COOKIE_SECURE = False CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure' CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN' CSRF_TRUSTED_ORIGINS = [] CSRF_USE_SESSIONS = False DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': ‘X.X.X.X', 'PORT': '', 'OPTIONS': {'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4'}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}} DATABASE_ROUTERS = [] DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440 DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000 DATETIME_FORMAT = 'N j, Y, P' DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y'] DATE_FORMAT = 'N j, Y' DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y'] DEBUG = False DEBUG_PROPAGATE_EXCEPTIONS = False DECIMAL_SEPARATOR = '.' DEFAULT_CHARSET = 'utf-8' DEFAULT_CONTENT_TYPE = 'text/html' DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter' DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage' DEFAULT_FROM_EMAIL = 'postorius(a)mailman.ardc.net <mailto:postorius@mailman.ardc.net>' DEFAULT_INDEX_TABLESPACE = '' DEFAULT_TABLESPACE = '' DISALLOWED_USER_AGENTS = [] EMAILNAME = 'mailman.ardc.net <http://mailman.ardc.net/>' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_HOST_PASSWORD = '********************' EMAIL_HOST_USER = '' EMAIL_PORT = 25 EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = '********************' EMAIL_SUBJECT_PREFIX = '[Django] ' EMAIL_TIMEOUT = None EMAIL_USE_LOCALTIME = False EMAIL_USE_SSL = False EMAIL_USE_TLS = False FILE_CHARSET = 'utf-8' FILE_UPLOAD_DIRECTORY_PERMISSIONS = None FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler'] FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440 FILE_UPLOAD_PERMISSIONS = None FILE_UPLOAD_TEMP_DIR = None FILTER_VHOST = False FIRST_DAY_OF_WEEK = 0 FIXTURE_DIRS = [] FORCE_SCRIPT_NAME = None FORMAT_MODULE_PATH = None FORM_RENDERER = 'django.forms.renderers.DjangoTemplates' HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/var/lib/mailman3/web/fulltext_index'}} HOSTNAME = 'localhost.local' IGNORABLE_404_URLS = [] INSTALLED_APPS = "('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')" INTERNAL_IPS = [] LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')] LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur'] LANGUAGE_CODE = 'en-us' LANGUAGE_COOKIE_AGE = None LANGUAGE_COOKIE_DOMAIN = None LANGUAGE_COOKIE_NAME = 'django_language' LANGUAGE_COOKIE_PATH = '/' LOCALE_PATHS = [] LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}} LOGGING_CONFIG = 'logging.config.dictConfig' LOGIN_REDIRECT_URL = 'list_index' LOGIN_URL = 'account_login' LOGOUT_REDIRECT_URL = None LOGOUT_URL = 'account_logout' MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1', '10.4.16.129', '44.1.1.29')" MAILMAN_ARCHIVER_KEY = '********************' MAILMAN_REST_API_PASS = '********************' MAILMAN_REST_API_URL = '********************' MAILMAN_REST_API_USER = '********************' MANAGERS = [] MEDIA_ROOT = '' MEDIA_URL = '' MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage' MESSAGE_TAGS = {40: 'danger'} 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')" MIGRATION_MODULES = {} MONTH_DAY_FORMAT = 'F j' NUMBER_GROUPING = 0 PASSWORD_HASHERS = '********************' PASSWORD_RESET_TIMEOUT_DAYS = '********************' POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/ <http://localhost/mailman3/>' PREPEND_WWW = False Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5} ROOT_URLCONF = 'urls' SECRET_KEY = '********************' SECURE_BROWSER_XSS_FILTER = False SECURE_CONTENT_TYPE_NOSNIFF = False SECURE_HSTS_INCLUDE_SUBDOMAINS = False SECURE_HSTS_PRELOAD = False SECURE_HSTS_SECONDS = 0 SECURE_PROXY_SSL_HEADER = None SECURE_REDIRECT_EXEMPT = [] SECURE_SSL_HOST = None SECURE_SSL_REDIRECT = False SERVER_EMAIL = 'root(a)mailman.ardc.net <mailto:root@mailman.ardc.net>' SESSION_CACHE_ALIAS = 'default' SESSION_COOKIE_AGE = 1209600 SESSION_COOKIE_DOMAIN = None SESSION_COOKIE_HTTPONLY = True SESSION_COOKIE_NAME = 'sessionid' SESSION_COOKIE_PATH = '/' SESSION_COOKIE_SAMESITE = 'Lax' SESSION_COOKIE_SECURE = False SESSION_ENGINE = 'django.contrib.sessions.backends.db' SESSION_EXPIRE_AT_BROWSER_CLOSE = False SESSION_FILE_PATH = None SESSION_SAVE_EVERY_REQUEST = False SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' SETTINGS_MODULE = 'settings' SHORT_DATETIME_FORMAT = 'm/d/Y P' SHORT_DATE_FORMAT = 'm/d/Y' SIGNING_BACKEND = 'django.core.signing.TimestampSigner' SILENCED_SYSTEM_CHECKS = [] SITE_ID = 1 SOCIALACCOUNT_PROVIDERS = {} STATICFILES_DIRS = '()' STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')" STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage' STATIC_ROOT = '/var/lib/mailman3/web/static' STATIC_URL = '/mailman3/static/' TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}] TEST_NON_SERIALIZED_APPS = [] TEST_RUNNER = 'django.test.runner.DiscoverRunner' THOUSAND_SEPARATOR = ',' TIME_FORMAT = 'P' TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M'] TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_THOUSAND_SEPARATOR = False USE_TZ = True USE_X_FORWARDED_HOST = True USE_X_FORWARDED_PORT = False WSGI_APPLICATION = 'wsgi.application' X_FRAME_OPTIONS = 'SAMEORIGIN' YEAR_MONTH_FORMAT = 'F Y’

7 19

Messages attached to probe messages
by Bjoern Franke July 15, 2022

July 15, 2022

Hi, some time ago I started a discussion where I wrongly assumed that probe messages were sent accidentally from example.com Some digging showed now that the sender of the probe messages are correct, but the attached messages seem to be wrong. An attached example for bouncing messages was: From: Mailman <mailman(a)example.com> To: Mailman Bounces <mailman-bounces(a)example.com> Subject: SMTP Delivery Failure Message-ID: <165577237837.35.8042057157021349872@mailman-core> Date: Tue, 21 Jun 2022 00:46:18 +0000 Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI X-Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI Mail to bjo(a)schafweide.org failed at outgoing SMTP Error code: 554 Error message: b'5.7.1 Spam message rejected' I took a look into the logs and found no example.com, but: Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) handling connection Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'LHLO mail.ffnw.de' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'MAIL FROM:<yzvotmm(a)forestanes.mom> SIZE=293338' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) sender: yzvotmm(a)forestanes.mom Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'RCPT TO:<vorstand(a)lists.ffnw.de>' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) recip: vorstand(a)lists.ffnw.de Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'DATA' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'QUIT' Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) connection lost Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) Connection lost during _handle_client() Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> response exception: (554, b'5.7.1 Spam message rejected') Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> response exception: (554, b'5.7.1 Spam message rejected') Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> smtp to vorstand(a)lists.ffnw.de for 6 recips, completed in 0.7157599925994873 seconds Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> post to vorstand(a)lists.ffnw.de from vorstand(a)lists.ffnw.de, 294362 bytes, 6 failures Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to foo(a)stadel.info failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to abc(a)ffnw.de failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to def(a)ffnw.de failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to xyz(a)ffnw.de failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> delivery to blabla(a)osnabrueck.freifunk.net failed with code 554, b'5.7.1 Spam message rejected' Jun 21 00:46:49 2022 (35) <165577240769.30.3077851374384466408@mailman-core> smtp to vorstand(a)lists.ffnw.de for 1 recips, completed in 0.5507137775421143 seconds

3 6

Adding user - Error 409 Subscription request already pending
by kevin＠coastalaska.org July 14, 2022

July 14, 2022

We have a couple of people trying to subscribe to our list but receive an error similar to: {"title": "409 Conflict", "description": "Subscription request already pending"} If I try to Mass Subscribe them in Postorius I get this error: HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}' In Postorius I don't see them hung up in Subscription requests. What to do? Thanks, Kevin

5 17

message size
by ronald.clarke＠sydney.edu.au July 12, 2022

July 12, 2022

Dear Mailman users, I recently had a message from a user of my Mailman account blocked because there were attachments that exceeded 2 MB. This is the message I got: "Message body is too big: 5312119 bytes with a limit of 2000 KB". Is there any way to increase the maximum allowable size of attachments? Thanks, Ron Clarke

3 2

message size
by Ronald Clarke July 12, 2022

July 12, 2022

Dear Mailman users, I recently had a message from a user of my Mailman account blocked because there were attachments that exceeded 2 MB. This is the message I got: Message body is too big: 5312119 bytes with a limit of 2000 KB. Is there any way to increase the maximum allowable size of attachments? Thanks, Ron Dr Ronald J. Clarke Associate Professor of Physical Chemistry | German Academic Exchange Service (DAAD) Ambassador Humboldt Fellow | Secretary-General of the International Union of Pure and Applied Biophysics (IUPAB) Privat-Dozent for Physical Chemistry, Johann Wolfgang Goethe-University, Frankfurt (Main) Room 517, School of Chemistry (F11) | The University of Sydney | NSW | 2006 T +61 2 9351 4406 | F +61 2 9351 3329 | E ronald.clarke(a)sydney.edu.au<mailto:ronald.clarke@sydney.edu.au>

1 0

mailman 3.x upgrade and downgrade
by skooperit＠gmail.com July 12, 2022

July 12, 2022

Hi all, I have a few contradictory questions. 1. How to upgrade the 3.x version? 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1? 3. If so, what would be the best way to do that? My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: django-mailman3 1.3.5 mailman 3.3.2 mailman-hyperkitty 1.1.0 mailman-web 0.0.3 mailmanclient 3.3.2 postorius 1.3.3 We have ~200 lists with more than a decade of history. thanks -- Carlos Souza

3 4

Mailman 3 stops delivering to a domain after too many bounces
by Julian Kippels July 12, 2022

July 12, 2022

Hi, We have recently upgraded from Mailman 2 to Mailman 3. Since then I have observed many user reports that mails to mailing lists don't reach all members. My suspicion is that there are too many "dead" members on those lists. This was not a problem on Mailman 2, but has become a problem on Mailman 3. It seems to me that for example Mailman 3 sends mails to the first 5 existing member addresses from domain A, then encounters several (20 or so seems to be the threshold) "dead" member addresses from domain A that generate a bounce and then does not even attempt to reach the remaining 800 member adresses from domain A and only sends to members on domain B and domain C. Is there a way to globaly ignore bounces and send out mails to all members of a list, no matter what? Thanks, Julian

4 7

Notes about successfuly upgrade from python 3.7 to 3.9
by Guillermo Hernandez (Oldno7) July 12, 2022

July 12, 2022

I've successfuly upgrade servers with mailman3 lists from FreeBSD 12.3 with python 3.7 to FreeBSD 13.1 with python 3.9 After doing the O.S. and all the python related apps upgraded I did the following steps: (note that my mailman3 installation is system-wide, pip drived and apache24/uwsgi served. The user that owns mailman3 is "mailman3" and all the stuff lies in "/usr/local/mailman3") -> su -> cd /usr/local/mailman3 -> pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi -> mod_wsgi-express module-config (it returns the path for the apache24 httpd.conf adjustments. I edited it) -> su -m mailman3 -c "python3 manage.py collectstatic" -> su -m mailman3 -c "python3 manage.py migrate" -> su -m mailman3 -c "python3 manage.py compress" -> cd /usr/local/lib/python3.9/site-packages/ -> cd postorius -> django-admin compilemessages -> cd ../hyperkitty -> django-admin compilemessages -> cd ../django_mailman3 -> django-admin compilemessages I had to edit again /usr/local/lib/python3.9/site-packages/mistune/scanner.py and add this two lines (this is a little bit annoying) from mistune.util import escape_html from mistune.util import escape_url And that was all. Restarted the servers and all is going smoothly All of this steps have been documented in this list by Mark & Stephen whom I'm very grateful. P.S.: As I did some upgrades ago, I didn't have to modify settings.py in the Hyperkitty area to add DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' But if you come from an old mailman/Hyperkitty version, you'll have to include in it. And the it's same if you are using UWSGI, you have to include in your apache config: WSGIPassAuthorization On -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 2

Walk-thru for Ubuntu Bionic Mailman 3 Full setup
by kelly.close＠lrewater.com July 9, 2022

July 9, 2022

I hope this is helpful to the Ubuntu folks out there. Once some critical small things were figured out, turns out it's pretty easy to get Mailman 3 running successfully under Ubuntu 18.04. The linked google doc includes my own walkthru, which includes using a cloud server image for Ubuntu 18.04 and a LAMP setup with Apache 2 and PHP, as well as Python and PostgreSQL, and the mailman3-full package that comes with that Ubuntu distribution. The walk-thru uses Postfix for mail and PostgreSQL for the back end database. https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… If you use this and see needed corrections or additions, please let me know! ~Kelly

6 21