From: Leah Neukirchen <leah@vuxu.org>
To: Eric Wong <e@80x24.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, meta@public-inbox.org
Subject: Re: BUG?: The UI shows an "In-Reply-To" value different than the actual value
Date: Tue, 20 Nov 2018 13:43:01 +0100 [thread overview]
Message-ID: <87y39n9ay2.fsf@vuxu.org> (raw)
In-Reply-To: <20181120074553.72ayiqorwdsvdfoi@dcvr> (Eric Wong's message of "Tue, 20 Nov 2018 07:45:53 +0000")
Eric Wong <e@80x24.org> writes:
> When I was working on this, I found References: more consistent
> and easier-to-parse than In-Reply-To; as the latter could
> contain random human-readable phrases. Thus the code favors
> using the References header for threading.
>
> lib/PublicInbox/MID.pm has this, currently:
>
> # last References should be IRT, but some mail clients do things
> # out of order, so trust IRT over References iff IRT exists
This is also what jwz recommends (https://www.jwz.org/doc/threading.html):
>> I've been informed that recent versions of Eudora violate this
>> standard: they put the parent Message-ID in the In-Reply-To header,
>> but do not duplicate it in the References header: instead, the
>> References header contains the grandparent, great-grand-parent,
>> etc.
>> This implies that to properly reconstruct the thread of a message
>> in the face of this nonstandard behavior, we need to append any
>> In-Reply-To message IDs to References.
(mthread(1) of mblaze does the same.)
--
Leah Neukirchen <leah@vuxu.org> http://leah.zone
prev parent reply other threads:[~2018-11-20 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:48 BUG?: The UI shows an "In-Reply-To" value different than the actual value Ævar Arnfjörð Bjarmason
2018-11-20 7:45 ` Eric Wong
2018-11-20 12:43 ` Leah Neukirchen [this message]
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y39n9ay2.fsf@vuxu.org \
--to=leah@vuxu.org \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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://80x24.org/public-inbox.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).