October 2021 - Mailman-users - lists.mailman3.org

list admin via email
by Christian Stalberg 28 Oct '21

28 Oct '21

I'm unclear on how to approve via email a message sent to a list. As list owner you receive a 'requires approval' email. It then says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." Question: if I want to approve the message, where do I "...include an Approved: header with the list password in it" ? TY!

2 1

Mailman import of 2000 lists
by dancab＠caltech.edu 27 Oct '21

27 Oct '21

I'm working on importing nearly 2000 lists and have been doing some testing prior to migrating from Mailman2. I'm using the mailman create command via for loop. It takes quite a while to do all the work including updating MySQL and re-generating the LMTP files for each list. As the number of lists increases the process gets slower. Do you have any recommendations for speeding up this process? I am running the system in AWS using EFS for storage of the LMTP files. Thanks! -- Dan Caballero Caltech

4 6

Message of the day
by Henrik Rasmussen 27 Oct '21

27 Oct '21

Are there any way of displaying a "Mesage of the day" to the users of Postorius and Hyperkitty?

2 1

Docker container issues.
by Mark Sapiro 26 Oct '21

26 Oct '21

There have been a few recent requests for help with the Mailman Docker container images. These are packaged by Abhilash and I have no experience with Docker at all. The doc at https://docs.mailman3.org/en/latest/install/docker.html points to detailed docs at https://asynchronous.in/docker-mailman/ and suggest that issues should be reported on GitHub https://github.com/maxking/docker-mailman/issues where Abhilash will respond as he can. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: uncaught bounce messages
by Mark Sapiro 26 Oct '21

26 Oct '21

Putting back on the list. On 10/23/21 1:37 PM, David Bremner wrote: > Mark Sapiro <mark(a)msapiro.net> writes: >> >> If you send me the complete bounce message off list, I can see if it >> should be added to the recognition at >> https://gitlab.com/warsaw/flufl.bounce/. > > Please find attached. Thank you. I tested that DSN with current flufl.bounce and it is recognized as a temp failure for the reported address and that in turn should just be ignored by Mailman's bounce runner and not reported as unrecognized. What version of Mailman core is this and what version of flufl.bounce? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 8

Struggle on upgrading mailman3-web to new version - Not Found: /mailman//
by Stefan Bauer 26 Oct '21

26 Oct '21

Dear Users, I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the web-interface via https://my.mailinglistserver.local/mailman3/postorius/lists/ I receive Not Found: /mailman//postorius/lists/ [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1) Where does the wrong path come from (mailman vs. mailman3) After enabling Debug, i see in the browser the following: Page not found (404) Request Method: GET Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ Using the URLconf defined in urls, Django tried these URL patterns, in this order: ^$ ^postorius/ ^hyperkitty/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] ^accounts/ ^admin/ The current path, /postorius/lists/, didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. My apache configuration is very simply: # more /etc/apache2/conf-enabled/mailman3.conf Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> I dont see where the path gets traversed in the wrong way. Any help is greatly appreciated. thank you. Stefan

4 8

equivalent mailman 3 commands from 2.0
by bob B 25 Oct '21

25 Oct '21

For my 2.0 environment, I have scripts to dump list info, but i can't find the equivalent in mailman 3, for some commands, for example I use: /usr/lib/mailman/bin/list_lists which equates in mailman3 to "mailman lists" /usr/lib/mailman/bin/list_members which equates in mailman3 to "mailman members [listname]" But I also use /usr/lib/mailman/bin/list_admins [listname] /usr/lib/mailman/bin/config_list [listname] Are there equivalent command line commands to get this info in mailman3? The mailman3 "mailman withlist [listname]" takes me into an interactive prompt not sure where to go from there. I can use the API curl --user [ADMIN]:[password] http://[IP]]/3.1/lists/[listname]/config | python3 -m json.tool But just curious if there is a command line equivalent like in mailman2?

2 2

Mailman and Exim 4.94.2 (Debian Bullseye)
by Andrew Hodgson 25 Oct '21

25 Oct '21

Hi. I moved Mailman instance to a machine running Debian Bullseye last week. Ran into an issue with the Exim transport from this doc: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… The issue I ran into was that Exim wasn't able to resolve localhost in order to connect to the LMTP listener. I changed VPS provider at the same time (moved from Bytemark to Gandi) so not sure if they were doing anything different with DNS, but by default Exim doesn't use standard libraries to lookup hosts: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-the_dnslookup_… I solved the issue by using the following configuration on the Mailman router: # /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost gethostbyname hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true I haven't defined the lmtp settings at all in mailman.cfg meaning they are using the default settings of 127.0.0.1:8024. Is this the best modification to make to the Exim config or should I go an alternative route? Thanks. Andrew.

2 1

The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.
by Marco Marinello 25 Oct '21

25 Oct '21

Hi everybody, as per subject, I'm getting this error in the hyperkitty log when mailman daemon tries to archive a mail. I've setup the hyperkitty.cfg file with api_key = MAILMAN_ARCHIVER_KEY in settings_local.py but still nothing. I've seen here and in GitLab issues some errors concerning a wrong api key but here it says that it wasn't sent at all. All packages installed via pip install + latest .zip release, including mailman-hyperkitty. Currently running on apache with mod_wsgi_py3 without https. Any clue? All the best, Marco Marinello

2 9

uncaught bounce messages
by David Bremner 23 Oct '21

23 Oct '21

I'm getting (many) uncaught bounce messages for one user. Other than forcibly unsubscribing them, is there anything I can do? I hesitate to post this message publically, but here is what I can see, somewhat anonymized The MIME structure looks like └┬╴multipart/mixed 7030 bytes ├─╴text/plain 442 bytes ├─╴message/delivery-status 176 bytes └─╴text/rfc822-headers 5301 bytes In /var/log/mailman3/bounce.log I see lines like Oct 23 08:20:00 2021 (5320) Bounce message w/no discernable addresses: <hex-digits(a)foo.bar> In the delivery-status part I see Final-Recipient: rfc822; fub(a)foo.bar Action: delayed Status: 4.0.0 The initial text/plain part looks like Hi! This is the MAILER-DAEMON, please DO NOT REPLY to this email. A message is delayed for more than 4 hours for the following list of recipients: fub(a)foo.bar: Network error on destination MXs Please note that this is only a temporary failure report. The message is kept in the queue for up to 7 days. You DO NOT NEED to re-send the message to these recipients. Below is a copy of the original message:

2 1

2023

2022

2021

2020

2019

2018

2017

2016

Mailman-users October 2021