From: Dave Berry <dave@kal.com>
To: Pierre Weis <Pierre.Weis@inria.fr>, garrigue@kurims.kyoto-u.ac.jp
Cc: caml-list@inria.fr
Subject: RE: Newsgroup for Caml?
Date: Thu, 15 Jun 2000 14:32:50 +0100 [thread overview]
Message-ID: <3145774E67D8D111BE6E00C0DF418B66252AAE@nt.kal.com> (raw)
It is possible to block spam from a newsgroup:
- create a "moderated" newsgroup, with an e-mail address for submissions
- put a spam filter on the submission address
- gateway the submission address directly to the newsgroup (with no manual
intervention)
I think the comp.lang.dylan/info-dylan newsgroup/mailing list works like
this. I know the list is gatewayed to and from the group, and I'm fairly
certain it isn't actively moderated.
It might be possible to filter out cross-postings as well.
Dave.
-----Original Message-----
From: Pierre Weis [mailto:Pierre.Weis@inria.fr]
Sent: Thursday, June 15, 2000 12:29 PM
To: garrigue@kurims.kyoto-u.ac.jp
Cc: caml-list@inria.fr
Subject: Re: Newsgroup for Caml?
> If Pierre is for a newsgroup, it is probably because the flow on the
> caml-list is becoming very time-consuming to moderate. So it would
> probably be nice to have a non-moderated comp.lang.caml.
Absolutely. This way I would not have the burden to answer directly to
naive questions, that can be sent to the news group.
> Also I'm not sure that people who don't like newsgroups would really
> enjoy reading such a non-moderated caml-list, with the flame-wars and
> spam one can expect.
IMHO, you're absolutely right.
> What about keeping a moderated caml-list mainly for announcements, the
> newsgroup being there for questions and discussions?
Yes, but I would like a slightly more general mailing list, opened to
suggestions (libraries and language design improvements). The rest
(including comparison between Caml and whatever) being freeely posted
to the unmoderated newsgroup.
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://cristal.inria.fr/~weis/
next reply other threads:[~2000-06-15 16:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 13:32 Dave Berry [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-16 18:41 Brent Fulgham
2000-06-19 10:24 ` Jean-Francois Monin
2000-06-15 12:31 Damien Doligez
2000-06-15 9:22 Dave Berry
2000-06-13 17:02 Dave Berry
2000-06-14 7:18 ` Sven LUTHER
2000-06-12 19:05 Daniel de Rauglaudre
2000-06-13 16:53 ` Pierre Weis
2000-06-13 23:18 ` Markus Mottl
2000-06-15 3:07 ` Jacques Garrigue
2000-06-15 11:29 ` Pierre Weis
2000-06-15 12:53 ` Benjamin C. Pierce
2000-06-15 20:36 ` Michael Vanier
2000-06-15 12:22 ` Markus Mottl
2000-06-16 8:01 ` Sven LUTHER
2000-06-14 8:08 ` Jean-Yves Moyen
2000-06-13 19:16 ` Michael Vanier
2000-06-15 13:47 ` Xavier Leroy
2000-06-16 8:07 ` Niall Dalton
2000-06-16 16:44 ` Daniel de Rauglaudre
2000-06-16 8:32 ` Jacques Garrigue
2000-06-16 11:25 ` Alexander I. Zhezherun
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=3145774E67D8D111BE6E00C0DF418B66252AAE@nt.kal.com \
--to=dave@kal.com \
--cc=Pierre.Weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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