Tom, Good point. It has been a LONG time since I wandered into attempting to read email headers. Here is a sample header from the list that recently had the domain related bounce issue Let me know if you see anything that is mis-configured. BTW, the ISP is going to switch to the current Mailman version 3 fairly soon. I don't know if this is going to help the situation or not.
================================================================================================================ Delivered-To: [email protected] Received: by 2002:a54:3e8d:0:0:0:0:0 with SMTP id a13csp437307ecq; Fri, 15 Jan 2021 14:00:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJzGX0l1jB2LKv4yfEwbTh6FFEfBqAZH+gPwf8d70fYYf9yO2CYfAzrNdDHIr9sWEvUGiZ/y X-Received: by 2002:a25:ac5a:: with SMTP id r26mr3257896ybd.336.1610748030970; Fri, 15 Jan 2021 14:00:30 -0800 (PST) Return-Path: <[email protected]> Received: from duke.deltaforce.net (duke.deltaforce.net. [2600:3c02::f03c:91ff:fe71:4634]) by mx.google.com with ESMTP id v201si10664463ybe.88.2021.01.15.14.00.30; Fri, 15 Jan 2021 14:00:30 -0800 (PST) Received-SPF: pass (google.com: domain of [email protected] designates 2600:3c02::f03c:91ff:fe71:4634 as permitted sender) client-ip=2600:3c02::f03c:91ff:fe71:4634; Authentication-Results: mx.google.com; dkim=pass [email protected] header.s=201912 header.b=bz9GJB1w; arc=fail (body hash mismatch); spf=pass (google.com: domain of [email protected] designates 2600:3c02::f03c:91ff:fe71:4634 as permitted sender) smtp.mailfrom= [email protected]; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from= lists.msinglinks.org Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id 1FF7C200C8; Fri, 15 Jan 2021 17:00:01 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1610748001; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=ORdvQKi3OGyn08xnXH+vGvjhYXIfAwAjoa5QXyL8H5s=; b=bz9GJB1wEvlLHiI0bLrum1IHXRIND3T2g4MeZTgJtD3HbXfndhr6twd1MRk+H8hDuP4MPs cq5ACo1Fs/+5DBOcx/3piPI1u+wL+PdpJfoBXpWCzSa+wQ2pyEq5oKvjA6KwBW6y4GHTcP hTWUEwqtx3QKwMQZVOQImagCizVcT2c= X-Original-To: [email protected] Delivered-To: [email protected] Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by duke.deltaforce.net (Postfix) with ESMTP id F123B2008B for <[email protected]>; Fri, 15 Jan 2021 16:59:58 -0500 (EST) Received: by mail-ed1-x536.google.com with SMTP id r5so11141282eda.12 for < [email protected]>; Fri, 15 Jan 2021 13:59:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=hUMg9j8t3zLn90bOZgjF1+yZ+P6ZmnsiCMjsoVW4BLY=; b=I/y7UITY1M2yop5zIvY8DgSvwCsQZSmYxAfbV41YGfHBG/e5ijjlCaofgOXFmahlaa RxFPJMFFbi/pmtuZwToxAF9cWwjH7kfxcslMHs6mh1meopCvnVXh+xHPFjl96aow1vo7 BludusxmM3RndqSVTImePOWzHTv22UIQ/Y9clTULaF3pWbxJfSJ4spBXfheZtcBrLItD 1nGqVJIZ21EJgt1CmDVal4tdzoOcXHijZFDBtbebIuG034OyXILCRf+Bla73sIHMRynx 3vXnC72hWl6fXGYtOZE43xhN9eOF/tYA2yUrxCTwt/7juJDVNCnIZRsGODFrZU8sc8iF UxVA== X-Gm-Message-State: AOAM533p+34DdDQ6FEq8DYXx1JUTJiL+/BYroqOgWaXkrl1pPbZxOlmz QYPsE0T0jTzEjzw0rXizMEb7Xw2FaAnyH+xubWVWsMzms6c= X-Received: by 2002:a05:6402:ca2:: with SMTP id cn2mr11237658edb.137.1610747997902; Fri, 15 Jan 2021 13:59:57 -0800 (PST) MIME-Version: 1.0 Date: Fri, 15 Jan 2021 16:59:47 -0500 Message-ID: <CAKPKP=dXW6XJ3_Nu2= [email protected]> To: MSing Links Ride List <[email protected]> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= msinglinks.org; s=201912; t=1610747999; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=hUMg9j8t3zLn90bOZgjF1+yZ+P6ZmnsiCMjsoVW4BLY=; b=eYUz7XqRPBl8imwhZzXmE0nj37PkcVPwt+owOmeHUg3Dd1RWvqwt5L9h9UcR6P7JxQHiiM MXXN8mKzEUaWob3KuLs0yTqiFQqyzjyjs1Pihs49LyZhANm9C2Hm1zzJgEsbzYEhb3rqvS cGemsva5TWzBYkVQeUipYXhTBdvPlGI= ARC-Seal: i=1; s=201912; d=msinglinks.org; t=1610747999; a=rsa-sha256; cv=none; b=tU04RuUB4ViYt0S6yasddLeRwK6dUJZSo9mN1e5CLnVqxGJC+Qnm+xXTB3Irkhn+ijqcKr lPg3zHE+gwT9vO4OOiosJtKiWUgG9fQwQBvdblZa8GqSFldtA2xtqliqdcCp0IMAIAwHQQ utsAYGMN7fjAtoNxvN0sSHxeTKGA93A= ARC-Authentication-Results: i=1; duke.deltaforce.net; dkim=pass header.d= gmail.com header.s=20161025 header.b=hRBk2AdT; spf=pass (duke.deltaforce.net: domain of [email protected] designates 2a00:1450:4864:20::536 as permitted sender) [email protected] X-Spam-Status: No, score=-1.40 X-Content-Filtered-By: Mailman/MimeDel 2.1.34 Subject: [MSing_Links-Ride] test X-BeenThere: [email protected] X-Mailman-Version: 2.1.34 Precedence: list List-Id: MSing Links Ride Announce / Chat List < msing-ride.lists.msinglinks.org> List-Unsubscribe: <https://lists.msinglinks.org/mailman/options/msing-ride>, <mailto:[email protected]?subject=unsubscribe> List-Archive: <https://lists.msinglinks.org/mailman/private/msing-ride/> List-Post: <mailto:[email protected]> List-Help: <mailto:[email protected]?subject=help> List-Subscribe: <https://lists.msinglinks.org/mailman/listinfo/msing-ride>, <mailto:[email protected]?subject=subscribe> From: Donald Belk via MSing-ride <[email protected]> Reply-To: Donald Belk <[email protected]> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: [email protected] Sender: MSing-ride <[email protected]> ============================================================================================================= On Sun, Jan 31, 2021 at 12:46 PM Thomas Coradeschi via Mailman-Users < [email protected]> wrote: > > > On 30 Jan 2021, at 5:22 PM, steve lund <[email protected]> wrote: > > > > Mark, > > > > On Fri, Jan 29, 2021 at 10:36 AM Mark Sapiro <[email protected]> wrote: > > > >> On 1/29/21 5:38 AM, steve lund wrote: > >>> > >>> ...And everyone else who replied, yes, this does indeed look like a > DMARC > >>> issue. I looked at the help pages and it looks like some things can be > >>> changed but from what I gather any changes would likely affect > >>> functionality for the users. > >>> > >>> I am a member of a different list that munged the FROM header to the > list > >>> address with the down side that ALL replies had to go back through the > >> list > >>> even if it was specific to one individual. Not a great experience just > to > >>> pick up a few members who had AOL email domains. > >> > >> > >> Is this a Mailman list? Both Mailman 2.1 and Mailman 3 take pains to > >> create Munged From messages which exhibit the same behavior for 'reply' > >> and 'reply-all' as non-munged messages. Here's what we say: > >> > > > > I don't know if it was a Mailman list or not. This was 2-3 years ago. I > > looked at a current list message and there is no indication of the list > > sender. Is there any way that I can send a query to get this information? > > Look at the message headers - if it’s a mailman list, you should find > > X-Mailman-Version: xx.yy.zz > > > — > Tom Coradeschi > [email protected] > > ------------------------------------------------------ > Mailman-Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/mailman-users.python.org/ > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > https://www.mail-archive.com/[email protected]/ > https://mail.python.org/archives/list/[email protected]/ > ------------------------------------------------------ Mailman-Users mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/[email protected]/ https://mail.python.org/archives/list/[email protected]/
