From: Teemu Likonen <tlikonen@iki.fi>
To: Daniel Corbe <daniel@corbe.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Fixed Message-ID trouble
Date: Mon, 25 Sep 2023 15:00:40 +0300 [thread overview]
Message-ID: <87y1guqx7b.fsf@iki.fi> (raw)
In-Reply-To: <9F44B9F8-E2DB-4B01-8196-2AA48036A992@corbe.net>
[-- Attachment #1.1: Type: text/plain, Size: 770 bytes --]
* 2023-09-25 07:33:23-0400, Daniel Corbe wrote:
> Silly question, I know, but have you actually tried reaching out to
> the user?
Not silly, but I don't even know who the person is. All I see is the
mess, and everything else is my interpretation of the cause. Notmuch
Emacs tree mode shows messages' relations but they are not accurate if
references are messed up. It's difficult to dig into Message-ID level of
relations.
Perhaps my wish is that there was an easy way to break threads: mark a
message as origin of a new thread. Or perhaps I just use my custom
ignore mechanism to mark messed threads automatically as read and move
on.
--
/// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/
// OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2023-09-25 12:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 8:54 Fixed Message-ID trouble Teemu Likonen
2023-09-25 10:52 ` Teemu Likonen
2023-09-25 10:59 ` Michael J Gruber
2023-09-25 11:33 ` Daniel Corbe
2023-09-25 12:00 ` Teemu Likonen [this message]
2023-09-25 13:10 ` Alexander Adolf
2023-09-26 10:13 ` David Bremner
2023-09-26 11:44 ` Alexander Adolf
2023-09-26 12:15 ` Andreas Kähäri
2023-09-26 16:22 ` Alexander Adolf
2023-09-26 10:07 ` David Bremner
2023-09-26 12:46 ` Teemu Likonen
2023-09-26 17:17 ` David Bremner
2023-09-25 21:53 ` Gregor Zattler
2023-09-25 23:00 ` Andy Smith
2023-09-25 22:45 ` Daniel Kahn Gillmor
2023-09-27 16:48 ` David Bremner
2023-09-28 5:51 ` Teemu Likonen
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=87y1guqx7b.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=daniel@corbe.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).