Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: No Followup-To header defaults
Date: Sat, 03 Sep 2005 18:16:37 +0200	[thread overview]
Message-ID: <v9psrqkty2.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <871x4d5yze.fsf@teufel.hartford-hwp.com>

On Mon, Aug 29 2005, Haines Brown wrote:

> Reiner Steib <reinersteib+from-uce@imap.cc> writes:
[...]
>> Gnus doesn't know that groups x and y exist.  Maybe in your previous
>> setup, Gnus knew about the groups x and y (IIRC unsubscrkilledibed

Oops, s/unsubscrkilledibed/unsubscribed and killed/

>> groups are also considered here).
>
> I had assumed that when I followed up to a message, the header of my
> reply would read the Newsgroups: line of the message to which I am
> responding. 

Correct.

> Your answer implies that this not so, and the behavior about which
> I'm complaining is normal.
>
> You seem to imply that in my previous setup gnus didn't read the
> Newsgroups: line, 

No, that's not what I said.

> but would somehow otherwise know of these groups, even if I had
> never subscribed to them or killed them.

On sending, several checks are done.  One test is to check if the
newsgroups exists (I'm not sure about the details, sorry), see the
variable `message-syntax-checks'.

Maybe you had disabled the check `existing-newsgroups' in
`message-syntax-checks'?  Or you can disable it there, if the prompt
annoys you.

> For example, I'm involved in a discussion on a newsgroup, but the OP
> had distributed his message to several groups, including
> uk.politics.misc. When I follow up to up his messages, the
> uk.politics.misc group in my old setup would appear automatically in
> the "Newsgroups:" line of my outgoing header.

Unless there's a Followup-To header, all groups from the Newsgroups
line should also appear in when following up.

> In my old setup, ~/News contained a set of files corresponding to the
> groups to which I subscribed. For example, linux.debian.user.SCORE,
[...]

(This is completely irrelevant for the current issue.)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/


  reply	other threads:[~2005-09-03 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 17:31 Haines Brown
2005-08-24 18:00 ` Bernard Adrian
2005-08-24 22:52   ` Haines Brown
2005-08-25 10:15   ` Reiner Steib
2005-08-25 15:25     ` Bernard Adrian
2005-08-25 17:47     ` Haines Brown
2005-08-28 17:28       ` Reiner Steib
2005-08-29  1:10         ` Haines Brown
2005-09-03 16:16           ` Reiner Steib [this message]
2005-08-24 22:47 ` Katsumi Yamaoka

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=v9psrqkty2.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).