From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (unknown [IPv6:2600:3c03::f03c:91ff:fe50:73f]) by sourceware.org (Postfix) with ESMTPS id D87393877027 for ; Wed, 18 Mar 2020 16:22:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D87393877027 Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jEbT0-0001up-Vy; Wed, 18 Mar 2020 16:22:51 +0000 Received: from fche by elastic.org with local (Exim 4.92.3) (envelope-from ) id 1jEbT0-000ULq-IJ; Wed, 18 Mar 2020 12:22:50 -0400 Date: Wed, 18 Mar 2020 12:22:50 -0400 From: "Frank Ch. Eigler" To: Bernd Schmidt Cc: Overseers mailing list , overseers@gcc.gnu.org, "Frank Ch. Eigler via Gcc" , Alexander Monakov , Segher Boessenkool , "Frank Ch. Eigler" , Florian Weimer Subject: Re: Not usable email content encoding Message-ID: <20200318162250.GG112952@elastic.org> References: <20200317194613.GH22482@gate.crashing.org> <20200317195158.GC112952@elastic.org> <874kumt0bh.fsf@mid.deneb.enyo.de> <20200318110109.GA5496@redhat.com> <20200318142239.GF112952@elastic.org> <3af9771e-e577-f2a1-843e-c2b078bfc4ea@t-online.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3af9771e-e577-f2a1-843e-c2b078bfc4ea@t-online.de> X-Sender-Verification: "" X-Spam-Status: No, score=-96.9 required=5.0 tests=DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_SBL_CSS, SPF_HELO_PASS, SPF_PASS, USER_IN_WHITELIST autolearn=no 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2020 16:22:54 -0000 Hi - > > 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. AIUI, all this effort is driven by wanting to defeat not just spammers but also real security problems like phishing enabled by forgery, including specifically the From: header. - FChE