From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: info-gnus-english-mXXj517/zsQ@public.gmane.org
Cc: gmane-discuss-8Df2Q3VNN1VeQc5e7gblnA@public.gmane.org
Subject: Re: threading broken in g.e.gnus
Date: Wed, 03 Apr 2013 17:38:07 +0000 [thread overview]
Message-ID: <87fvz7o6ps.fsf@riseup.net> (raw)
In-Reply-To: <87wqsj4lmq.fsf@rash.fl.quadium.net>
Tim Howe <vsync-n9BkStgIQNfR7s880joybQ@public.gmane.org> writes:
> On 03 Apr 2013, wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse) wrote:
>
>> Tim Howe <vsync-n9BkStgIQNfR7s880joybQ@public.gmane.org> writes:
>>
>>> I'm noticing many of the threads in here are completely broken. It
>>> seems the Message-IDs are getting replaced by Mailman ones so References
>>> and In-Reply-To headers are left dangling.
>>>
>>> http://i.imgur.com/xgxuZT0.png
>>
>> You can try customizing `gnus-summary-thread-gathering-function'.
>> Gnus's default is indeed to fall back on Subject if References are
>> wrong
>
> Thanks for that, but I was actually commenting on the munging itself,
> not how Gnus is handling it on display. It seems something (GMANE?) is
> chewing on the articles and replacing the Message-IDs with "Mailman"
> ones, meaning that references and threading are broken non-predictably
> depending on the path messages take.
Yes, the problem seems correlated to [followups to] posts made from
info-gnus-english-mXXj517/zsQ@public.gmane.org, as opposed to the Gmane or Google Groups
routes. It's still noticeable, although not as frequently, with my
display settings for Gnus ( http://ompldr.org/vaHo3dQ ).
Crossposting to gmane.discuss to see if the Gmane admins have an idea
about this.
Best,
Will
--
BOFH excuse #12:
dry joints on cable plug
prev parent reply other threads:[~2013-04-03 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.23008.1364502994.855.info-gnus-english@gnu.org>
2013-04-03 15:40 ` threading broken in g.e.gnus (was: Can't send emails to this list via gmane?) Tim Howe
2013-04-03 16:05 ` threading broken in g.e.gnus W. Greenhouse
[not found] ` <mailman.23407.1365005109.855.info-gnus-english@gnu.org>
2013-04-03 16:36 ` Tim Howe
2013-04-03 17:38 ` W. Greenhouse [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=87fvz7o6ps.fsf@riseup.net \
--to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
--cc=gmane-discuss-8Df2Q3VNN1VeQc5e7gblnA@public.gmane.org \
--cc=info-gnus-english-mXXj517/zsQ@public.gmane.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).