From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Mail-Followup-To
Date: Sat, 22 Mar 2008 08:22:47 +0900 [thread overview]
Message-ID: <87lk4bfyrc.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <v9bq57q4dj.fsf_-_@marauder.physik.uni-ulm.de>
Reiner Steib writes:
> Mail-Followup-To is for mail messages. See
> e.g. <http://cr.yp.to/proto/replyto.html>
With all due respect to Professor Bernstein, his home page is not on
the standards track, and his page on reply-to is not even close to
being useful for a standard because it doesn't say when to generate
those headers, or who may generate them. IIRC, the standards track
proposals I've seen all generalized it to news, and agree on how to
specify it for news, but not for mail. Gnus itself claims conformance
to an ancient expired internet-draft, not Bernstein's proposal, AFAIK.
I agree that emacs-devel posters should be encouraged to consider
using MUAs that respect M-F-T, or adding it to their MUAs. But this
is a matter of "courtesy beyond the call of duty", not of standard
conformance.
next prev parent reply other threads:[~2008-03-21 23:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 15:08 mode-line tooltips for "[" and "]" in recursive-edit Dan Nicolaescu
2008-03-20 16:46 ` Drew Adams
2008-03-20 17:04 ` Dan Nicolaescu
2008-03-20 17:26 ` Drew Adams
2008-03-20 17:42 ` Lennart Borgman (gmail)
2008-03-21 7:07 ` Dan Nicolaescu
2008-03-21 14:28 ` Drew Adams
2008-03-21 17:45 ` [OT] Mail-Followup-To, Outlook (was: mode-line tooltips for "[" and "]" in recursive-edit) Reiner Steib
2008-03-21 18:42 ` Drew Adams
2008-03-21 19:45 ` [OT] Mail-Followup-To, Outlook Reiner Steib
2008-03-22 1:02 ` Stefan Monnier
2008-03-21 18:36 ` mode-line tooltips for "[" and "]" in recursive-edit Stephen J. Turnbull
2008-03-21 18:22 ` Stephen J. Turnbull
2008-03-21 19:11 ` Mail-Followup-To (was: mode-line tooltips for "[" and "]" in recursive-edit) Reiner Steib
2008-03-21 23:22 ` Stephen J. Turnbull [this message]
2008-03-21 23:51 ` Mail-Followup-To Reiner Steib
2008-03-21 8:38 ` mode-line tooltips for "[" and "]" in recursive-edit Jan Djärv
2008-03-21 21:47 ` Nick Roberts
2008-03-21 22:03 ` Lennart Borgman (gmail)
2008-03-21 22:10 ` Nick Roberts
2008-03-22 1:29 ` Juri Linkov
2008-04-09 9:38 ` Jan Djärv
2008-04-10 6:20 ` Nick Roberts
2008-04-10 7:27 ` Jan Djärv
2008-04-10 8:38 ` Nick Roberts
2008-04-10 9:06 ` Jan Djärv
2008-04-10 16:18 ` Drew Adams
2008-04-10 18:32 ` Stefan Monnier
2008-04-10 18:45 ` Drew Adams
2008-04-10 21:21 ` Stefan Monnier
2008-04-11 5:23 ` Jan Djärv
2008-04-11 6:47 ` Jan Djärv
2008-04-11 16:28 ` Stefan Monnier
2008-04-10 20:29 ` Jan Djärv
2008-04-10 21:14 ` Drew Adams
2008-04-11 5:21 ` Jan Djärv
2008-03-20 23:59 ` Juri Linkov
2008-03-21 7:06 ` Dan Nicolaescu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lk4bfyrc.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=Reiner.Steib@gmx.de \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).