From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r104691: Don't reuse previous Message-id when resending.
Date: Wed, 29 Jun 2011 23:40:12 +0200 [thread overview]
Message-ID: <87oc1giaf7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 83mxh1swob.fsf@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Uday S Reddy <usr.vm.rocks@gmail.com>
>> Date: Tue, 28 Jun 2011 14:28:52 +0100
>>
>> Richard's problem was that it got partially sent to some of the
>> recipients.
>
> No, it was that it bounced from some place on the way. Which could be
> the local machine or some remote server.
>
> I hope that everyone who participates in this discussion knows what
> the function we are discussing does. Here's the relevant parts of the
> doc string of rmail-retry-failure:
>
> Edit a mail message which is based on the contents of the current
> message. For a message rejected by the mail system, extract the
> interesting headers and the body of the original message. ... The
> variable `rmail-retry-ignored-headers' is a regular expression
> specifying headers which should not be copied into the new message.
>
> And here's what the Emacs manual says about it:
>
> Sometimes a message does not reach its destination. Mailers usually
> send the failed message back to you, enclosed in a "failure message".
> The Rmail command `M-m' (`rmail-retry-failure') prepares to send the
> same message a second time: it sets up a `*mail*' buffer with the same
> text and header fields as before. If you type `C-c C-c' right away,
> you send the message again exactly the same as the first time.
> Alternatively, you can edit the text or headers and then send it. The
> variable `rmail-retry-ignored-headers', in the same format as
> `rmail-ignored-headers' (*note Rmail Display::), controls which headers
> are stripped from the failed message when retrying it.
>
> So it even isn't necessarily about bounced messages, and the result
> may well be a different message entirely.
If stripping a header like a Message-ID is a sensible thing to do, but
the user might want to unstrip it in rare cases, it might be an option
to place it in a form where Gnus will automatically remove it when
sending, something like
X-Remove: Message-Id: <xxxxx>
Then the user can still, if he considers the removal inappropriate, edit
the message accordingly and let the old header be used in that manner.
--
David Kastrup
next prev parent reply other threads:[~2011-06-29 21:40 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
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 [this message]
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=87oc1giaf7.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--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).