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

Setting base_url for the domain to use it in the templates.
by Timour Bakeev Sept. 8, 2024

Sept. 8, 2024

Hi all! I'm trying to use extended placeholders for the [templated texts](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/res… in the message footer that are sent to the members: > Along with these, Mailman supports placeholder as URLs for web interface when `base_url` property is set at the Domain level. These include: > domain_url - URL to homepage for a domain. > mailinglist_url - URL to homepage for a mailinglist. > held_message_url - URL to page for handling all held messages. > pending_subscriptions_url - URL to page for handling pending subscription requests. > pending_unsubscriptions_url - URL to page for handling pending unsubscriptions. The REST API docs mention `base_url` as the property of the domain: [domain URLs](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest… But my attempts to use REST API to set it fail: ``` curl --user 'restapi:restpass' \ -X PATCH \ -H "Content-Type: application/json" \ -H 'Accept: application/json' \ -d '{ "base_url": "https://example.net/mailman3" }' \ http://localhost:8001/3.1/domains/example.net | jq '.' { "title": "400 Bad Request", "description": "Unexpected parameters: base_url" } ``` My MM3 instance is the latest(3.3.9), provided by the maxking mailman-core docker image. It looks like there is a lot of confusion about `base_url` in general, as hyperkitty seems also use the property with the same name, for example: https://lists.mailman3.org/hyperkitty/list/mailman-users@mailman3.org/threa… So what is the correct way to get those extended placeholders to work in the templates? It's also not clear to me, what the the primary domain should be for the installation - server hostname, as in `lists.mailman3.org` or the domain, used in the mailing list(s) itself, like `mailman3.org` for mailman-users(a)mailman3.org... With best regards, Timour Bakeev

4 6

Archive not updated
by mailman3＠escapade.ch Sept. 6, 2024

Sept. 6, 2024

Hi All, Env: Debian bookworm debian pkg mailman 3.3.8-2~deb12u2 Status I moved from MM2 to MM3 Import of the archives worked, no issue problem: current emails sent to the list are not being archived. What have I done: - based on the list here I've checked different settings in the cfg files - looked for errors in the log What else can I do to solve this problem ? Many thanks in advance for your help. Manny

3 2

Can you use @list to include members in accept these non-members in v3?
by Lieuallen, Thomas Otis Sept. 5, 2024

Sept. 5, 2024

In Mailman v2, one could use @listname in ‘accept_these_nonmembers’: A line consisting of the @ character followed by a list name specifies another Mailman list in this installation, all of whose member addresses will be accepted for this list. I don’t see this option listed in version 3. Is it no longer supported/allowed? Is there another option? We often send email to lists of lists and have loved that @listname option to help us deliver email to 20+ lists without needing to approve the emails each time or reconfigure all the lists when another sender needs to be added. Thank you Tom Lieuallen Oregon State University

3 4

security app causing django Internal Server Error: /archives/search emails
by sun zi Sept. 5, 2024

Sept. 5, 2024

Greetings, I have set up a few lists and all seems to be working as expected, however I get a large number of emails due to internal server errors received when my security application is testing exploits to list URLs such as the following: https://<mylistdomain>/archives/search?sort=177120&cauft=&page=1&q=../../../../../../../../../../tmb/wditeteet424465304.txt. Is there any django logging filter changes that can be made to avoid receiving these emails? Any assistance would be greatly appreciated. Thank you!

3 3