1 Return-Path: <notmuch@equaeghe.nospammail.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by arlo.cworth.org (Postfix) with ESMTP id F2CF26DE140C
\r
6 for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 11:45:57 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-0.668 tagged_above=-999 required=5 tests=[AWL=0.053,
\r
12 DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7,
\r
13 RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
\r
15 Received: from arlo.cworth.org ([127.0.0.1])
\r
16 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id 48T6wt_8sy0V for <notmuch@notmuchmail.org>;
\r
18 Sun, 10 Jan 2016 11:45:55 -0800 (PST)
\r
19 Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
\r
21 by arlo.cworth.org (Postfix) with ESMTPS id 22B686DE0C66
\r
22 for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 11:45:54 -0800 (PST)
\r
23 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
\r
24 by mailout.nyi.internal (Postfix) with ESMTP id 4278520214
\r
25 for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 14:45:52 -0500 (EST)
\r
26 Received: from frontend1 ([10.202.2.160])
\r
27 by compute2.internal (MEProxy); Sun, 10 Jan 2016 14:45:52 -0500
\r
28 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=nospammail.net; h=
\r
29 content-transfer-encoding:content-type:date:from:in-reply-to
\r
30 :message-id:mime-version:references:subject:to:x-sasl-enc
\r
31 :x-sasl-enc; s=mesmtp; bh=8mNiB4QbBc1LdY63YGWan2v8aNo=; b=No2kFU
\r
32 3NAM7jTx6ngRTl/GL5LwgQIeFz/jtYDpJ0LR1vSfdOhZXro0JYHjyB+XBceonBGo
\r
33 ByQjbUIVFLMEvy21DM9vatOrVp0JOmwnxzyiFiCgAz1eWpQOMlLGo16NP5VCtcNZ
\r
34 JPRIX+bhmgJ5wlh4IPvuF/6ryGn6Y/SZ8jEIQ=
\r
35 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
\r
36 messagingengine.com; h=content-transfer-encoding:content-type
\r
37 :date:from:in-reply-to:message-id:mime-version:references
\r
38 :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=8mNiB4QbBc1LdY6
\r
39 3YGWan2v8aNo=; b=p6JmCdWqYhuITAgL26PbzEuCvMxrZghHKR6/8hA4x/H9ygY
\r
40 ZXzMvGLNCIQp1gVOxMhJ4i5S34++vl53JzeNTDW7okohVx0aIeSv34W/G/TaHqG8
\r
41 jqR6HvI8FTyGI9lJ2d4Dh/N8pLJrQZ7GQvDmU44BsD12nYGBruBPt+UHb+b4=
\r
42 X-Sasl-enc: CWzHu6H+b47jIe+d9ilPwVmN6nFUra8PKu+ghvKqd1Ru 1452455151
\r
43 Received: from sysoppad.localnet (cust-5286ecc8.wba.access.stipte.nl
\r
45 by mail.messagingengine.com (Postfix) with ESMTPA id E8295C00017
\r
46 for <notmuch@notmuchmail.org>; Sun, 10 Jan 2016 14:45:51 -0500 (EST)
\r
47 From: Erik Quaeghebeur <notmuch@equaeghe.nospammail.net>
\r
48 To: notmuch@notmuchmail.org
\r
49 Subject: Re: Message-ID's vs. Resent-Message-ID
\r
50 Date: Sun, 10 Jan 2016 20:45:49 +0100
\r
51 Message-ID: <1797484.KB5JPIe8ts@sysoppad>
\r
52 User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; )
\r
53 In-Reply-To: <m2a8odcsvx.fsf@guru.guru-group.fi>
\r
54 References: <2154153.mZhPRoAGrk@sysoppad> <m2a8odcsvx.fsf@guru.guru-group.fi>
\r
56 Content-Transfer-Encoding: 7Bit
\r
57 Content-Type: text/plain; charset="us-ascii"
\r
58 X-BeenThere: notmuch@notmuchmail.org
\r
59 X-Mailman-Version: 2.1.20
\r
61 List-Id: "Use and development of the notmuch mail system."
\r
62 <notmuch.notmuchmail.org>
\r
63 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
65 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
66 List-Post: <mailto:notmuch@notmuchmail.org>
\r
67 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
68 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
69 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
70 X-List-Received-Date: Sun, 10 Jan 2016 19:45:58 -0000
\r
72 Thanks, Tomi, for your quick response.
\r
74 > > * If yes, for resent messages
\r
75 > > (https://tools.ietf.org/html/rfc2822#section-3.6.6), does notmuch use
\r
76 > > (the chronologically last) Resent-Message-ID, or the Message-ID?
\r
80 Hmm. Is this a conscious decision, or is the resending case just not taken into account?
\r
82 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).
\r
84 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?
\r