From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org, rms@gnu.org
Subject: Re: master 13bd79e34f: Add more headers to default value of rmail-retry-ignored-headers.
Date: Thu, 22 Sep 2022 08:25:42 +0300 [thread overview]
Message-ID: <83illgt1yh.fsf@gnu.org> (raw)
In-Reply-To: <8735ckov20.fsf@melete.silentflame.com> (message from Sean Whitton on Wed, 21 Sep 2022 22:08:23 -0700)
> From: Sean Whitton <spwhitton@spwhitton.name>
> Date: Wed, 21 Sep 2022 22:08:23 -0700
>
> Hello,
>
> On Wed 21 Sep 2022 at 08:43AM -04, Richard M. Stallman wrote:
>
> > branch: master
> > commit 13bd79e34fc6085410057f669cea435f2d1d046a
> > Author: Richard Stallman <rms@gnu.org>
> > Commit: Richard Stallman <rms@gnu.org>
> >
> > Add more headers to default value of rmail-retry-ignored-headers.
> >
> > * rmail.el (rmail-retry-ignored-headers): Add more headers to default.
> > Don't bother with `purecopy'. Split value readably.
> > ---
>
> Could this variable be merged with message-ignored-resent-headers? I
> can't see why we might want to have both.
I don't think that Rmail's rmail-retry-failure and message.el's
message-resend do the same job, do they? The doc string of the former
says:
"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.
IOW, this deals with a message that was rejected by the MTA. It
doesn't sound like a simple resend, AFAIU.
next prev parent reply other threads:[~2022-09-22 5:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166376423746.15379.7272033149632466931@vcs2.savannah.gnu.org>
[not found] ` <20220921124357.F2CE6C11DF3@vcs2.savannah.gnu.org>
2022-09-21 13:54 ` master 13bd79e34f: Add more headers to default value of rmail-retry-ignored-headers Po Lu
2022-09-21 15:42 ` Robert Pluim
2022-09-22 5:33 ` Po Lu
2022-09-22 5:08 ` Sean Whitton
2022-09-22 5:25 ` Eli Zaretskii [this message]
2022-09-22 16:12 ` Sean Whitton
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=83illgt1yh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=spwhitton@spwhitton.name \
/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).