From: "Rollins, Jameson" <jrollins@caltech.edu>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: viewing duplicate messages
Date: Thu, 30 May 2019 16:34:36 +0000 [thread overview]
Message-ID: <877ea7zyss.fsf@caltech.edu> (raw)
This is essentially a wishlist report...
It would be nice to have an easy way in notmuch-emacs-show to know if
there are multiple messages with the same message-id in the store, and
to cycle through viewing each individually.
It's possible (even likely) that one has multiple messages with the same
message-id in their mail store. For example, this can happen when sent
messages are saved with an fcc and the same message is received on a
mailing list. Notmuch indexes all copies, but it only shows you one of
the copies when you ask to view the message.
This behavior would be fine if all copies of the message were identical.
But it's more likely that the copies are in fact different, for example
because the mailing list has altered the received message in some way,
it was mangled in transit, or someone is explicitly trying to attack
your mail store [0].
It would be nice to have better exposure of the fact that multiple
copies exist, and to have an easy way to view alternate copies. For
notmuch-emacs a key could just cycle through available copies.
jamie.
[0] https://notmuchmail.org/pipermail/notmuch/2012/009965.html
next reply other threads:[~2019-05-30 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:34 Rollins, Jameson [this message]
2019-05-30 22:11 ` viewing duplicate messages Jorge P. de Morais Neto
2019-05-30 22:17 ` Rollins, Jameson
2019-05-30 23:02 ` Daniel Kahn Gillmor
2019-05-31 15:45 ` Jorge P. de Morais Neto
2019-05-31 16:32 ` Daniel Kahn Gillmor
2019-08-17 22:12 ` Jorge P. de Morais Neto
2019-08-18 20:20 ` Daniel Kahn Gillmor
-- strict thread matches above, loose matches on Subject: below --
2019-07-17 14:50 drebs
2019-07-17 15:08 ` Georg Faerber
2019-07-29 1:07 ` Daniel Kahn Gillmor
2019-07-29 13:34 ` Georg Faerber
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=877ea7zyss.fsf@caltech.edu \
--to=jrollins@caltech.edu \
--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).