From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, overseers@sourceware.org
Subject: Re: Broken DMARC workaround for glibc mailing lists
Date: Mon, 08 May 2017 05:34:00 -0000 [thread overview]
Message-ID: <20170508053452.GA7516@ednor.casa.cgf.cx> (raw)
In-Reply-To: <e08f223a-d42f-527f-c652-3777a8aef625@redhat.com>
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.
cgf
next prev parent reply other threads:[~2017-05-08 5:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:29 Florian Weimer
2017-04-30 2:32 ` Christopher Faylor
2017-04-30 15:41 ` Christopher Faylor
[not found] ` <20170430053402.GA6286@ednor.casa.cgf.cx>
2017-05-01 10:18 ` Florian Weimer
2017-05-02 14:07 ` Christopher Faylor
2017-05-05 10:32 ` Florian Weimer
2017-05-08 5:34 ` Christopher Faylor [this message]
2017-05-08 6:15 ` Christopher Faylor
2017-05-08 6:44 ` Florian Weimer via overseers
2017-05-08 14:22 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170508053452.GA7516@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).