Mailman 3 May 2023 - Mailman-Users

Running two list with same email prefix
by Andrea Cappelli 27 Feb '24

27 Feb '24

Hi all, I'm running a mail server with Debian Lenny, MTA is Postfix and i will use postfix-to-mailma.py script to run list I would set up Mailman for running mailing list with same email prefix on different domains, obvious with different list names For example we have ml.domain1.com and ml.domain2.net, i would like to have LISTADDRESS LISTNAME tech(a)ml.domain1.com tech-ml.domain1.com tech(a)ml.domain.2.net tech-ml.domain2.net In this way i can have the same address on differente domains and Mailman (my version is 2.1.11) can distinguish between lists because the list name is different. The list name will be also used to access web interface, so we have http://ml.domain1.com/mailman/admin/tech-ml.domain1.com http://ml.domain2.net/mailman/admin/tech-ml.domain2.net Is possible to accomplish this task? Any idea?

4 5

Hide list address?
by Ricardo Kleemann 17 Nov '23

17 Nov '23

Hi, Is there any way to configure Mailman such that, for an announcement-only type list, when a message is sent to the list, the To: shows the member's address, rather than the list address? Some list software allows the ability to hide the list address itself, so that address is not advertised. I couldn't find any configuration specific to that.

7 6

Hevy resource footprint forces backdrop to mailman 2.1
by Martin Lorenz 05 Aug '23

05 Aug '23

Greetings, after many years of smoothly running a mailman2 instance I had to migrate my virtual server to a new provider. There I found, that mailman2 was no longer supported and tried to migrate to mailman3 .. with much pain and no success. Mailman3 keeps crashing my v-server and swallows almost every mail sent to any of the migrated lists. So I wanted to switch back to mailman 2.1.39 by installing from the source package and found that this also fails due to missing python2 support. How to solve this? Thank you very much

7 22

Size limit leads to rejection instead of moderation
by Thomas Gramstad 04 Jun '23

04 Jun '23

I have a size limit on postings to my mailing lists so that I can check and decide whether to approve or reject big postings. That is, they go to the moderation approval queue. However, a list has started to reject messages back to the sender, instead of putting them in the moderation queue. This is new, unexpected and unwanted behavior. I thought some list parameter may have been changed, but I have looked through the setting pages and I can't find where or what. How can I restore the desired behavior, that big messages are put in the moderation queue, and not automatically rejected? Thomas Gramstad

4 3

Barrage of bounce notifications
by Krone, Elizabeth C 27 May '23

27 May '23

Good afternoon all, I manage a few listservs (maintaining members and tending pending posts) and today I have received almost 80 separate "Uncaught bounce notification" emails for one of the lists. There are rarely any for this list and I would like to know if there is something I can do to stop the spam. I have received 5 more while typing this email. I am not a tech person but any suggestions are welcome. Thank you! Elizabeth

7 14

Question about content filtering in message body
by Scott High 26 May '23

26 May '23

Hi, Newbie, so please bear with me. I'm looking for a way to content filter the text of the message body (i.e. blacklist bad words, etc) to a list. I've looked at Content Filtering, but that appears to be associated with message type, not message text? And Topics filters appears to just be focused on the header and subject information? Can someone point me in the right direction? Thanks!

5 6

Sending messages to address <>
by Jigme Datse 10 May '23

10 May '23

I'm pretty sure this is a configuration issue on my part, but when I send messages to my list, it will send with a: To: <> Though I'm not *quite* sure if that's the To: line, or the RCPT TO... I suspect the latter.

2 2

problem with reply behavior
by public＠eli-damon.info 07 May '23

07 May '23

Hi, all. I am trying to set up a Mailman list, and I've encountered a problem. I'm new to this, and I could really use some help. I want replies to go to the individual poster, but they're going to the list instead. I have first_strip_reply_to set to No and reply_goes_to_list set to Poster. I've tried posting an original message from two different email clients (Thunderbird and Roundcube), and I've also tried replying to those message using the same two clients. You can an example below. Do you have any idea what I'm missing? Thank you. Eli ================ Return-Path: <comm-disability-bounces(a)eli-damon.info> Delivered-To: public(a)eli-damon.info Received: from bexa.itabix.com by bexa.itabix.com with LMTP id cAdDGKBhVWRqGQAAiAjaog (envelope-from <comm-disability-bounces(a)eli-damon.info>) for <public(a)eli-damon.info>; Fri, 05 May 2023 16:05:52 -0400 Return-path: <comm-disability-bounces(a)eli-damon.info> Envelope-to: public(a)eli-damon.info Delivery-date: Fri, 05 May 2023 16:05:52 -0400 Received: from [::1] (port=58672 helo=bexa.itabix.com) by bexa.itabix.com with esmtp (Exim 4.96) (envelope-from <comm-disability-bounces(a)eli-damon.info>) id 1pv1ge-0002tG-1n; Fri, 05 May 2023 16:05:52 -0400 Received: from 071-010-231-086.res.spectrum.com ([71.10.231.86]:59560) by bexa.itabix.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from <eli(a)eli-damon.info>) id 1pv1gd-0002si-0a for comm-disability(a)eli-damon.info; Fri, 05 May 2023 16:05:51 -0400 Message-ID: <ecb5c14d-711c-5b0d-0e40-5d2747591b34(a)eli-damon.info> Date: Fri, 5 May 2023 16:05:50 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Content-Language: en-US To: comm-disability(a)eli-damon.info From: Eli Damon <eli(a)eli-damon.info> Subject: [COD] test 5 X-BeenThere: comm-disability(a)eli-damon.info X-Mailman-Version: 2.1.39 Precedence: list List-Id: "Commission On Disability $internal$" <comm-disability.eli-damon.info> List-Unsubscribe: <http://eli-damon.info/mailman/options/comm-disability_eli-damon.info>, <mailto:comm-disability-request@eli-damon.info?subject=unsubscribe> List-Archive: <http://eli-damon.info/mailman/private/comm-disability_eli-damon.info/> List-Post: <mailto:comm-disability@eli-damon.info> List-Help: <mailto:comm-disability-request@eli-damon.info?subject=help> List-Subscribe: <http://eli-damon.info/mailman/listinfo/comm-disability_eli-damon.info>, <mailto:comm-disability-request@eli-damon.info?subject=subscribe> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: comm-disability-bounces(a)eli-damon.info Sender: "comm-disability" <comm-disability-bounces(a)eli-damon.info> Test 5 -- comm-disability mailing list comm-disability(a)eli-damon.info http://eli-damon.info/mailman/listinfo/comm-disability_eli-damon.info ================

2 1

rebuilding and replacing.
by Jeffrey Westgate 06 May '23

06 May '23

Greetings. It's been a while since I've had an issue, mostly because mailman just works. (and thank you for that) We're running old - SciLin 7.9 / Mailman 2.1.20, but are upgrading out of necessity. We've chosen RHEL 8.7 and Mailman 2.1.39 All installed, created a new list... and stopped. Not sure what I missed, but in 2.1.20, after a newlist is created, we get a block of all the required aliases to put in the /etc alias file - similar to (for example) - ##jeffslist mailing list jeffslist: "|/usr/lib/mailman/mail/mailman post jeffslist" jeffslist-admin: "|/usr/lib/mailman/mail/mailman admin jeffslist" jeffslist-bounces: "|/usr/lib/mailman/mail/mailman bounces jeffslist" jeffslist-confirm: "|/usr/lib/mailman/mail/mailman confirm jeffslist" jeffslist-join: "|/usr/lib/mailman/mail/mailman join jeffslist" jeffslist-leave: "|/usr/lib/mailman/mail/mailman leave jeffslist" jeffslist-owner: "|/usr/lib/mailman/mail/mailman owner jeffslist" jeffslist-request: "|/usr/lib/mailman/mail/mailman request jeffslist" jeffslist-subscribe: "|/usr/lib/mailman/mail/mailman subscribe jeffslist" jeffslist-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe jeffslist" We then run 'newalises' and move along. This block did not appear, and it's been over a decade since I built the old one. I don't remember doing anything special to get the new alias information, so I'm blindly assuming - something changed? How do I get this information now? I can't seen any difference in the scripts. thank you - Jeff W

3 2

Re: Amazon SES and mailman
by Sam Darwin 06 May '23

06 May '23

Also posted this question to the mailman3 list yesterday. Andrew Hodgson sent an informative answer, so that's probably it. "Amazon SES rewrites the Message-ID. Yep and for this reason I don't use it. The problem is worse in Mailman3 because it has a much more superior archive display which gets ruined when people reply to messages with different Message-Id headers and the threading can't be observed. I also had to use the anonymous mode with my list as Amazon didn't like me using random addresses in the From: header. I'm still looking for a tolerant mail gateway to use with Mailman." On Thu, May 4, 2023 at 9:18 AM Sam Darwin <samuel.d.darwin(a)gmail.com> wrote: > > Hi, > > We are running mailman2 with postfix and CentOS. For a long time the > mail gateway was mailgun. Recently switched to Amazon SES. > > Now there are complaints that "threading" isn't right. That is, > organizing the results according to topic, and correlating replies > with specific other replies. > > It turns out that "The Amazon Simple Email Service (AWS SES) rewrites > the Message-ID header of outgoing emails." > > This means the References and In-Reply-To headers can't be relied on > anymore also, since they won't always match up. These headers: > > Message-ID: <127401d9389b$e874b7f0$b95e27d0$(a)gmail.com> > References: <126301d93891$58081b80$08185280$(a)gmail.com> > In-Reply-To: <126301d93891$58081b80$08185280$(a)gmail.com> > > might now appear as: > > In-Reply-To: <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000000(a)us-east-2.amazonses.com> > References: <010f0187d80eb0dd-93bebdd9-cabf-4ad6-a7f4-b5515bd22d31-000000(a)us-east-2.amazonses.com> > <010f0187dca41ec8-478dfff5-d27d-4879-ab72-072be2f76176-000000(a)us-east-2.amazonses.com> > > But perhaps a main problem is that for a large outgoing mailing, the > Message-ID might not be consistent when sending to 1000's of > recipients. Maybe not everyone sees the same Message-ID. > > Any thoughts on the topic? > > Has anyone used Amazon SES, and does the "threading" in the archives > line up correctly? > > Thanks, > Sam

1 0