Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: ding@gnus.org
Subject: Re: resending bounces: DKIM and Message-ID:
Date: Tue, 07 Nov 2023 08:49:35 -0500	[thread overview]
Message-ID: <rmifs1hk70w.fsf@s1.lexort.com> (raw)
In-Reply-To: <87lebal401.fsf@dataswamp.org> (Emanuel Berg's message of "Tue, 07 Nov 2023 02:57:18 +0100")

Emanuel Berg <incal@dataswamp.org> writes:

> Greg Troxel wrote:
>
>> My experience is that almost all bounces are because I typed
>> something wrong.
>
> Do you have a ~/.mailrc file with aliases?

No, I use bbdb, and not everything is there.

> If so, you can type the alias and see if it expands, if it
> does it should be a valid e-mail.

Sure, but it is not mandatory to use aliases, and someone typing an
email address in To: or CC: is not contrary to documentation.  So I
don't think we can say "the bounce resend function should never allow
editing because the user should never had made a mistake".

For me, bounces because I mistype are not that common.  It is just that
of the bounces where I want to resend it, they are the majority.




  parent reply	other threads:[~2023-11-07 13:50 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 [this message]
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
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=rmifs1hk70w.fsf@s1.lexort.com \
    --to=gdt@lexort.com \
    --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).