Re: Message-ID's vs. Resent-Message-ID

diff --git a/ca/58a94e75a7fe116401430d05cc93ab368d59c5 b/ca/58a94e75a7fe116401430d05cc93ab368d59c5
new file mode 100644 (file)
index 0000000..f3542df
--- /dev/null
+++ b/ca/58a94e75a7fe116401430d05cc93ab368d59c5
@@ -0,0 +1,68 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id E091F6DE1422\r
+ for <notmuch@notmuchmail.org>; Mon, 11 Jan 2016 04:15:03 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.309\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[AWL=0.242,\r
+  RP_MATCHES_RCVD=-0.55, SPF_PASS=-0.001] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id EtigPvWJITHg for <notmuch@notmuchmail.org>;\r
+ Mon, 11 Jan 2016 04:15:01 -0800 (PST)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id 094786DE141B\r
+ for <notmuch@notmuchmail.org>; Mon, 11 Jan 2016 04:15:00 -0800 (PST)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1aIbN0-00062J-TT; Mon, 11 Jan 2016 07:14:46 -0500\r
+Received: (nullmailer pid 20037 invoked by uid 1000);\r
+ Mon, 11 Jan 2016 12:14:54 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Tomi Ollila <tomi.ollila@iki.fi>, Erik Quaeghebeur <notmuch@equaeghe.net>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: Message-ID's vs. Resent-Message-ID\r
+In-Reply-To: <m2r3hoprge.fsf@guru.guru-group.fi>\r
+References: <2154153.mZhPRoAGrk@sysoppad> <m2a8odcsvx.fsf@guru.guru-group.fi>\r
+ <1797484.KB5JPIe8ts@sysoppad> <m2r3hoprge.fsf@guru.guru-group.fi>\r
+User-Agent: Notmuch/0.21+26~g9404723 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Mon, 11 Jan 2016 08:14:54 -0400\r
+Message-ID: <87wprg5n41.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 11 Jan 2016 12:15:04 -0000\r
+\r
+Tomi Ollila <tomi.ollila@iki.fi> writes:\r
+\r
+> (One thing to remember (for anyone perhaps planning to do something about\r
+> this) is that if we'd use Resent-Message-ID: as message identification \r
+> if it exists, then Message-ID: of the message should act as In-Reply-To:\r
+> or References: -header...)\r
+\r
+It actually seems like one of the more benign cases of message-id\r
+collision that currently exist in notmuch. The fact that by default you\r
+see only one copy of a message that arrived two different ways is a\r
+design choice; it's hard to get closer than the resent message case.  I\r
+suspect any change would have to be configurable, since most existing\r
+notmuch users would be pretty surprised to suddenly see lots of\r
+duplicate messages.\r
+\r
+d\r
+\r