Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Richmond <dnomhcir@gmx.com>
Cc: info-gnus-english <info-gnus-english@gnu.org>
Subject: Re: Gnus notification of replies to my articles
Date: Thu, 12 Mar 2020 09:48:08 +0000	[thread overview]
Message-ID: <87a74luco7.fsf@ucl.ac.uk> (raw)
In-Reply-To: <7yeety0vwp.fsf@richmond.example.com> (Richmond's message of "Thu, 12 Mar 2020 09:23:02 +0000")

On Thursday, 12 Mar 2020 at 09:23, Richmond wrote:
> OK so the message-id I set (*richmond.example.com) was moved from
> message-id to references, which breaks the thread on the news
> server. But seems to work ok for email.

I am not sure I understand what you are saying here.

When you write an email (or post a news item), that email has a
particular message ID.  If somebody responds to it, the original message
ID goes into the references header and the response has its own message
ID.  This provides a link between emails.


-- 
Eric S Fraga via Emacs 28.0.50 & org 9.3.6 on Debian bullseye/sid

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2020-03-12  9:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 15:21 Richmond
2020-03-10 17:38 ` Eric S Fraga
2020-03-10 17:49   ` Adam Sjøgren via info-gnus-english
2020-03-10 21:09     ` Clemens Schüller
2020-03-11 20:09       ` Richmond
2020-03-12  6:47         ` Eric S Fraga
2020-03-12  9:16           ` Richmond
2020-03-12  9:22             ` Eric S Fraga
2020-03-12  9:23             ` Richmond
2020-03-12  9:48               ` Eric S Fraga [this message]
2020-03-12 12:59                 ` Richmond
2020-03-12 15:57           ` Richmond
2020-03-12 17:38             ` Eric S Fraga
2020-03-13 15:02 ` Helmut Waitzmann

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=87a74luco7.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=dnomhcir@gmx.com \
    --cc=info-gnus-english@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.
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).