From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>,
Erik Quaeghebeur <notmuch@equaeghe.net>,
notmuch@notmuchmail.org
Subject: Re: Message-ID's vs. Resent-Message-ID
Date: Mon, 11 Jan 2016 08:14:54 -0400 [thread overview]
Message-ID: <87wprg5n41.fsf@zancas.localnet> (raw)
In-Reply-To: <m2r3hoprge.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> (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...)
It actually seems like one of the more benign cases of message-id
collision that currently exist in notmuch. The fact that by default you
see only one copy of a message that arrived two different ways is a
design choice; it's hard to get closer than the resent message case. I
suspect any change would have to be configurable, since most existing
notmuch users would be pretty surprised to suddenly see lots of
duplicate messages.
d
prev parent reply other threads:[~2016-01-11 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 15:35 Message-ID's vs. Resent-Message-ID Erik Quaeghebeur
2016-01-10 16:16 ` Tomi Ollila
2016-01-10 19:45 ` Erik Quaeghebeur
2016-01-11 6:20 ` Tomi Ollila
2016-01-11 12:14 ` David Bremner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wprg5n41.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@equaeghe.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).