Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <youngs@xemacs.org>
Subject: Re: Followup-To header
Date: Thu, 27 Dec 2001 09:27:58 +1000	[thread overview]
Message-ID: <microsoft-free.x4k7v9muip.fsf@slackware.mynet.pc> (raw)
In-Reply-To: <m3lmfpq5sg.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Wed, 26 Dec 2001 11:55:53 -0500")

|--==> "PJ" == Paul Jarc <prj@po.cwru.edu> writes:

  PJ> Steve Youngs <youngs@xemacs.org> wrote:
  >>Following up to an article with a 'Followup-To:' header set in a group
  >>with 'to-list' & 'to-address' set Gnus doesn't honour that header.

  PJ> to-list and to-address are for mail; Followup-To is for news.

Oops.  I guess I was suffering from too much Xmas cheer.

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
|            XEmacs - It's not just an editor.             |
|                    It's a way of life.                   |
|------------------------------------<youngs@xemacs.org>---|



      reply	other threads:[~2001-12-26 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26  1:13 Steve Youngs
2001-12-26 16:55 ` Paul Jarc
2001-12-26 23:27   ` Steve Youngs [this message]

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=microsoft-free.x4k7v9muip.fsf@slackware.mynet.pc \
    --to=youngs@xemacs.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).