From: Jason R Mastaler <jason@mastaler.com>
Subject: Threading MH messages
Date: 12 Jul 1997 14:10:23 -0600 [thread overview]
Message-ID: <x7soxknia8.fsf@mastaler.com> (raw)
Why is it that Gnus doesn't like to thread replies that are composed
with MH? I've noticed this for a long time now. Take these three
summary buffers for example.
!A [ 31: Lars Magne Ingebrigt] Qua Vadis, Quassia?
R [ 8: Vinnie Shelton ] Re: Qua Vadis, Quassia?
O [ 41: Cedric Jaboulet ] pb with rcvdist
O [ 15: Frank Swasey ] Re: pb with rcvdist
R [ 21: Dave Golden ] smapd address parsing fixes
R [ 13: Rick Murphy ]
The second message of the first two buffers was composed with MH and
thus weren't threaded. The second message of the third buffer was
composed with Windows Eudora and was threaded fine (like with most
other MUAs). Thus, MH seems to be the exception. This is especially
annoying in large mailing lists where I'm following a thread and then
later find a stray reply pages and pages down because it wasn't added
to the thread. In most of these cases, the message indeed turns out
to be an MH message.
Jason R. Mastaler jason@mastaler.com
next reply other threads:[~1997-07-12 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-12 20:10 Jason R Mastaler [this message]
1997-07-14 15:09 ` David S. Goldberg
1997-07-14 21:16 ` Andrew Hobson
1997-07-14 23:02 ` Jason R Mastaler
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=x7soxknia8.fsf@mastaler.com \
--to=jason@mastaler.com \
/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).