From: Richmond <dnomhcir@gmx.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: info-gnus-english <info-gnus-english@gnu.org>
Subject: Re: Gnus notification of replies to my articles
Date: Thu, 12 Mar 2020 09:16:36 +0000 [thread overview]
Message-ID: <7yimja0w7f.fsf@richmond.example.com> (raw)
In-Reply-To: <87a74mvzlo.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 12 Mar 2020 06:47:31 +0000")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Wednesday, 11 Mar 2020 at 20:09, Richmond wrote:
>>> Thanks. This seems complicated by mailing lists. I have changed the
>>> message id to something more recognisable, but I am not sure if I can
>>> post here through the news server...
>>
>> Well it looks like it didn't, so this is going through email...
>
> Mailing lists, or at least this one, do not touch the message id
> header. In my experience, although the message-id may not be truly
> unique, when I used the references scoring option, it worked well. Try
> with a reasonable regex for your typical message id and see if it works
> generally before worrying about having to make it unique?
Something wasn't quite right, because when looking at the news server,
and I pressed ^ from your article, it did not find my article. I have
complicated things by using different instances of gnus for email and
news. So when I use this email instance and did the same thing, it did
find the article.
So this post is by email and I have tried to set a message-id...
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-03-12 9:16 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 [this message]
2020-03-12 9:22 ` Eric S Fraga
2020-03-12 9:23 ` Richmond
2020-03-12 9:48 ` Eric S Fraga
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=7yimja0w7f.fsf@richmond.example.com \
--to=dnomhcir@gmx.com \
--cc=e.fraga@ucl.ac.uk \
--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).