From: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Subject: Re: in-reply-to hell?
Date: Tue, 24 Jun 2003 01:43:12 +0200 [thread overview]
Message-ID: <m34r2gjr73.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <sdn0gdrbn0.fsf@wanderer.hardakers.net>
Wes Hardaker <wes@hardakers.net> writes:
> So, my threads have been broken by many mail readers that don't do
> references: headers all the time. I thought at least at one point in
> time gnus used in-reply-to as a fallback for threading? But it
> doesn't seem to use them properly (I didn't check to see if they were
> broken, which I suppose they could be). Help?
Gnus does use In-Reply-To, but mail agents like Eudora even gets
In-Reply-To wrong -- it sticks the last Message-ID from the References
header into In-Reply-To, so that it looks like it's a response to the
parent of the article it's a response to.
(Hm. I should probably rewrite that last sentence.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-06-23 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 21:38 Wes Hardaker
2003-06-23 23:43 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m34r2gjr73.fsf@quimbies.gnus.org \
--to=larsi@quimbies.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).