From: Stefan Agner <stefan@agner.ch>
To: git@vger.kernel.org
Cc: digetx@gmail.com
Subject: git send-mail sends with duplicate In-Reply-To/References header fields
Date: Tue, 17 Apr 2018 10:42:06 +0200 [thread overview]
Message-ID: <997160314bbafb3088a401f1c09ccb08@agner.ch> (raw)
Hi,
Using git format-patch --thread + send-mail leads to
In-Reply-To/References headers added twice (with the very same value).
This is not allowed according to RFC 5322 Section 3.6:
https://tools.ietf.org/html/rfc5322#section-3.6
Ideally probably git-format-patch should be smart about whether
In-Reply-To/References are already present...
I noticed this after looking through emails catched by my spam filter
more carefully. It seems that this particular violation is penalized
quite harshly, leading to those emails landing in my spam folder. It
seems that there are multiple kernel developers which use the above work
flow and hence send emails not adhering to spec...
--
Stefan
reply other threads:[~2018-04-17 8:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=997160314bbafb3088a401f1c09ccb08@agner.ch \
--to=stefan@agner.ch \
--cc=digetx@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).