From: "Jon Harrop" <jon@ffconsultancy.com>
To: "Caml List" <caml-list@inria.fr>
Subject: RE: [Caml-list] posting policy
Date: Wed, 20 Apr 2011 19:05:54 +0100 [thread overview]
Message-ID: <028f01cbff85$984764a0$c8d62de0$@ffconsultancy.com> (raw)
In-Reply-To: <015f01cbfd37$737f9200$5a7eb600$@ffconsultancy.com>
I just noticed the caml-list's own archive stopped at the end of last year:
http://caml.inria.fr/pub/ml-archives/caml-list/index.en.html
> -----Original Message-----
> From: Jon Harrop [mailto:jonathandeanharrop@googlemail.com]
> Sent: 17 April 2011 20:41
> To: 'caml-list'
> Subject: RE: [Caml-list] posting policy
>
> Thank you. For anyone who is interested, it is worth noting that this
sympa-
> roc.inria.fr site also has a nice archive of the caml-list that goes all
the way back
> to Claude Fleurey's e-mail about Caml on AIX from 30th September 1992!
>
> I've also noticed that Google Groups is no longer archiving fa.caml... :-(
>
> Cheers,
> Jon.
>
> > -----Original Message-----
> > From: Xavier Leroy [mailto:Xavier.Leroy@inria.fr]
> > Sent: 17 April 2011 17:35
> > To: caml-list
> > Subject: [Caml-list] posting policy
> >
> > Dear caml-list subscribers,
> >
> > As you probably noticed, spam has been on the rise on the caml-list
> > since
> it was
> > moved to INRIA's heavy-duty Sympa list server. The reason is that we
> > lost
> one
> > level of spam filtering during the move, and my Sympa administrator
> informed
> > me that there is nothing that can be done about it except restrincting
> > who
> can
> > post to the list.
> >
> > Based on the results of a quick poll at the OCaml meeting last Friday,
> > the
> caml-
> > list is therefore now in "subscribers or confirmation" mode, meaning
that:
> >
> > - if you post from an e-mail address that is subscribed to the list,
> > the post goes through;
> > - otherwise, the poster receives an e-mail with a confirmation link
> > that needs to be visited before the post goes through.
> >
> > Of course, to avoid the inconvenience of confirming posts, you can
> > change
> your
> > subscription so that it reflects the address you post from, and/or
> subscribe
> > multiple e-mail addresses to the list and arrange so that only one
> receives
> > messages. All this can be done from the Web interface:
> > https://sympa-roc.inria.fr/wws/info/caml-list
> >
> > Regards,
> >
> > - Xavier Leroy
> >
> > --
> > Caml-list mailing list. Subscription management and archives:
> > https://sympa-roc.inria.fr/wws/info/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2011-04-20 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 16:34 Xavier Leroy
2011-04-17 19:41 ` Jon Harrop
2011-04-17 20:41 ` Joel Reymont
2011-04-17 21:11 ` Jon Harrop
2011-04-18 10:57 ` Paolo Donadeo
2011-04-20 18:05 ` Jon Harrop [this message]
2011-04-20 21:27 ` Alan Schmitt
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='028f01cbff85$984764a0$c8d62de0$@ffconsultancy.com' \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
/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