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 09:47:01 +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; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1539938933 17647 195.159.176.226 (19 Oct 2018 08:48:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 19 Oct 2018 08:48:53 +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 10:48:49 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 1gDQSf-0004VJ-4i for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Oct 2018 10:48:49 +0200 Original-Received: from localhost ([::1]:47917 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gDQUl-0002Xg-Nh for geh-help-gnu-emacs@m.gmane.org; Fri, 19 Oct 2018 04:50:59 -0400 X-Received: by 2002:a1c:9609:: with SMTP id y9-v6mr225986wmd.3.1539938822214; Fri, 19 Oct 2018 01:47:02 -0700 (PDT) Original-Path: usenet.stanford.edu!r123-v6no396597wmd.0!news-out.google.com!m141-v6ni1717wmd.0!nntp.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!ecngs!feeder2.ecngs.de!78.46.240.70.MISMATCH!weretis.net!feeder4.news.weretis.net!news.albasani.net!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 42 Original-X-Trace: news.albasani.net ZKFhpaC4XXR39b1c+g1RGD1pgXrrYd812A0rJaZWHF5xbrsd3fK9iyLO9MWfog0inIo2JHpShXkwhcS0Sz3XEw== Original-NNTP-Posting-Date: Fri, 19 Oct 2018 08:47:02 +0000 (UTC) Original-Injection-Info: news.albasani.net; logging-data="nOgAPP/BiquCPmNNYX85CIHZFZREyTJaguWNhyt4ZlTf1+d3WokyggvjRWo1R8Z7mqmM4Q2Mqb0XwzB4X5rJY3fvxrfcjVNGEZCXn62lEmWdwTuICEWueEhPFj/eVeVm"; mail-complaints-to="abuse@albasani.net" Cancel-Lock: sha1:WeIqu3jTjZR7sEXwaco+/KDp3JI= Original-Xref: usenet.stanford.edu gnu.emacs.help:224211 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:118337 Archived-At: On 2018-10-18, Garreau, Alexandre wrote: > On 2018-10-18 at 12:44, Bob Proulx wrote: >> This is a deja vu as we have discussed this before. This link jumps >> right into some detail from that previous discussion. >> >> http://lists.gnu.org/archive/html/help-gnu-emacs/2016-06/msg00147.html >> >> Of course the web email address redactor with all of the address >> hidden redactions make reading that on the web quite difficult. One >> could ftp down the mailbox and then have the full mailbox of messages. >> >> 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. >> >> In the intervening two years since the previous discussion nothing >> substantial has happened. > > So I was right, it is the news-mail interface, and it is in standford, > so now the question is: who to contact? is that GNU people? > > Maybe to as “X-Complaints-To” header suggests? > or ? 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. Alexandre, did you send the post I am replying to through USENET as well? It has the following In-Reply-To: In-Reply-To: <20181018121955500722783@bob.proulx.com> (Bob Proulx's message of "Thu, 18 Oct 2018 12:44:57 -0600") -- Nuno Silva