From: Richard Stallman <rms@gnu.org>
To: jh@physics.ucf.edu
Cc: bug-gnu-emacs@gnu.org, jh@physics.ucf.edu
Subject: Re: rmail reply creates 2 CC: fields, violates RFC 2822
Date: Sat, 22 Dec 2007 16:08:43 -0500 [thread overview]
Message-ID: <E1J6BaN-0000hb-NL@fencepost.gnu.org> (raw)
In-Reply-To: <wl8wsragzj2.fsf@glup.physics.ucf.edu> (message from Joe Harrington on Wed, 19 Dec 2007 16:12:01 -0500)
It is ridiculous to restrict the user in this way.
I often send messages with multiple CC lines. I put in multiple CC
lines by hand. I'd rather program Rmail to automatically delete those
warnings (which should be easy) than go to the trouble of
consolidating CC fields.
Who should we contact to call for a change in RFC 2822?
prev parent reply other threads:[~2007-12-22 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 21:12 rmail reply creates 2 CC: fields, violates RFC 2822 Joe Harrington
2007-12-22 21:08 ` Richard Stallman [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
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=E1J6BaN-0000hb-NL@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=jh@physics.ucf.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.
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).