From: Chandler Carruth <chandlerc@google.com>
To: Rafael Avila de Espindola <rafael.espindola@gmail.com>
Cc: Ian Lance Taylor <ian@airs.com>,
"overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: ezmlm warning
Date: Thu, 09 Oct 2014 05:26:00 -0000 [thread overview]
Message-ID: <CAGCO0Kg8Mr8EWRH7dJRcVBEd2tyE_W-pkNSgRkDEqAmrDRn1ew@mail.gmail.com> (raw)
In-Reply-To: <3C873376-21FF-4176-8101-C1FE137DCACF@gmail.com>
On Wed, Oct 8, 2014 at 10:18 PM, Rafael Avila de Espindola
<rafael.espindola@gmail.com> wrote:
>
> Sent from my iPhone
>
> > On Oct 8, 2014, at 20:51, Ian Lance Taylor <ian@airs.com> wrote:
> >
> > Rafael Espíndola <rafael.espindola@gmail.com> 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 mailing 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.
next prev parent reply other threads:[~2014-10-09 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1412716173.8985.ezmlm-warn@gcc.gnu.org>
2014-10-08 17:23 ` Fwd: " Rafael Espíndola
2014-10-09 0:51 ` Ian Lance Taylor
2014-10-09 5:19 ` Rafael Avila de Espindola
2014-10-09 5:26 ` Chandler Carruth [this message]
2014-10-09 11:54 ` Joseph S. Myers
[not found] <1398055301.29540.ezmlm-warn@gcc.gnu.org>
2014-04-23 11:07 ` Fwd: " Mike Stump
2014-04-23 15:44 ` Frank Ch. Eigler
2014-04-23 17:04 ` Mike Stump
2013-04-01 4:45 overseers-help
[not found] <1134362992.10249.ezmlm-warn@gcc.gnu.org>
2005-12-14 0:44 ` Fwd: " Mike Stump
2005-12-14 2:28 ` Ian Lance Taylor
2006-01-30 18:30 ` Mike Stump
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 17:05 overseers-help
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=CAGCO0Kg8Mr8EWRH7dJRcVBEd2tyE_W-pkNSgRkDEqAmrDRn1ew@mail.gmail.com \
--to=chandlerc@google.com \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.org \
--cc=rafael.espindola@gmail.com \
/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).