October 2025 - Mailman-users - lists.mailman3.org

Sendgrid experiences
by Andrew Hodgson Oct. 6, 2025

Oct. 6, 2025

Hi. I am temporarily using Sendgrid now on my Mailman instance. Initial observations have been positive. A list with 100 users is racking up email delivers though, I am on the basic paid account which gives me 50k emails per month. I was hoping to use a cheaper provider and pay overage costs per email on the assumption that I'm seeing a spike in traffic today because people have started getting the messages again. Sendgrid is maintaining the Message-Id header which is good for archiving. It is re-writing the Return-Path header though which means that bounce handling in Mailman won't work, but I think all the services do this in some way so I am happy to live with that for the moment. Hope this helps. Andrew.

10 24

Mailman3 equivalent of list_owners binary
by l.reilly＠ucl.ac.uk Oct. 3, 2025

Oct. 3, 2025

Hi, In our Mailman 2 environment we have a script that uses the binaries 'mailman/bin/list_owners' and 'mailman/bin/sync_members' to keep a list of owners up to date. This is handy for sending out service notifications to all list owners. Unfortunately, there doesn't seem to be an exact equivalent in Mailman 3 for list_owners. I've tried using the command 'mailman members --role administrator LISTSPEC' whilst looping through each list from the output of 'mailman lists'. It almost does the job, but in cases where an owner has a display name set the sync fails as it cannot parse these lines. e.g. Cannot parse as valid email address (skipping): Smith, John <john.smith(a)example.com> I can probably try to clean the output of "mailman members" before doing 'mailman syncmembers'. I just wondered if anybody is doing something similar and has a better approach I'm missing? Thanks

3 3

deleting a list of spammers from non-member list
by Philip Bondi Oct. 2, 2025

Oct. 2, 2025

Hello to all: I've studied the following: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… ```bash mailman shell -l mmlist.domain.ca << EOF | tr , '\012' > nonmember.txt list(m.nonmembers.members) EOF ``` I was able to produce a clean list of 50 non-member email addresses that are spammers. How would I take this list of non-members and delete them? I was unable to use mailman delmembers

2 1

Login confusion
by Markus Grandpré Oct. 2, 2025

Oct. 2, 2025

Dear list, We've encountered an issue with Postorius after migrating from Mailman 2.1. It appears that Postorius is treating email addresses with differing capitalization as distinct user accounts. For example, <markus.grandpre(a)uni-konstanz.de> and <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate identities. This is causing significant confusion. Users registered with one capitalization pattern are not seeing the list subscriptions and settings that were previously associated with their account (imported from Mailman v2.1) which used a different capitalization. Is there a known configuration option or method within Postorius (or Mailman 3 itself) to normalize or unify account identification, effectively treating email addresses as case-insensitive for account matching? We need a solution that ensures users see their correct list memberships regardless of the capitalization they use when logging in or that was used during the original Mailman 2.1 import. Thank you in advance Markus -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

11 24