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

Footer question...
by David Partain 27 Jul '21

27 Jul '21

Hi, Background: I have a painful mailman3 installation based on ubuntu 18.04 packages, a mistake I regret but have to live with until I can finish a fresh install of the latest. Currently running on mailman 3.1.1-9 and python-django-mailman3 version 1.1.0-4 (if that matters). I migrated > 1200 lists from an old mailman2 installation. That brought along all of the footers (naturally), and now I'm trying to get rid of them but failing miserably. I've spent a fair bit of time reading archives of this list, but I'm still stuck. Here's what's configured... In /etc/mailman3/mailman.cfg: -------------------------------------------------------------------------------------------------------------------------- var_dir: /var/lib/mailman3 # Root directory for site-specific template override files. template_dir: $var_dir/templates -------------------------------------------------------------------------------------------------------------------------- In that directory, list-specific directories like: /var/lib/mailman3/templates/lists/list.mydomain/ and, as an example, en/list_member_digest_footer.txt For the migrated lists, that might have: ------------------------------------------------------------------------------------------------------------------------- _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} ------------------------------------------------------------------------------------------------------------------------ Based on what I've read elsewhere, my first attempt was to create an empty file doing 'cp /dev/null list_member_digest_footer.txt' to replace the one installed in migration. That had no effect. As a shot-in-the-dark, I did 'cp /dev/null list:member:regular:footer.txt' to see if that might have some effect. Nope. I suppose some decision is made earlier in the process to tack on the footer, so these files I'm manipulating have zero effect. Anyone have suggestions of what I can do? Thanks in advance. David

2 1

requiring questionnaire from new users
by Ethan Furman 27 Jul '21

27 Jul '21

Greetings! Is there a way to require new users to answer a questionnaire when they subscribe? I suspect that one of the lists I manage is getting a lot of subscribers who don't understand what that particular list is for, and having to answer a question or two would allow me to direct them to better resources. Any and all info appreciated! -- ~Ethan~

2 1

non-members issue with held email
by Lars Schimmer 20 Jul '21

20 Jul '21

Hi I want to check a issue with a few mailing lists of us. We do run mailman3 on debian with debian package 3.2.1-1 (not yet updated for backup reasons). We created a new mailinglist, added 3 owner and several members. Now we want some email addresses to post to that list but not receive mails from the list. So I added those to the "non-member" area of the mailinglist and checked every non-member to "acceppt at once". But on a test, a email address, which is owner AND non-member, cannot send to mailinglist, always get a "HOLD: ...... The message is not from a list member" The Email address in that HOLD log entry is the same as in the owner/non-member list. Any idea howto check the mailman3 logs for this case? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

2 1

Deleting default "example.com" domain breaks everything
by mcarter＠corneredrats.com 18 Jul '21

18 Jul '21

Hello. I'm new with v3 of mailman. Installed via aptitude on deb10. After I logged in as admin, I created my actual domain, as "example.com" was there by default. I then deleted example.com, and everything broke. The only site I had was still using example.com. How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? Thanks.

3 2

Debian10 pkg install: set up Postorius superuser?
by mcarter＠corneredrats.com 16 Jul '21

16 Jul '21

Hey, all. I've installed mailman3 to replace mailman2 from the Deb10 package mailman3-full. Command line appears to work, but I had to manually add the Uwsgi module to get the user web site to run. I can't find a reference to what the default admin user password is, and running "python settings.py createsuperuser" doesn't work with error: root@mail:/usr/share/mailman3-web# python manage.py createsuperuser Traceback (most recent call last): File "manage.py", line 8, in <module> from django.core.management import execute_from_command_line ImportError: No module named django.core.management Any idea what else needs to get installed that the aptitude package missed? Any way to just manually set the admin's password without having to install anything else?

1 1

Problems with hyperkitty
by Lucia Moreno 15 Jul '21

15 Jul '21

Dear mailman support, We have an issue with hyperkitty. In the last month the space used by hyperkitty_email postgres table has increased from 54GB to 400GB and it is constantly increasing with no end. Is there any simple way of knowing what is taking so much space? Like for example display how much archiving space (or achived emails) is used by each mailing list? Looks like a mailing list has gone crazy but from the logs everything looks fine. Any help is very much appreciated. THanks a lot for your precious help!!

2 1

[MM3-users]Is it possible to grant all users the ability to Create List
by Carrie Knox 13 Jul '21

13 Jul '21

Hello, Our company is evaluating mailman3 as an option for company internal list serving. One of the requirements is that anyone with access to the list server be allowed to create and manage lists. Is this possible? If so, how? Is there a "create list" role that can be added for all registered users? Thanks

5 5

accept mails from several Users, not list members beside members, howto
by Lars Schimmer 13 Jul '21

13 Jul '21

Hi I do look out for a method to accept mails from list members and a number of 20-30 Email addresses (not list members) to a mailing list. All others should be denied to post to the list. I can add those as non-members, but AFAIK I cannot define a special rule for them in "message acceptance". Under "message acceptance" the line "non-members" is set to deny, but if I set it to "default procesessing" - will it allow ALL email addresses, or just the group of "non-member" users? Thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 3

cache files?
by Dave McGuire 13 Jul '21

13 Jul '21

Hi folks. I'm seeing quite a few .css files, thousands of them totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. Some of them date back to when I set up the mm3 instance a few years ago. Is this expected, or am I missing a cron job or something to clean them up? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

2 3

Trying basic install of mailman3 in docker, but how do you set allowed hosts?
by bob B 12 Jul '21

12 Jul '21

I am starting small, My goal is just to get mailman3 running in docker and test the website access via curl from the host, then I will move on from there In the docker instructions it says SERVE_FROM_DOMAIN: The domain name from which Django will be served. To be added to ALLOWED_HOSTS in django settings. Default value is not set. This also replaces Django's default example.com SITE and becomes the default SITE (with SITE_ID=1). But where do I set the ALLOWED_HOSTS I added this to the yaml file - ALLOWED_HOSTS=127.0.0.1 under environments mailman-web: image: maxking/mailman-web:0.3 container_name: mailman-web hostname: mailman-web depends_on: - database links: - mailman-core:mailman-core - database:database volumes: - /opt/mailman/web:/opt/mailman-web-data environment: - UWSGI_STATIC_MAP=/static=/opt/mailman-web-data/static - ALLOWED_HOSTS=127.0.0.1 - DATABASE_TYPE=postgres - DATABASE_URL=postgres://mailman:mailmanpass@database/mailmandb - SECRET_KEY=333blah-blah-secret - HYPERKITTY_API_KEY=333someapikey ports: - "127.0.0.1:8000:8000" # HTTP - "127.0.0.1:8080:8080" # uwsgi networks: mailman: But when I try: [docker-mailman]# curl 127.0.0.1:8000 <h1>Bad Request (400)</h1>[root@bmimailmandr1 docker-mailman]# [root@bmimailmandr1 docker-mailman]# I see this in the logs [docker-mailman]# cat /opt/mailman/web/logs/mailmanweb.log WARNING 2021-07-08 17:40:46,979 1642 django.request Bad Request: / ERROR 2021-07-08 19:20:58,416 1641 django.security.DisallowedHost Invalid HTTP_HOST header: '127.0.0.1:8000'. You may need to add '127.0.0.1' to ALLOWED_HOSTS. WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: / WARNING 2021-07-08 19:20:59,032 1641 django.request Bad Request: /

2 1