From: "Edward J. Sabol" <sabol@thuban.gsfc.nasa.gov>
Subject: Re: Gnus v5.2.24 is released
Date: Mon, 24 Jun 1996 16:35:58 -0400 [thread overview]
Message-ID: <199606242035.QAA28479@thuban.gsfc.nasa.gov> (raw)
In-Reply-To: <199606232214.RAA00572@grendel.austin.texas.net> (message from Firebeard on Sun, 23 Jun 1996 17:14:48 -0500)
Excerpts from mail: (23-Jun-96) Re: Gnus v5.2.24 is released by Firebeard
> Then why is Gnus (apparently) not using the X- convention?
Because the plan is that someday, someone is going to write the RFC for it
and make it at a quasi-official and well-documented e-mail header that we
hope other MUAs will endorse and implement in a similar fashion. Today, Gnus;
tomorrow, the world! Bwah-ha-ha-ha-ha.
> I certainly don't want Gnus handling the header one way, and then have the
> Mail-Copies-To header defined to be addresses to CC on replies.
Actually, that's exactly what it means. Two examples:
Mail-Copies-To: never
means "Don't ever CC: me on a posting to a newsgroup or mailing list"
even if the user tries to do so
Mail-Copies-To: me@my.email.address.net
means "Please CC: this e-mail address when you post your follow-up to
the newsgroup (or mailing list)"
Later,
Ed
next prev parent reply other threads:[~1996-06-24 20:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-21 16:06 Lars Magne Ingebrigtsen
1996-06-21 18:00 ` Steven L Baur
1996-06-21 19:06 ` Mark Borges
1996-06-21 19:24 ` Mark Borges
1996-06-21 19:36 ` Steven L Baur
1996-06-22 21:28 ` Firebeard
1996-06-23 17:09 ` Per Abrahamsen
1996-06-23 22:14 ` Firebeard
1996-06-24 7:04 ` Per Abrahamsen
1996-06-24 20:35 ` Edward J. Sabol [this message]
1996-06-21 21:11 ` Per Abrahamsen
1996-06-22 18:50 ` Steven L Baur
1996-06-23 20:05 ` Mark Borges
[not found] ` <sdbuichi8t.fsf_-_@teal.ece.ucdavis.edu>
1996-06-22 9:07 ` Happy Face paren detection bug Lars Magne Ingebrigtsen
1996-06-21 19:09 ` Gnus v5.2.24 is released Stephen Saroff
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=199606242035.QAA28479@thuban.gsfc.nasa.gov \
--to=sabol@thuban.gsfc.nasa.gov \
/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).