From: Jeremy Kerr <jk@ozlabs.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Anton Blanchard <anton@samba.org>,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Subject: Re: mailman From rewriting [was perf jit: genelf makes assumptions about endian]
Date: Wed, 30 Mar 2016 13:30:12 +0800 [thread overview]
Message-ID: <56FB6464.4010609@ozlabs.org> (raw)
In-Reply-To: <20160329210639.12136fd5@canb.auug.org.au>
Hi Stephen,
>> Do you know why mailman would be re-writing From: there? It's confusing
>> patchwork, as multiple mails are now coming from that address.
>
> Yep, Anton posts from samba.org. They publish a DMARC policy that
> breaks mailing lists.
(╯°□°)╯︵ ┻━━┻
This also breaks git-am:
[jk@pudge linux]$ git am incoming.eml
Applying: perf jit: genelf makes assumptions about endian
[jk@pudge linux]$ git log --format='format:%an <%ae>' -1
Anton Blanchard via Linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
> The best thing we can do is to do the above rewrite of the From header.
OK, it looks like we're stuck either way with DMARC. Could we make this
a little more tolerable by stashing the original From: value in a new
header? I know it's already in Reply-To, but that could also be set by
arbitrary other (non-mailman-DMARC-rewrite) sources.
Alternatively, if there's some other way to tell that this a mail has
been rewritten, we can know to use Reply-To in preference to From.
Otherwise, I guess we could require that *all patch submitters* put
their From: line in the content of their mails, as git send-email does
when user != author. But that's a little less-than-optimal.
Cheers,
Jeremy
next prev parent reply other threads:[~2016-03-30 5:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 6:59 [PATCH] perf jit: genelf makes assumptions about endian Anton Blanchard
2016-03-29 8:56 ` mailman From rewriting [was perf jit: genelf makes assumptions about endian] Jeremy Kerr
2016-03-29 10:06 ` Stephen Rothwell
2016-03-30 2:55 ` Michael Ellerman
2016-03-30 5:30 ` Jeremy Kerr [this message]
2016-03-30 6:57 ` Stephen Rothwell
2016-03-30 9:03 ` Michael Ellerman
2016-03-30 9:08 ` Michael Ellerman
2016-03-30 2:38 ` [PATCH] perf jit: genelf makes assumptions about endian Michael Ellerman
2016-03-30 21:15 ` Arnaldo Carvalho de Melo
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=56FB6464.4010609@ozlabs.org \
--to=jk@ozlabs.org \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).