--- /dev/null
+Return-Path: <tomi.ollila@iki.fi>\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 2E94F6DE140C\r
+ for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 22:20:45 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.662\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.662 tagged_above=-999 required=5 tests=[AWL=0.010, \r
+ SPF_NEUTRAL=0.652] 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 cq9xx31isSey for <notmuch@notmuchmail.org>;\r
+ Sun, 10 Jan 2016 22:20:41 -0800 (PST)\r
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])\r
+ by arlo.cworth.org (Postfix) with ESMTP id A682C6DE0C66\r
+ for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 22:20:40 -0800 (PST)\r
+Received: from guru.guru-group.fi (localhost [IPv6:::1])\r
+ by guru.guru-group.fi (Postfix) with ESMTP id 71A4E100080;\r
+ Mon, 11 Jan 2016 08:20:49 +0200 (EET)\r
+From: Tomi Ollila <tomi.ollila@iki.fi>\r
+To: Erik Quaeghebeur <notmuch@equaeghe.nospammail.net>,\r
+ notmuch@notmuchmail.org\r
+Subject: Re: Message-ID's vs. Resent-Message-ID\r
+In-Reply-To: <1797484.KB5JPIe8ts@sysoppad>\r
+References: <2154153.mZhPRoAGrk@sysoppad> <m2a8odcsvx.fsf@guru.guru-group.fi>\r
+ <1797484.KB5JPIe8ts@sysoppad>\r
+User-Agent: Notmuch/0.21+32~g73439f8 (http://notmuchmail.org) Emacs/24.3.1\r
+ (x86_64-unknown-linux-gnu)\r
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL\r
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F\r
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z\r
+Date: Mon, 11 Jan 2016 08:20:49 +0200\r
+Message-ID: <m2r3hoprge.fsf@guru.guru-group.fi>\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 06:20:45 -0000\r
+\r
+On Sun, Jan 10 2016, Erik Quaeghebeur <notmuch@equaeghe.nospammail.net> wrote:\r
+\r
+> Thanks, Tomi, for your quick response.\r
+>\r
+>> > * If yes, for resent messages\r
+>> > (https://tools.ietf.org/html/rfc2822#section-3.6.6), does notmuch use\r
+>> > (the chronologically last) Resent-Message-ID, or the Message-ID?\r
+>> \r
+>> the Message-ID\r
+>\r
+> Hmm. Is this a conscious decision, or is the resending case just not\r
+> taken into account?\r
+\r
+(most probably just) not taken into account\r
+\r
+> What happens if I have both a message and my own copy of it after\r
+> resending it to somebody else? I would like to have a record of whom I\r
+> resent it to, as with forwarded messages (where the forwarded message\r
+> does have a different message id).\r
+\r
+Both of the copies are "files" of the same message; i.e.\r
+\r
+notmuch search --output=files id:<Message-ID> will list both (all)\r
+filenames\r
+\r
+> Are the Resent-* headers of the resent message merged into the database\r
+> entry? I guess this last question is more general: with multiple messages\r
+> with the same Message-ID but differences (for whatever reason), how will\r
+> these messages be merged in the database?\r
+\r
+Database has fixed set of headers stored per message and (afaik) none\r
+of the Resent-* headers are there (merged or separate).\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
+Tomi\r
+\r
+> Best,\r
+>\r
+> Erik\r