From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <matz@suse.de>
Received: from mx2.suse.de (mx2.suse.de [195.135.220.15])
 by sourceware.org (Postfix) with ESMTPS id 743D0385DC1A
 for <overseers@sourceware.org>; Tue,  7 Apr 2020 15:56:13 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 743D0385DC1A
X-Virus-Scanned: by amavisd-new at test-mx.suse.de
Received: from relay2.suse.de (unknown [195.135.220.254])
 by mx2.suse.de (Postfix) with ESMTP id 6FA23AB89;
 Tue,  7 Apr 2020 15:56:11 +0000 (UTC)
Date: Tue, 7 Apr 2020 15:56:09 +0000 (UTC)
From: Michael Matz <matz@suse.de>
To: "Frank Ch. Eigler" <fche@elastic.org>
cc: Jonathan Wakely <jwakely.gcc@gmail.com>, 
 "Maciej W. Rozycki" <macro@wdc.com>, overseers@gcc.gnu.org, 
 "Frank Ch. Eigler via Gcc" <gcc@gcc.gnu.org>, 
 Overseers mailing list <overseers@sourceware.org>, 
 Segher Boessenkool <segher@kernel.crashing.org>, 
 Alexander Monakov <amonakov@ispras.ru>, 
 "Frank Ch. Eigler" <fche@redhat.com>, Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Not usable email content encoding
In-Reply-To: <20200407152204.GD323051@elastic.org>
Message-ID: <alpine.LSU.2.21.2004071553350.29756@wotan.suse.de>
References: <20200318110109.GA5496@redhat.com>
 <alpine.LSU.2.21.2003181415360.30534@wotan.suse.de>
 <20200318142239.GF112952@elastic.org>
 <3af9771e-e577-f2a1-843e-c2b078bfc4ea@t-online.de>
 <20200318162250.GG112952@elastic.org>
 <alpine.LFD.2.21.2004062133190.461@redsun52.ssa.fujisawa.hgst.com>
 <20200406210946.GY323051@elastic.org>
 <alpine.LFD.2.21.2004062244470.461@redsun52.ssa.fujisawa.hgst.com>
 <CAH6eHdTqJEM90d9+nNWrAa_zZrQQha79oMbnbVsRt_2Zd90PdA@mail.gmail.com>
 <alpine.LSU.2.21.2004071512010.29756@wotan.suse.de>
 <20200407152204.GD323051@elastic.org>
User-Agent: Alpine 2.21 (LSU 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Spam-Status: No, score=-12.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: overseers@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Overseers mailing list <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2020 15:56:14 -0000

Hello,

On Tue, 7 Apr 2020, Frank Ch. Eigler wrote:

> > I find that unconvincing, because even googlegroup email lists don't 
> > mangle From: from sender domains that are now mangled by sourceware.org 
> > :-/
> 
> It turns out receiving mail FROM google-groups mail is itself
> sometimes at risk because it fails to do this From: mangling, and its
> ARC/DKIM re-signature of mail requires even more software to process
> and bless.  (Its current behaviour on some groups-gmail lists I'm on
> are DMARC non-compliant.)

In a way that's amusing and just reinforces my p.o.v. that DMARC is 
bollocks.

> > Can we please switch it off?  It's not like we really had a problem
> > before the switch to mailman.
> 
> We have offered some first-hand evidence that there were problems,
> just they were worked on by people in the background.

Okay, now the question is, are those problems offsetting the current 
problems?  IMHO they don't, but of course I'm heavily biased, not having 
had those old problems  :)


Ciao,
Michael.