[notmuch] [PATCH (rebased)] Handle message renames in mail spool
cworth at cworth.org
Fri Dec 4 16:39:50 PST 2009
On Fri, 4 Dec 2009 14:09:46 -0500, Michael Alan Dorman <mdorman at ironicdesign.com> wrote:
> Besides, in notmuch, what's the difference going to be? It'll still be
> threaded the same, etc., but you'd be able to tell that this one came
> to you rather than through the list, no?
There's one other point I should make here while talking about duplicate
messages, (as determined by identical Message ID).
Currently notmuch just indexes the first version of any given message it
sees, and simply ignores anything else it sees in the future.
We're planning to change it to at least save each of the filenames for
messages with multiple files. That way if some duplicates are deleted,
then notmuch will still be able to find one of the others.
Also, we could make notmuch index duplicate messages and add any
additional terms found to the document for the message. Currently, that
wouldn't make a big difference since notmuch is only indexing the body
and a few specific headers, (From, Subject, To, Cc, Bcc, Messsage-ID,
So any differences there should be quite minor (a "[LIST]" prefix in
subject? an extra footer in the boday?), under the assumption that no
mail files will ever exist with the same message ID but disparate
Now, we have a TODO item to allow for indexing additional headers,
(either by default or by user configuration). Once we start doing that,
it probably will make sense to at least index the duplicates.
But when viewing an actual message, I'm still planning on having notmuch
just return an arbitrary filename from the list of filenames associated
with that message. Does anyone see any problem with that? Can you think
of a case where you'd really care about seeing one or the other of
a particular duplicated message?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the notmuch