From: "Nuno Silva" <nunojsilva@invalid.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: Fixing news-mail gateway [Was: Re: Newsgroups mailing-list gateway broken thread]
Date: Fri, 19 Oct 2018 20:12:19 +0100 [thread overview]
Message-ID: <pqdaaj$fee$1@news.albasani.net> (raw)
In-Reply-To: mailman.2463.1539974929.1284.help-gnu-emacs@gnu.org
On 2018-10-19, Bob Proulx wrote:
> Nuno Silva wrote:
>> Bob Proulx wrote:
>> > AFAICT messages through the Stanford newsgroup to email relay do not
>> > include the In-Reply-To header and therefore break threading. A
>> > message may have the References header with information about previous
>> > messages in the thread causing the message to thread before where it
>> > should thread, and if only one deep them be completely disconnected
>> > from the original thread.
>>
>> I might be wrong, but it looks like the In-reply-to header *is* sent,
>> but the message-ids are being rewritten somewhere, so one message can
>> end up with two different message-ids, and threading by In-reply-to will
>> not work as expected. The "Message not available" entries in the web
>> archive are probably those message-ids.
>
> Hmm... You are right that at least some mail messages from the
> Stanford newsgroup gateway do include In-Reply-To headers. Most do
> not however. In the last three months of the archive 38 messages that
> came through the gateway included In-Reply-To out of 285 messages
> total through that gateway with 247 not including it. At least some
> of those not including it were starting a new thread and were not
> replies so that normal for those.
And you are right some (most?) don't include In-Reply-To. I checked some
messages that were sent through USENET, but somehow I avoided checking
my own messages. The message you are replying to lacks In-Reply-To (at
least here). (But it has References, which I suppose should be enough to
do threading?)
(A message posted to the group/list through USENET will probably not
break threading on the same server it was posted to.)
> This nature of it with some having it and some not having it is a good
> clue that I had previously missed. It might indicate that one of the
> newsgroup relays is causing the issue and it depends upon how the
> message routed through the newsgroup relays before arriving at
> Stanford and getting gatewayed to the mailing list. It will need more
> analysis to see if we can correlate it with one specific host.
>
> Bob
>
--
Nuno Silva
next prev parent reply other threads:[~2018-10-19 19:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 22:21 Newsgroups mailing-list gateway broken thread Garreau, Alexandre
2018-10-18 10:05 ` Emanuel Berg
2018-10-18 16:57 ` Garreau, Alexandre
2018-10-18 18:44 ` Bob Proulx
2018-10-18 19:24 ` Fixing news-mail gateway [Was: Re: Newsgroups mailing-list gateway broken thread] Garreau, Alexandre
2018-10-21 3:39 ` Who to contact about the gateway [Was: Re: Fixing news-mail gateway [Was: Re: Newsgroups mailing-list gateway broken thread]] Garreau, Alexandre
2018-10-21 4:11 ` Emanuel Berg
[not found] ` <mailman.2530.1540095533.1284.help-gnu-emacs@gnu.org>
2018-10-21 13:49 ` Garreau, Alexandre
2018-10-21 17:39 ` Emanuel Berg
[not found] ` <mailman.2398.1539890933.1284.help-gnu-emacs@gnu.org>
2018-10-19 8:47 ` Fixing news-mail gateway [Was: Re: Newsgroups mailing-list gateway broken thread] Nuno Silva
2018-10-19 18:48 ` Bob Proulx
[not found] ` <mailman.2463.1539974929.1284.help-gnu-emacs@gnu.org>
2018-10-19 19:12 ` Nuno Silva [this message]
2018-10-21 3:11 ` Garreau, Alexandre
2018-10-19 10:17 ` Newsgroups mailing-list gateway broken thread Emanuel Berg
2018-10-19 10:33 ` Nuno Silva
2018-10-19 12:32 ` Emanuel Berg
2018-10-19 19:02 ` Bob Proulx
[not found] ` <mailman.2466.1539975763.1284.help-gnu-emacs@gnu.org>
2018-10-19 19:38 ` Nuno Silva
2018-10-21 3:13 ` Garreau, Alexandre
2018-10-21 3:17 ` Garreau, Alexandre
2018-10-21 9:06 ` Nuno Silva
2018-10-19 18:50 ` Bob Proulx
2018-10-19 20:34 ` Emanuel Berg
2018-10-19 15:07 ` Emanuel Berg
[not found] ` <mailman.2380.1539881862.1284.help-gnu-emacs@gnu.org>
2018-10-18 18:37 ` Emanuel Berg
2018-10-18 19:28 ` Garreau, Alexandre
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='pqdaaj$fee$1@news.albasani.net' \
--to=nunojsilva@invalid.invalid \
--cc=help-gnu-emacs@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.