From: Kevin Shell <kshell@gmx.com>
To: ding@gnus.org
Subject: Re: Gnus wrong message threading
Date: Sun, 20 Sep 2020 18:33:17 +0800 [thread overview]
Message-ID: <87wo0o20wi.fsf@fedora.osfans.org> (raw)
In-Reply-To: <878sd4ojxy.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Kevin writes:
>
>> Two reply messages with no In-Reply-To/References headers linked
>> to the wrong parent message, maybe it's a bug with Gnus.
>
>> The two messages' ID are:
>> Message-ID:
>> <CADnJ0kFP9d+hnV=9tLnRsLZ=sBqHuX1kLYDC6bW0hQ+8vGDKOg@mail.gmail.com>
>>
>> Message-ID:
>> <20120116105258.46140@gmx.com>
>
> The thread looks like this:
>
> . [ 58: Dwayne Henderson ] Improving the WHOIS format
> . [ 39: Jase Thew ]
> . [ 48: Dwayne Henderson ]
> . [ 65: Dwayne Henderson ]
> . [ 63: Jase Thew ]
> . [ 176: Dwayne Henderson ]
> . [ 198: Charles Howard ]
> . [ 98: Dylan Thiedeke ]
> . [ 38: Marc Hartstein ]
> . [ 16: Mark ]
> . [ 25: Jase Thew ]
> . [ 80: Dwayne Henderson ]
> . [ 20: Jase Thew ]
> . [ 77: Dwayne Henderson ]
> . [ 45: Marc Hartstein ]
> . [ 76: Dwayne Henderson ]
> . [ 48: David Romano ]
> . [ 25: David Romano ]
> . [ 78: Charles Howard ]
> **. < 107: Tony >
> . [ 29: David Romano ]
> . [ 143: Dwayne Henderson ]
> . [ 173: Dwayne Henderson ]
> . [ 73: Tony ]
> . [ 18: David Romano ]
> . < 67: David Romano >
> . [ 162: Dwayne Henderson ]
> . [ 123: David Romano ]
> . [ 362: Dwayne Henderson ]
> . [ 93: David Romano ]
> . [ 293: Dwayne Henderson ]
> . [ 59: tabris ]
> . [ 53: David Romano ]
> . [ 170: Dwayne Henderson ]
> . [ 30: Marc Hartstein ]
> . [ 60: Dwayne Henderson ]
> . [ 49: Ross Timson ]
> **. < 50: Marra Hemsedal >
> . [ 14: Timo Sirainen ]
>
> The two emails you say are threaded wrong I have marked with **.
>
My Gnus is configured with:
(setq gnus-summary-line-format "%U%R%z%B%s -- %n\n")
(setq gnus-sum-thread-tree-root "● ")
(setq gnus-sum-thread-tree-single-leaf "`->")
Viewing with this config is straightforward.
> Where would you have expected them to be linked, when all that connects
> them is the Subject, as they have no In-Reply-To/References?
>
How about linked to root message with special marks characters and
add two commands/functions like link-threads break-thread
and let the user joining the two threads together.
> Would you have preferred that they weren't included in the same thread?
>
> If so, you can set gnus-summary-thread-gathering-function to
> 'gnus-gather-threads-by-references.
>
[...]
>> They are web mailers that don't generate In-Reply-To and References headers.
>
> Really? I'm quite sure that both Gmail and GMX generate In-Reply-To and
> Reference headers when you reply to an email.
>
> If Gmail didn't there would have been an uproar.
>
> You are right that those two emails do not have In-Reply-To and
> Reference headers, but emails from Gmail and GMX usually do.
They are mails back in year *2012*.
--
kevin
next prev parent reply other threads:[~2020-09-20 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 2:15 Kevin Shell
2020-09-19 11:23 ` Adam Sjøgren
2020-09-19 13:56 ` Kevin Shell
2020-09-19 14:08 ` Adam Sjøgren
2020-09-20 2:33 ` Kevin Shell
2020-09-20 9:51 ` Adam Sjøgren
2020-09-20 10:33 ` Kevin Shell [this message]
2020-09-20 10:58 ` Adam Sjøgren
2020-09-20 11:31 ` Kevin Shell
2020-09-20 12:17 ` Adam Sjøgren
2020-09-19 14:14 ` 황병희
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wo0o20wi.fsf@fedora.osfans.org \
--to=kshell@gmx.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).