From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Nuno Silva" Newsgroups: gmane.emacs.help Subject: Re: Fixing news-mail gateway [Was: Re: Newsgroups mailing-list gateway broken thread] Date: Fri, 19 Oct 2018 20:12:19 +0100 Organization: albasani.net Message-ID: References: <87lg6w43k8.fsf@portable.galex-713.eu> <861s8nefj5.fsf@zoho.com> <874ldjtcow.fsf@portable.galex-713.eu> <20181018121955500722783@bob.proulx.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1539976402 27150 195.159.176.226 (19 Oct 2018 19:13:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 19 Oct 2018 19:13:22 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Oct 19 21:13:18 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gDaD0-0006xF-Gl for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Oct 2018 21:13:18 +0200 Original-Received: from localhost ([::1]:52284 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gDaF6-0003LP-Vp for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Oct 2018 15:15:29 -0400 X-Received: by 2002:a5d:530e:: with SMTP id e14-v6mr3190321wrv.4.1539976339344; Fri, 19 Oct 2018 12:12:19 -0700 (PDT) Original-Path: usenet.stanford.edu!r123-v6no1171269wmd.0!news-out.google.com!m141-v6ni4590wmd.0!nntp.google.com!proxad.net!feeder1-2.proxad.net!weretis.net!feeder4.news.weretis.net!news.albasani.net!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 47 Original-X-Trace: news.albasani.net XyTT66f0x7onvNikitnmGr+oY3YHBMQkM+vXSNLD2ini4jW4MpraVnAyHs1ufMiLXWpCYYQDL7+fSUbrxzGuoQ== Original-NNTP-Posting-Date: Fri, 19 Oct 2018 19:12:19 +0000 (UTC) Original-Injection-Info: news.albasani.net; logging-data="O5ulhNtxWAIeebOZGqtMb6mMQLXaieItYxzHbNXieFix4/b8XDSuzBDZMfuzqoz+5ar60WICqEeXA4mXelA0v4sSabtkQNRS+jhP998MI0pKZ8nBWfQ0dZMDAvRtH8Hw"; mail-complaints-to="abuse@albasani.net" Cancel-Lock: sha1:pFxp9UUNTkdLYa8RSfFKX1Pf7mQ= Original-Xref: usenet.stanford.edu gnu.emacs.help:224224 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:118350 Archived-At: 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