- Mailman-users - lists.mailman3.org

Trying to set up mailman3 on my mail server
by Shawn Heisey Oct. 15, 2021

Oct. 15, 2021

I'm having a lot of trouble with trying to set up mailman3 on my mail server. It's on an AWS instance, running Ubuntu 20.04 LTS. All software is installed from Ubuntu packages. Mailman version is 3.2.2. The problem I am trying to troubleshoot first is how this can be happening: Oct 14 11:27:26 2021 (2341) ACCEPT: <f36e1ed0-9d25-b661-9c94-4ce999f6d5fd(a)elyograg.org> Oct 14 11:27:27 2021 (2344) Cannot connect to SMTP server 127.0.0.1 on port 25 From the shell, I can "telnet localhost 25" successfully, even as the "list" user. Apparmor is disabled. The UFW firewall is enabled, which allows all traffic on the loopback interface. I disabled ipv6 at the kernel level, but had the same problem with ipv6 enabled, so I don't think ipv6 is related at all. I do not see any connections in the postfix log that correspond to the mailman connection error. From a fresh install of mailman, I created two mailing lists. Once upon a time I had those lists active on a Debian 6 machine running mailman 2.1.13 ... I copied the mailing list config from that machine over and used the "import21" facility to import the configuration into the new mailman3 install. That worked without error and I can see the lists and their members with the "mailman" command. I found instructions for integration with postfix, and added the required three config lines to the postfix config. When I try to send a message to the list, I get what I pasted above in the mailman log. I think that means the postfix integration is working, and is forwarding to mailman. I'm hoping somebody can give me some pointers, and if more information is needed for troubleshooting, let me know what is needed. I'm also having trouble with the web UI ... I thought I had found what to do with Apache, but it's having problems and I do not know what to do so it works. The UI is not super important right now, I'd like to get the lists working first. I first tried to get help on the IRC channel, but that appears to be a dead end. I did give it several hours. Thanks, Shawn

3 5

'Failed adding message' error when migrating a list from mailman2 to mailman3
by Prasanth Nair Oct. 15, 2021

Oct. 15, 2021

Hello, I'm in the process of migrating some of the lists from mailman2 to mailman3. I'm getting the below error message when I migrate a particular list. *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec can't encode character '\ufffd' in position 252: ordinal not in range(128).* I ran the check_hk_import script before migrating and it was not giving any error. Any idea how to fix this? Kind regards, Prasanth

3 4

Hyperkitty and mailman-hyperkitty releases
by Abhilash Raj Oct. 13, 2021

Oct. 13, 2021

Hello Everyone, I have just tagged and released Hyperkitty 1.3.5 and mailman-hyperkitty plugin 1.2.0 to PyPI. This release includes some changes in the authentication between mailman-hyperkitty plugin and Hyperkitty. For that reason, it is important to upgrade both Hyperkitty and mailman-hyperkitty plugin to the latest versions, or it could result in a broken installation. This release of Hyperkitty has bugfixes, some new features and some security enhancements. A full list of changes is available at: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-5 The release tarball is available at PyPI: https://pypi.org/project/HyperKitty/#files https://pypi.org/project/mailman-hyperkitty/#files You can upgrade your installations by running: pip install mailman-hyperkitty hyperkitty -U After the upgrade, please make sure to run these commands: https://docs.mailman3.org/en/latest/upgrade-3.2.html#post-upgrade Also, make sure to restart Mailman Core after upgrading mailman-hyperkitty plugin. Finally, many thanks to all the people who contributed to this release. -- thanks, Abhilash Raj (maxking)

1 0

Trying to get mailman3 in docker working with external Mysql database
by bob B Oct. 11, 2021

Oct. 11, 2021

Our database group has created the database with (charset=utf8mb4&use_unicode=1) and a user For my docker-compose.yaml I will only have two container sections mailman-core mailman-web which should have these database variables set under each: -DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.server.ip]:[databseport]/[database_name] - DATABASE_TYPE=mysql - DATABASE_CLASS=mailman.database.mysql.MySQLDatabase Are these all correct? in looking at documentation should it be: DATABASE_URL=mysql+pymysql://[database_user]:[database_password]@[database.server.ip]:[databseport]/[database_name]?charset=utf8mb4&use_unicode=1 Or/and should I also use? DATABASE_URL=mysql+pymysql://.... or DATABASE_URL=mysql://... or DATABASE_URL=pymysql://.... Do I have to install pymysql? or is it installed in the dock images? Do I have to run any other commands on the database first? I assume mailman does everything it needs for the database at first launch?

2 2

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

Activation of HyperKitty archive on Debian
by Eggert Ehmke Oct. 4, 2021

Oct. 4, 2021

Is there a straighforward instruction how to make it work on Debian Bullseye? All instructions I find seem to use the git method, and also there are warnings to mix the methods. Installing mailman3 with Debian methods was straightforward, and worked out of the box. Though it purged my mailman2 installation without warning, that was a hard blow. Had to reinstall all my lists in a night session. Also lost the old archives and can't get the new get running.

1 0

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