Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Mail-Followup-To
Date: 10 Feb 1998 22:13:35 +0100	[thread overview]
Message-ID: <m3oh0fmadc.fsf@sparky.gnus.org> (raw)
In-Reply-To: Stainless Steel Rat's message of "10 Feb 1998 15:00:40 -0500"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> Yes, RFC 822 did not make a distinction between reply-to-author and
> reply-to-list.  These are aspects of the mail client, not the message
> format.  To a well-written MUA, these headers are redundant; the client
> already makes the appropriate distinction.  A badly written MUA, one that
> does not make the distinction, is not going to honor these headers.

Yup.  But there are useful things that can be done with these
headers.  For instance -- on mailing lists where everyone that posts
is assumed to be subscribed (like this one), the listserv could add a
"Mail-Followup-To: ding@gnus.org" header.  It can also be used by the
sender as a way to signal "I am subscribed to the list; don't Cc me or
anybody else".

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1998-02-10 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <larsi@ifi.uio.no>
1998-02-10 19:21 ` Mail-Followup-To Lars Magne Ingebrigtsen
1998-02-10 19:37   ` Mail-Followup-To Stephen Zander
1998-02-10 20:42   ` Mail-Followup-To Richard Coleman
     [not found]   ` <x7soprkz6f.fsf@peorth.gweep.net>
1998-02-10 21:13     ` Lars Magne Ingebrigtsen [this message]
1998-02-10 21:25       ` Mail-Followup-To Richard Coleman
     [not found]       ` <x77m73kvav.fsf@peorth.gweep.net>
1998-02-10 23:22         ` Mail-Followup-To Justin Sheehy
1998-02-11 13:33         ` Mail-Followup-To Lars Magne Ingebrigtsen
1998-02-11 21:48   ` Mail-Followup-To Jason R Mastaler

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=m3oh0fmadc.fsf@sparky.gnus.org \
    --to=larsi@gnus.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).