From: "Perry E. Metzger" <perry@piermont.com>
Cc: nmh-workers@math.gatech.edu, exmh-users@sunlabs.Eng.Sun.COM,
ding@gnus.org
Subject: Re: Mail-{Reply,Followup}-To considered harmful
Date: Wed, 11 Feb 1998 18:43:13 -0500 [thread overview]
Message-ID: <199802112343.SAA12669@jekyll.piermont.com> (raw)
In-Reply-To: Your message of "Wed, 11 Feb 1998 17:19:30 EST." <199802112219.RAA12647@math34.math.gatech.edu>
Richard Coleman writes:
> > Please don't implement support for Mail-Reply-To and Mail-Followup-To
> > in nmh. Not only are they nonstandard, they're a poor fix for the
> > problem.
>
> Well, everything is nonstandard until it becomes standard.
Keith is the IETF applications area director, and used to chair the
DRUMS working group. I strongly agree with his statements.
> I also believe this proposal is a good way of fixing this problem.
The working group debated it at length and did not agree.
Perry
next prev parent reply other threads:[~1998-02-11 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802111920.OAA21297@spot.cs.utk.edu>
1998-02-11 22:19 ` Richard Coleman
1998-02-11 23:15 ` Robert Elz
1998-02-11 23:43 ` Perry E. Metzger [this message]
1998-02-13 6:37 ` Keith Moore
1998-02-13 16:00 ` cwg-dated-4706b1d0ee55baea
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=199802112343.SAA12669@jekyll.piermont.com \
--to=perry@piermont.com \
--cc=ding@gnus.org \
--cc=exmh-users@sunlabs.Eng.Sun.COM \
--cc=nmh-workers@math.gatech.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).