Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: resending bounces: DKIM and Message-ID:
Date: Sun, 19 Nov 2023 16:36:52 -0500	[thread overview]
Message-ID: <87o7fpifwr.fsf@uwo.ca> (raw)
In-Reply-To: <8734x1ply0.fsf@ericabrahamsen.net>

Eric wrote:

>>> I have a solution! Potentially. When a user runs SDb, we first prompt
>>> "Edit original (bounced) message before sending?"
>>>
>>> If the user chooses "no", we resend immediately using `message-bounce',
>>> including the original Message-ID and all that jazz (though still
>>> respecting `message-ignore-bounced-headers'). If the user chooses "yes",
>>> we sneakily delegate to SDe, dumping them in a *Unsent Message* buffer.

I like that solution.

I don't like the status quo, since when you do `S D b', it drops you
in a message buffer, inviting you to edit it, but then makes the
assumption that you won't edit it (by preserving the Message-ID, etc).

My second choice is to just assume that it may be edited, and
remove the appropriate headers.

Dan



  reply	other threads:[~2023-11-19 21:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 12:23 Greg Troxel
2023-11-03 16:14 ` Emanuel Berg
2023-11-03 23:14 ` Eric Abrahamsen
2023-11-05 15:55   ` Greg Troxel
2023-11-05 19:30     ` Eric Abrahamsen
2023-11-07  0:53       ` Greg Troxel
2023-11-07  1:57         ` Emanuel Berg
2023-11-07  3:15           ` Emanuel Berg
2023-11-07 13:49           ` Greg Troxel
2023-11-07 13:59             ` Emanuel Berg
2023-11-07  3:38         ` Eric Abrahamsen
2023-11-11 16:58           ` Greg Troxel
2023-11-19 19:44             ` Eric Abrahamsen
2023-11-19 21:36               ` Dan Christensen [this message]
2023-11-20  0:01                 ` Greg Troxel
2023-11-10 16:38         ` Eric Abrahamsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7fpifwr.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).