From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: resending bounces: DKIM and Message-ID:
Date: Sun, 19 Nov 2023 11:44:39 -0800 [thread overview]
Message-ID: <8734x1ply0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <rmi1qcwz0oy.fsf@s1.lexort.com>
Greg Troxel <gdt@lexort.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Greg Troxel <gdt@lexort.com> writes:
>
>>> I'm basically saying that wanting to resend a bounce exactly feels rare,
>>> and that even if it is the same, you want a fresh message-id and a fresh
>>> dkim signature so that you don't have problems from state created
>>> perhaps wrongly by the original message.
>>
>> 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.
>
>> This way the user is the one deciding "is this a new message or not?" If
>> they decide to edit, they're essentially sending a new message.
>>
>> WDYT?
>
> That could be ok. I personally feel that SDb without editing is so
> rare as to not be worth accomodating. And, the headers that are
> included are potentially added by other systems. I would like to see
> only headers that were present when the message was sent from gnus (or
> whatever MUA) to the originating MTA.
>
> Which makes me think that all of this should tend to keep fewer headers,
> and not keep those added by intermedaite systems.
At this point it feels like we're just turning SDb into SDe, except an
SDe that works on a received bounce rather than the user's original sent
message. I understand that all this is annoying, and points to a real
issue, but it also doesn't quite seem worth disturbing
compatibility/expected behavior. WDYT?
next prev parent reply other threads:[~2023-11-19 19:45 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 [this message]
2023-11-19 21:36 ` Dan Christensen
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=8734x1ply0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).