From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r104691: Don't reuse previous Message-id when resending.
Date: Sat, 25 Jun 2011 16:14:19 -0400 [thread overview]
Message-ID: <ix7h89y8h0.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvmxh6f34w.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 25 Jun 2011 09:32:42 -0400")
Stefan Monnier wrote:
> Why?
>> Don't reuse previous Message-id when resending.
To spell it out more explicitly, this change appears to be incorrect.
http://tools.ietf.org/html/rfc2822
3.6.6. Resent fields
Resent fields SHOULD be added to any message that is reintroduced by a
user into the transport system. [...] No other fields in the message are
changed when resent fields are added.
[...]
resent-msg-id = "Resent-Message-ID:" msg-id CRLF
[...]
Resent fields are used to identify a message as having been reintroduced
into the transport system by a user. The purpose of using resent fields
is to have the message appear to the final recipient as if it were sent
directly by the original sender, with all of the original fields
remaining the same.
[...]
Note: Reintroducing a message into the transport system and using
resent fields is a different operation from "forwarding".
[...]
Note: When replying to a resent message, replies behave just as they
would with any other message, using the original "From:",
"Reply-To:", "Message-ID:", and other fields.
[...]
The "Resent-Message-ID:" field provides a unique identifier for the
resent message.
next prev parent reply other threads:[~2011-06-25 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1QZnWt-0001JW-56@colonialone.fsf.org>
2011-06-25 13:32 ` [Emacs-diffs] /srv/bzr/emacs/trunk r104691: Don't reuse previous Message-id when resending Stefan Monnier
2011-06-25 20:14 ` Glenn Morris [this message]
2011-06-26 16:17 ` Richard Stallman
2011-06-27 7:17 ` Stephen J. Turnbull
2011-06-27 16:28 ` Richard Stallman
2011-06-27 17:47 ` Uday S Reddy
2011-06-28 16:14 ` Richard Stallman
2011-06-27 20:28 ` Stephen J. Turnbull
2011-06-27 23:03 ` Richard Stallman
2011-06-28 1:31 ` Stephen J. Turnbull
2011-06-28 1:45 ` Daniel Colascione
2011-06-28 2:56 ` Eli Zaretskii
2011-06-28 13:28 ` Uday S Reddy
2011-06-28 17:17 ` Eli Zaretskii
2011-06-29 21:40 ` David Kastrup
2011-06-28 16:13 ` Richard Stallman
2011-06-28 17:51 ` Richard Riley
2011-06-29 10:57 ` Richard Stallman
2011-06-30 16:46 ` Stefan Monnier
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=ix7h89y8h0.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).