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 5993A394443B
 for <overseers@sourceware.org>; Wed, 18 Mar 2020 16:42:15 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5993A394443B
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 09657AD4F;
 Wed, 18 Mar 2020 16:42:14 +0000 (UTC)
Date: Wed, 18 Mar 2020 16:42:13 +0000 (UTC)
From: Michael Matz <matz@suse.de>
To: "Frank Ch. Eigler" <fche@elastic.org>
cc: Bernd Schmidt <bernds_cb1@t-online.de>, 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: <20200318162250.GG112952@elastic.org>
Message-ID: <alpine.LSU.2.21.2003181638490.30534@wotan.suse.de>
References: <caf17b7a-e198-8885-d306-ab8285d02d72@suse.cz>
 <alpine.LNX.2.20.13.2003161650490.15005@monopod.intra.ispras.ru>
 <20200317194613.GH22482@gate.crashing.org>
 <20200317195158.GC112952@elastic.org> <874kumt0bh.fsf@mid.deneb.enyo.de>
 <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>
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=0.0 required=5.0 tests=KAM_DMARC_STATUS,
 RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE,
 SPF_PASS 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: <http://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: Wed, 18 Mar 2020 16:42:16 -0000

Hello,

On Wed, 18 Mar 2020, Frank Ch. Eigler via Gcc wrote:

> > > The From: header rewriting for DMARC participants is something sourceware
> > > is doing now.
> > 
> > Out of curiousity, is this rewriting you are talking about the cause for a
> > lot of mails showing up as "From: GCC List" rather than their real senders?
> > This has become very annoying recently.
> 
> Yes, for emails from domains with declared interest in email
> cleanliness, via DMARC records in DNS.  We have observed mail
> -blocked- at third parties, even just days ago, when we failed to
> sufficiently authenticate outgoing reflected emails.

Was this blocking also a problem before mailman (i.e. two weeks ago)?  
Why did nobody scream for not having received mail?  Or why is it blocked 
now, but wasn't before?  Can it be made so again, like it was with ezmlm?

(And DMARCs requirement of having to rewrite From: headers should make it 
clear to everyone that it's stupid).


Ciao,
Michael.