From: Ian Kelling <iank@fsf.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: Andrew Donnellan <ajd@linux.ibm.com>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Jonathan Nieder <jrnieder@gmail.com>,
patchwork@lists.ozlabs.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Eric Blake <eblake@redhat.com>,
git@vger.kernel.org
Subject: Re: [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes
Date: Fri, 11 Oct 2019 13:36:16 -0400 [thread overview]
Message-ID: <871rvjdw1b.fsf@fsf.org> (raw)
In-Reply-To: <6574162.ouEm0onZRE@silver>
Christian Schoenebeck <qemu_oss@crudebyte.com> writes:
> 4. MTA's should also address this DKIM issue more accurately.
I agree that Exim should be changed as you suggest.
>
> By taking these things into account, emails of domains with strict DMARC
> policies are no longer munged on gnu lists.
Additional info: Migration of many gnu/nongnu.gnu.org lists is still in
progress for another week or so, then that will be true for most of
them. For a minority of lists, the list administrators have set weird
settings like making all messages have from: rewritten as from this
list, and we are leaving them as is since the list administrators opted
in to that at some point. But if the list deals with patches and not
modifying the headers is useful to the people on the list, I think a
request to change the list settings is likely to be accepted by the list
admin.
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
prev parent reply other threads:[~2019-10-11 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191010062047.21549-1-ajd@linux.ibm.com>
2019-10-10 19:41 ` [PATCH] parser: Unmangle From: headers that have been mangled for DMARC purposes Jonathan Nieder
2019-10-10 21:13 ` Andrew Donnellan
2019-10-10 23:16 ` Daniel Axtens
2019-10-10 23:40 ` Stephen Rothwell
2019-10-10 22:54 ` Jeff King
2019-10-10 23:01 ` Andrew Donnellan
2019-10-10 23:06 ` Jeff King
2019-10-11 15:42 ` Daniel Axtens
2019-10-11 15:51 ` Jeff King
2019-10-13 11:05 ` Andrew Donnellan
2019-10-11 4:29 ` Junio C Hamano
2019-10-11 4:36 ` Andrew Donnellan
2019-10-11 4:50 ` Andrew Donnellan
2019-10-11 13:13 ` Christian Schoenebeck
2019-10-11 17:36 ` Ian Kelling [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rvjdw1b.fsf@fsf.org \
--to=iank@fsf.org \
--cc=ajd@linux.ibm.com \
--cc=alexandre.belloni@bootlin.com \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=patchwork@lists.ozlabs.org \
--cc=peff@peff.net \
--cc=qemu_oss@crudebyte.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).