Return-Path: <tomi.ollila@iki.fi>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
 by arlo.cworth.org (Postfix) with ESMTP id 2E94F6DE140C
 for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 22:20:45 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at cworth.org
X-Spam-Flag: NO
X-Spam-Score: 0.662
X-Spam-Level: 
X-Spam-Status: No, score=0.662 tagged_above=-999 required=5 tests=[AWL=0.010, 
 SPF_NEUTRAL=0.652] autolearn=disabled
Received: from arlo.cworth.org ([127.0.0.1])
 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id cq9xx31isSey for <notmuch@notmuchmail.org>;
 Sun, 10 Jan 2016 22:20:41 -0800 (PST)
Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
 by arlo.cworth.org (Postfix) with ESMTP id A682C6DE0C66
 for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 22:20:40 -0800 (PST)
Received: from guru.guru-group.fi (localhost [IPv6:::1])
 by guru.guru-group.fi (Postfix) with ESMTP id 71A4E100080;
 Mon, 11 Jan 2016 08:20:49 +0200 (EET)
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Erik Quaeghebeur <notmuch@equaeghe.nospammail.net>,
 notmuch@notmuchmail.org
Subject: Re: Message-ID's vs. Resent-Message-ID
In-Reply-To: <1797484.KB5JPIe8ts@sysoppad>
References: <2154153.mZhPRoAGrk@sysoppad> <m2a8odcsvx.fsf@guru.guru-group.fi>
 <1797484.KB5JPIe8ts@sysoppad>
User-Agent: Notmuch/0.21+32~g73439f8 (http://notmuchmail.org) Emacs/24.3.1
 (x86_64-unknown-linux-gnu)
X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
 !)g;OY^,BjTbr)Np:%c_o'jj,Z
Date: Mon, 11 Jan 2016 08:20:49 +0200
Message-ID: <m2r3hoprge.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: text/plain
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Use and development of the notmuch mail system."
 <notmuch.notmuchmail.org>
List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2016 06:20:45 -0000

On Sun, Jan 10 2016, Erik Quaeghebeur <notmuch@equaeghe.nospammail.net> wrote:

> Thanks, Tomi, for your quick response.
>
>> > * If yes, for resent messages
>> > (https://tools.ietf.org/html/rfc2822#section-3.6.6), does notmuch use
>> > (the chronologically last) Resent-Message-ID, or the Message-ID?
>> 
>> the Message-ID
>
> Hmm. Is this a conscious decision, or is the resending case just not
> taken into account?

(most probably just) not taken into account

> What happens if I have both a message and my own copy of it after
> resending it to somebody else? I would like to have a record of whom I
> resent it to, as with forwarded messages (where the forwarded message
> does have a different message id).

Both of the copies are "files" of the same message; i.e.

notmuch search --output=files id:<Message-ID> will list both (all)
filenames

> Are the Resent-* headers of the resent message merged into the database
> entry? I guess this last question is more general: with multiple messages
> with the same Message-ID but differences (for whatever reason), how will
> these messages be merged in the database?

Database has fixed set of headers stored per message and (afaik) none
of the Resent-* headers are there (merged or separate).

(One thing to remember (for anyone perhaps planning to do something about
this) is that if we'd use Resent-Message-ID: as message identification 
if it exists, then Message-ID: of the message should act as In-Reply-To:
or References: -header...)

Tomi

> Best,
>
> Erik