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

Negative number for digest size
by Gila Halpern Nov. 19, 2021

Nov. 19, 2021

If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting?

3 4

Moderation Action Changed After Import
by Brian Carpenter Nov. 12, 2021

Nov. 12, 2021

I migrated a Mailman 2 list using import21 and the list's config.pck into a Mailman 3 list. The list owner reported back that about 98% of the list members had their moderation setting changed to Reject (with notification). He said the previous moderation was the list's default which was hold for moderation. Is such a thing possible with an import job? Is this perhaps a bug that has been reported previously? -- Brian Carpenter Harmonylists.com Emwd.com

3 10

Edit archived email? Is it possible?
by Prasanth Nair Oct. 8, 2021

Oct. 8, 2021

Hello, Does anyone know how to edit an archived email in Mailman3? It is possible in Mailman2 ( https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M…) Is there any option similar to this in Mailman3? Kind regards, Prasanth

3 8

Confirmation emails to Users has wrong domain name (example.com!)
by Odhiambo Washington Oct. 3, 2021

Oct. 3, 2021

1. Confirmation emails to Users has wrong domain name (example.com!) <https://docs.mailman3.org/en/latest/faq.html#id1> <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> This happens when your reverse (SSL) proxy isn’t setting up the correct headers when proxying requests. Fix this by setting the right proxy_set_header directives: # For Nginx. location / { proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Host $host; proxy_pass http://localhost:8000/; } Appropriate headers for different web servers needs to be set if something other the How is this supposed to be mitigated in Apache when using WSGI? My config: WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman user=mailman group=mailman WSGIPythonHome "/usr/local" WSGIProcessGroup hyperkitty <VirtualHost *:443> ServerName lists.doma.ain ServerAdmin odhiambo(a)gmail.com SSLEngine on SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL SSLCertificateFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/cert.pem" SSLCertificateKeyFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/privkey.pem" SSLCertificateChainFile "/usr/local/etc/letsencrypt/live/lists.doma.ain/chain.pem" CustomLog /var/log/mm3-lists-access.log combined ErrorLog /var/log/mm3-lists-error.log LogLevel info Alias /favicon.ico /usr/local/mailman/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman/static <Directory "/usr/local/mailman/static"> Order Allow,Deny Require all granted Allow from all </Directory> WSGIScriptAlias /mailman3 /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman/etc/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman/etc/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman/"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup mailman-web </Directory> </VirtualHost> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 11

Broken web interface Ubuntu 20.04
by Simon Brown Oct. 1, 2021

Oct. 1, 2021

Hello, Whilst I wasn't looking something has broken the web interface to mailman on our list server. On the list index page I get the Postorius header, but no list index, instead a Page not found error. Curiously the Postorius header is also broken, the links point to https://host/mailman/(postorius/lists|hyperkitty) not https://host/mailman3/(postorius/lists|hyperkitty) like it should I've poked around and I can't find any useful errors and I don't know exactly when this happened, but I think it was this week. Mailman itself is running happily underneath. Any suggestions as to what might have gone wrong? Simon P.S. Hopefully I've got the right list this time. -- Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown(a)eiscat.se

5 6

Upgrading mailman 3 venv installation
by Morris Jones Sept. 30, 2021

Sept. 30, 2021

Congratulations on the new release for Mailman 3 Core! I'm not a daily pip/python user, so I'm probably behind on the safe and proper way to update my installation (which is working pretty well). In my virtual environment, I ran `pip list -o` and got a significant list. I noticed that all of the mailman packages seemed to be "Type sdist" and the framework packages "Type wheel". (Dunno what "Type" means in this context.) So I tried `pip list -o | grep sdist` and got a smaller list: (venv) mailman@mail:~$ pip list -o | grep sdist atpublic 2.1.1 2.3 sdist django-allauth 0.43.0 0.45.0 sdist django-mailman3 1.3.4 1.3.7 sdist flufl.i18n 3.1.3 3.2 sdist flufl.lock 5.0.3 6.0 sdist HyperKitty 1.3.3 1.3.4 sdist lazr.config 2.2.2 2.2.3 sdist mailman 3.3.2 3.3.5 sdist mailmanclient 3.3.1 3.3.3 sdist mysqlclient 2.0.1 2.0.3 sdist postorius 1.3.3 1.3.6 sdist Is this a reasonable list of the packages that I should update? Are there framework updates I should be concerned with? I'm remembering that a specific non-current version of django was required for mailman. The one I have installed is 3.0.11, with 3.2.7 listed as Latest. My plan is to archive the virtualenv directory, upgrade the packages listed above. If something breaks, I should be able to restore the archived virtualenv. I'm running a single server, Ubuntu 18.04.6, with Zimbra running alongside. Best regards, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

2 3

Ann: Mailman Core 3.3.5b1 is out
by Abhilash Raj Sept. 29, 2021

Sept. 29, 2021

Hello Everyone, I am pleased to announce that Mailman Core 3.3.5b1 is now out. It is a pre-release for 3.3.5, which is slated to come out in 3 weeks from now. I am planning for a 2 week beta period, after which I'll release the first RC and then stable a week after. Right now I am not planning to release a second beta version, but if there are several changes in Core in the next week or so, then I might. This release includes a lot of bug fixes and some new features. It also includes a security enhancement that improves the authentication of REST API by adding resistance to some timing channel attacks. A full list of changes in this version can be found here[1]. [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… We have also made improvements in the i18n workflow and now the email templates are updated from the translated messages in the .po files that we get from Weblate. Documentation for translators is available here[2] if you want to help translate Mailman into your native language. [2]: https://docs.mailman3.org/en/latest/translation.html This is a pre-release version, if you want to test it with your setup, you can install it using: $ pip install --pre mailman==3.3.5b1 If you want to download a release tarball, you can do so from here: https://pypi.org/project/mailman/3.3.5b1/#files This release received a lot of contributions from community, which I am really happy about! I'd like to thank everyone who made this release possible! -- thanks, Abhilash Raj (maxking)

5 8

Centralizing logging
by Odhiambo Washington Sept. 29, 2021

Sept. 29, 2021

Hello crew, Installing Mailam3 on FreeBSD. In mailman.cgf, I have set: var_dir: /usr/local/mailman/var When I ran "mailman -C mailman.cgf info" it created the necessary directory tree. There is /usr/local/mailman/var/logs/ However, there is this process that *forced* me to create usr/local/mailman/*logs/mailmansuite.log *as opposed to it just writing to var/logs/ path above Is there a way to make it write its log $var_dir ? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

2 2

Ann: Postorius 1.3.6b1 is now out
by Abhilash Raj Sept. 29, 2021

Sept. 29, 2021

Hey Everyone, I am pleased to announce that Postorius 1.3.6b1 is now out. This is the first pre-release for 1.3.6, which is slated to release next week soon after Mailman Core 3.3.5 release. This release requires Mailman Core 3.3.5 release, so if you are trying out this release, please also upgrade Mailman Core to 3.3.5rc1 (which was just released today). This release includes several new features and bug fixes. A full list of changes is available here[1]. With this release, we have also improved on the localization of the interface, if you want to help out before the release of the stable 1.3.6, please see the instructions for translators here[2]. We use Weblate for translations, so if you are familiar with that, you can directly head over there[3]. Since this is a pre-release version, you can install this using pip via: $ pip install --upgrade --pre postorius django-mailman3 mailmanclient Please also ensure to run the post-install commands as per the upgrade documentation[4] (commands _after_ pip install, needs a post-install heading/anchor in there :-). A release tarball is available on PyPI: https://pypi.org/project/postorius/1.3.6b1/#files Finally, thanks to all the folks who helped with this release in any capacity and made it possible. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-6 [2]: https://docs.mailman3.org/en/latest/translation.html [3]: https://hosted.weblate.org/projects/gnu-mailman/postorius/ [4]: https://docs.mailman3.org/en/latest/upgrade-3.2.html#virtualenv-install thanks, Abhilash

4 5

"this held message has been lost"
by Ethan Furman Sept. 29, 2021

Sept. 29, 2021

I have now seen this message on two different occasions. Any ideas on what is happening? Happy to provide additional information if I am told what is needed (and how to get it -- I'm a web moderator for the list without access to the machine it runs on). :) -- ~Ethan~

2 1