The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780)
Date: Thu, 16 Mar 2023 22:30:06 -0500	[thread overview]
Message-ID: <20230317033006.aawbkyuovoyhxszm@illithid> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2303171413440.86309@aneurin.horsfall.org>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

At 2023-03-17T14:17:34+1100, Dave Horsfall wrote:
> On Thu, 16 Mar 2023, G. Branden Robinson wrote:
> 
> > [replying only to list]
> 
> Short of replying to the sender alone, is there any other way to reply?  

Apparently there is; reply-all seems to have become the norm over the
past 20 years.  I used to rail against it but I gave up.  Now it seems
some people (mainly younger people, perhaps) regard it as rude if I
_don't_ CC them on mailing replies.  Maybe they fear being ignored or
circumvented in decision processes.

> I get annoyed by people blindly using "Reply to all" and are too lazy
> to edit the recipient list; I will see my own copy, after all...

Years ago, the header "Mail-Followup-To" was developed as a convention
to get this under control.[1]  Maybe because the maintainers of GMail,
Outlook, and other web email portals that provided spam filtering
services, found themselves with better things to do than support it, we
arrived where we are today.  :(

Regards,
Branden

[1] https://cr.yp.to/proto/replyto.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-03-17  3:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 11:59 [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 21:08   ` Clem Cole
2023-03-15 21:15     ` Luther Johnson
2023-03-15 21:18     ` Seth Morabito
2023-03-15 21:22       ` Larry McVoy
2023-03-15 21:27         ` Clem Cole
2023-03-15 21:38           ` KenUnix
2023-03-16 23:18             ` Clem Cole
2023-03-16 23:48               ` Charles H. Sauer (he/him)
2023-03-17  1:08                 ` Steve Nickolas
2023-03-15 21:46           ` Steve Nickolas
2023-03-15 21:50         ` Luther Johnson
2023-03-15 21:56         ` steve jenkin
2023-03-15 22:15           ` Larry McVoy
2023-03-15 23:30           ` Warner Losh
2023-03-15 23:41             ` Luther Johnson
2023-03-16  0:29               ` Warner Losh
2023-03-16  0:36                 ` Rich Salz
2023-03-16  1:55                   ` G. Branden Robinson
2023-03-16 21:14                   ` Dave Horsfall
2023-03-17  0:33                     ` Rich Salz
2023-03-17  1:03                       ` [TUHS] copyright (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17  1:05                       ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 segaloco via TUHS
2023-03-17  2:03                         ` G. Branden Robinson
2023-03-17  3:17                           ` Dave Horsfall
2023-03-17  3:30                             ` G. Branden Robinson [this message]
2023-03-17 15:12                               ` [TUHS] Re: Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780) Pete Turnbull
2023-03-17 15:33                                 ` segaloco via TUHS
2023-03-17 16:42                                   ` Steve Nickolas
2023-03-17 18:27                                     ` Marc Donner
2023-03-16  1:15               ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Larry McVoy
2023-03-16  2:14                 ` Luther Johnson
2023-03-15 23:44             ` Brad Spencer
2023-03-16  4:37         ` Dave Horsfall
2023-03-15 23:56   ` [TUHS] Re: OSF/1.0 Sources Joseph Holsten
2023-03-17  2:28   ` [TUHS] Re: UNIX System V Warren Toomey via TUHS

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=20230317033006.aawbkyuovoyhxszm@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=tuhs@tuhs.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).