From: yoann padioleau <padator@wanadoo.fr>
To: caml-list@yquem.inria.fr
Subject: Deni de service
Date: Sat, 30 Jul 2005 10:55:21 +0200 [thread overview]
Message-ID: <E67CDE00-CD69-4238-9C24-9454AED143CA@wanadoo.fr> (raw)
It seems that I am the one who is responsible for the hundreds of
empty messages
received on the Caml list. I am very sorry.
Yesterday I changed of email adress (from something@irisa.fr to
something@wanadoo.fr)
and configured my old email account to forward my mails to the new
account.
Then I used fetchmail to get all my old mail, and all my previous
mails that concerns
the caml-list seems to be a problem. I dont understand cos I am a
subscriber of other
mailing lists, such as haskell, and there was no pb with those
mailing lists.
So I unsubscribe to the caml mailing list hoping that the process
would stop.
Again I am very sorry for the inconvenience.
next reply other threads:[~2005-07-30 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 8:55 yoann padioleau [this message]
2005-07-31 8:09 ` [Caml-list] " Xavier Leroy
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=E67CDE00-CD69-4238-9C24-9454AED143CA@wanadoo.fr \
--to=padator@wanadoo.fr \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).