ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@coe.uga.edu>
Subject: Re: replies
Date: 20 Aug 2000 20:51:27 -0400	[thread overview]
Message-ID: <m3pun3mo6o.fsf@coe.uga.edu> (raw)
In-Reply-To: Berend de Boer's message of "Thu, 17 Aug 2000 21:20:02 +0200"

Berend de Boer <berend@pobox.com> writes:

> Ed L Cashin wrote:
> 
>  
> > Munging the email headers is a kludge to support broken email
> > clients.
> > 
> > An email client should provide a "reply to all" feature which will
> > reply to the author and the list.
> 
> Having to hit a different button depending on broken mailing list
> servers is my idea of a kludge :-)

In one situation, the user is empowered: if all the headers remain
intact, then the user can reply to the author, or reply-to-all.
Hitting different keys to do different things is a natural part of
computing.  

The alternative is to change the headers.  When that happens, if I hit
"reply" in order to reply to the author, then I get the wrong thing,
the list address, in my header.  Lots of embarrassing emails have been
posted to lists because of that.  If the headers are changed, then I
have to delete the wrong header from my outgoing email, go find the
author's real address, and retype it or paste it into the headers.  It
shouldn't be that difficult to reply to the author.  When I reply, it
shouldn't go to the list, because the list didn't write the email.

Regarding the extra copy produced from replying to all, that is normal
and is called a courtesy copy.  If someone doesn't want to receive
courtesy copies, then there is a special header that can be added to
outgoing mail which many mail clients will respect by not sending the
courtesy copy.

-- 
--Ed Cashin                     PGP public key:
  ecashin@coe.uga.edu           http://www.coe.uga.edu/~ecashin/pgp/


      reply	other threads:[~2000-08-21  0:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-12 10:09 notation, manual siepo
2000-08-12 10:29 ` Berend de Boer
2000-08-12 12:05   ` manual siepo
2000-08-12 17:19   ` replies Hraban
2000-08-12 22:29     ` replies Johannes Hüsing
2000-08-16 11:13     ` replies Ed L Cashin
2000-08-16 23:49       ` replies Uwe Koloska
2000-08-17 19:20       ` replies Berend de Boer
2000-08-21  0:51         ` Ed L Cashin [this message]

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=m3pun3mo6o.fsf@coe.uga.edu \
    --to=ecashin@coe.uga.edu \
    /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).