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

Disabled by bounce
by Allan Hansen 11 Sep '24

11 Sep '24

Hi all, Apparently Google just started to get very aggressive about DKIM settings. Some hundreds of my subscribers have had their subscriptions disabled because of Google's bounces. I tried to 'Enable' some of them, expecting that their bounce scores would be reset, but when I list the users, the bounce scores are still 5. Please advise. Will enabling them without the bounce score being reset just cause the server to disable them again. Yours, Allan

10 19

Recipient address rejected: User unknown in local recipient table
by eyoelz＠gmail.com 11 Sep '24

11 Sep '24

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

How to remove Held Unsubscriptions
by Mark 10 Sep '24

10 Sep '24

Hi As a moderator I receive an email each day for "Held Unsubscriptions" for a subscriber that was unsubscribed by the Owner sometime ago (using "Mass operations"). +++++++++++++++++++++++++++++++ The listname(a)domain.com list has 1 moderation requests waiting. Held Unsubscriptions: User: bart(a)example.com Please attend to this at your earliest convenience. +++++++++++++++++++++++++++++++ There is nothing showing under "Subscription requests > Pending approval". Could anyone tell me how I can stop these email notifications? I have access to the mailman shell and the databases. Thanks, Mark

4 6

when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented
by Ken Alker 09 Sep '24

09 Sep '24

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 08 Sep '24

08 Sep '24

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 08 Sep '24

08 Sep '24

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

Can you use @list to include members in accept these non-members in v3?
by Lieuallen, Thomas Otis 05 Sep '24

05 Sep '24

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 05 Sep '24

05 Sep '24

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

Assistance Needed for Ubuntu 22.04 Mailman3 Installation and Configuration
by smiithjohn90＠gmail.com 31 Aug '24

31 Aug '24

Hello Everyone, I'm trying to install Mailman3 on an Ubuntu 22.04 server right now, and I've run across a few obstacles that I'd like help with. I've followed the installation instructions, but I'm having trouble in a couple places, so I was hoping an experienced someone might help me out. This is what I have completed thus far: - I used the apt-get package manager to install Mailman3. - PostgreSQL was configured as the database backend. - Postfix was installed and set up to function as the Mail Transfer Agent (MTA). - Assemble Postorius, Hyperkitty, and the Mailman3 core. Problems I'm Having: Postorius and Hyperkitty Connectivity: I'm having problems making sure that the Mailman core is correctly connected to Postorius and Hyperkitty. I get a 502 Bad Gateway error when I try to access the web interfaces. Despite checking my specifications, I am unable to identify the problem. Problems with Email Delivery: I'm also having trouble with email delivery. Although Mailman appears to be receiving emails, it is not appearing to be sending any out. I think there might be a Postfix problem, but I'm not sure how to solve it. Generally Suggested Practices: Are there any particular security best practices I should be aware of when it comes to Mailman3 installations? I want to confirm that my configuration is both performance- and security-optimized. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://www.igmguru.com/salesforce/salesforce-developer-training https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I would be grateful for any advice or resources! It would be really beneficial if someone with a similar setup could share their settings or troubleshooting procedures. Thank you in advance.

2 1

Dist. List forwarding and DMARC Reject circumvention. Will this pattern work?
by titan160＠hotmail.com 26 Aug '24

26 Aug '24

I would be grateful if someone could vet and verify (or guide otherwise) the following pattern please. With the major mail vendors move to DMARC - Full Reject, I have a small challenge. - We have a number of 365 Distribution List addresses. - These lists accept email from anyone and, currently, then forward those emails onto list members. - List members, however, are NOT necessarily email addresses within the list's mail domain. They might be outlook.com, Gmail, yahoo, Hotmail, username(a)local.ISP. Consequently, DMARC Reject policies are causing these emails to be marked spam as the 365 Dist. List forwarding is not doing any header manipulation. My thinking is: - I could set up a Mailman list (elists.mydomain.com) alongside the 365 Exchange mail domain (mydomain.com) - I leave inbound mail deliver to the 365 Dist. lists. - I reconfigure the (mylist(a)mydomain.com) Dist. Lists to fwd to a similarly-named Mailman address at the email sub-domain (mylist(a)elists.mydomain.com) - The Mailman list, by virtue of having to use the 365 MTA, should be able to accept all inbound from the list (mylist(a)mydomain.com). - Mailman would then need to re-write the mail headers such that the inbound email to-be-forwarded from the Mailman list, both appears to come from the (mylist(a)mydomain.com) address, and also has the 365 'mydomain.com' SPF and DKIM records. And given Mailman has to use the 365 MTA, it would actually be coming from that main mail domain. - Somewhere in there, the original sender's email address would need to be included, such that a Reply-to-All from a receiving List member would not only go back to the List, but also the original sender. My thinking is that with this pattern, I don't need to worry about inbound emails to the list address as that would simply continue to function as normal, and fwdd mails from the List to recipient list members would not be marked spam as the headers would all be good. Is my thinking good? Or am I out of my cotton-pickin' mind?

2 1