From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: pb sg .73 gnus-xmas-find-glyph-dir XEmacs
Date: 16 Apr 1996 19:47:57 +0200 [thread overview]
Message-ID: <w8sn34cawmq.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: <199604161010.MAA03065@irsun29.ifp.fr>
Nathanael.MAKAREVITCH@ifp.fr (Nathanael Makarevitch) writes:
> this mailing-list does not send mails with a Reply-To" pointing to
> itself. is it deliberate, in order to keep the amount of traffic low by
> inviting participants to use private email ?
Only broken mailing lists (IMHO) insert a Reply-To that points to the
list itself. When one "replies", the response should go to the person
who wrote the article; when one "follows up", the response should go
to a wider range of people.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-04-16 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-15 9:19 Nathanael Makarevitch
1996-04-15 17:01 ` NNTP server is not specified Steven L Baur
1996-04-15 18:21 ` Kai Grossjohann
1996-04-15 18:39 ` Justin Zaglio
1996-04-16 10:10 ` pb sg .73 gnus-xmas-find-glyph-dir XEmacs Nathanael Makarevitch
1996-04-16 15:45 ` Colin Rafferty
1996-04-16 17:47 ` Lars Magne Ingebrigtsen [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=w8sn34cawmq.fsf@hler.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).