- Mailman-users - lists.mailman3.org

Trying to understand the mailman.cfg from the virtualenv installation guide
by unite42＠disroot.org Sept. 11, 2024

Sept. 11, 2024

Hello, I'm trying to install Mailman3 following the Virtualenv Installation guide. I would like to understand why the configurations in the displayed mailman.cfg are recommended. Especially the following two: [archiver.prototype] enable: yes "The prototype archiver stores messages individually in var/archives/prototype/LIST_NAME/." https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Do I need this, when using hyperkitty? Is this a fail-safe recommendation? [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 What is the background of these recommendations? Thank you for your help! Greetings unite42

4 4

Recipient address rejected: User unknown in local recipient table
by eyoelz＠gmail.com Sept. 11, 2024

Sept. 11, 2024

Hi, I set up mailman3 following the instruction on the mailman3 website. Everything went well until I got to the “Hooking up your mail server” at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… . I followed the instructions, but when I try to send an email to one of the lists I created, I get the error below. I have postfix installed on the same server as mailman3. I was wondering if I missed something during the mail server set up process. Relevant parts of my config files are below. Error: Aug 19 15:06:10 xxx-rocky9 postfix/smtpd[153746]: NOQUEUE: reject: RCPT from xxxx.xxxxxx-xx.iphmx.com[xx.x.xx.xxx]: 550 5.1.1 <devops(a)xxx.xxx.edu>: Recipient address rejected: User unknown in local recipient table; from=<xxx(a)xxxx.edu> to=<xxx(a)xx.xx.edu> proto=ESMTP helo=<xx.xx-xx.iphmx.com> mailman.cfg [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no mailman/config/postfix.cfg [postfix] postmap_command: /usr/sbin/postmap transport_file_type: hash main.cf smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = xxx.xxx.edu alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = $myhostname, mailman, localhost.localdomain, , localhost relayhost = [xx.xx.xx.xx] mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 recipient_delimiter = + inet_interfaces = all inet_protocols = all transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps =$alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains Thanks, Eyoel Mengesha

3 2

Best practice when deleting a mailing-list (archiving an old list)
by Marc SCHAEFER Sept. 10, 2024

Sept. 10, 2024

Hello, With Mailman2, my list deletion procedure was quite simple: - export the list configuration with config_list - export the list members - archive the archives somewhere - remove the aliases manually - delete the list I think that with Mailman3, the above can be done as follows: - export the list configuration with https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… - export the list members with https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/model/docs… - archive the archives somewhere: this is my main question - remove the aliases manually: this is automatic - delete the list So, is there a simple way to export a list's archives in a way it can be reimported, now that everything seems to be in the database? Archiving the whole database is an issue here (its compressed dump size > 2 GB). Thank you for your ideas or pointers!

2 1

Mass Subscribe caused Delivery Status to become "unset"
by chad.hays86＠gmail.com Sept. 9, 2024

Sept. 9, 2024

One of the admins on our Mailman site said they recently performed a mass subscribe operation on list, however they noticed that for each user they subscribed, their "Delivery status" was unset, so they weren't receiving email updates whenever there was new activity on the list. They had to go in after the fact and manually set it to "Enabled" for each user that was subscribed via the mass subscription operation. Is this behavior expected? During the mass subscribed, pre-confirm, pre-approved, and pre-verified checkboxes were all checked.

3 3

It takes a very long time to display the list archives
by bryan.kartzman＠yu.edu Sept. 9, 2024

Sept. 9, 2024

When I try to display the archives of any list in my mailman3 installation it takes forever for it to display. We are talking a good three or four minutes. It doesn't matter if there are 100 messages in the archives or just one. We are using postgres for the mailman3 and django databases. On the server, when I click to display a list's archives, I see the process "gunicorn: worker [gunicorn]" is using nearly 100% of available CPU.

1 0

when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented
by Ken Alker Sept. 9, 2024

Sept. 9, 2024

We have been experiencing a strange anomaly. We are running a small-ish list. When a particular subscriber to the list sends an email to the list, a couple of dozen (or more) of the recipient's of the message end up with their bounce scores incrementing. This particular subscriber uses about three different email addresses when he sends his messages and every one of them causes this behavior. There is another subscriber who also causes this behavior when he sends an email to the list, but only one of the two email addresses he sends from causes this behavior. There is a third person who causes this behavior every time. There are dozens of other subscribes who don't generate this behavior when they send to the list. I can't figure out why this is occurring. I *assume* that Mailman re-writes the headers to add DKIM, etc., before sending them to the list recipients but it sure seems like something in the header from the original sender is ending up in the final header (or something is LACKING) which is not liked by the recipient's MTA's. It doesn't seem like a subscriber sending an email to the list should be able to cause this behavior - but I'm no expert. The recipients appear to be using many different mail platforms (ie. their addresses are not all, or even mostly, @google.com or some other domain; the recipients appear to be a pretty good cross section of platforms). This has been going on all year (maybe longer). Any help or troubleshooting suggestions would be greatly appreciated.

5 9

How to tell which lists on my server are being used?
by Bryan Kartzman Sept. 8, 2024

Sept. 8, 2024

Is there an easy way to tell which lists on my Mailman 3 installation are being used (i.e. received posts in the last two or three months)?

4 4

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