From: Ed L Cashin <ecashin@coe.uga.edu>
Cc: ConTeXt <ntg-context@ntg.nl>
Subject: Re: replies
Date: 16 Aug 2000 07:13:25 -0400 [thread overview]
Message-ID: <m3pun9h31m.fsf@coe.uga.edu> (raw)
In-Reply-To: Hraban's message of "Sat, 12 Aug 2000 19:19:31 +0200"
Hraban <angerweit@gmx.net> writes:
> Berend de Boer wrote:
> > Yes, I also hate it that reply replies to the sender instead of the
> > list. That doesn't facilitate list communication.
>
> I get other mailing lists where the list server overwrites
> the "reply-to" with the list address -- isn't this possible
> for the ntg server?
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.
--
--Ed Cashin PGP public key:
ecashin@coe.uga.edu http://www.coe.uga.edu/~ecashin/pgp/
next prev parent reply other threads:[~2000-08-16 11:13 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 ` Ed L Cashin [this message]
2000-08-16 23:49 ` replies Uwe Koloska
2000-08-17 19:20 ` replies Berend de Boer
2000-08-21 0:51 ` replies Ed L Cashin
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=m3pun9h31m.fsf@coe.uga.edu \
--to=ecashin@coe.uga.edu \
--cc=ntg-context@ntg.nl \
/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).