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
Date: Sun, 10 Jan 2016 18:16:02 +0200 [thread overview]
Message-ID: <m2a8odcsvx.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <2154153.mZhPRoAGrk@sysoppad>
On Sun, Jan 10 2016, Erik Quaeghebeur <notmuch@equaeghe.nospammail.net> wrote:
> Hi,
>
>
> I've become interested in notmuch. After looking at the documentation of
> the Python bindings, I have the following questions:
> * Is it correct that a message's Message-ID used as its unique key in the
> notmuch database?
yes
> * If yes, is it correct that two messages with the same Message-ID, but
> with different contents/other headers, will have only one entry in the
> database?
yes
> * 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
>
>
> Best,
likewise :)
>
> Erik
Tomi
next prev parent reply other threads:[~2016-01-10 16: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 [this message]
2016-01-10 19:45 ` Erik Quaeghebeur
2016-01-11 6:20 ` Tomi Ollila
2016-01-11 12:14 ` David Bremner
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=m2a8odcsvx.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=notmuch@equaeghe.nospammail.net \
--cc=notmuch@notmuchmail.org \
/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).