From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <overseers-return-12697-listarch-overseers=sources.redhat.com@sourceware.org>
Received: (qmail 26189 invoked by alias); 12 May 2014 16:33:45 -0000
Mailing-List: contact overseers-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <overseers.sourceware.org>
List-Archive: <http://sourceware.org/ml/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-help@sourceware.org>,
	<http://sourceware.org/ml/#faqs>
Sender: overseers-owner@sourceware.org
Received: (qmail 26180 invoked by uid 89); 12 May 2014 16:33:44 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: yosemite.airs.com
Received: from yosemite.airs.com (HELO yosemite.airs.com) (64.13.131.148)
 by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with SMTP; Mon, 12 May 2014 16:33:43 +0000
Received: (qmail 2808 invoked by uid 10); 12 May 2014 16:33:42 -0000
Received: (qmail 23414 invoked by uid 500); 12 May 2014 16:33:25 -0000
From: Ian Lance Taylor <ian@airs.com>
To: Mike Stump <mikestump@comcast.net>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>,
  dw <limegreensocks@yahoo.com>
Subject: Re: yahoo.com address on gcc-patches
References: <8DDA6547-14A9-49C9-9547-D5C84945742C@comcast.net>
	<m37g5uv3sd.fsf@pepe.airs.com>
	<B0650D05-BE12-4266-BB91-5AF3C7369301@comcast.net>
Date: Mon, 12 May 2014 16:33:00 -0000
In-Reply-To: <B0650D05-BE12-4266-BB91-5AF3C7369301@comcast.net> (Mike Stump's
	message of "Fri, 9 May 2014 19:06:08 -0700")
Message-ID: <m3ha4v554a.fsf@pepe.airs.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2014-q2/txt/msg00042.txt.bz2

Mike Stump <mikestump@comcast.net> writes:

> In time, new mailing list software will have to do something sensible,
> hopefully that will take less than 3 years=E2=80=A6 The biggest problem is
> that no one has designed and documented the solution in an rfc and
> implemented it yet.

I don't actually see what mailing list software can do.

With the current state of affairs, the only approach I can see is for
the mailing list software to rewrite the From address to a local
address, and implement forwarding, so that replies will continue to
work.  But that is obviously problematic in various ways.

So I think the only possible end result of this will be that people will
stop honoring dmarc settings, just as people have stopped honoring SPF
settings.

Ian