From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15815 invoked by alias); 9 Oct 2014 05:26:28 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 15767 invoked by uid 89); 9 Oct 2014 05:26:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail-vc0-f174.google.com Received: from mail-vc0-f174.google.com (HELO mail-vc0-f174.google.com) (209.85.220.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 09 Oct 2014 05:26:26 +0000 Received: by mail-vc0-f174.google.com with SMTP id hq12so401619vcb.5 for ; Wed, 08 Oct 2014 22:26:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fsf3LBaCnNMdJ0T/oauHR9nLqsKbJj3oyw4262m8Quk=; b=JDhxu3pLgv2UQUYwgGGQlDZA42c4C8N1yPyLzDNFECfc6tOZOrO1a3GeX1pVAVmjjD JanJ67DQhBb76Zu0qi8dKcr+zqJ+88mmnPAX+zXpYyTlASLXL+2qfgwlbFLj3mVd9weG ITG5aHcRwqF5mfLkVceb1tWw3gBovwUAjcx7cfVGy0V1JAj2ZLJDD65W3dw0yvwFWOjP YhAcYq6c1zTWsv98cTIFQTAyDHfc+44BqEeZ1RrF3N2fb/d1BnmoOmJNxvBP6XTFi4Ks 3kiBi7sd2qRantzScxewM98iZP+HkuE8gSz9CqiJ7gg/wyp1gTvlPt5ZJM/VrCl94McR BhFQ== X-Gm-Message-State: ALoCoQm1Bf/QIUQ9SfeaDILVlI58e5EKLwiSky03ZGwI1o2hl/79yz65M+6YW8NFcKmxdiwjslfU MIME-Version: 1.0 X-Received: by 10.220.17.145 with SMTP id s17mr9303886vca.77.1412832383556; Wed, 08 Oct 2014 22:26:23 -0700 (PDT) Received: by 10.52.96.229 with HTTP; Wed, 8 Oct 2014 22:26:23 -0700 (PDT) In-Reply-To: <3C873376-21FF-4176-8101-C1FE137DCACF@gmail.com> References: <1412716173.8985.ezmlm-warn@gcc.gnu.org> <3C873376-21FF-4176-8101-C1FE137DCACF@gmail.com> Date: Thu, 09 Oct 2014 05:26:00 -0000 Message-ID: Subject: Re: ezmlm warning From: Chandler Carruth To: Rafael Avila de Espindola Cc: Ian Lance Taylor , "overseers@gcc.gnu.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-SW-Source: 2014-q4/txt/msg00012.txt.bz2 On Wed, Oct 8, 2014 at 10:18 PM, Rafael Avila de Espindola wrote: > > Sent from my iPhone > > > On Oct 8, 2014, at 20:51, Ian Lance Taylor wrote: > > > > Rafael Esp=C3=ADndola writes: > > > >> This looks like the same issues we had some time ago in the LLVM lists: > >> > >> http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-May/072967.html > > > > There are no reasonable actions that we can take. Yahoo! has chosen to > > break mailing lists. > > > > Perhaps we should simply ban @yahoo.com addresses. This won't help. It isn't just Yahoo. Dropbox and others are equally impacted. DMARC is here to stay, and mailing lists will have to adapt I'm afraid. Even Google will change its policies here eventually. > Chandler mentioned something about a way to manage the headers in a mail= ing list that would avoid the problem. Yes, there is a reasonable path forward for mailing lists: http://wiki.list.org/display/DEV/DMARC The far and away best approach is under the section "Munge the From: header". By re-writing the email to indicate it is indeed from the list server, DMARC issues are essentially completely resolved.