From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id 70D9E1F404;
	Thu,  1 Mar 2018 17:55:26 +0000 (UTC)
Date: Thu, 1 Mar 2018 17:55:26 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: multiple Message-ID headers in messages
Message-ID: <20180301175526.GA31516@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
List-Id: <meta.public-inbox.org>

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