From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37361 invoked by alias); 8 May 2017 14:22:47 -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 37273 invoked by uid 89); 8 May 2017 14:22:47 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_00,HK_OBFDOM,SPF_HELO_PASS,SPF_NEUTRAL autolearn=no version=3.3.2 spammy=txt, TXT, tomorrow, night X-HELO: cgf.cx Received: from external.cgf.cx (HELO cgf.cx) (107.170.62.102) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 08 May 2017 14:22:45 +0000 Received: by cgf.cx (sSMTP sendmail emulation); Mon, 08 May 2017 10:22:45 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx AD99E40564 Date: Mon, 08 May 2017 14:22:00 -0000 From: Christopher Faylor To: overseers@sourceware.org Subject: Re: Broken DMARC workaround for glibc mailing lists Message-ID: <20170508142245.GA5854@ednor.casa.cgf.cx> Mail-Followup-To: overseers@sourceware.org References: <3c0d0086-7cae-87df-1208-121656b890e3@redhat.com> <20170430023242.GA869@ednor.casa.cgf.cx> <20170430053402.GA6286@ednor.casa.cgf.cx> <90c4c146-d703-c481-7065-839856769093@redhat.com> <20170502140737.GA3801@ednor.casa.cgf.cx> <20170508053452.GA7516@ednor.casa.cgf.cx> <545e933c-8019-9a72-b9e9-f4b6171add5f@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <545e933c-8019-9a72-b9e9-f4b6171add5f@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2017-q2/txt/msg00057.txt.bz2 On Mon, May 08, 2017 at 08:44:34AM +0200, Florian Weimer via overseers wrote: >On 05/08/2017 07:34 AM, Christopher Faylor wrote: >> On Fri, May 05, 2017 at 12:32:38PM +0200, Florian Weimer wrote: >>> The most recent message didn't have rewriting applied. I assume that >>> gmail.com has strict DMARC policies and would ordinarily trigger >>> rewriting. However, I don't see this happening on other sourceware.org >>> lists, either. Maybe we'd need a test posting from google.com. >> >> I think this may be a bug in the patched ezmlm that we're using. It >> may be looking at "gmail.com": >> >> _dmarc.gmail.com. 300 IN TXT "v=DMARC1; p=none; rua=mailto:mailauth-reports@google.com" >> >> rather than google.com (which handles gmail's mx): >> >> _dmarc.google.com. 183 IN TXT "v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com" >> >> It should be easy to fix. I'll look at it tomorrow. > >Huh. This is not what I expected. I think this means that gmail.com >does not have a strict DMARC policy after all. So I was wrong to expect >rewriting for it. > >(Just to be clear: it would be wrong to apply the google.com DMARC >policy to gmail.com because the MX host location does not matter for >this policy.) Yeah, I realized that as I was drifting off to sleep last night. Email I sent to test-list from gmail to gmail worked so I should have realized that meant that gmail didn't enforce and that this wassn't an issue.