From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: multiple Message-ID headers in messages
Date: Thu, 1 Mar 2018 17:55:26 +0000 [thread overview]
Message-ID: <20180301175526.GA31516@dcvr> (raw)
Having multiple Message-ID headers is a problem that happens in
the real world. git send-email used to do it, even(*). So v2
will support it, as it'll even be useful for dealing with
duplicates...
I've been thinking of ways to handle different messages which
use the same Message-Id. It doesn't happen currently; but it
could be a potential vector for someone who doesn't want their
messages archived. The WWW interface can deal with it as the
HTML rendering is not tied to any RFCs or client implementations,
but the NNTP interface is...
So I think injecting a _new_ Message-ID when this happens will
be the course of action. That way, different messages which
share the same Message-ID won't be hidden from NNTP readers.
(*) https://80x24.org/mirrors/git.git/patch?h=4f3d37035a7c735a3b69f962656819f4ff7e4927
reply other threads:[~2018-03-01 17:55 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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180301175526.GA31516@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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).