December 2022 - Mailman-users - lists.mailman3.org

500 error on Held Messages page
by Dan Caballero March 30, 2023

March 30, 2023

Hello, I searched the list but couldn't find anything specific to the error seeing with held messages for this specific list. See output below from the mailman.log. The problem doesn't seem to be related to the database listarchiver table. Please advise. -- Dan Caballero Caltech Systems Administrator MySQL [mailman3_prod]> select * from listarchiver where mailing_list_id='4899'; +------+-----------------+--------------+-------------+ | id | mailing_list_id | name | _is_enabled | +------+-----------------+--------------+-------------+ | 1872 | 4899 | mhonarc | 0 | | 1873 | 4899 | mail-archive | 0 | | 1874 | 4899 | prototype | 0 | | 1875 | 4899 | hyperkitty | 1 | +------+-----------------+--------------+-------------+ 4 rows in set (0.001 sec) -------------------------------------------------------------------------------------------------- 2022-09-20 14:44:17 [FALCON] [ERROR] GET /3.1/lists/jewishlife(a)caltech.edu/held?count=10&page=1 => Traceback (most recent call last): File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 182, in on_get resource = self._make_collection(request) File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in _make_collection entries = [as_dict(resource) for resource in collection] File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> entries = [as_dict(resource) for resource in collection] File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 173, in _resource_as_dict assert resource is not None, resource AssertionError: None

3 13

mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected
by Christian Stalberg March 8, 2023

March 8, 2023

Environment: Debian 10; Postfix 3.4.14; GNU Mailman 3.3.5; Mailman Core API Version 3.1; Mailman Core Python Version 3.7.3 Digging a hole after having simply created a new mailing list. This has not happened before. Steps taken: -Created list via web interface -Added subscribers via web interface -Sent email to listname -Received error bounce: This is the mail system at host zarathustra.ccalternatives.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <Deepadaptation(a)lists.ccalternatives.org>: mail for lists.ccalternatives.org loops back to myself -Added lists.ccalternatives.org to the mydestination line in /etc/postfix/main.cf and restarted Postfix -Now a new error message: <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command)

5 7

Multi-domain oddities in Hyperkitty and Postorius
by Jeremy Stanley Feb. 16, 2023

Feb. 16, 2023

In the OpenDev Collaboratory we've got a bunch of separate Mailman 2.1 vhosts we've started migrating into a single Mailman 3.3.7 server, desiring to take full advantage of its improved multi-domain support. For the most part everything is working great (kudos to everyone who maintains the software and documentation, it's excellent). One of the things our users noticed fairly quickly was Hyperkitty on the second vhost was incorrectly showing the FQDN of the first vhost near the top of its pages. This is covered in the FAQ of course, and seems to imply that what we want is to switch the SITE_ID from 1 to 0 in our settings.py in order to take advantage of magic domain-guessing behavior. So far so good. Unfortunately, SITE_ID = 0 seems to explicitly require the addition of "mail hosts" (or "mail domains" from Django's perspective), and all the web routing returns error pages for any list sites besides the first one since, by default, our server did not have these predefined. What's odd is that, if I log into Postorius as admin and visit the "manage domains" page, suddenly the database gets populated with mail hosts for all of the FQDNs associated with our imported mailing lists. I would not have expected merely visiting that page as an admin to have a side effect of adding entries for the "missing" mail hosts, is that an intentional behavior or merely a bug? Once these entries are automatically added by visiting that page, they're all associated with the one "web host" ("site" in Django) we have for the server, and now the list filtering functionality in Postorius breaks and any of the vhosts all display the full set of mailing lists on the server rather than only those associated with a particular vhost (note that this seems to only be confusing Postorius, Hyperkitty has them correctly filtered still). Okay, so it looks like this is because the mail hosts are all tied to the one web host. We can create additional "sites" in the Django admin UI and then switch the association of the mail hosts to those distinct web hosts. But after doing so, the first vhost still seems to show an unfiltered list of all lists in Postorius (Hyperkitty continues to be fine), while Postorius on the other vhosts correctly shows their filtered sets of lists instead. I also noticed when mailman-web is starting up, its log claims the first site is being set as the "default domain," so have to wonder if that's related to this behavior. Should we create an extra web host to serve as the "default" so that all our typical vhosts get the expected list filtering behavior, or am I completely off-base and there's a much better approach I've missed? Sorry this is so long, I feel like I have at most a tenuous grasp of the details and variables involved, but hopefully it makes sense to someone. Thanks in advance for any recommendations or guidance. -- Jeremy Stanley

2 9

About to Install MM3 -- Seeking clarification
by Onyeibo Oku Jan. 30, 2023

Jan. 30, 2023

Good Morning Everyone, I installed and managed mailman 2 for about two years. I am now ready to try Mailman 3. The documentation for version 2 was lucid and this forum was quite helpful in the past. Now I'd like to proceed with installating MM3 but I doubt my understanding of the docs. It seems to assume that users will know what to do. Okay, don't laugh! I just want to be sure what I am doing. Does the following sequence resemble the proper steps? 1. Download the source from a git repo (I understood that one) 2. Create a virtual environment (venv perhaps ... not stated explicitly) 3. activate the virtual environment 4. from the git project root, run: ./mailman start I know, its stupid. I had to ask. It would really build my confidence someone would confirm the above steps or counter then with something very explicit. What about process ownership? Do I need to have a unix mailman user? What else do I need to get mailman up and running before proceeding to configuration. Ahaa! I perused the config docs a bit. Where can I find the .cfg file? I hope these questions are not too annoying. Regards Onyeibo

6 46

Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )
by Patrick Brückner Jan. 13, 2023

Jan. 13, 2023

Hi everyone, one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back. What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list. The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain. Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again. According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API. Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)? Thanks in advance, Patrick

4 7

Docker or virtualenv?
by Johannes Rohr Jan. 7, 2023

Jan. 7, 2023

Dear all, I have noticed that Ubuntu's current LTS no longer contains packages for mailman2 and its mailman3 packages are incomplete. So, prior to upgrading the server, I will have to migrate from mailman2 / distro packages to mailman3 installed either in virtualenv or docker. I have got zero experience with virtualenv and some experience with Docker. Overall, the docker method looks easier. Is docker the default method by now? Thanks! Johannes

7 13

Extracting mailing list users
by Jan Eden Jan. 2, 2023

Jan. 2, 2023

Hi, I would like to export users of my mailing lists including their full name (if present). The export button in Postorius creates a CSV with addresses only, and the tool bin/list_members mentioned in the [Mailman 2 FAQ] does not seem to be available in Mailman 3. I have full access to the server/database, so scraping the web interface with [Mark's script] seems unneccessary. Is there an SQL statement (or an equivalent of bin/list_members) to extract the data? Thanks, Jan [Mailman 2 FAQ]: https://wiki.list.org/DOC/How%20do%20I%20extract%20%28export%29%20a%20list%… [Mark's script]: https://www.msapiro.net/scripts/mailman-subscribers3.py

6 19

Web UI setup
by Lars Bjørndal Dec. 31, 2022

Dec. 31, 2022

Thanks a lot for all your valuable help! I've followed the guide at <https://docs.mailman3.org/en/latest/install/virtualenv.html> I need to run mailman 2 and mailman 3 in parallel until I've migrated all lists, on several domains. I created the file /etc/httpd/conf.d/mailman3.conf with the content <VirtualHost *:80> ErrorLog logs/mailman3-error_log CustomLog logs/mailman3-access_log common RewriteEngine on RewriteCond %{HTTPS} off [NC] RewriteRule ^/mailman3(/.*) https://%{HTTP_HOST}/mailman3$1 [L,R=permanent] </VirtualHost> <VirtualHost *:443> ErrorLog logs/mailman3-error_log CustomLog logs/mailman3-access_log common include conf.d/certref.inc SSLEngine on </VirtualHost> <location /mailman3> ProxyPass http://localhost:8000 </location> The idea is to prepare mailman3 for several virtual domains. When I connect to lamasti.net/mailman3, the title is example.com. How can I change that? Thanks Lars

2 1

Apache
by Lars Bjørndal Dec. 31, 2022

Dec. 31, 2022

I have already Apache installed and running for mailman2 and other resources. How do I serve mailman3 from Apache for the respective domains? Thanks in advance Lars

3 3

Early release of mailman 3.3.8 possible?
by Torge Riedel Dec. 31, 2022

Dec. 31, 2022

Dear list / devs, is it possible to release 3.3.8 early? As far as I can see it is a prereq for my planned upgrade of the server from Ubuntu LTS 20.04 to Ubunto LTS 22.04. I use MySQL in my setup (own installation in venv), so my installation is affected by #1044, which is closed in 3.3.8 Also Ubuntu LTS 22.04 comes with Python 3.10 (https://packages.ubuntu.com/search?suite=jammy&keywords=python3) where the support is also stated earliest for 3.3.8 (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.…) Am I right with my findings? I planned to upgrade the server until end of this year, because there is less traffic in the last days of a year. But I think unless 3.3.8 is not released, I cannot update the server. Kind regards Torge

4 5