- Mailman-users - lists.mailman3.org

Notifying owners of membership changes but not moderators
by Perry Kollmorgen Nov. 27, 2024

Nov. 27, 2024

Hi, It looks like this list setting under Automatic Responses is the primary control for if email notifications regarding membership changes are sent or not: Notify admin of membership changes: Yes/No Should administrator get notices of subscribes and unsubscribes? Which is this setting name: "admin_notify_mchanges" I have a fair number of moderators however who don't want these notifications and only a single owner who appreciates the notifications on membership changes. Is there any way to have these only for Owners ? Cheers, Perry

2 4

Migrating users from MM2 to MM3 on a new server?
by jkoral＠luc.edu Nov. 25, 2024

Nov. 25, 2024

Is there a way to copy users from the old MM2 server to a new MM3 server? Also, will it copy their password as well?

2 1

Unexpexted error: if you are sure you want to run as root, specify --run-as-root"
by w.schoener＠alp.dillingen.de Nov. 25, 2024

Nov. 25, 2024

I want to execute some commands in mailman shell. I log in terminal as super user. But when I use the command mailman shell -l my.list.id i get the responce: "error: if you are sure you want to run as root, specify --run-as-root" I tried: mailman shell -l --run-as-root my.list.id but this does not help. Thank you for all hints. Wolfgang

3 3

Moving existing lists to a new domain
by Jeremy Stanley Nov. 21, 2024

Nov. 21, 2024

I've moved lists and archives between domains in Mailman 2.1 and Pipermail, but not yet with Mailman 3 and Hyperkitty. I have a working multi-domain deployment, and one of the organizations using it is working on changing their domain name. Forwarding incoming messages at the MTA and setting up redirects on the Web server are simple enough, but internally within MM3/Django reside the bits I'm less certain about. Since all the lists for the given domain will be moving to the same unused new domain on the existing server, and can move at the same time, I suppose this could be done through (offline if necessary) backend database update queries. Is there anything outside the DB which would need updating or regenerating for this too? Is this how others have tackled similar tasks in the past, or is it recommended to export/import lists one at a time out of one domain and into another? Any tips are greatly appreciated! -- Jeremy Stanley

2 6

Hyperkitty configuration
by Alain D D Williams Nov. 21, 2024

Nov. 21, 2024

Well, I have finally got it to archive something. One simple thing that tripped me up was the ARCHIVER_KEY • mailman-hyperkitty.cfg says: # The shared api_key, must be identical except for quoting to the value of # MAILMAN_ARCHIVER_KEY in HyperKitty's settings. api_key: SecretArchiverAPIKey Which is confusing as it is referring to "# Mailman API credentials" in the file mailman-web.py • mailman-web.py says: MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' It would be good if the lines in mailman-web.py were: # The value below is the same as api_key in mailman-hyperkitty.cfg except that the value here has quotes round it MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' And the lines in mailman-hyperkitty.cfg were: # The shared api_key, must be identical except for quoting to the value of # MAILMAN_ARCHIVER_KEY in HyperKitty's settings (mailman-web.py) # The value here does not have quotes api_key: SecretArchiverAPIKey And if you want to be really nice check if the api_key value is enclosed in quotes and generate a message if so. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

2 1

Must issue a STARTTLS command first when forwarding from old server to new server
by jkoral＠luc.edu Nov. 20, 2024

Nov. 20, 2024

I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS?

2 3

Problems configuring hyperkitty
by Alain D D Williams Nov. 20, 2024

Nov. 20, 2024

I am having another go at installing mailman3 - I seem to have mailman3 & postorius working - although basic testing, much more needed to confirm that I understand it. I want to get hyperkitty working before I start full testing. I am running Debian 12 - Bookworm and have installed the Debian packages. The database is Mysql. This is not a virtualenv setup. There is no documentation in the hyperkitty package so I am following: https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html I read the following: "The database can be created with the following command: django-admin migrate --pythonpath example_project --settings settings " I assume that that will create some database tables. Hopefully this will have been done by installing package python3-mailman-hyperkitty. • What database & tables will that be ? It would be really useful to be told so that I can check. • The config file is: /etc/mailman3/mailman-hyperkitty.cfg This does not contain any comment about databases. Where does hyperkitty get its database parameters from ? • I have several different maildomains each with several lists. Some lists in different domains have the same name. Do I need a different example_project/settings.py for each domain, if so what changes ? One of the next things that I will need to do is to import archives from mailman2. How does the command below change for the different domains ? django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] Is there some better documentation that I have failed to find ? Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

3 2

MM2.1 -> MM3.3 migration. To hold or not hold
by mark＠suburbia.org.au Nov. 19, 2024

Nov. 19, 2024

Hi, I've spent the past week slowly migrating from MM2.1 to MM3.3. One of the lists migrated was set to hold all user posts for moderation, as the list isn't a discussion list but a newsletter sent out on occasion to user/members. I am seeing unexpected behaviour post-migration. The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a non-member posts to the list" -- it says `Hold for moderation` The migrated members when viewed all have a Moderation Action of `Hold for moderation`, which is also expected. When I add new members through Mass operations -> Mass subscribe, the new members have a Moderation Action of `None`. I've looked through the archives of this list, and from what I can tell: According to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > None does not mean no moderation. None means use the list default > as opposed to one of the specific actions defined The thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… seems to also repeat the above, that `none` means the configured setting for the list. However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is `None`, but when I posted to the list from the address, it was not held for moderation, and went through. Am I missing something with the expected functionality? If it helps; Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.11.2 (main, Sep 14 2024, 03:00:30) [GCC 12.2.0] Postorius Version 1.3.8 Cheers, Mark

3 11

Template for Password Reset Email
by Mark Nov. 18, 2024

Nov. 18, 2024

Hi, I have a list and user account set with French as the preferred language. Most message emails (such as the Welcome email) all arrive in French, but not the Password Reset email (shown below) - it arrives in English. I'm guessing that there may not be an .mo file for it. I don't see a template for the Password Reset email in the list's administration settings. Is it possible to create a template for it? Something like "list:user:action:reset"? My thinking is, if creating a template is possible, to (a) write it in French for this list; and (b) rewrite it differently as it's confusing some users. Regards, Mark ----------------------------------------------------------------------- Subject: [lists.domain.com] Password Reset Email ----------------------------------------------------------------------- Hello from lists.domain.com! You are receiving this email because you or someone else has requested a password for your user account. However, we do not have any record of a user with email imark(a)myemail.com in our database. This mail can be safely ignored if you did not request a password reset. If it was you, you can sign up for an account using the link below. https://lists.domain.com/accounts/signup/ Thank you for using lists.domain.com! lists.domain.com

2 6

Removing a moderator via the REST API
by Andy Matthews Nov. 15, 2024

Nov. 15, 2024

You can currently add moderators to a mailing list via the REST API by posting to the `members` endpoint with `role` set to `moderator`. However it doesn't appear that you can remove a person as moderator via the API, per a comment made by Mark on 8/12/24 in this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… We've already got scripts we use to manage moderators on lists, but we're trying to convert everything over to use the API. Does anyone have an idea of when this functionality will make it into the API? Thank you.

2 3