- Mailman-users - lists.mailman3.org

User authentication against IMAP or AD
by Adam Minski 10 Sep '21

10 Sep '21

Hello, is there any supported way to authenticate users against IMAP or Microsoft Active Directory? As a workaround I thought about a OpenID-IMAP or OpenID-AD Bridge, are there any experiences? Thx.

2 1

New messages not being archived
by Sarah H 07 Sep '21

07 Sep '21

I have 2 active lists that are properly mailing out and working, plus an admin testing list that is as well. The list info pane correctly shows the mail volume and the imported archives from the previous 2.1 installation are present for both active lists. None of the 3 lists are generating new entries in the archive, all 3 are set up with default settings except 1 active and admin are set to private. I know that hyperkitty is showing some new content as admin was created in postorius and the list is present in hyperkitty and working in mailman. None of the logs show anything of note, mailmanweb.log has no new entries since it caused a serious issue when I changed the domain, uwsgi-error is the same and uwsgi.log has proper access logs. When trying to add a new thread via the hyperkitty interface I can see the email go through the maillog, I get the email with the entered content and everything else works, it just doesn't add a new thread to the archive. The installation is set up with the default settings from the virtualenv installation guide. Any assistance would be appreciated.

5 30

Mailman container images 0.3.12 is now out
by Abhilash Raj 05 Sep '21

05 Sep '21

Hey Everyone, I have just tagged release 0.3.12 on Github for container images for Mailman 3[1]. This release includes the fix for CVE-2021-40347 that was announced earlier today. For the folks using 0.3 or 0.3.11 release tags, it is highly recommended that you upgrade to this release. This release also bumps the version of Mailman Core to 3.3.4, Mailmanclient to 3.3.3 and Django-mailman3 to 1.3.7. Note that is since the main and v0.3.12 branches are different in many ways, the default documentation[2] and the docker-compose.yaml files in the main branch aren't accurate if you are using the stable release. Please refer to the README[3] at v0.3.12 tag in the Github repo for more accurate docker-compose.yaml and documentation. The project has grown large enough that we need to start versioning the documentation, if someone has experience with versioning docs using Github pages and mkdocs, then I very much need some help here! For those of you who are using the rolling release, it is recommended that you **don't** upgrade to this stable release. The fixes have been pulled into the rolling tags too, so just make sure that you upgrade to the latest published version of rolling release, which as of this writing should be based off on fda837f8d15540e190992c30f7971f50fca54dac commit[4]. This might not be the latest by the time you upgrade if I add a new commit, so look for versions published after 4:00 PM PST 9/5/2021. I am also working on cutting a new release, 0.4.0, which is backwards incompatible with the setup required to talk to web server and MTA (hence the minor version bump!). That should bring the rolling releases and stable releases closer to each other and add improvements around not needing static IPs in the docker network anymore, plus several bug fixes. If someone wants to test the upgrade to 0.4.0 from 0.3 release and is willing to try out the instructions at [5], it would give me some confidence in cutting out the release sooner. The only thing stopping the release of 0.4.0 images is that I haven't verified if the upgrade from 0.3 is documented enough or not. For all the registries listed in README[6], I am still trying to push to Quay (maybe I need to just skip pushing to Quay :-). So, just use the other two to pull the images, Github (ghcr.io) has more generous pull download policy for un-authenticated users though. [1]: https://github.com/maxking/docker-mailman/releases/tag/v0.3.12 [2]: https://asynchronous.in/docker-mailman/ [3]: https://github.com/maxking/docker-mailman/tree/v0.3.12 [4]: https://github.com/maxking/docker-mailman/commit/fda837f8d15540e190992c30f7… [5]: https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release [6]: https://github.com/maxking/docker-mailman#container-registries -- thanks, Abhilash Raj (maxking)

1 0

Hosting
by mail＠peterowens.com.au 05 Sep '21

05 Sep '21

Hi Does anyone know of a server provider offering Mailman3 hosting in Australia? Or a reliable provider OS thanks Peter

2 2

New vulnerability in Hyperkitty master branch
by Abhilash Raj 05 Sep '21

05 Sep '21

Hey Everyone, A new vulnerability was reported against Hyperkitty’s git master branch branch which can expose the archives of a private Mailing List through the new Feeds API that was added to Hyperkitty recently to someone who isn't a member or logged-in. Thanks to Ngo Wei Lin for reporting this vulnerability. This bug does not affect any stable released version of Hyperkitty and only affects installations from source (1.3.5b1 version). To differentiate from the vulnerable version, I have bumped the version in master branch to 1.3.5b2, so if you have 1.3.5b1 installed, you should upgrade! The fix for this bug has been committed to master branch[1][2] less than an hour ago as of this writing. If you are using git branches to install Hyperkitty, you can upgrade using the following command: $ pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master I have also triggered a build for Mailman container images[3] with this changes, so if you are using the rolling container images (which are the only affected ones), then you should upgrade to the latest one when the build[1] finishes (approximately in next 30mins). Do note that this version of rolling release of mailman-web image also includes the fix for the vulnerability announced against Postoruis earlier today. You can verify that you have the fixed version of Hyperkitty in the image by running: $ docker run -it --entrypoint bash maxking/mailman-web:rolling bash-5.0# pip list | grep HyperKitty HyperKitty 1.3.5b2 Ensure that you get 1.3.5b2 version. [1]: https://gitlab.com/mailman/hyperkitty/-/merge_requests/362 [2]: https://gitlab.com/mailman/hyperkitty/-/commit/ed086015acbf66ba377e2af7f6e7… [3]: https://github.com/maxking/docker-mailman/runs/3519658592 -- thanks, Abhilash Raj (maxking)

1 0

CVE-2021-40347: New security release for Postorius
by Abhilash Raj 05 Sep '21

05 Sep '21

Everyone, A security vulnerability was reported against Postorius recently which allows any logged-in user to unsubscribe any other member on any other list on same Mailman installation using a specially crafted POST request due to a missing ownership check. This has been assigned CVE-2021-40347. This affects all past versions of Postorius including 1.0.0. Thanks to Kunal Mehta for the security report and a quick patch to fix the vulnerability. I am also attaching a minimal patch that fixes it along with this email, without tests and NEWS so that it applies to older versions of Postorius easily (I have tested the included patch with 1.3.3, 1.3.2 git tags). Upgrading to 1.3.5 release is highly recommended and it mostly includes the fix for this vulnerability (and a small compatibility fix for django-mailman3 1.3.6) so it shouldn’t introduce any other bugs. You can upgrade to this release by running: $ pip install postorius==1.3.5 A full change log is available here[1] as usual and can be downloaded from PyPI[2]. [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-5 [2]: https://pypi.org/project/postorius/1.3.5/ Since there aren't many changes, this release requires 3.5+ like 1.3.4. Although, note that the next release will drop support for 3.5 and will support 3.6 only. For those of you who use container images, I am working on 0.3.12 of container images right now, so look out for that announcement. For those of you using the rolling releases, you can already upgrade to the latest version of the rolling release as it has the fix. -- thanks, Abhilash Raj (maxking)

1 0

domain owner role
by Rainer Herbst 01 Sep '21

01 Sep '21

Dear all, recently, I have added one account to a domain as domain owner. I did expect the new owner to see all lists in that domain in Postorius, but he sees no list at all. Is this the way it should be? How can I add administrators able to perform administrative tasks on all lists in Postorius? Viele Grüße, Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

2 1

How to increase maximum size of the message in mailman
by Shashikanth Komandoor 31 Aug '21

31 Aug '21

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in-built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values. I am almost running 2200 lists with 128 GB RAM and 24 Cores on a single VM and on which all the mailman 3 components are running. I have been running this setup in production for the past 2 years and 6 months. I have recently encountered a scenario where a user sent mail with a PPT attachment to one of the lists on the said mailman server. The mail is received by postfix on the mailman server and is handed over to mailman at *0.0.0.0:8024 <http://0.0.0.0:8024>.* But the /var/log/maillog says the below error during the above hand shake. *status=bounced (host 0.0.0.0[0.0.0.0] said: 552 Error: Too much mail data* I have browsed google for understanding and fixing the issue. During which I encountered the information given by Mr. Mark Sapio at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…. But I could not fix the issue as it is mentioned the default size limit is 33554432. I request someone to suggest where I can customize the value 33554432 and put a higher value or can be configured without any limit. I have configured message_size_limit as 100MB at postfix level. I would like to configure, in fact, the same at mailman level too. But I don't understand where to edit. I tried editing the variable DATA_SIZE_DEFAULT value in /var/lib/mailman/mailman/.tox/py36-nocov/lib/python3.6/site-packages/aiosmtpd/smtp.py file but unfortunately no luck. So, could someone please help us in this regard ? Also, please also let me know if there is any limitation specific for the attachments so that I can customize that too respectively. -- Thanks & Regards, Shashi Kanth.K 9052671936

3 2

how to become member of mailman-users list
by Shashikanth Komandoor 31 Aug '21

31 Aug '21

Hi Team, One of my colleagues is trying to become a member of the mailman-users list but she is not able to become so even after sending multiple emails to the list. Could someone suggest this ? -- Thanks & Regards, Shashi Kanth.K 9052671936

2 2

Question about message bounce stats
by Ruth Ivimey-Cook 30 Aug '21

30 Aug '21

When I used Mailgun some time back, it had a feature of, for any specific outgoing mailing, being able to show you stats and other details of which mails were received ok, which bounced, and which were undeliverable, which I found helpful to check every so often. Their system also kept track of long-term trends, eg for addresses that frequently failed. Does Mailman3 keep such stats, and if so is there any way to get access to them, even if only API? I would think it useful to do so (and yes, for individual outgoing messages at least for a period). Regards, Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 9