Mailman-Users February 2021

mailman-users@python.org

30 participants
26 discussions

by nikos

Hello list. I'm receiving a lot of fake Subscription Requests and spend time to discard them. 1. how can I "lock" lists not to receive requests except administrator's mass subscription? 2. how can I mass discard those request from console? Thank you in advance, Nikos.

1 month, 3 weeks

Mailing List Bounce Issues

by steve lund

Hello, I am the mailing list administrator for a charity cycling team. The list currently has about 150 members. The list and our website is hosted by a local ISP who is running Mailman 2.1.34. We seem to be having all too frequent occurrences of multiple bounces that seem to be related only to the domain of the address recipient. Previously we have had issues with AOL.com and Mindspring.com email domains. The main result of these are disabled subscriptions due to excessive bounces. The latest in this continuing saga occurred on Monday morning when I received notification that 12! list members with Yahoo.com email domain addresses had been unsubscribed from the list! I am assuming that this is the sum total of ALL yahoo addresses in our list. The interesting thing about this occurrence other than losing the name associated with the email address (since the members were unsubscribed not just disabled) is that I NEVER received ANY bounce notifications other than the unsubscribe notification. I find this quite odd and unsettling considering that the list shows that it IS configured to send earlier bounce notifications and I have received them in the past... just not leading up to this latest incident. The typical error message is: jonxx_dajxxn(a)yahoo.com <jones_dajuan(a)yahoo.com> has been removed from MSing-ride. (disabled address) So I guess that my question is whether or not these types of problems are now endemic to all email lists or if....Our ISP is technically "challenged" and 1. Doesn't know how to properly configure Mailman to send out the requested notifications. 2. Continues to get blacklisted for sending SPAM even though they don't. Thanks for any insight. Steve

4 months, 3 weeks

Does mailman work well for large lists?

by David.barden＠mail.com

Good day, Looking for a solution to have about 50-200 lists for subscribers. Any good examples of mailman being used for 50+ lists you can share for me to see? Trying to see the feasibility of implementing a solution in next 90 days. Would like to see a working one, where a user would go to a site, and pick a list to subscribe. Is mailman easy to setup and maintain? Windows or Linux server recommended? Thank you. David.

4 months, 4 weeks

Weird no-posting no-moderation queue bouncing of posts

by Thomas Gramstad

I have a strange, occasionally occurring phenomenon on one of my mailing lists (in Mailman 2.29) which I don't understand: 1. A subscribed address to the list tries to post a message to the list. 2. The attempted posting does not go through to the list, nor does it go to the moderation queue. Instead, I the list admin receives a message via the bounces-address with a copy of the attempted posting. 3. The bounce message looks like/similar to the bounce message that is generated when a bounce happens at one single individual subscriber's e-mail address. But in that case the list archive as well as other subscribers (including me) will get a copy of the posting. And that is not the case here. No copy to me, nothing in the archive. So the only trace I can see of the posting is the weird bounce message containing a copy of the posting. Why doesn't the attempted posting go to the moderator queue, if there is something about the subscriber or the message that prevents it from being distributed? (The list in question is unmoderated for subscribers.) Below is a copy of one of the strange bounce postings. Thomas Gramstad thomas(a)gramstad.no ----

4 months, 4 weeks

API/App based access to Mailman/Archives

by Steven Clift

Is it technically possible to interact via an API from a simple mobile app with different Mailman servers? My thought is something simple that could in theory be expanded into an app that interfaces with your groups and public groups on Mailman, BuddyPress, Discourse and other open source hosted online groups. You'd paste in the URLs of your online groups/list sites in some way. Like the olden days of news groups and the experience of an RSS reader, you could quickly scan the number of new posts over X time or since you last opened the app and then dip into the groups of interest and if you can authenticate yourself, post on lists/groups where you are a member. Thoughts? I am evaluating whether in the age of Facebook Groups, NextDoor, and mobile apps if an open source/non-commercial path to viable online neighborhood groups with mass participation is possible. We have a bunch of online groups to move from GroupServer for E-Democracy.org. Thanks, Steven Clift P.S. I see that this is out there for Discourse: https://play.google.com/store/apps/details?id=com.discourse

5 months

Re: Daily "pending moderator requests" despite empty moderation queue

by JACKSON＠encompasserve.org

On Thu, 18 Feb 2021 09:28:46 +0100, Johannes Rohr <jorohr(a)gmail.com> wrote: > Dear all, > > for some lists, the listowners in the last few days keep getting "pending > moderator requests" emails every day, even though there are no pending > requests. > > What mechanism generates these requests and how can I get rid of those > redundant mails? (short of migrating to mailman 3 which I plan on doing) > > Cheers, thanks a lot in advance, > > Johannes Hi Johannes, this may not be your problem, but I had a similar one: https://mail.python.org/archives/list/mailman-users@python.org/message/JC7A… In case that wraps badly for you: https://mail.python.org/archives/list/mailman-users@python.org and search "SOLVED" and sort by latest first. It will be on top. The version of Mailman it refers-to is shown in the subject line. Kind regards

5 months, 1 week

Daily "pending moderator requests" despite empty moderation queue

by Johannes Rohr

Dear all, for some lists, the listowners in the last few days keep getting "pending moderator requests" emails every day, even though there are no pending requests. What mechanism generates these requests and how can I get rid of those redundant mails? (short of migrating to mailman 3 which I plan on doing) Cheers, thanks a lot in advance, Johannes

5 months, 1 week

Examples of custom themes for HyperKitty?

by Steven Clift

Hey all, I am looking for examples where folks have further adapted their HyperKitty archives to engage users looking for more of a social network/blog like experience. Suggestions? I am looking for examples that essentially feature the original post in full and then present expandable replies below like comments. Thanks, Steve

5 months, 1 week

Add "sender's name/email" to BODY of mail as header?

by Mal

I want all mails sent to the list to come from the list's email address... But, in this case, if the user forgets to sign their name at the bottom of their mail body, effectively the mail to the list is anonymous...! Is there a way to add the user name (or email address) to the top of each mail so that the mails have the name of the sender, while the mail itself comes from the list address? I have looked high and low for an answer, but noone seems to have the solution. Thank you! Mal

5 months, 1 week

Subject field not included in wrapper of DMARC emails

by Sam Kuper

Dear Mailman folk, I am subscribed to an OpenWRT mailing list, which (according to the X-Mailman-Verson header in emails I receive from the list) uses Mailman 2.1.29. Most of the mail on that list comes through just fine. DMARC email comes through with the Subject: field blank, though. Is that expected? https://wiki.list.org/DEV/DMARC does not appear to mention the Subject: header being left out of the wrapper, when Mailman wraps a message to satisfy DMARC. This means that in my MUA, those messages are displayed without a Subject. An example of an affected email is shown below, including the full headers. Is there a Mailman 2 setting that I could recommend to the OpenWRT list managers, that would make Mailman copy the Subject: header from the original message to the wrapper, so that my MUA would show the subject as intended by the sender? Thank you in advance for your help, Sam ----- Forwarded message from "Etan Kissling (IC) via openwrt-devel" ----- Return-Path: <openwrt-devel-bounces+sampablokuper=posteo.net(a)lists.openwrt.org> Delivered-To: unknown Received: from posteo.de (185.67.36.145:993) by zian2 with IMAP4-SSL; 08 Feb 2021 21:32:21 -0000 Delivered-To: sampablokuper(a)posteo.net Received: from proxy02.posteo.name ([127.0.0.1]) by dovecot12 (Dovecot) with LMTP id 5oSRHYDhIGBLfgAAJesNpQ for <sampablokuper(a)posteo.net>; Mon, 08 Feb 2021 10:02:45 +0100 Received: from proxy02.posteo.de ([127.0.0.1]) by proxy02.posteo.name (Dovecot) with LMTP id GTflGLf5IGDQWQEAGFAyLg ; Mon, 08 Feb 2021 10:02:45 +0100 Received: from mailin04.posteo.de (unknown [10.0.0.64]) by proxy02.posteo.de (Postfix) with ESMTPS id 4DZ0Qq63k7z12Ck for <sampablokuper(a)posteo.net>; Mon, 8 Feb 2021 10:02:27 +0100 (CET) Received: from mx04.posteo.de (mailin04.posteo.de [127.0.0.1]) by mailin04.posteo.de (Postfix) with ESMTPS id 9627620F6B for <sampablokuper(a)posteo.net>; Mon, 8 Feb 2021 10:02:27 +0100 (CET) X-Virus-Scanned: amavisd-new at posteo.de X-Spam-Flag: NO X-Spam-Score: -1.533 X-Spam-Level: X-Spam-Status: No, score=-1.533 tagged_above=-1000 required=7 tests=[MAILING_LIST_MULTI=-1, MISSING_SUBJECT=1.767, POSTEO_BTC_B=0.01, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RCVD_IN_ABUSIX_WHITE=0.01] autolearn=disabled Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) by mx04.posteo.de (Postfix) with ESMTPS id 4DZ0Qk1lB3z10Zm for <sampablokuper(a)posteo.net>; Mon, 8 Feb 2021 10:02:21 +0100 (CET) Authentication-Results: posteo.de; dmarc=none (p=none dis=none) header.from=lists.openwrt.org Authentication-Results: posteo.de; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=(a)lists.infradead.org header.b=xkN+h566; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Type:List-Help: Reply-To:List-Archive:List-Unsubscribe:List-Subscribe:Cc:From:List-Post: List-Id:Message-ID:MIME-Version:To:References:Date:In-reply-to:Subject: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=BodNZRxYJ/ulISXrw/8ihEr0xuP4150RxcU4mqQbzK4=; b=xkN+h566WmBldbwfdHkBfI157 PDL/CI0WdfrRg5YTGiuFXnzvBoBLF5IU/Bhnrmhetwjs9z85NME1nKUXF49jqPTUc3D2/zqtd5vMk eVXY3/uAHIzbMWZL/bQQkRCADY44YEKBGflD0HlIttHy9gtqaZLBalRL435qoqxfhab8GntX0GiVO GSBqAmBp5VObGm+1oj//HwddZz4QuFWyEObG4MPsqtw7MFGK8FVw1Dumq36cUxICpD7teIcUhDP1y jLQ5xuMsSXJfeGL+NPp4Ki5pWywa/L4W9GAlOijWiFXVtk++j66AoyHHsjDwYyklgieQzOW/37ha/ G0ztzuEKw==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1l92Nh-0000HM-50; Mon, 08 Feb 2021 08:58:53 +0000 In-reply-to: <YBz6Pjl2SFe6Ky0L@thunderclap> Date: Mon, 08 Feb 2021 09:58:38 +0100 References: <YBz6Pjl2SFe6Ky0L@thunderclap> To: Baptiste Jonglez <baptiste(a)bitsofnetworks.org> MIME-Version: 1.0 Message-ID: <mailman.1473.1612774732.941.openwrt-devel(a)lists.openwrt.org> List-Id: OpenWrt Development List <openwrt-devel.lists.openwrt.org> List-Post: <mailto:openwrt-devel@lists.openwrt.org> From: "Etan Kissling (IC) via openwrt-devel" <openwrt-devel(a)lists.openwrt.org> Precedence: list Cc: openwrt-devel(a)lists.openwrt.org X-Mailman-Version: 2.1.29 X-BeenThere: openwrt-devel(a)lists.openwrt.org List-Subscribe: <https://lists.openwrt.org/mailman/listinfo/openwrt-devel>, <mailto:openwrt-devel-request@lists.openwrt.org?subject=subscribe> List-Unsubscribe: <https://lists.openwrt.org/mailman/options/openwrt-devel>, <mailto:openwrt-devel-request@lists.openwrt.org?subject=unsubscribe> List-Archive: <http://lists.openwrt.org/pipermail/openwrt-devel/> Reply-To: "Etan Kissling (IC)" <etan_kissling(a)apple.com> List-Help: <mailto:openwrt-devel-request@lists.openwrt.org?subject=help> Content-Type: multipart/mixed; boundary="===============4994977490922860622==" Sender: openwrt-devel <openwrt-devel-bounces(a)lists.openwrt.org> Errors-To: openwrt-devel-bounces+sampablokuper=posteo.net(a)lists.openwrt.org X-getmail-retrieved-from-mailbox: INBOX Content-Length: 7001 The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. Received: from ma1-aaemail-dr-lapp02.apple.com ([17.171.2.68]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1l92Nd-0000EE-Uz for openwrt-devel(a)lists.openwrt.org; Mon, 08 Feb 2021 08:58:51 +0000 Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.42/8.16.0.42) with SMTP id 1188r62T023472; Mon, 8 Feb 2021 00:58:42 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=+2HgbfEc8d2AnW/LqWiaafnkQdP0EWNyIoczFiPBM/Q=; b=i8Hp/kqjR8nz8o0yxx5I898YX8rveNwKUkxOQoINhu4EFpDNIpuiNp31MRQ2U/8UnP5N PvyWiHBqu3F8ccfF/gWXFT2SxV5hiucAXwfYxMDJqehDFXA0mFmu7JCjeA5QtGKH485K KiTzkGqyTQ2oGBg7YJAkH3Em6d80BdwSJIY6kJtmrlBmau+2C7tRiPDJVTI522TzblY2 KLcSq+AVpYhnoM2m2fIYzQZYT8pXAz9h7Y8P8OpsO/xlpr0Rt3gmfoIXLbkLOXVgZKXo TEyQj5ElOrieQUanyx0B3g9EpiuS6R7uUsABjyz+9GeSY41T7GwnXOlMKoma0n3FwqHS nQ== Received: from crk-mailsvcp-mta-lapp02.euro.apple.com (crk-mailsvcp-mta-lapp02.euro.apple.com [17.66.55.14]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 36hrnvuw60-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 08 Feb 2021 00:58:42 -0800 Received: from crk-mailsvcp-mmp-lapp02.euro.apple.com (crk-mailsvcp-mmp-lapp02.euro.apple.com [17.72.136.16]) by crk-mailsvcp-mta-lapp02.euro.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPS id <0QO700RCRCXS0B00(a)crk-mailsvcp-mta-lapp02.euro.apple.com>; Mon, 08 Feb 2021 08:58:40 +0000 (GMT) Received: from process_milters-daemon.crk-mailsvcp-mmp-lapp02.euro.apple.com by crk-mailsvcp-mmp-lapp02.euro.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) id <0QO700K00CFZA900(a)crk-mailsvcp-mmp-lapp02.euro.apple.com>; Mon, 08 Feb 2021 08:58:40 +0000 (GMT) X-Va-A: X-Va-T-CD: 9afdb31050d7d5317f70deb897281ad1 X-Va-E-CD: 67e6792f740908ddf1e16c3353593782 X-Va-R-CD: b67e6762d78a271b674cde5fdf0795bd X-Va-CD: 0 X-Va-ID: 3c6f3588-7a2f-4a6c-b999-58547bff9a59 X-V-A: X-V-T-CD: 9afdb31050d7d5317f70deb897281ad1 X-V-E-CD: 67e6792f740908ddf1e16c3353593782 X-V-R-CD: b67e6762d78a271b674cde5fdf0795bd X-V-CD: 0 X-V-ID: a85131a9-49e2-48c0-b1b4-e57b988944b5 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.737 definitions=2021-02-08_02:2021-02-08,2021-02-08 signatures=0 Received: from [17.235.216.39] by crk-mailsvcp-mmp-lapp02.euro.apple.com (Oracle Communications Messaging Server 8.1.0.7.20201203 64bit (built Dec 3 2020)) with ESMTPSA id <0QO700FJLCXQ2B00(a)crk-mailsvcp-mmp-lapp02.euro.apple.com>; Mon, 08 Feb 2021 08:58:40 +0000 (GMT) Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Subject: Re: Upcoming 19.07.7 release From: "Etan Kissling (IC)" <etan_kissling(a)apple.com> In-reply-to: <YBz6Pjl2SFe6Ky0L@thunderclap> Date: Mon, 08 Feb 2021 09:58:38 +0100 Cc: openwrt-devel(a)lists.openwrt.org Content-transfer-encoding: quoted-printable Message-id: <1C978121-80FE-4E89-B587-60893371EF8A(a)apple.com> References: <YBz6Pjl2SFe6Ky0L@thunderclap> To: Baptiste Jonglez <baptiste(a)bitsofnetworks.org> X-Mailer: Apple Mail (2.3654.60.0.2.21) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369,18.0.737 definitions=2021-02-08_02:2021-02-08,2021-02-08 signatures=0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210208_035850_214778_58700E6F X-CRM114-Status: GOOD ( 16.59 ) X-Spam-Score: -5.8 (-----) X-Spam-Report: SpamAssassin version 3.4.4 on merlin.infradead.org summary: Content analysis details: (-5.8 points) pts rule name description ---- ---------------------- -------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at https://www.dnswl.org/, high trust [17.171.2.68 listed in list.dnswl.org] -0.0 RCVD_IN_MSPIKE_H2 RBL: Average reputation (+2) [17.171.2.68 listed in wl.mailspike.net] -0.0 SPF_PASS SPF: sender matches SPF record -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.6 DKIMWL_WL_HIGH DKIMwl.org - High trust sender I have posted a few backports to 19.07 from master a few weeks back, with these subjects: 1. [PATCH 19.07] mbedtls: add config option to compile with hkdf 2. [PATCH 19.07] hostapd: add multicast_to_unicast and per_sta_vif 3. [PATCH 19.07] hostapd: enable CTRL_IFACE_MIB for hostapd-full 4. [PATCH 19.07] nf-conntrack: allow querying conntrack info in nfqueue 5. [PATCH 19.07] libnetfilter-queue: update to 1.0.5 My patches don't end up in Patchwork for some reason. If those are acceptable, be sure to take the latest submission for the patches that were submitted multiple times. Thanks Etan > On 5 Feb 2021, at 08:56, Baptiste Jonglez <baptiste(a)bitsofnetworks.org> wrote: > > Hi, > > We are planning a new 19.07 release in about a week (probably next week-end). > > If you are aware of changes that need to be integrated, now is the time to > do it or mention it here! > > I plan to test & integrate a workaround for this ramips stability issue: > https://bugs.openwrt.org/index.php?do=details&task_id=2628 > > Baptiste > > PS: please don't ask about 21.XX > _______________________________________________ > openwrt-devel mailing list > openwrt-devel(a)lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel(a)lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ----- End forwarded message -----

5 months, 1 week