Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Cc: khan@cs.purdue.edu (Muhammad Farrukh Khan), ding@ifi.uio.no
Subject: Re: gnus-reply-to-function for replying to everybody
Date: 20 Mar 1996 09:53:32 +0100	[thread overview]
Message-ID: <vafd968rvqr.fsf@dusty.informatik.uni-dortmund.de> (raw)
In-Reply-To: Roderick Schertler's message of Wed, 20 Mar 1996 00:31:00 -0500

>>>>> On Wed, 20 Mar 1996 00:31:00 -0500, Roderick Schertler
>>>>> <roderick@gate.net> said:

  Roderick> This isn't appropriate in the general case.  I gateway
  Roderick> mailing lists into actual local newsgroups (rather than
  Roderick> reading mail groups in ding) so that other local users can
  Roderick> read them, and maintaining my own to-address group
  Roderick> parameter or the like seems silly when the proper address
  Roderick> is already right there in the To or Cc header.

Well, this is a special case.  `F' works just fine for `real' news
postings and for `real' mail messages, but for news postings that are
really mail messages, you will of course see some strange behavior.  I
suggest actually setting to-list (or was it to-address?) so that
follow-ups are not posted to the news group.

Or you could just ignore the problem and post the follow-ups to the
newsgroup as well as sending them by mail to all recipients.  (The
latter will be done in all cases.)

        kai
--
~/.signature


  reply	other threads:[~1996-03-20  8:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-20  3:33 Roderick Schertler
1996-03-20  4:45 ` Muhammad Farrukh Khan
1996-03-20  5:31   ` Roderick Schertler
1996-03-20  8:53     ` Kai Grossjohann [this message]
1996-03-20 19:19     ` Lars Magne Ingebrigtsen
1996-03-20  4:58 ` d. hall
1996-03-20  5:36   ` Roderick Schertler
1996-03-20  8:49 ` Kai Grossjohann
1996-03-20 22:49   ` Roderick Schertler

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=vafd968rvqr.fsf@dusty.informatik.uni-dortmund.de \
    --to=grossjoh@charly.informatik.uni-dortmund.de \
    --cc=ding@ifi.uio.no \
    --cc=khan@cs.purdue.edu \
    /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).